Normalization in the Sender Adapter (SAP Library

Normalization in the Sender Adapter

The sender SAP Business Connector adapter provides the option of extracting data from an external message protocol and using it to assemble the header of the XI message. This procedure is known as normalization or party conversion. The structure of the XI message header depends on the message protocol that is used.

After the XI message header is successfully built, a sender agreement that corresponds to this XI header is searched for. The sender agreement found refers to a communication channel, which contains additional information for the processing of the message in the SAP Business Connector adapter.

Message Protocol RFC XML with Envelope

The fields of the XI message header occur in the same order that is specified in the following table:

Structure of the XI Message Header

Field	Structure
Interface	The name of the RFC-enabled function module is used. This is the name of the first XML tag that follows the body tag of the RFC XML envelope. This tag has to be in the XML namespace urn:sap-com:document:sap:rfc:functions. Since the ABAP namespace identifiers /namespace/ are not permitted in XML, the sender uses the following format in XML: _-namespace_- When used, this format is then switched back.
Interface Namespace	The fixed namespace urn:sap-com:document:sap:rfc:functions is used.
Sender Service	If the From field in the RFC XML envelope contains six characters, the characters are interpreted as the SAP system ID and client. A search is made for a party without service that contains this system ID and client as adapter-specific identifiers. See Adapter-Specific Identifiers in Service. The service without party that is found is used as the sender service. If a field contains anything other than six characters, or if the search for the service was not successful, the actual contents of the From field from the RFC XML envelope are used as sender service.
Sender Party	This field is left blank.
Receiver Service	This field is left blank.
Receiver Party	This field is left blank.

Message Protocol IDoc-XML

The sender adapter builds the XI message header using the rules below.

The following terms are used:

· The variables specified below are fields from the IDoc control record. See also: Fields of the IDoc Control Record

· The plus sign (+) is used to join two text elements into one

· The term "example" describes the fixed text element example, without the quotation marks (" ")

Structure of the XI Message Header

Field	Structure
Interface	MESTYP + “.” + IDOCTYP If the field CMITYP exists, the following is added to the interface names: “.“ + CMITYP
Interface Namespace	The fixed namespace urn:sap-com:document:sap:idoc:messages is used here.
Sender Service	If the field SNDPOR contains "SAP" followed by a three-digit system ID, an attempt is made to find a service without party that contains this SAP system ID and the value of the MANDT field as the adapter-specific identifiers. See Service, then Adapter-Specific Identifiers, IDoc Adapter and RFC Adapter. If the contents of the field SNDPOR do not start with "SAP", an attempt is made to find a service without party that contains the contents of the SNDPOR field in its adapter-specific identifiers (IDoc adapter). The service without party that is found is used as the sender service.
Sender Party	If the field SNDPRT contains LS, the service is a logical system and the sender party remains blank. If it is not a logical system, a party is determined by means of the alternative identifiers (for the party). The following are used as identifiers: · Agency is the sender service found · Scheme is “ALE#“ + SNDPRT. If the field SNDPFC contains a value, the following is added: “#“ + SNDPFC · Name is SNDPRN These values are used to search across all parties. The party that is found is used as the sender party.
Receiver Service	This field is always left blank.
Receiver Party	If the field RCVPRT contains LS, the service is a logical system and the receiver party remains blank. If it is not a logical system, an attempt is made to determine a party by means of the alternative identifiers (for the party). The following are used as identifiers: · Agency is the sender service found · Scheme is “ALE#“ + RCVPRT. If the field RCVPFC contains a value, the following is added: “#“ + RCVPFC · Name is RCVPRN The party that is found is used as the receiver party.

Caution

The receiver adapter does not evaluate the header of the XI message for party conversion. The XI message payload is sent directly to the receiving SAP Business Connector. The message must therefore contain the correct IDoc-XML document, including the IDoc control record.