Thanks to visit codestin.com
Credit goes to www.scribd.com

Scribd
Upload
28 views2 pages

An Overview of Integration

Integrations facilitate data exchange between SAP and non-SAP systems, triggered by predefined events and utilizing middleware like PI/PO for data transfer. Different integration types, such as IDoc, web services, and RFC, are selected based on project requirements, with distinctions in their operation modes (synchronous vs. asynchronous). IDocs use fixed segments and XML format for data sharing, while web services can be standard or custom depending on the integration needs.

Uploaded by

Sonder
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
28 views2 pages

An Overview of Integration

Integrations facilitate data exchange between SAP and non-SAP systems, triggered by predefined events and utilizing middleware like PI/PO for data transfer. Different integration types, such as IDoc, web services, and RFC, are selected based on project requirements, with distinctions in their operation modes (synchronous vs. asynchronous). IDocs use fixed segments and XML format for data sharing, while web services can be standard or custom depending on the integration needs.

Uploaded by

Sonder
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

An overview of integration:

Integrations are used to either push data (outbound) to non sap system or pull data (inbound) to
sap.

Integrations are developed to exchange data between sap to sap system (ECC to SAP BI or
BW) or sap to non sap system (SAP to MES) as well.

Integrations are triggered based on predefined events. Events are finalized by discussing with
business.
Ex.: Event to trigger a data exchange can be an order release.

Scheme of data transfer:

Data transferred between 2 systems will take place through a middle ware. Generally
middleware will be PI/PO.
Flow is data packet will be pushed to middleware and from there to the required system.
Also field names may be different between 2 systems like AUFNR and Order_no for order
number in sap and other system. Mapping of these 2 fields will be done in middleware.
While sending or recieving data, initial segment can contain extra fields and only required can
be sent further. Control can be exercised in PI/PO.

Synchronous and Asynchronous messages :

Synchronous: Message is called as synchronous, if the message is triggered on real time basis,
that is at the time of the event.

Asynchronous: if the message is triggered on a scheduled basis. Generally outbound can be a


scheduled task.
Ex: To push the released orders to non sap system.

Integrations can be of different types like Idoc, web service (API) or RFC.

How are the different integration types selected:


1. If in the same project few messages have to be triggered on real time and few messages
are scheduled (will be done by scheduler, scheduler can be arranged on sap or non sap
system) , then web services are used.
2. If the messages are triggered on real time only. Then we can use idoc or webservice
3. If the message is to be triggered on command from external system, then RFC is used.
RFC is remote function call.
Ex: RFC is used to download inspection lot in released status on LIMS application. Here,
lot will be processed further after download. This way of sending data is neither
scheduled nor real time basis. Message is sent on RFC call made by user.
Difference between Idoc, web service and RFC function module:

As discussed above, depending on project requirement different type of interfaces will be


selected.

Idoc:
For checking idoc WE series tcodes to be used. WE02 tcode gives an overview of all the
message types (each idoc will have individual name).
Every message type would have a segment, with predefined set of fields and the order of the
fields being fixed.
Data is shared in XML format.

Idocs can be standard -SAP provided like iord, into in PM, Matmas in MM , batmas in pp etc.
For PM scenario standard idocs would generally not be suitable , as a custom status would be
sent based on different system status of orders in sap.

Webservice:

There are standard and custom web services.

But if we are trying to connect a non sap application for results recording with SAP, then in such
cases custom web services are developed.

Written by
Venkatesh K.

You might also like