Scribd
Upload
14 views12 pages

BOOMI EDI 850 Inbound and Order Status Via ODATA API

EDI Corp faced challenges with EDI integration due to diverse trading partner standards and ERP limitations. By implementing an OData API, the company streamlined data exchange, improved integration efficiency, and enhanced real-time order status tracking. The solution resulted in reduced costs, improved accuracy, and increased flexibility in EDI processes.

Uploaded by

Mario antelo ribera
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
14 views12 pages

BOOMI EDI 850 Inbound and Order Status Via ODATA API

EDI Corp faced challenges with EDI integration due to diverse trading partner standards and ERP limitations. By implementing an OData API, the company streamlined data exchange, improved integration efficiency, and enhanced real-time order status tracking. The solution resulted in reduced costs, improved accuracy, and increased flexibility in EDI processes.

Uploaded by

Mario antelo ribera
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 12

Boomi EDI and ODATA API

Problem

EDI Corp Company was facing a number of challenges with its EDI integration. The
company had a large number of trading partners, each with their own unique EDI
standards. This made it difficult to integrate with all of their trading partners. Additionally,
the company's ERP systems were not designed to easily integrate with EDI. This made
it difficult to exchange data with trading partners in a timely and accurate manner.

One Use Case:

TP Corp a.k.a. partner is one of the partner which send EDI 850 purchase order. EDI
Corp uses BOOMI as middleware for EDI integrations.
Once TP Corp sends a purchase order, they want to get relatime status of the Order
and on demand as well. TP corp wants status of the order based on processing status,
order name , Ship to address or any other parameter.

Solution

EDI Corp Company decided to implement an OData API to solve its EDI integration
challenges. OData is an open data protocol that allows for the easy exchange of data
between systems. By implementing an OData API, ABC Company was able to create a
single, unified interface for exchanging data with trading partners. This made it much
easier to integrate with new trading partners and to exchange data with existing trading
partners.

Benefits

Since implementing the OData API, EDI Corp Company has experienced a number of
benefits. The company has been able to:

• Reduce the time and cost of integrating with new trading partners
• One Unified interface to get real time data for the partners and internal
applications on order status. Order status could be based on order number,
processing status of the order any of the acceptable parameters.We are just
creating one API and one integration process for ODATA API in this scenario.
• Improve the accuracy and timeliness of data exchange with trading partners
• Increase the flexibility of its EDI integration
• Improve the overall efficiency of its business processes

Lets Build the integration process

1. Create the Trading partner components. Establish the communication method with TP.
2. Create the EDI profile
3. Create the target profile ( here I am using Azure SQL DB), so JSON profile.
4. Create the map component.
5. Build your integration process.
1. Lets Deploy and run the job to connect to TP CORP and get some edi 850
2. Check the process reporting page . Notice we can track the document flow based on Trading
partner, Document (Tracked filed ) or based on the process tab as well.
Data is updated/inserted into the database.

Lets Build ODATA to give status of the order to TP

1. Start with integration process


a. Build /configure shared web server oprations.
b. Create xml profile to be used as ODATA response.
c. Create Database connection and operation to get data from Database. Please
note, on database opration we can select * from Orders table as OADTA will take
care filter.
d. Create a map component to convert the data into ODATA XML reposne.
2. Lets Build ODATA API component
3. Deploy the listener process and ODATA API.
Lets get into APIM to validate the metdata URL and ODATA entity

OData Metadata Path


https://c02-usa-west.integrate-test.boomi.com/ws/odata2/$metadata
Test the ODATA API using different filter criteria and select queries

Get orders where status is Processed or Rejected

https://c02-usa-west.integrate-
test.boomi.com/ws/odata2/orders/?$filter=Status%20eq%20%27Processed%27%20or%20Status%20eq
%20%27Rejected%27
To get received order id and status

https://c02-usa-west.integrate-test.boomi.com/ws/odata2/orders/?$select=ORDER_ID,Status
To know specific status of an order based on order id

https://c02-usa-west.integrate-
test.boomi.com/ws/odata2/orders/?$filter=ORDER_ID%20eq%20%270065-9182075-0588%27
Conclusion

The implementation of an OData API has been a success for EDI CORP Company. The
company has been able to improve its EDI integration and achieve a number of
benefits, including reduced costs, improved accuracy, and increased flexibility.

You might also like