- Events, Blogs & News
Many of us have been in a business scenario where we need to iterate several Orchestration steps over one or more set of records. This overview will demonstrate how to iterate an orchestration over a set of records that are an outcome from a database request.
Customers have many external warehouses (3PLs/third party logistics) to manage the stock they buy and sell. The transportation documents (pick slip and BOL) are currently sent to those warehouses manually by email by the users. Customers would like to have these documents sent automatically by email via a JD Edwards EnterpriseOne Orchestration.
Create an Orchestration in JD Edwards EnterpriseOne with the series of steps to be performed:
Create a Connector for the above Orchestration – this will allow it to iterate the entire Orchestration over one or more set of records.
Create a new Orchestration using the below steps:
In the above example, the first orchestration launches the second orchestration with an input from the warehouse. The second orchestration pulls all eligible Sales Orders for that warehouse and prints the pick slip and BOL documents. The first orchestration calls the second orchestration based on the list of warehouses (derived from DB request) Using the DB request over the Business Unit table (F0006) allowed us to select all the Outside Warehouses.
Syntax has over 40 years of Oracle ERP experience and over 20 years providing cloud and managed services for JD Edwards EnterpriseOne solutions. To learn more about JD Edwards, visit our JD Edwards insights page, where you can access JDE whitepapers, webinars, data sheets, and much more.