How to Iterate an Orchestration Over a Set of Records in JD Edwards EnterpriseOne

Introduction

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.

Business Scenario

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.

  • Let us assume users would not print the pick slip report anymore. Instead, an automatic job would run every hour to process all pick slip for order at next status 540 for a specific branch
  • The associated BOL (Bill of Lading) document would also be produced but not emailed
  • The user needs the documents sent via email to the warehouse contact (specifically for their 3PL warehouses)

Solution

Step 1

Create an Orchestration in JD Edwards EnterpriseOne with the series of steps to be performed:

  • Service Data Request to retrieve Sales Orders by Business Unit
  • Condition to only perform the process IF records are available
  • Custom Function F(X) to retrieve Warehouse Contact Email
  • Launch the Pick Slip UBE
  • Message request to Warehouse Contact
  • Launch BOL UBE
Step 2

Create a Connector for the above Orchestration – this will allow it to iterate the entire Orchestration over one or more set of records.

Step 3

Create a new Orchestration using the below steps:

  • Create a DB request which will pull all eligible warehouses and pass each warehouse to the Connector that was created in Step 2.

  • Call the Connector which was created in Step 2 and pass the Business Unit as an input to the Orchestration. And then select the option called “iterate over”.

Conclusion

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.