Oracle by Example brandingCreating an Orchestration with Multiple Components

section 0Before You Begin

This 30-minute Oracle By Example (OBE) shows you how to create a multifaceted orchestration that retrieves and evaluates customer data from EnterpriseOne and invokes another orchestration if certain criteria is met.

Background

This OBE employs the following scenario to show you how to create a complex orchestration. You need an orchestration that contains a condition to determine if a hold should be placed on a customer’s credit, and if so, invokes the Credit Hold orchestration (created in the Creating a Simple Orchestration in the JD Edwards Orchestrator Studio OBE).

To do so, you will perform the following tasks:

  • Create a data request to retrieve a customer’s credit limit.
  • Create a data request to retrieve a total sum of outstanding customer order amounts.
  • Create a rule with a condition for placing a hold on a customer’s credit.
  • Invoke the Credit Hold orchestration.
  • Add the data requests, rule, and orchestration to a new “Customer Credit Check” orchestration.
  • Test the orchestration.

What Do You Need?

  • A JD Edwards EnterpriseOne test environment with a minimum of EnterpriseOne Tools 9.2.6.0.

section 1Creating a Data Request to Retrieve a Customer's Credit Limit

This section demonstrates how to create a data request to retrieve a customer’s credit limit from the customer master view (V03012F) in EnterpriseOne.

  1. Access the Orchestrator Studio.
  2. On the Orchestrator Studio home page, click the Data Requests icon, and then click the New button.
  3. On the Data Request design page, complete these fields:
    • Name = Get Customer Credit Limit
    • Enter Short Description = Retrieve Customer Credit Limit
  4. In the Table/View Name field, enter V03012F, and click Load.
    This business view contains the F0101 and F03012 tables for the Customer Master program.
  5. In the grid, click the Filter icon next to Address Number[F0101] - AN8. This adds the filter to the condition box in the Filter Criteria section on the right.
    • In the Filter Criteria section on the right, make sure Match All is selected for the Match Type.
    • Make sure the equals (=) operand is selected and leave the variable that appears in the field by default. The orchestration uses this variable to pass the address book number of the customer to EnterpriseOne.
  6. Change the variable in the Values column from ${Address Number 1} to ${Customer}.
  7. To define the field values that you want the data request to return:
    In the Fields grid on the left, click the Return icon next to the following fields:
    • Credit Limit [F03012]
    • Alpha Name [F0101] (Scroll down in the grid to find this field.)
      The fields will be placed in the Return Fields and Variable Names section on the right.
  8. Change the text in the Variable column for the return fields just added:
    • Credit Limit [F03012] = Credit Limit
    • Alpha Name [F0101] = Name
  9. Click Save. The data request should look like this when complete:
    10. Schedule Window
    Get Customer Credit Limit Data Request Window

section 2Creating a Data Request to Retrieve a Total Sum of Customer Order Amounts

This section demonstrates how to create a data request to retrieve order totals from the sales order table (F4201) in EnterpriseOne.

  1. On the Data Requests page, click the New button.
  2. Complete these fields:
    • Name = Order Totals 
    • Enter Short Description = Calculate total sum of order amounts
  3. In the Table/View Name field, enter F4201 and click Load.
    This is the Sales Order table that contains customer order amounts.
  4. Toggle the switch next to Aggregation to the on position.
  5. In the grid, click the Filter icon next to the following fields:
    • Address Number
    • Order Date
  6. In the Conditions box, for Address Number, make sure that = is selected as the operand.
  7. In the adjacent field, change the ${Address Number 1} variable to ${Customer}for the variable name, and verify that it looks like the following screenshot:
    8. Schedule Window
    Address Number Conditions
  8. For Order Date, select > (greater than) as operand.
  9. Use the arrow next to the variable name to open the Special Value dialog, and select “Today minus 1 Year”, and verify that it looks like the following screenshot:
    10. Schedule Window
    Order Date Conditions
  10. To specify the aggregate or the total sum of order amounts that you want returned, in the Fields grid on the left, scroll down to the Order Amount row and click the Aggregate icon.
  11. In the pop-up window that appears on the right side of the page, select Sum.
  12. In the Aggregations and Variable Names area on the right, click the Include Count switch.
  13. In the field adjacent to Order Amount: Sum, enter Total Order Amount for the variable name.
    The variable enables you to map the total sum amount returned from this data request to another orchestration step.
  14. Click Save. The data request should look like this when complete:
    15. Schedule Window
    Order Totals Data Request Window

section 3Creating a Rule with a Condition for Placing a Hold on a Customer’s Credit

This section demonstrates how to create a rule with condition for order amounts that are greater than a customer’s credit limit.

  1. In the upper left corner of the Orchestrator Studio, click the Home link in the breadcrumbs.
  2. On the home page select Rules, click New, and then click Standard.
  3. In the area on the right, complete the following fields for the new rule:
    • Name = Over Credit Limit 
    • Description = Condition for open order amount greater than credit limit
  4. To enter a condition for open order amounts that exceed the credit limit:
    1. From the Match Type drop-down list, select Match All.
    2. In the first row of the grid, in the Rule Type column, select Numeric from the drop-down list.
    3. In the Value 1 column, enter OpenOrderAmt as a variable for this input.
    4. In the Operator column, select > (greater than symbol).
    5. In the Value 2 column, enter CreditLimit as a variable for this input.
  5. Click Save.
  6. The rule should look like this:
    7. Schedule Window
    Over Credit Limit Rule Window

