The Change View 'Logical Systems': Overview window is displayed.ĭescription of the illustration ale_inbound2a.gif It indicates that the table is cross-client.ĭescription of the illustration ale_imgmessage.gif This name is assigned explicitly to one client in an SAP system.ĭescription of the illustration ale_saletransaction.gifĭescription of the illustration ale_inbound1.gifĪ message window is displayed. In SAP, the name of the logical system is used as the unique ID. In any distributed environment, each participating system must have a unique ID to avoid confusion. You must perform the following steps to configure SAP for inbound IDoc processing: This ensures that the external system can receive the data quickly and reliably (automatically).

This is done independently in the second step. If a partner is defined with the corresponding message in partner profiles, the IDoc is then processed further. If the upstream system is recognized, then the IDoc is saved in the database. The technical parameters of this port definition can (and usually are) overwritten by the upstream system. A port definition, which provides a unique ID for the upstream system, must be available for the port.

For this reason, you do not have to specify a port in the inbound partner profiles the IDoc interface only must recognize the upstream system as a port. SAP inbound processing requires the upstream system to transfer an IDoc to the IDoc interface through the R/3 System port.

Sample customer xml inbound file in aif