Create an EDIFACT Agreement in Azure BizTalk Services
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:
-
Create your first logic app, or quickly get started using a pre-built template
-
View all the available connectors you can use in your logic apps
The topics in this section list the steps to create an EDIFACT agreement.
Configure EDIFACT General Settings
In the BizTalk Services Portal home page, select Agreements.
On the Agreements page, select the EDI tab, and then select Add.
In the New Agreement page, enter the following:
Field
Description
Name
Enter a unique name for the agreement.
Protocol
Select EDIFACT for EDIFACT agreements.
Description
Enter notes or a description of the agreement.
Hosted Partner
Select the hosted partner for the agreement. Hosted partner is the partner that BizTalk Services deploys the EDIFACT send and receive pipelines.
The default profile is displayed in the Profile field. Choose the desired profile which has been configured for the partner.
Guest Partner
Select the partner for the agreement. A guest partner is the partner that the hosted partner wants to achieve B2B messaging.
The default profile is displayed in the Profile field. Choose the desired profile which has been configured for the partner.
Identities
Hosted Partner Identification
Enter an identification value for the hosted partner. This can be an alphanumeric value ranging between 1 and 35 characters.
Hosted Partner Code Qualifier
Select a business identity code qualifier that provides unique business identities to the trading partners. Trading partners can opt for a mutually agreed business identity.
Guest Partner Identification
Enter an identification value for the guest partner. This can be an alphanumeric value ranging between 1 and 35 characters.
Guest Partner Code Qualifier
Select a business identity code qualifier that provides unique business identities to the trading partners. Trading partners can opt for a mutually agreed business identity.
Select Continue. The Receive Settings and Send Settings tabs are added. Each tab creates a one-way agreement between the two partners: one to receive messages from the guest partner and another for sending messages to the guest partner.
Configure EDIFACT Receive Settings
The receive settings for an EDIFACT agreement primarily include the EDIFACT protocol settings. These settings are used while receiving an EDIFACT message from a trading partner. The Receive Settings tab is displayed after you enter the General Settings for the agreement.
The Protocol page allows you to enter the EDIFACT protocol settings between the two partners. These can be divided into Basic and Advanced settings.
Basic Settings
Identifiers
Field |
Description |
UNB6.1 (Recipient Reference Password) |
Enter an alphanumeric value ranging between 1 and 14 characters. |
UNB6.2 (Recipient Reference Qualifier |
Enter an alphanumeric value with a minimum of one character and a maximum of two characters. |
Acknowledgements
Receipt of Message (CONTRL) |
Select this checkbox to return a technical (CONTRL) acknowledgment to the interchange sender. The acknowledgment is sent to the interchange sender based on the Send Settings for the agreement. |
Acknowledgement (CONTRL) |
Select this checkbox to return a functional (CONTRL) acknowledgment to the interchange sender The acknowledgment is sent to the interchange sender based on the Send Settings for the agreement. |
Schemas
UNH2.1 (TYPE) |
Select a transaction set type. |
UNH2.2 (VERSION) |
Enter the message version number. (Minimum, one character; maximum, three characters). |
UNH2.3 (RELEASE) |
Enter the message release number. (Minimum, one character; maximum, three characters). |
UNH2.5 (ASSOCIATED ASSIGNED CODE) |
Enter the assigned code. (Maximum, six characters. Must be alphanumeric). |
UNG2.1 (APP SENDER ID) |
Enter an alphanumeric value with a minimum of one character and a maximum of 35 characters. |
UNG2.2 (APP SENDER CODE QUALIFIER) |
Enter an alphanumeric value, with a maximum of four characters. |
SCHEMA |
Choose or upload a schema. The receive pipeline disassembles the incoming message by matching the values for the different fields in the incoming message with the values you set here, and the schema of the incoming message with the schema you set here. To upload a schema:
|
Advanced Settings
Control Numbers
Field |
Description |
Disallow Interchange Control Number duplicates |
Select this checkbox to block duplicate interchanges. If selected, the BizTalk Services Portal checks that the interchange control number (UNB5) for the received interchange does not match the interchange control number. If a match is detected, then the receive pipeline does not process the interchange. If you opted to disallow duplicate interchange control numbers, you can specify the number of days at which the check is performed by giving the appropriate value for Check for duplicate UNB5 every x days option. |
Disallow Group control number duplicates |
Select this checkbox to block interchanges with duplicate group control numbers (UNG5). |
Disallow Transaction set control number duplicates |
Select this checkbox to block interchanges with duplicate transaction set control numbers (UNH1). |
EDIFACT Acknowledgement Control Number |
To designate the transaction set reference numbers to be used in an acknowledgment, enter a value for the prefix, a range of reference numbers, and a suffix. |
Validation
Message Type |
Select the message type. Select the + sign to add validation rules for other message types. If no rules are specified, then the row marked as default is used for validation. |
EDI Validation |
Select this check box to perform EDI validation on data types as defined by the EDI properties of the schema, length restrictions, empty data elements, and trailing separators. |
Extended Validation |
Select this check box to enable extended (BizTalk XSD) validation of interchanges received from the interchange sender. This includes validation of field length, optionality, and repeat count in addition to XSD data type validation. |
Allow Leading/Trailing Zeroes |
Select Allow to allow leading/trailing zeros; NotAllowed to not allow leading/trailing zeros, or Trim to trim the leading and trailing zeroes. |
Trailing Separator Policy |
|
Internal Settings
Create empty XML tags if trailing separators are allowed |
Select this check box to have the interchange sender include empty XML tags for trailing separators. |
Use dot (.) as decimal separator |
Select this check box to include a dot (.) in the XML message created out of an interchange that contains a decimal number. |
Inbound batching processing |
Options include:
|
Character Sets and Separators
UNA1 (Component data element separator) |
Enter a value for the component data element separator that separates simple data elements within composite data elements. Select Char for a character data element or Hex for a hexadecimal data element. The character you enter automatically changes if you change its format. |
UNA2 (Data element separator) |
Enter a value for the data element separator that separates composite data elements consisting of two or more simple data elements or simple data elements that are not part of a composite. Select Char for a character data element or Hex for a hexadecimal data element. The character you enter automatically changes if you change its format. |
UNA3 (Decimal notation) |
Select whether you want to use a Comma or Decimal as the decimal notation to be used in the outgoing interchange. |
UNA4 (Release Indicator) |
Enter a value for the release indicator that indicates that the following character is not a syntax separator, terminator, or release character, but is part of the original data. Select Char for a character data element or Hex for a hexadecimal data element. The character you enter automatically changes if you change its format. |
UNA5 (Repetition Separator) |
Enter a value for the repetition separator to separate segments that repeat within a transaction set. Select Char for a character data element or Hex for a hexadecimal data element. The character you enter automatically changes if you change its format. |
UNA6 (Segment Terminator) |
Enter a value for the segment terminator that indicates the end of an EDI segment. Select Char for a character data element or Hex for a hexadecimal data element. The character you enter automatically changes if you change its format. |
Suffix |
Select whether you want to use carriage return (CR), line feed (LF), both, or none as the end-of-line character that is used with the segment terminator. |
Configure EDIFACT Send Settings
The EDIFACT send settings configure the agreement configuration for sending messages from hosted partner to guest partner, and batching and protocol settings. These sections list the steps to configure the send-side settings of an EDIFACT agreement. The Send Settings tab is displayed only after you entered the General Settings.
Add a Batch
The Batching page on the Send Settings tab allows you to create batches to send several messages as a batch to a partner. You can also enter rules based on which batch is triggered. These rules are based on the values of promoted properties you defined in the earlier stages.
On the Batching page, select Add Batch to launch a wizard.
In the Batch details page, enter a batch name and a batch description, and then select Next.
In the Batch criteria page, enter the criteria based on which a batch configuration is triggered. The batch criterion is specified using the values of the promoted properties at runtime. You can either select the value from a grid to specify the batching condition or use a standard SQL 92 syntax to define the batching condition. To understand this better, let us assume you promoted a property (P1) whose value is set to ‘100’ at runtime. To use this property as a condition for triggering a batch, you can do either of the following:
Select the option for the grid, and then select the (+) icon to select the property you promoted. From the grid, select P1, enter the Operation as (==), and set the value to 100.
OR
Select the Use advanced definitions option, and specify a SQL 92 expression, such as:
P1 == 100You can use this option to provide more detailed query expressions using other operators as well. In the example used here, during the agreement processing if a property P1 is created and its value is set to 100, then this batch is triggered.
Select Next.
In the Batch release criteria page, enter the criteria for batching messages together. The drop-down lets you select more than one criterion for batching. However, there are four key criterion that can be used together to provide different combinations:
InterchangeSizeBased – For the Size(max) property, enter the number of characters to create and send a batch. The agreement accumulates batching elements until the character count in those elements exceeds the specified character count.
MessageCountBased – For the Count property, enter the number of messages that must be processed together as a batch.
ScheduleBased – For this option, enter the following properties:
Occurs – Specifies the unit of measurement of time in terms of minutes, hours, days, or weeks.
First release – Specifies which day and at what time the first batch is released.
Recurs every – Specifies the frequency or recurrence, after the first occurrence. For example, if you set this property to 2 and the Occurs property to Hourly, then the messages are batched every 2 hours after the first release.
Note
There could be a variation of +/- 10 seconds while releasing batches based on these criteria. Also, the time period starts when the first message is received by the bridge.
TimeoutBased – This property specifies the timeout (in minutes) at which a batch is triggered, irrespective of whether any other criterion is met or not. This property is always used along with another property. For example, if you set the batch release criteria to MessageSizeBased, TimeoutBased and the values to 3 messages and 5 minutes respectively, then the agreement first waits to collect three messages to constitute a batch. If three messages do not arrive in 5 minutes, the agreement goes ahead and processes the batch with whatever number of messages that is available. Note that the timeout value is the idle time from the last released batch. For the first batch, this timeout is the idle time from the start of the batch.
Note
There could be a variation of +/- 10 seconds while releasing batches based on these criteria. Also, the time period starts when the first message is received by the bridge.
You can select different combinations of these key criterions to define when a batch is released.
In the Summary page, verify the batch configuration and then select Save.
Certain points to consider regarding batches:
When you finish these steps, a batch is created. A batch is deployed only when you deploy the agreement containing the batch.
You cannot edit a batch when the agreement is deployed. To edit a batch, you must first stop the batch by select the Stop Batch link next to the batch.
Once you finish editing a batch, you must redeploy the agreement to ensure that the updated batch configuration is used for further batch processing.
If you are redeploying an agreement, you do not need to stop the batches associated with it. However, you must ensure that the changes that are made to the agreement do not affect the running batches. For example, if an agreement is updated to not process a specific schema, then you must ensure that none of the running batches are processing a message of that schema. If such batches are not stopped, the messages are suspended when the batch is released.
Before you delete an agreement, you must stop any batches associated with the agreement.
Enter the Protocol settings
The Protocol page of the Send Settings tab allows you to enter the protocol settings between the two partners. The settings you enter on this page are used to create an EDIFACT message before it is sent to the guest partner. These settings can be divided into Basic and Advanced settings.
Basic Settings
Identifiers
UNB1.2 (Syntax version) |
Select a value between 1 and 4. |
UNB2.3 (Sender Reverse Routing Address) |
Enter an alphanumeric value with a minimum of one character and a maximum of 14 characters. |
UNB3.3 (Recipient Reverse Routing Address) |
Enter an alphanumeric value with a minimum of one character and a maximum of 14 characters. |
UNB6.1 (Recipient Reference Password) |
Enter an alphanumeric value with a minimum of one and a maximum of 14 characters. |
UNB6.2 (Recipient Reference Qualifier) |
Enter an alphanumeric value with a minimum of one character and a maximum of two characters. |
UNB7 (Application Reference ID) |
Enter an alphanumeric value with a minimum of one character and a maximum of 14 characters |
Acknowledgements
Receipt of Message (CONTRL) |
Select this checkbox if the hosted partner expects to receive to receive a technical (CONTRL) acknowledgment. This setting specifies that the hosted partner, who is sending the message, requests an acknowledgement from the guest partner. |
Acknowledgement (CONTRL) |
Select this checkbox if the hosted partner expects to receive a functional (CONTRL) acknowledgment. This setting specifies that the hosted partner, who is sending the message, requests an acknowledgement from the guest partner. |
Generate SG1/SG4 loop for accepted transaction sets |
If you chose to request a functional acknowledgement, select this checkbox to force generation of SG1/SG4 loops in functional CONTRL acknowledgments for accepted transaction sets. |
Schemas
UNH2.1 (TYPE) |
Select a transaction set type. |
UNH2.2 (VERSION) |
Enter the message version number. |
UNH2.3 (RELEASE) |
Enter the message release number. |
SCHEMA |
Choose a schema to specify how the BizTalk Services Portal converts the XML message to EDIFACT before sending it to the guest partner. To upload a schema:
|
Advanced Settings
Envelopes
UNB8 (Processing Priority Code) |
Enter an alphabetical value which is not more than one character long. |
UNB10 (Communication Agreement) |
Enter an alphanumeric value with a minimum of one character and a maximum of 40 characters. |
UNB11 (Test Indicator) |
Select this checkbox to indicate that the interchange generated is test data |
Apply UNA Segment (Service String Advice) |
Select this checkbox to generate a UNA segment for the interchange to be sent. |
Apply UNG Segments (Function Group Header) |
Select this checkbox to create grouping segments in the functional group header in the messages sent to the guest partner. The following values are used to create the UNG segments:
|
Character Set and Separators
Other than the UNB 1.1 system identifier, you can specify a different set of delimiters to be used for each message type. If a character set is not specified for a given message schema, then the default character set is used.
UNB1.1 (System Identifier) |
Select the EDIFACT character set to be applied on the outgoing interchange |
Schema |
Select the (+) symbol and select a schema from the drop-down list. For the selected schema, select the separators set to be used:
|
Control Numbers
UNB5 (Interchange Control Number ) |
Enter a prefix, a range of values for the interchange control number, and a suffix. These values are used to generate an outgoing interchange. The prefix and suffix are optional; the control number is required. The control number is incremented for each new message; the prefix and suffix remain the same. |
UNG5 (Group Control Number) |
Enter a prefix, a range of values for the interchange control number, and a suffix. These values are used to generate the group control number. The prefix and suffix are optional; the control number is required. The control number is incremented for each new message until the maximum value is reached; the prefix and suffix remain the same. |
UNH1 (Message Header Reference Number) |
Enter a prefix, a range of values for the interchange control number, and a suffix. These values are used to generate the message header reference number. The prefix and suffix are optional; the reference number is required. The reference number is incremented for each new message; the prefix and suffix remain the same. |
Validation
Message Type |
Select the message type. Select the + sign to add validation rules for other message types. If no rules are specified, the row marked as default is used for validation. |
EDI Validation |
Select this check box to perform EDI validation on data types as defined by the EDI properties of the schema, length restrictions, empty data elements, and trailing separators. |
Extended Validation |
Select this check box to enable extended (BizTalk XSD) validation of interchanges received from the interchange sender. This includes validation of field length, optionality, and repeat count in addition to XSD data type validation. |
Allow Leading/Trailing Zeroes |
Select Allow to allow leading/trailing zeros; NotAllowed to not allow leading/trailing zeros, or Trim to trim the leading and trailing zeroes. |
Trailing Separator Policy |
|
Select Save to save the agreement.