Ansicht
Dokumentation
MES_INT_BASIC - Basic Settings for MES Integration
PERFORM Short Reference BAL_S_LOG - Application Log: Log header dataThis documentation is copyright by SAP AG.
This Customizing document provides you with an overview of the necessary settings for the integration of an SAP ERP system and a Manufacturing Execution system (MES) (in particular, an SAP MES).
You can use the integration option only if you have previously activated the business function LOG_PP_MES_INT_02.
Set Up an ALE Model
Master data and documents in the production environment are distributed to the MES via IDocs, whereby the criteria for the distribution are usually controlled by the Data Replication Framework (DRF). The following IDoc messages are provided for integration purposes:
| Object | Message Type | Basis Type* |
|---|---|---|
| Planned Order | LOIPLO | LOIPLO02 |
| Production Order | LOIPRO | LOIPRO05 |
| Inventory Management | INVCON | INVCON02 |
| Maintenance order | IORDER | IORDER01 |
| Equipment | EQUIPMENT_CREATE | EQUIPMENT_CREATE02 |
| Material | MATMAS | MATMAS06 |
| Work center | LOIWCS | LOIWCS03 |
| Routing | LOIROU | LOIROU04 |
| Shift Grouping | PP_SHIFT | PP_SHIFT01 |
)* 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.
@AI@Note
- Further messages may be required for the integration with the MES. Currently, these cannot yet be distributed via the DRF.
To set up the IDoc communication, you must perform the following steps:
- Maintain a logical system through which the MES is identified. Also create a logical system that identifies the sending client (if this has not yet been done).
- Assign the logical system of the sender to the client from which the messages are sent (if this setting has not yet been made).
- Define the RFC destination for the MES system and specify the technical properties of this RFC connection.
- Create a port for the MES using the logical system created in step 3.
- Maintain the partner profiles of type LS using the logical system for the MES, the port created above, and the message types listed.
- Maintain the ALE distribution model for your own sending logical system and the logical system of the MES as the receiver. Assign the above-mentioned message types to this distribution model.
Set Up the DRF Integration
Create Replication Models
The sending of the IDocs to the MES is controlled via the DRF for the most important objects. To activate the integration, you must set up at least one replication model for the above-mentioned objects in DRF Customizing:
| Object | Message Type | DRF business object |
|---|---|---|
| Planned Order | LOIPLO | 92 |
| Production Order | LOIPRO | 97 |
| Inventory Management | INVCON | 467 |
| Maintenance order | IORDER | 468 |
| Equipment | EQUIPMENT_CREATE | 183 |
| Material | MATMAS | 194 |
| Work center | LOIWCS | 493 |
| Routing | LOIROU | 223 |
To do so, carry out the steps described here using the example of the production order. Only the specified parameters need to be maintained in the DRF; no additional settings are required in DRF Customizing for the MES integration.
- Create a business system that represents the MES installation and enter the logical system and RFC connection that you created in the previous section. You do not need to register this business system in the SLD; you can ignore the corresponding warning by choosing the ENTER key to confirm.
- Create a replication model and enter a description. Specify the number of days after which you want the log for the distribution to expire. A period of a few days is sufficient. Once the deadline has expired, the logs can be cleaned up.
- Select the replication model and assign the outbound implementation 97_1 for the production order in the next level of the maintenance dialog.
- Select the outbound implementation 97_1 and assign the business system defined above in the next level of the maintenance dialog.
- Activate the replication model on the overview page.
It is advisable to create different replication models for the master and transactional data at least, because these data types are distributed with different frequencies. As a rule, the distribution of the transactional data is carried out directly, whereas the distribution of master data has to be triggered explicitly.
For other master data, such as the bill of material, you must use the existing ALE transactions for distribution purposes.
Define Filter Criteria
After defining the replication models, specify the filter criteria for the individual business objects within the distribution models. You maintain the filter criteria as master data in the production client of your system. Before the activated DRF replication models are transported into your productive system, you need to make sure that selection criteria are already defined there. To do so, use the Transport function in transaction DRFF with which you can transport the selection criteria specified in the development system into the productive system.
If you miss out this step and import the activated replication models into the productive system without filter criteria, all the documents or master data distributed by the DRF are identified as relevant for distribution until you maintain filter criteria in the productive system.
If you can only define the final filter criteria in the productive system because the master data required for this is not available in the development system, you can block the unintended distribution of data in the productive system by defining an impenetrable filter criterion in the development system, for example:
Material is $%&§
Once you have transported these filter criteria into the productive system, you can maintain the final criteria there.
Set Up the Distribution of Transactional Data
If you have included the business objects for the transactional data in a DRF replication model, they will be distributed as soon as the filter criteria are satisfied. In the case of production and maintenance orders, distribution does not take place until they are released. Additional settings are necessary for some business objects.
Earmark Production Orders for Distribution
If you want to use the DRF for distribution purposes, you do not have to make any further settings in the IMG to make orders distribution-relevant. Distribution is controlled via the DRF filter criteria.
Earmark Planned Orders for Distribution
To make planned orders distribution-relevant, you must ensure that the following prerequisites are satisfied:
- The planned order must be relevant to repetitive manufacturing. To satisfy this prerequisite, create a suitable repetitive manufacturing profile and assign it to the material you wish to manufacture. For the integration with the MES, you should specify (in the control data) that planned orders assigned to the production version are to be reduced in the case of confirmations.
- A production version that is relevant to repetitive manufacturing must be assigned to the planned order. You maintain the production version in the material master of the material being produced.
- You have created a routing (transaction CA01) or a rate routing (transaction CA21) for the material to be produced. Alternatively, you can also reference an ME routing from SAP ME. This ME routing is created as a routing in ERP and can be used in the planned order.
- In the production version for the material to be produced, you have specified the task list type, the task list group, and the group counter of the routing that is to be used.
- Check the Customizing settings for automatic routing determination.
- Determine the selection ID that is used for automatic selection of the routing alternative by calling the Customizing activity Define Scheduling Parameters for Planned Orders. Check the scheduling settings for your plant and your order type, if necessary, to see which selection ID has been set for detailed scheduling or rate-based scheduling. In the standard system, the selection ID 01 or 02 is used.
- Call the Customizing activity for automatic routing selection and check if there is an entry that matches your master data for the selection ID determined above, the routing type (N or R), the routing usage, and the release status. If necessary, add the missing entry.
- The opening date of the planned order must be the current day's date or a date in the past. The opening horizon is part of the scheduling margin key for the float and is assigned to the material master. You maintain the scheduling margin key in Customizing here.
RFUMSV00 - Advance Return for Tax on Sales/Purchases Addresses (Business Address Services)
This documentation is copyright by SAP AG.
Length: 12674 Date: 20240523 Time: 212242 sap01-206 ( 172 ms )
