Mohsin Kalam’s Blog

October 9, 2007

PAM

Filed under: R2 EDI — Mohsin Kalam @ 2:00 pm

Goal:

To describe various settings used by the BizTalk EDI runtime components stored in PAM.

Overview:

Partner Agreement Manager (PAM) is the central repository for the configuration settings accessed by the EDI runtime components during document processing. It is a UI driven model which plugs in the BizTalk Administration Console.

PAM defines 2 levels: Global and Party. Settings from the Global level are used during processing if no party is resolved for a document. R2 gives the users the ability to customize processing of individual documents by resolving them to a specific party. In other words, the global settings are enough to perform processing. Party specific properties are just an addition to the process that allows fine grain customization.

In addition to the levels, PAM defines 2 roles under Party settings: Party as Interchange Sender and Party as Interchange Receiver. Settings from Interchange Sender role are used during parsing and settings from Receiver role are used during serialization.

The following diagram explains the above

Roles

Global Settings:

The global properties are defined in a detailed post here.

Party Settings:

A party can be created by selecting the party node under BizTalk Server 2006 Administration Console and right clicking on the right hand view and selecting New->Party. Once a party is created, the EDI Party properties are accessed by right clicking on that party and selecting “EDI Properties“. The following snapshot shows the EDI properties view

EDI Properties

Party properties are divided into a General section used by all EDI components, a contact information tab and a separate EDIFACT and X12 section that is subdivided for Engine Receive, Send and Batching.

General Properties:

General properties include Activating Status Reporting which is turned off by default. It also has an option of copying settings from an already configured party. It also specifies certain agreement details like start and end date and a text field to add notes related to this agreement. General settings are applied for all EDI runtime components (except AS2 that has a separate page dedicated to it).

Contact Information:

Allows you to enter the contact information for the party. It includes fields like Name, Company and email etc.

EDIFACT Properties:

EDIFACT properties are used by the EDI runtime to process an EDIFACT encoded interchange. It is described in great detail here.

X12 Properties:

X12 properties are used by the EDI runtime to process X12 encoded interchange. It is described in great detail here.

Validation:

Validation of certain fields specified in PAM are done according to the standard defined by X12 and EDIFACT. The following rules are followed:

  • Validation of ISA, GS, UNB and UNG fields are done against the control schema deployed under the BizTalk EDI Application. These include checking for min/max length and performing data type validation.
  • Validation of delimiters is done to ensure the delimiters do not collide with other delimiters and they are under the valid range of 0-127 ASCII
  • For EDIFACT, UNB2.1, UNB2.2, UNB3.1 and UNB3.2 are validated as a quartet to ensure they are unique among all parties. The same applies for ISA5-8
  • For control numbers (ISA13, GS6, ST2, UNB5, UNG5 and UNH1), validation is performed to ensure their length is within the allowed range. Invalid values are not saved. If during processing of a doc the control numbers exceed maximum length, an error is raised in the event viewer and the document is suspended. A user has to manually reset the control number to allow further processing

End Note:

I hope this post has been useful in understanding PAM and how it is used by the runtime components during processing of an EDI document. Your comments/questions are always welcome.

Thanks

Mohsin Kalam

Advertisements

Leave a Comment »

No comments yet.

RSS feed for comments on this post. TrackBack URI

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Blog at WordPress.com.

%d bloggers like this: