A port definition, which provides a unique ID for the upstream system, must be available for the port.The technical parameters of this port definition can (and usually are) overwritten by the upstream system.Below is the standard documentation available and a few details of the fields which make up this Table.You can view further information about Table ADRC and the data within it using relevant SAP transactions such as SE11, SE80 or SE16.ADRC is a standard SAP Table which is used to store Addresses (Business Address Services) information.
Regards Daniel Graversen Figaf In specific third party business scenario we have used WMMBXY as SAP message type and EDI ANSI 940 as input feed to load the data as inbound IDOC and posted into MIGO with little customization in SAP. I am trying to find out what the functional differences are are behind the delivery advice, the shipment confirmation and the shipment advise. blog=/pub/u/252038725 I actually owe a copy of this blog to EDIGenie as well. I found a copy by searching Google for "X12 110 Invoice". As for what you would map it to in SAP, I haven't worked with it but my guess would be either the a vendor invoice (IDoc message type INVOIC) or an FI invoice (message type ACLPAY). But you'll need to work with your SAP functional folk to figure out where they want it to post and from there you'll be able to figure out the IDoc and the mapping. As I have indicated before, the question is not so much what IDoc can you map to which EDI transaction because you can map anything to anything.Cloud Foundry-based environment on SAP Cloud Platform includes an SAP HANA as a Service offering, which enables the XS Advanced Programming Model now also on SAP Cloud Platform.If you don’t know the XS Advanced Programming Model, learn more in this blog post by Sven Kohlhaas.During inbound (client) processing, IDocs are transferred to the interface and stored in the R/3 System.The document data is generated in a second step, also in the course of a workflow.