Show TOC

Background documentationOperational Data Store (ODS) Locate this document in the navigation structure

 

The Operational Data Store (ODS) tables provide storage for SAP ME data needed for internal and external reporting. They contain both detail and summary data for many of the objects and processes managed by SAP ME.

During real-time transactions, SAP ME stores data in the Work In Process (WIP) database tables. These tables are designed and indexed to optimize data management for the real-time functions of SAP ME. Production data can be periodically transferred to the ODS tables and summarized in the ODS summary tables. These tables are designed and indexed to optimize their use in the creation and running of reports. WIP data modified through the SAP ME maintenance activities can be stored in the Audit Log tables of the ODS database. The SAP ME Archive function stores SFC-related data in the Archive tables of the ODS database.

The following figure illustrates the high level data landscape for SAP ME:

This graphic is explained in the accompanying text.

ODS acronym stands for both the ODS database and the ODS tables, as opposed to the Audit Log tables and the Archive tables, within the ODS database. This Help information is focused primarily on the ODS tables and how they are used.

Implementation Considerations

When you set up ODS, you decide the following:

  • Types of data to be stored in the ODS tables

  • When the data is to be stored

  • How the data is to be summarized

  • Time granularity for data summarization

  • How long data is to be retained in the ODS tables

  • How long data stored in ODS is to be retained in the WIP database tables

  • Whether or not summarized data is to be copied to the Global ODS database

  • Parameters controlling the expansion of database record handles

Caution Caution

If you use ODS for the SAP ME installation, set up ODS at the time that the system is installed 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.

Integration

ODS is integrated with the SAP ME BObj Reporting feature primarily through the SAP ME BObj universes. For more information about the use of ODS with BObj Reporting, see the SAP BusinessObjects Reporting Guide at   http://service.sap.com/instguides   SAP Business Suite Applications   SAP Manufacturing   SAP Manufacturing Execution  .

ODS is integrated with the SAP ME WIP database through database synonyms and ETL (extract, transform and load) software.

Configuration of ODS in SAP ME is achieved through the use of the following maintenance activities:

Features

ODS provides the following features:

  • Extracting, transforming, loading and summarizing WIP data

    ODS enables the querying and reporting of SAP ME operational data without impacting the performance of the WIP transactional database and production use of SAP ME. You can configure how frequently data is copied from the WIP database into the ODS tables and how the data is summarized.

  • Copying ODS summary data to Global ODS

    You can periodically copy Summary data in the ODS tables to the Global ODS tables, through ODS scripts, for enterprise wide manufacturing reporting.

  • Deleting WIP and ODS data

    You can periodically delete data from WIP tables through ODS scripts. This is only for WIP tables that contain data that does not get archived to the Archive tables and that have corresponding ODS tables. Data in the ODS tables can be periodically deleted through ODS scripts.

For more information, see Work with Operational Data Store (ODS).

The ODS process involves the following:

  • Extracting data from the WIP database

  • Transforming it by expanding the record handles

  • Loading it into the ODS detail data tables

  • Summarizing some of the data and storing it into the ODS summary data tables

  • Copying the summary data to the Global ODS database

  • Deleting expired WIP and ODS data

The ODS process accomplishes these functions through scheduled ODS scripts (.bat files for Windows and .ksh files for Unix) that execute SAP ME Java programs (see Scheduling of ODS Scripts). Once the ODS process is configured and the scripts are scheduled, some monitoring of the script executions is required.

The figure below illustrates the primary flow of the ODS process. The scripts can be scheduled independently.

This graphic is explained in the accompanying text.

Recommendation Recommendation

We recommend monitoring the ODS process through the log file, ODSLog.txt, (usually located on the ODS database server in $USER_INSTALL_DIR$/scripts/) or through the ODS extract control date table.

End of the recommendation.

See also: SAP ME Installation Guide, SAP ME ODS Reporting Guide, SAP ME BusinessObjects Reporting Guide at   http://service.sap.com/instguides   SAP Business Suite Applications   SAP Manufacturing   SAP Manufacturing Execution  .

More Information

Work with Operational Data Store (ODS)

Scheduling of ODS Scripts

Setting Up Operational Data Store (ODS)

ODS Data Summarization