Java IDoc Adapter Partner Conversion

Use

Inbound Conversion

  • Determining Sender XI Service

    1. Retreive SAP ID and Client from fields SNDPOR and MANDT.

    2. Find the right XI service for which adapter-specific attributes (SAP SID and Client) are maintained as above.

  • Determining Sender XI Party (if SNDPRT != LS)

    Identify Party for which PartyIdentifier is kept as (agency, schema, identifier) -> (XI Senderservice, ALE#SNDPRT[#SNDPFC], SNDPRN)

  • Determining Receiver XI Service/XI Party

    You must maintain the receiver system details as empty.

Outbound Conversion

  • Sender service

    From sender service identifiers fill MANDT, SNDPOR (and SNDPRN in case of No Party)

  • If sender party is available

    Find SNDPRN from PartyIdentifier (agency, schema, identifier) -> (Channel sender agency {= sender service}, Channel sender schema {= ALE#SNDPRT[#SNDPFC]}, Identifier {=SNDPRN})

  • Receiver service

    From receiver service identifiers fill RCVPOR (and RCVPRN in case of No Party)

  • If receiver party available

    Find RCVPRN from PartyIdentifier (agency, schema, identifier) -> (Channel receiver agency {= receiver service}, Channel receiver schema {= ALE#RCVPRT[#RCVPFC]}, Identifier {=RCVPRN})

Interface Conversion Logic

XI interface name is calculated from following headers in the form <MSGTYP> . <IDOCTYP> . <CIMTYP>

Interface namespace is always urn:sap-com:document:sap:idoc:messages

Some of the relevant control records used are:

  • MANDT: client of sender system

  • SNDPOR: Port of Sender System (ideally in format SAP <SID> ) For example: SAPBCE

  • SNDPRN: Partner Number of sender system

  • SNDPRT: Sender Partner Type (LS correspond to No Party and Others[KU,LI,etc..] for party-based

  • SNDPFC

  • RCVPOR

  • RCVPR

  • RCVPRT

  • RCVPFC

  • MSGTYP

  • IDOCTYP

  • CIMTYP

For more information, see The Control Record Fields of the IDoc Adapter (AAE)