Professional Documents
Culture Documents
Topics
Answers
Blogs
Events
Programs
Resources
What's New
Home
Community
Blogs
Ask a Question
Write a Blog Post
Login / Sign-up
Technical Articles
Roman Gorbenko
Quote.
“The increased scale and complexity of SAP and non-SAP systems challenges require that we look
for
ways to simplify the system-integration requirements”
This quote about a series of blog-posts (“Integrate it…”) about integration between different SAP and
non-SAP systems
Another posts from this series (The list is being updated.)
Integrate it! – Qlick View/Sense and SAP integration. Step-by-step guide
About.
Manufacturing execution systems (MES) are computerized systems used in manufacturing, to track
and document the transformation of raw materials to finished goods. MES provides information that
helps manufacturing decision-makers understand how current conditions on the plant floor can be
optimized to improve production output. MES works in real-time to enable the control of multiple
elements of the production process (e.g. inputs, personnel, machines, and support services).
MES may operate across multiple function areas, for example, management of product definitions
across the product life-cycle, resource scheduling, order execution, and dispatch, production
analysis and downtime management for overall equipment effectiveness (OEE), product quality, or
materials track and trace. MES creates the “as-built” record, capturing the data, processes, and
outcomes of the manufacturing process. This can be especially important in regulated industries,
such as food and beverage or pharmaceutical, where documentation and proof of processes,
events, and actions may be required.
Benefits of MES:
1. Reduced waste, re-work, and scrap, including quicker setup times
2. More accurate capture of cost-information (e.g. labor, scrap, downtime, and tooling)
3. Increased uptime
4. Incorporate paperless workflow activities
5. Manufacturing operations traceability
6. Decreases downtime and easy fault finding
7. Reduced inventory, through the eradication of just-in-case inventory
Common use cases where MES system integrated with SAP EWM and/or SAP ERP systems
MES-system consume a master-data (Materials, Batches, Containers and so on) from ERP-system
Prerequisites.
You want to know more about SAP-MES Integration with SAP PI/PO in the outline.
Resolution.
Step 0. Intro
In this integration scenario:
SAP ERP – SAP S/4HANA
Message bus (integration broker) – SAP PO
Let’s first take a quick look at the integration scenario blueprint:
N.B.
IDoc, short for Intermediate Document, is a SAP document format for business transaction data
transfers. The IDoc itself is a structured Text-File, that means IDocs can be used on all platforms,
there is no need to translate binary data
SAP transactions:
Step 3.1.1. Settings in SM59
Transaction SM59 – Configuration of RFC Connections
Connection Type – T (TCP/IP Connections)
Gateway Host – Path to SAP PI/PO
Program ID –
1)A RfcAdapter sender channel registers itself with this Program ID as a RFC-Server at the SAP
Gateway. The sending system uses the same Program ID to identify the RFC-Server at the SAP
Gateway.
During the sending system sends some RFC calls, the SAP Gateway will search its registration list
for the Program ID supplied by the sending system
2)The Program ID is case sensitive.
3)The same Program ID should be given in RFC Sender Channel.
Gateway service – sapgw<SID>
Step 3.1.2. Settings in WE31
Transaction – WE31 – Development IDoc Segment
Bindings between IDoc Segment and Data Elements
For example Segment type E1BATMAS and Fields in Segment like as MATERIAL
Transaction – SE80 – Object Navigator and other development tools like an SM30 and SE38
(creation of package / subpackages, structures, function modules, programs and so on)
For example Generated Proxy Z-Structure for Material
Step 3.2.3. Scheduling
For RFC:
SM36 -> Create Background job for each custom ABAP program which sends data to integration
Step 4. Integration from MES standpoint
A quick look at the integration scenario from the MES standpoint.
For example MES system with integration part based on Apache Camel.
Small quote about architecture:
“ERP data is exchanged as XML text files that comply with a selected set of SAPIDOCs. The IDOCs
from a file system is transformed from XML to common business objects and delivered to FTPC
through JMS message queues. Using an event sheet, Shop Operations Server reads the messages
from this queue and launches a specific activity set to process each message.”
Architecture and configuration:
Integration Configuration:
Java Message Service Providers:
Inbound Configuration
Outbound Configuration
Step 5. Monitoring
Monitoring from the ERP side:
Transaction – WE02 (Display IDoc)
Transaction – WE05 (IDoc List)
Example:
Message 29 – Error in ALE service
Transaction – BD87 – Status Monitor for ALE Messages
Status Monitor for ALE Messages for example status for LOIPRO (Production Order)
Alert Moderator
Assigned tags
Related Questions
Help on Integrating Sales force integration with PO over Rest OAuth 2.0
By Former Member, Oct 25, 2017
BPM and BRM step by step guide
By Sreenivasa V, Oct 12, 2019
Integration with sfdc adapter
By Former Member, Sep 18, 2017
Be the first to leave a comment
You must be Logged on to comment or reply to a post.
Find us on
Privacy
Terms of Use
Legal Disclosure
Copyright
Trademark
Cookie Preferences
Newsletter
Support