Technical Context Objects (SAP Library - Managing Services in the Enterprise Services Repository)

Technical Context Objects

Use

Technical context objects enable you to access message header fields:

● Sender and receiver information for all imported RFC and IDoc interfaces

● Information about the send step of an integration process that is assigned an abstract message interface

Features

Technical Context Objects for Interfaces in the Enterprise Services Repository

Repository Object Type	Context Object		Set By
Repository Object Type	Namespace	Name	Set By
RFC request	urn:sap-com:document:sap:rfc:functions	Destination	RFC Adapter
IDoc	urn:sap-com:document:sap:idoc:messages	SNDPRN	IDoc Adapter
		SNDPRT
		SNDPFC
		RCVPRN
		RCVPRT
		RCVPFC
		MESTYP
		MESCOD
		MESFCT
Request message of abstract message interfaces	http://sap.com/xi/XI/System	ProcessStep	Business Process Engine

Technical Context Objects for Message Header Fields

The following technical context objects all have the same namespace http://sap.com/xi/XI/System.

Technical Context Objects for Message Header Fields

Path in Header	Context Object Name (ABAP Name)	Meaning
Main/MessageClass	MessageClass (MESSAGE_CLASS)	Classification of message. Possible values: ● ApplicationMessage: Asynchronous or synchronous request message ● ApplicationResponse: Response to request message ● SystemAck, ApplicationAck, SystemError, ApplicationError: Acknowledgments
Main/@versionMajor	VersionMajor (VERSION_MAJOR)	XI message protocol version. Example: For the XI 3.0 message protocol VERSION_MAJOR = 3 and VERSION_MINOR = 0.
Main/@versionMinor	VersionMinor (VERSION_MINOR)
Main/ProcessingMode	ProcessingMode (PROCESSING_MODE)	The mode of a message can be synchronous or asynchronous. Correspondingly, these constants can have the value synchronous or asynchronous.
Main/MessageId	MessageId (MESSAGE_ID)	The message ID. It can change during communication: Response messages get a new message ID. If new messages result from a message (the message is copied at multiple receivers), the new messages get new message IDs.
Main/RefToMessageId	RefToMessageId (REF_TO_MESSAGE_ID)	The ID of a referenced message that belongs semantically to this message. For example, a response message uses this field to note which request message it belongs to.
Main/ConversationId	ConversationId (CONVERSATION_ID)	This field is not mandatory in the message. It enables an ID to be used to group messages that belong together. This field is not intended to be used for message serialization and has nothing to do with the serialization context (see context object QueueId).
Main/TimeSent	TimeSent (TIME_SENT)	Time stamp specifying when the message was sent by the sender. The format of the time stamp is as follows: YYYY-MM-DDTHH:MM:SSZ The letter ‘T’ separates the date and the time, which is generally specified in UTC. If it is a local time, the closing ‘Z’ is omitted.
Main/Interface	Interface (INTERFACE)	Sender interface name.
Main/Interface/@namespace	InterfaceNamespace (INTERFACE_NAMESPACE)	Sender interface namespace.
Main/Sender/Party	SenderParty (SENDER_PARTY)	Communication party that sent the message.
Main/Sender/Party/@agency	SenderPartyAgency (SENDER_PARTY_AGENCY)	Issuing agency for the message sender.
Main/Sender/Party/@scheme	SenderPartyScheme (SENDER_PARTY_SCHEME)	Identification scheme used by the sender
Main/Sender/Service	SenderService (SENDER_SERVICE)	Service on the sender side that sent the message. For example, the name of a business system.
Main/Receiver/Party	ReceiverParty (RECEIVER_PARTY)	Communication party to receive the message.
Main/Receiver/Party/@agency	ReceiverPartyAgency (RECEIVER_PARTY_AGENCY)	Issuing agency for the message receiver.
Main/Receiver/Party/@scheme	ReceiverPartyScheme (RECEIVER_PARTY_SCHEME)	Identification scheme used by the receiver.
Main/Receiver/Service	ReceiverService (RECEIVER_SERVICE)	Service on the receiver side that receives the message. For example, the name of a business system.
ReliableMessaging/QualityOfService	QualityOfService (QUALITY_OF_SERVICE)	Specifies the quality of service used to process the message. Possible values are BestEffort, ExactlyOnce, or ExactlyOnceInOrder.
ReliableMessaging/QueueId	QueueId (QUEUE_ID)	Only relevant for QualityOfService=”ExactlyOnceInOrder”. The value in this field corresponds to the serialization context that a sender uses to bundle related asynchronous messages (see also: ABAP runtime, Java proxy runtime).

Note

You can query most of the message header fields during a mapping. See also: Container Object (message mappings), Java Mapping, XSLT Mapping.

The following message header fields are only relevant for MessageClass=”ApplicationMessage” and ProcessingMode=”asynchronous”(see above). They can have the Boolean value true or false. See also: Acknowledgments.

Technical Context Objects for Message Header Fields for Acknowledgments

Path in Header	Context Object Name (ABAP Name)	Meaning
ReliableMessaging/@SystemAckRequested	SystemAckRequested (SYSTEM_ACK_REQUESTED)	If the value of this field is true, the sender requested a positive system acknowledgment.
ReliableMessaging/@SystemErrorAckRequested	SystemErrorAckRequested (SYSTEM_ERROR_ACK_REQUESTED)	If the value of this field is true, the sender requested a negative system acknowledgment.
ReliableMessaging/@ApplicationAckRequested	ApplicationAckRequested (APPLICATION_ACK_REQUESTED)	If the value of this field is true, the sender requested a positive application acknowledgment.
ReliableMessaging/@ApplicationErrorAckRequested	ApplicationErrorAckRequested (APPLICATION_ERROR_ACK_REQUESTD)	If the value of this field is true, the sender requested a negative application acknowledgment.