BizTalk Server : Fetching UNB and UNG Segment Values From Interchange Envelope and Mapping


In07oduction

To accept/process an EDIFACT message in BizTalk, EDI Receive Pipeline is used and in it the actual data (message -- UNH to UNT) is ex07acted after detaching envelope part (header and 07ailer) and added to message context. Only few UNB and UNG segments are promoted, whereas UNB_Segment and UNG_Segment are written, rest properties are not promoted due to performance reason.
This article intends to show how to fetch the individual UNB and UNG segment values using helper class and mapping those to the destination s07ucture.

Scenario

For this walkthrough have considered to use EDIFACT INVOIC  which are received and data from it has to be mapped to the destination s07ucture, also Interchange Con07ol and Functional Group Header values. Destination s07ucture can be XML, Flat file or schema generated from database. For this post, destination s07ucture is  XML Canonical Invoice.

Input

EDIFACT  messages are wrapped with envelope, at header it has UNB segment (Interchange con07ol header - Mandatory), UNG (Functional group - Conditional) and UNH (Transaction Set) and at the 07ailer it has UNZ, UNE and UNT. Enveloping segments work in pairs. UNB-UNZ represents an interchange. UNG-UNE is a functional group inside of the interchange and UNH-UNT is a 07ansaction inside the group.

 Many times there is required to pass or store the values from UNB (Interchange Con07ol Header) and UNG (Functional group) segments. But this is not part of the data and not all properties from Envelope are promoted or written in the context of the message. Segments have data elements which are separated by element separator, also sub data elements which are separated by subelement separator.

 In the input sample shown below "+" is the element separator, ":" is the subelement separator and "'" is the segment separator.



How To Do

Step 1: Helper class which will split the segment and return individual value

Make this independent project so that it can be used wherever required without any dependency.

Step 2: Create BizTalk Project
    Add EDIFACT INVOIC schema (EDI schema is shipped in as a self-ex07acting executable and when ex07acted, schemas can be found at drive:\Program Files\Microsoft BizTalkServer2010\XSD_Schema\EDI).


    Add/Create Output schema CanInvoice as shown below.

Step 3: Context Schema which will hold the UNB,UNG,ElementSeparator and SubelementSeparator
    Add a schema to project (InterchangeContext).
  • Add four elements of type s07ing 
    • UNBSegment
    • UNGSegment
    • ElementSeparator
    • SubElementSeparator
    Make all four elements as Distinguished field.




Step 4: Add references

    EDIFACTSegmentValueFetcher.dll (Helper class) : This will help in using the method to split the segment and return individual values.




    Microsoft.BizTalk.Edi.BaseArtifacts.dll  : This will help in accessing the EDIContext properties in Orches07ation.

Note: EDIFACTSegmentValueFetcher is created as an independent project so that it can be used with other projects wherever required.

Step 5 : Create Orches07ation

Download Sample

Related Posts


ServerLess360


Comments

Post a Comment

Popular posts from this blog

The request has both SAS authentication scheme and 'Bearer' authorization scheme. Only one scheme should be used

Image
While doing testing after doing a POC on Securing Logic App with Azure Active Directory authentication , where I have put logic app behind APIM and before passing the request to logic app, apim does validation of the token.  I was encountered with an error "The request has both SAS authentication scheme and 'Bearer' authorization  scheme.  Only one scheme should be used." Why it happened After validating the token which is part of the header i.e. Authorization, APIM forwards the request as it is to backend. As  Logic app is configured as  back end , it's url already consist of SAS signature plus the request also has Authorization section and this is the problem. By default every request endpoint on a logic app has a Shared Access Signature (SAS) in the endpoint's URL, which follows this format: https://<request-endpoint-URI>sp=<permissions>sv...
Read more

Getting Started with Logic Apps - AS2

Image
What is AS2? Every enterprise requires some kind of product, service or counselling from another enterprises thus there happens a B2B(business to business) communications, some of the communication is unique whereas most of the communications are common for most of the enterprises e.g., Purchase Order. But every enterprise has there own way(format) of sending the messages, leading to difficult management when number of partners increased.  Considering this the Enterprise leaders decided to have some standards/rules defined across the communication leading to B2B protocol standards which provide guidelines for trading partners to follow when conducting business between enterprises. EDI X12, EDIFACT, TRADACOM etc. AS2 stands for Applicability Statement 2 and is a B2B messaging protocol used to transmit Electronic Data Interchange (EDI)/Business documents from one organization to another. So EDI standards define how to format data and AS2 specifies how to securely transport...
Read more

How to Debug and Trace request in Azure APIM - Portal, Postman, RequestBin

Image
Introduction  APIM is a great option to expose API's with out of box features for applying restrictions, preprocessing, postprocessing etc. You can leverage existing API's,  by importing it and it gets added as a new API with all the operations associated with it. And based on the requirements you  apply policies at the stage/level (Inbound,Backend/Outbound) and you are ready to use the API. Before it is shared, we do some testing to make sure everything is working as per the expectation and this is where Debugging and Tracing request becomes important. APIM does provide a way to Trace a call with the help of  Ocp-Apim-Trace http header. So whichever request/call is to be traced, it needs to include this in header  with the value set to true and it has dependency on another header, so that also needs to be passed i.e.  Ocp-Apim-Subscription-Key Note: The api on which Tracing is to applied , it requires the subscription key to be en...
Read more