Partilhar via


APPENDIX: Promoting Message Properties

 

Important

Microsoft Azure BizTalk Services (MABS) is being retired, and replaced with Azure Logic Apps. If you currently use MABS, then Move from BizTalk Services to Logic Appsprovides some guidance on moving your integration solutions to Logic Apps.

If you're brand new to Logic Apps, then we suggest getting started here:

Use BizTalk Services Portal to promote message properties. These properties are used by the agreement for processing such as message routing and batch configuration. There are two types of promoted properties – user-promoted properties and system-promoted properties. User-promoted properties are the properties that the users promote. These properties are defined as part of the agreement, both for the send and receive side. For information, see Create Agreements in Azure BizTalk Services.

System-promoted properties are the properties that are promoted by X12/AS2 bridges and are available to users. The following table lists the system-promoted X12 and AS2 properties. Just like the user-defined properties, you can use these properties as well for message routing and batch configuration.

X12 Send

InterchangeDate

InterchangeTime

ReceiverID

ReceiverQualifier

SenderID

SenderQualifier

AgreementID

SystemRequestID

MessageReceivedTime

SourceType

ErrorDescription

EDI.GE01

EDI.IEA01

X12 Receive

ISA05

ISA06

ISA07

ISA08

ISA09

ISA10

ISA12

ISA13

ISA14

ISA15

ISA_Segment

GS01

GS02

GS03

GS04

GS05

GS06

GS07

GS08

GE01

GS_Segment

ST01

ST02

ST03

MessageType

TA1_TA104

ReuseEnvelope

IsSystemGeneratedAck

AK901

Exception

InterchangeControlNo

InterchangeDate

InterchangeTime

ReceiverID

ReceiverQualifier

SenderID

SenderQualifier

TsSequenceNumberInGroup

AgreementID

IsInterchange

IsTransactionSet

IsInterchangeAck

IsFunctionalAck

SystemTrackingID

SystemRequestID

MessageReceivedTime

SourceType

SourceName

AS2 Receive

ISA5

ISA6

ISA7

ISA8

AS2From

Note

If the AS2 Receive bridge routes messages to an HTTP destination, this property shows up as AS2-From in the HTTP headers.

AS2To

Note

If the AS2 Receive bridge routes messages to an HTTP destination, this property shows up as AS2-To in the HTTP headers.

FileName

MessageReceivedTime

SourceType

SourceName

SystemRequestID

AgreementID

EDIFACT

UNA_Segment

UNB_Segment

UNB2_1

UNB2_2

UNB2_3

UNB2_4

UNB3_1

UNB3_2

UNB3_3

UNB3_4

UNB11

See Also

Configuring EDI, AS2, and EDIFACT on BizTalk Services Portal