Hierarchy
SAP_APPL (Software Component) Logistics and Accounting⤷
PP-MES (Application Component) Integration with Manufacturing Execution Systems⤷
CO_MES_INT (Package) Integration of Production w. Manufacturing Execution Systems
IMG Activity
| ID | MES_INT_BASIC | Basic Settings for MES Integration |
| Transaction Code | S_EBS_44000341 | (empty) |
| Created on | 20110112 | |
| Customizing Attributes | MES_INT_BASIC | Basic Settings for MES Integration |
| Customizing Activity |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | MES_INT_BASIC |
Use
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).
Requirements
You can use the integration option only if you have previously activated the business function LOG_PP_MES_INT02.
Standard settings
Activities
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 LOIPLO01
Production Order LOIPRO LOIPRO02
Inventory Management INVCON INVCON02
Work center LOIWCS LOIWCS02
Routing LOIROU 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.
@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 make the basic settings in DRF Customizing and set up at least one replication model for the above-mentioned objects:
Object Message Type DRF business object
Planned Order LOIPLO 92
Production Order LOIPRO 97
Inventory Management INVCON 467
Work center LOIWCS 493
Routing LOIROU 223
Perform the steps set out in DRF Customizing.
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. In doing so, note that after activation of the distribution model, as a basic rule, all objects are included in the selection list if no special filter criteria have been maintained.
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.
Example
Business Attributes
| ASAP Roadmap ID | 203 | Establish Master Data |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | MES_INT_BASIC | 0 | EBS0000003 | Integration with Manufacturing Execution Systems |
Maintenance Objects
| Maintenance object type |
History
| Last changed by/on | SAP | 20110113 |
| SAP Release Created in | 606 |
