The Control Record Fields of the IDoc Adapter (AAE)

Concept

The sender IDoc adapter (AAE) receives IDoc messages from the sender system (AS Java) over a TCP/IP connection. The adapter converts the IDocs to Idoc XML compatible format, puts the information in the payload of an XI message and performs a header mapping to the XI message.

As the communication channel corresponds to multiple business systems, the sender adapter transports the information dynamically. The inbound-IDoc adapter sets the party or service headers of the XI message based on the incoming IDoc's control record information.

You can use the transactions we20(Partner configuration) and we21(port configuration) in the R3 system to configure IDoc partner information.

The following table provides information about how the fields in the control record are filled by and mapped to the IDoc adapter (AAE).

More information about the structure of the control record: Control Record Structure

Field Name	Description
MANDT	Client
SNDPOR	Sender port The following valueas are possible: port = SAP+System_ID If the value of the SNDPRT field is not LS, MANDT and SNDPRT determine sender service. port <> SAP+System_ID If the value of the SNDPRT field is not LS, the field directly determines sender service.
SNDPRN	Sender partner number
SNDPRT	Sender partner type. The possible options for this field are: Logical system (LS) Customer (KU) Vendor (LI) User(US)
SNDPFC	Sender partner function (optional field)
RCVPOR	Receiver Port
RCVPRN	Receiver partner number
RCVPRT	Receiver partner type. The possible options for this field are: Logical system (LS) Customer (KU) Vendor (LI) User(US)
RCVPFC	Receiver partner function (optional field)
MSGTYP	Message type
IDOCTYP	Idoc type
CIMTYP	CIM type