section 4Adding the Data Requests, Rule, and Orchestration to the New Customer Credit Check Orchestration

This section demonstrates how to:

  • Create a “Customer Credit Check” orchestration with Customer Number as an input.
  • Add the data requests, rule, and orchestration components as steps in the orchestration.
  • Map the orchestration input to the inputs defined in the orchestration steps.
  1. Click the X in the top right corner to close the Rules page.
  2. Click the Orchestrations icon on the home page and then click New.
  3. Complete the following fields:
    • Name = Customer Credit Check
    • Description = Check customer credit limit and if exceeded, place a credit hold on customer
  4. Click the + icon on the line between the Start and End nodes.
  5. Select Data Request, scroll and find the Get Customer Credit Limit data request, and select it.
    The selected data request will be added as a node (step) in the orchestration diagram.
  6. Click the new data request step and click Transformations.
  7. Click Add Inputs to Orchestration.
  8. Click Auto Map. Now the Customer input has been added to the orchestration inputs and it has been mapped to the Customer input for this data request step.
    The transformations for this step should look like this:
    9. Schedule Window
    Get Customer Credit Limit Transformations Window
  9. Save the orchestration.
  10. Double-click on the line in the orchestration diagram between the Get Customer Credit Limit data request and the End node.
  11. Select Data Request.
  12. Find the Order Totals data request and select it. The data request will be added to the orchestration.
  13. Click the new Order Totals data request step in orchestration and select Transformations.
  14. Use the drop-down list to select Customer from Available Values under Orchestrator Inputs.
    The transformations for this step should look like this:
    15. Schedule Window
    Order Totals Transformations Window
  15. Save the orchestration.
  16. Double-click on the line in the orchestration diagram between the last data request (Order Totals) and the End node.
  17. Select Rule.
  18. Find the Over Credit Limit rule and select it. The rule will be added to the orchestration diagram.
  19. Click the new Over Credit Limit rule step (the left side of it) and select Transformations.
  20. For OpenOrderAmt, use the drop-down list in Available Values to select Total Order Amount (under Order Totals).
  21. For CreditLimit, use the drop-down list in Available Values to select Credit Limit (under Get Customer Credit Limit).
  22. Verify that the transformations for the rule looks like the following screenshot:
    23. Schedule Window
    Over Credit Limit Rule Transformations Window
  23. Double-click the True line of the rule and select Orchestration.
  24. Find the Set Credit Hold orchestration and select it. The orchestration will be added inside the rule.
  25. Click the new Set Credit Hold orchestration step and select Transformations.
  26. For Address_Number, select Customer under the Available Values. The transformations should look like this:
    27. Schedule Window
    Set Credit Hold Transformations Window
  27. Click the End node and select Outputs and Assertions.
  28. Enable the Select All option.
  29. Save the Orchestration. It should look like this:
    30. Schedule Window
    Customer Credit Check Orchestration

section 5Testing the Customer Credit Check Orchestration

Note: Before you test the orchestration, you must set the customer’s credit limit to $25.

To set the customers credit limit:

  1. Access EnterpriseOne and enter P01012 in the Fast Path field to access Work With Addresses.
  2. Search and select your customer number, and then select A/R from the Row menu.
  3. Click the Credit tab and in the Credit Limit field, enter 25.
  4. If the Credit Message is already set to 7, clear it.
  5. Click OK.

To test the Customer Credit Check orchestration:

  1. In the Orchestrator Studio, access your orchestration, click Tools, and click Run Orchestrations. Your orchestration will be automatically selected for you.
  2. In the Inputs area, enter a customer number for the Customer Number input.  Make sure you are using a customer number in the demo data provided with the EnterpriseOne data pack.
  3. Click Run.
  4. The orchestration output should look similar to this, if the customer selected had order totals higher than 25.
    5. Schedule Window
    Customer Credit Check Orchestration Output

To verify the customer credit hold was applied in EnterpriseOne:

  1. Access EnterpriseOne and enter P01012 in the Fast Path field to access Work With Addresses.
  2. Search and select your customer number, and then select A/R from the Row menu.
  3. On Work With Addresses, search for and select the customer from the grid and click OK.
  4. Click the Credit tab and verify that the Credit Message status is 7 – On Credit Hold per Accounting.

To verify the “Over Credit Limit” message was sent:

  1. Sign on to EnterpriseOne with a user that has the associated customer number.
  2. In EnterpriseOne, access the Message Center program (P980051X).
  3. Select the Work Center tab.
  4. Expand the Personal In Basket queue, where you should see the “Over Credit Limit” message for your customer.
  5. Click the message to view it.
  6. Click the Customer Master Revision action link (in the blue bar next to the message title).
  7. This shortcut will take you to the customer’s record in Customer Master Revisions, where you can click the Credit tab and see the 7 – On Credit Hold per Accounting status.

more informationWant to Learn More?