SAP
The conversion program supports:
- SAP Factory and Freeday calendars
- SAP Job definitions
These reports can be generated through a Stonebranch Utility.
Both formats can be read through the File Menu Option. Since there can be multiple calendar files, please read all factory calendars first and all freeday calendars second.
Third, read the directory containing the SAP Job definition files. The corresponding values in the CALENDARID keyword will hook up to the calendars and their custom days. The conversion program recognizes different SAP calendar records by their lengths. Records that do not match are discarded.
SAP Calendars
A calendar file can contain many calendar IDs, each describing different years. All unique calendar IDs are stored with a prefix describing its function. A working day (flagged 1 in the file) will be set accordingly in the created calendar, hence different workday definitions.
Custom Days
SAP custom day records describe each day of the year, flagged as 1 or 0. They can occur for different calendar IDs describing different years. Often, it is not necessary to convert all of them.
- Records older than 730 days are discarded, leaving only the last one or two years valid.
- Records newer than 1500 days are discarded, leaving the first 4 or 5 upcoming years valid.
The log will display which records are discarded.
SAP Job Definitions
Job definition files should be in a separate directory when using the conversion program.
Every file will be converted into a workflow, instead of a regular task, to enable the adding of extra functionality, such as like restart, dependencies, skip criteria, and run criteria.
Every ABAP step in the file then is converted into a separate task and automatically receives a dependency to its predecessor ABAP step.
Example
The following job definition file:
Converts to the following workflow (SAP_CONV_002_MULTI_STEP_DAILY):
EVENTPARM
If an EVENTPARM is present, a Task Monitor will be created pointing to the task in the EVENTPARM value.