In Customizing for Cross-Application Components, choose
.In the Customizing transaction Make Technical Setting for Business Systems, define the logical system or the RFC destination.
In the Customizing transaction Define Replication Models, specify what the replication model is to contain (for example, master data such as material or transactional data such as planned order or production order). By doing so, you specify which outbound implementation is to be sent and to which business system this object is sent. You can specify a different destination system (for example, SAP Manufacturing Execution) for each outbound implementation that contains the business object, the filter object, and the business logic.
As standard, the following filter objects are supplied for an MES integration:
Business object |
Outbound implementation |
Filter object |
IDoc Type )* |
Planned order |
92_1 |
92_1 |
LOIPLO01 |
Production order |
97_1 |
97_1 |
LOIPRO02 |
Maintenance order |
468_1 |
468_1 |
IORDER01 |
Material |
194_1 |
194_2 |
MATMAS03 |
Equipment |
183_1 |
183_1 |
EQUIPMENT_CREATE02 |
Goods movement |
467_1 |
467_1 |
INVCON02 |
Work center |
493_1 |
493_1 |
LOIWCS02 |
Routing |
223_1 |
223_1 |
LOIROU03 |
)* To use the enhanced interfaces, you must utilize at least the specified basis type or its successor for the integration. A prerequisite is that the receiving system is able to process the relevant basis type.
Call up the transaction Define Filter Criteria (DRFF) and refine your filter concept by defining further criteria. For more information, see Use of Data Replication Filters.
Note
If no filter criteria are defined for a replication model, all business objects in the replication model that are relevant for distribution are sent to the MES. This can lead to performance problems, particularly for objects distributed automatically during the course of the transaction. For this reason, you must ensure that you specify the filter criteria after the DRF replication model has been activated.
Call up the transaction Execute Data Replication (DRFOUT) to trigger the distribution of the master data on the basis of individual replication models. With the manual distribution, you can override filter criteria that you previously defined in the transaction Define Filter Criteria. If you want a material to be distributed immediately instead of via a background job, for example, you can use this transaction to trigger the distribution.
Furthermore, you can carry out an initial distribution or a delta distribution when changing the data.
The transaction data is distributed from the respective transactions.