Header Key/Header Value

These fields show the key value pairs associated with the current document, as indicated in this table:

Header Key	Header Value Example	Description
BODType	Process.PurchaseOrder and Sync.PurchaseOrder	The BOD verb and BOD noun types of a message, separated by a period
TargetLogicalId	infor.syteline.oh,infor.csi-audit.local	The full list of destination component logical IDs, separated by commas
MessageId	infor.syteline.oh:1235069421472:958	An ID that must be unique for each message. Typically this is a concatenation of the FromLogicalId and other values to create the unique ID
ToLogicalId	infor.syteline.oh	The logical ID of the destination (component that should receive the BOD). In a multi-site environment, the Inbound Bus Service uses the instance (site name) to determine the site for which the BOD should be processed
FromLogicalId	lid://infor.mdm-proxy.local	The logical ID of the origin (component that sent the BOD)
FromLogicalIdWithOverride	lid://infor.mongoose.mongoose	This macro is similar to the site logical ID. If there is a value for the process default property Outbound SUM Role LID Override, then the override value is used. If there is no value in the process default property and no override is specified, the value returns to the same value as FROMLOGICALID().
ReferenceId	infor.syteline.oh-02-20-15-45-13.138-128	Typically a concatenation of the ToLogicalId, the date (MM-DD) and time (down to milliseconds), and an integer counter, to create a unique ID
TenantId	infor	A name that identifies the message as belonging to a specific tenant and is used to separate data from other tenants