DRF Integration for MES Processes

To distribute your business objects, such as a planned order or a production order, you can make use of the Data Replication Framework (DRF). In doing so, you can use general Framework functions including a comprehensive filter concept, change pointer management, and error evaluation. The DRF enables you to send master and transaction data to an MES via IDoc. Using a replication model and the assigned outbound implementations, you can specify exactly which data you want to replicate.

Prerequisites

To be able to use DRF integration, you need to activate the BC Set CA_MDP_DRF_01. For more information, see Customizing for Cross-Application Components under Processes and Tools for Enterprise Applications Master Data Governance General Settings Data Replication Overall Information .

In addition, in Customizing for Cross-Application Components, choose Processes and Tools for Enterprise Applications Master Data Governance General Settings Data Replication Define Custom Settings for Data Replication .

For more information, see Setting Up DRF Integration for MES Processes.

Features

In the DRF, you can create a replication model for a business object (such as a planned order) and control its distribution through criteria defined in the DRF filter (for example, material, plant, production version).

You can integrate the following master and transaction data with the DRF:

SAP supplies certain Customizing presettings and filter details for these business objects. The filter objects control some prerequisites for replication and they check the relevance for distribution via the DRF. To further refine the filter concept, you can define further variable filter criteria such as material number and plant (transaction Define Filter Criteria).

If you have set up DRF integration for transactional data, replication is triggered in various scenarios and thus directly in the associated transactions. In this process, the filter criteria and other prerequisites for the distribution process are checked.

Planned order

All transactions for creating and changing planned orders lead to distribution of a relevant order to the MES. If a planned order that has already been distributed is changed manually or by means of planned changes, it is automatically distributed again to the MES.

Transaction	Description
MD01	MRP planning run
MD02	MRP - single-item, multi-level
MD11	Create planned order
MD12	Change planned order
MF50	Planning table for repetitive manufacturing If the opening date of the planned order lies in the future, no automatic distribution is carried out yet with the specified transactions. By scheduling report `RDRF_MESSAGE_OUT` periodically (transaction DRFOUT), you can ensure that planned orders are subsequently distributed when their opening date reaches the current date.
If you have set up DRF integration for planned orders, this affects the following listed transactions:
POIT	Download of transaction data; the planned order data can no longer be distributed to the target system of the DRF replication model using this transaction.
MFBF	Confirmation in Repetitive Manufacturing; If certain data (such as material, plant, or planned order number) are specified as MES-relevant filter criteria, confirmation is no longer possible via this transaction because the data cannot be synchronized any more.

Production order

All transactions for creating and changing production orders lead to distribution of a relevant order to the MES, provided it has been released. If a production order that has already been distributed is changed, it is automatically distributed again to the MES.

Transaction	Description
CO01	Create production order
CO02	Change production order
CO40	Create production order from planned order
CO41	Create production orders from planned orders (collective processing)
If you have set up DRF integration for production orders, this affects the following listed transactions.
POIT	Download of transaction data; the production orders can no longer be distributed to the target system of the DRF replication model using this transaction.
CO11N (and other confirmation transactions)	Confirmation of production orders; this transaction cannot be used to confirm production quantities and scrap for distributed production orders since this confirmation information is expected from the MES. The confirmation of working times is still permitted.

Maintenance order

If you have set up DRF integration for maintenance orders, maintenance orders are automatically distributed to the MES when they are created or changed, provided they have been released.

Transaction	Description
IW31	Create maintenance order
IW32	Change maintenance order

Material documents

If you have set up DRF integration of goods movements, relevant material documents are automatically distributed to the MES when created, regardless of with which transaction or by which operation they were created.

The distribution of the master data is carried out via the transaction Execute Data Replication (DRFOUT).

Log functions

You can display an overview of the distribution of master data and transaction data using the transaction Display Object Replication Status (DRFRSD). Using the transaction Analyze Application Log (SLG1), you can check the cause of distribution problems if necessary. To do so, enter the object DRF_OUTBOUND and restrict the selection period accordingly.

More Information

Detailed information about the DRF is available under Data Replication.