How can I process (validate, Parse) x12 EDI files in Azure. Can you please provide in detail steps.

Jaidhan Kosambe 0 Reputation points
2024-05-23T07:26:42.9433333+00:00

I want process EDI x12 files using Azure. I want perform below operations on file:

  1. Pickup file from FTP folder location
  2. Validate file as per EDI standard and Generate acknowledgement
  3. Convert x12 EDI file into xml or json
  4. Store file data(xml or json) in sql table

What are the details should I add in Schemes, Maps, Partners and Agreements to Process EDI file using Integration account?

What are the details should I add in logic app to process EDI file?

Azure Functions
Azure Functions
An Azure service that provides an event-driven serverless compute platform.
4,481 questions
Azure Blob Storage
Azure Blob Storage
An Azure service that stores unstructured data in the cloud as blobs.
2,542 questions
Azure Logic Apps
Azure Logic Apps
An Azure service that automates the access and use of data across clouds without writing code.
2,932 questions
Azure App Service
Azure App Service
Azure App Service is a service used to create and deploy scalable, mission-critical web apps.
7,151 questions
{count} votes

1 answer

Sort by: Most helpful
  1. SwathiDhanwada-MSFT 18,121 Reputation points
    2024-05-27T11:12:35.16+00:00

    @Jaidhan Kosambe The following diagram shows the high-level steps to start building B2B logic app workflows:

    User's image To process EDI X12 files using Azure, you can use an Integration Account in Azure. An Integration Account is a container for managing B2B artifacts such as schemas, maps, partners, and agreements. Here are the details you should add to the Integration Account to process EDI files:

    • Defines at least two trading partners that participate in the X12 operation used in your workflow. The definitions for both partners must use the same X12 business identity qualifier.
    • Defines an X12 agreement between the trading partners that participate in your workflow. Each agreement requires a host partner and a guest partner. The content in the messages between you and the other partner must match the agreement type. For information about agreement settings to use when receiving and sending messages, see X12 message settings.
    • Defines the schemas to use for XML validation.

    Once you have set up the Integration Account with the necessary artifacts, you can use a Logic App to process the EDI X12 files. Note that both your integration account and logic app resource must exist in the same Azure subscription and azure region. Here are the details you should add to the Logic App to process EDI files:

    1. FTP connector: You should add an FTP connector to the Logic App to pick up the EDI X12 files from the FTP folder location.
    2. Decode X12 connector: You can use decode x12 action in the Logic App to transform the EDI X12 files into XML or JSON format using the maps defined in the Integration Account. For example, refer this https://stackoverflow.com/questions/74310156/edi-conversion-in-azure and this https://learn.microsoft.com/en-us/azure/logic-apps/logic-apps-enterprise-integration-x12?tabs=consumption#decode-x12-messages
    3. SQL connector: You should add a SQL connector to the Logic App to store the transformed file data (XML or JSON) in a SQL table.
    4. Control connectors: You should add control connectors to the Logic App to handle errors and exceptions that may occur during the processing of the EDI files.
    0 comments No comments