Show TOC

Function documentationScheduling of ODS Scripts

 

Note Note

This topic is relevant only if you are using SAP ME with Oracle or Microsoft SQL Server database. If you are using SAP ME with SAP HANA database, see System Landscape Recommendations Guide for SAP ME on SAP HANA.

End of the note.

ODS scripts execute Java programs to perform extract, transform, and load (ETL) and/or summarization functions, copying data to the Global ODS, or deletion of data from a database.

The following ODS scripts (.bat files for Windows and .ksh files for Unix) are available to perform these functions:

  • Extract

    • ODSLaborExportSFC

    • ODSLaborExportUser

  • ETL and Summarization

    • ODSGenealogyETL

    • ODSNonconformanceETL

    • ODSProductionETL

    • ODSResourceETL

    • ODSShopOrderETL

  • Summarization

  • Copy Data to Global ODS

    • ODSDPMOETLGlobalCopy

    • ODSNonconformanceETLGlobalCopy

    • ODSProductionETLGlobalCopy

    • ODSResourceETLGlobalCopy

    • ODSShopOrderETLGlobalCopy

  • Delete Data from Database

    • ODSAging

    • ODSWIPAging

Features

You use the ODS Extract Control Date table to set the beginning date for the next ODS extract or summarization process for ODS tables. Not all ODS tables will have an entry in this table. This table is initialized to a date and time in 2004 by the ODSLoadControlDates SQL script during the creation and configuration of the ODS database. The beginning date for each table needs to be edited and set to a more current date prior to running the ODS scripts for the first time.

You schedule and execute the ODS scripts using the standard scheduling function of the operating system of the database server. For Windows systems, this is the Task Scheduler. For Unix systems, it is cron. For information on these functions, please see your operating system documentation or Help.

The following table lists the ODS functions performed by each of the above listed scripts:

Script Name

Function Name

ODSGenealogyETL

SFC BOM Extract

SFC BOM Expansion

Resource Time Log Extract

Resource Time Log Expansion

Resource Time Log Summary

Component Time Log Extract

Component Time Log Expansion

Time-Based Expansion

BOM Extract

BOM Expansion

NonconformanceETL

NC Data Extract

NC Data Expansion

NC Data Summary

DPMO Extract

DPMO Expansion

DPMO Summary

ProductionETL

Production Log Extract

Shop Order Extract

Shop Order Expansion

Production Log Expansion

Production Log Summary 1

Production Log Summary 2

Production Log Summary 3

Production Log Summary 4

Production Log Summary 5

ResourceETL

Resource Time Log Extract

Resource Time Log Expansion

Resource Time Log Summary

ShopOrderETL

Shop Order Extract

Shop Order Expansion

LaborExportSFC

Labor Tracking (LT) Export SFC

LaborExportUser

LT Export User

LaborRollup

LT Labor All

ODSGenealogyETL

SFC BOM Extract

Some functions are performed by two different scripts. Thus, if the GenealogyETL script is run, you do not need to run the ResourceETL script. Likewise, if the ProductionETL script is run, you do not need to run the ShopOrderETL script.

Recommendation Recommendation

Modify a copy of the ODSLoadControlDates SQL script to set the beginning dates to a date just prior to the date when the SAP ME system will be put into production. Run this modified script prior to running any of the ODS ETL scripts.

Schedule ETL scripts to run not more frequently than every 15 minutes for most SAP ME installations. How frequently the scripts can be run effectively depends upon the computing environment and the amount of data being copied to the ODS tables.

End of the recommendation.

Typically scripts are scheduled to run every 15 minutes up to every 24 hours. The functions include a number-of-minutes parameter which controls the maximum time span processed on each run. This ensures that the function can be completed without over-utilizing resources. Set this parameter to 60, if the script is not going to be run again for longer than that amount of time. The scripts provide a looping option to keep running each function or group of functions until the script end conditions are met. It is vital to monitor that the scripts are running without errors and that the date / times in the ODS Extract Control Date table are moving forward. It is also important to ensure the time taken for each script to run is less than the time between scheduled runs.

Caution Caution

Schedule the scripts to start running at the time that the SAP ME system is put into production in order to avoid difficulties in transferring the large amount of historical data that may be in the WIP database when starting up ODS at a later time.

End of the caution.

Caution Caution

If you schedule the ODSLaborRollup.bat file to run periodically, remove the last command (Pause) from the file.

End of the caution.