7 JD Edwards EnterpriseOne Orchestrations

This chapter contains the following topic:

Section 7.1, "Understanding JD Edwards EnterpriseOne Orchestrations"

7.1 Understanding JD Edwards EnterpriseOne Orchestrations

The JD Edwards EnterpriseOne orchestrations are prebuilt processes that can transform data that is collected from external devices into actionable business processes within JD Edwards EnterpriseOne. The JD Edwards EnterpriseOne Internet of Things Orchestrator processes these orchestrations to enable the immediate, real-time transformation of raw data into valuable data that can be used by the JD Edwards EnterpriseOne system.

An orchestration comprises the following components: service requests, rules, cross-references, and white lists. You define the metadata for each of these components in XML files, and the Internet of Things (IoT) Orchestrator uses the metadata in these XML files to perform AIS server calls that invoke JD Edwards EnterpriseOne transactions.

This chapter focuses on the predefined JD Edwards EnterpriseOne orchestrations that are available to address common use cases. You can use these orchestrations as examples to design your own orchestrations based on your business requirements.

7.2 Additional Orchestrations

The following prebuilt orchestrations are available:

  • Add Condition-Based Maintenance Alert

  • Update Meter Readings

  • Update Equipment Location

  • Kanban Check In

  • Kanban Check Out

  • Add Blend Operation

The IoT Orchestrator uses the input message defined for each of these orchestrations to make a service call to the AIS server which, in turn, invokes the respective JD Edwards EnterpriseOne application.

The AIS Server exposes each orchestration as an endpoint at http://<server>:<host>/jderest/orchestrator/<orchestration name>.

7.2.1 Add Condition-Based Maintenance Alert

You can use the Add Condition-Based Maintenance Alert orchestration to process a condition-based maintenance alert from a sensor reading associated with an asset.

For example, a sensor attached to a piece of equipment to monitor its health may send an alert when the tolerance level is crossed. The IoT Orchestrator uses the Add Condition-Based Maintenance Alert orchestration metadata to process the data from the sensor reading and convert it into transaction-capable information in the JD Edwards EnterpriseOne system.

This table includes information that the Add Condition-Based Maintenance Alert orchestration uses to process IoT data:

Application Invoked Application Version Endpoint URL
Condition-Based Alerts Revision (P1311) ZJDE0001 http://<server>:<host>/jderest/orchestrator/JDE_ORCH_12C_AddCBMAlert

This is an example of an input message defined for the Add Condition-Based Maintenance Alert orchestration:

{
     "inputs": [
         {
            "name": "EquipmentNumber",
            "value": "34665"
         },
         {
            "name": "MeasurementLocation",
            "value": "EG-01"
         },
         {
            "name": "Description",
            "value": "Orchestration Test"
         },
         {
            "name": "AlertLevel",
            "value": "1"
         },
         {
            "name": "Date",
            "value": "062415"
         },
         {
            "name": "Time",
            "value": "13:15:01"
         },
         {
            "name": "NotificationRecipient",
            "value": "6002"
         },
         {
            "name": "NotificationStructureType",
            "value": "WF1"
         },
         {
            "name": "PlannedStartDate",
            "value": "062615"
         },
         {
            "name": "AutomatedResponseType",
            "value": "1"
         }
     ]
}

7.2.2 Update Meter Readings

You can monitor meter readings on a piece of equipment and collect the data by using an IoT device. You can then use the Update Meter Readings orchestration to process the meter readings from the IoT device. For example, you can use meter readings to determine whether to initiate maintenance tasks for a machine or equipment based on the accumulated statistical units.

This table includes information that the Update Meter Readings orchestration uses to process IoT data:

Application Invoked Application Version Endpoint URL
Speed Meter Readings (P12120U) ZJDE0001 http://<server>:<host>/jderest/orchestrator/JDE_ORCH_13_UpdateMeterReadings

This is an example of an input message defined for the Update Meter Readings orchestration:

{
     "inputs": [
         {
            "name": "EquipmentNumber",
            "value": "34665"
         },
                             "name": "OdometerNewReading",
            "value": "61"
         },
         {
            "name": "FuelMeterNewReading",
            "value": "10"
         },
         {
            "name": "HourMeterNewReading",
            "value": "94"
         },
         {
            "name": "Meter4NewReading",
            "value": "4"
         },
         {
            "name": "Meter5NewReading",
            "value": "6"
         },
         {
            "name": "Meter6NewReading",
            "value": "8"
         }
     ]
}

7.2.3 Update Equipment Location

You use the Update Equipment Location orchestration to update the location of equipment. This orchestration processes the data forwarded by a location sensor and updates the Equipment Master Location Details table (F17311).

For example, a service technician might need to know the physical location of equipment to quickly and easily locate the equipment that requires maintenance. In such a situation, you can use an IoT location sensor attached to the equipment to record the equipment's geopositioning data, including the latitude and longitude. The Update Equipment Location orchestration then processes the sensor data and updates the F17311 table.

This table includes information that the Update Equipment Location orchestration uses to process IoT data:

Application Invoked Application Version Endpoint URL
Equipment Master Address Location Revisions (P1704) ZJDE0001 http://<server>:<host>/jderest/orchestrator/JDE_ORCH_17C_UpdateEquipmentLocation

This is an example of an input message defined for the Update Equipment Location orchestration:

{
     "inputs": [
         {
            "name": "EquipmentNumber",
            "value": "34665"
         },
         {
            "name": "CustomerNumber",
            "value": "4244"
         },
         {
            "name": "SiteNumber",
            "value": "4244"
         },
         {
            "name": "Remark",
            "value": "Orchestration Test"
         },
         {
            "name": "Latitude",
            "value": "39.632080"
         },
         {
            "name": "Longitude",
            "value": "-104.900376"
         },
     ]
}

7.2.4 Kanban Check In and Check Out

You can use the Kanban Check In and Check Out orchestrations to initiate kanban check-in and check-out transactions in the JD Edwards EnterpriseOne system.

You can use an IoT device to monitor the location of a kanban container or the inventory levels in a kanban container. For example, when a kanban container is removed from the consuming location indicating that it is empty, the IoT Orchestrator processes the data forwarded by the device by using the Kanban Check Out orchestration metadata, and initiates the check-out transaction in the Kanban Processing program (P3157). A kanban check-out transaction creates an order based on the source type and/or updates the kanban status.

Similarly, when replenishment occurs and the container is delivered to the consuming location, the IoT Orchestrator initiates the check-in transaction in the Kanban Processing program. A kanban check-in transaction performs an order completion or receipt and/or a transfer to the consuming location and kanban status update.

Note:

This prebuilt orchestration is designed to support the one-phase kanban transfer method where the completion of the kanban and transfer of inventory are performed concurrently (Kanban Transfer Method in the Kanban Master = 1).

This table includes information that the Kanban Check Out orchestration uses to process IoT data:

Application Invoked Application Version Endpoint URL
Kanban Processing (P3157) ZJDE0001 http://<server>:<host>/jderest/orchestrator/JDE_ORCH_31_KanbanCheckOut

Note:

You must verify the following processing option values for the ZJDE0001 version of the Kanban Processing program:
  • In the Mode tab, the processing option 1. Enter a '1' to set mode to Kanban Supply. If left blank, Kanban Consumption mode is assumed is set to a blank value.

  • In the Mode tab, the processing option 2. Enter a '1' to prompt the confirmation of a transaction is set to a blank value.

This table includes information that the Kanban Check In orchestration uses to process IoT data:

Application Invoked Application Version Endpoint URL
Kanban Processing (P3157) ZJDE0002 http://<server>:<host>/jderest/orchestrator/JDE_ORCH_31_KanbanCheckIn

Note:

You must verify the following processing option values for the ZJDE0002 version of the Kanban Processing program:
  • In the Mode tab, the processing option 1. Enter a '1' to set mode to Kanban Supply. If left blank, Kanban Consumption mode is assumed is set to 1.

  • In the Mode tab, the processing option 2. Enter a '1' to prompt the confirmation of a transaction is set to a blank value.

  • In the Process tab, the processing options 2. Enter a '1' to perform a blind execution of Hours Quantities, 3. Enter a '1' to perform a blind execution of Material Issues, 4. Enter a '1' to perform a blind execution of Work Order Completions, 5. Enter a '1' to perform a blind execution of Shipment Confirmation, and 6. Enter a '1' to perform a blind execution of Inventory Transfers are set to 1 to perform blind executions.

This is an example of an input message defined for the Kanban Check In and Check Out orchestrations:

{
     "inputs": [
         {
            "name": "KanbanID",
            "value": "664"
         },
         {
            "name": "CardNumber",
            "value": "1"
         },
     ]
}

7.2.5 Add Blend Operation

You use the Add Blend Operation orchestration to create a quality operation based on sensor readings. For example, when a sensor indicates that the temperature inside a wine tank has crossed the tolerance level, you can use the Add Blend Operation orchestration to process the sensor readings and trigger the creation of a quality operation in the JD Edwards EnterpriseOne system.

This table includes information that the Add Blend Operation orchestration uses to process IoT data:

Application Invoked Application Version Endpoint URL
Operation Search (P31B94) ZJDE0001 http://<server>:<host>/jderest/orchestrator/JDE_ORCH_31B_AddBlendOperation

This is an example of an input message defined for the Add Blend Operation orchestration:

{
     "inputs": [
         {
            "name": "OperationID",
            "value": "QAV"
         },
         {
            "name": "OperationDescription",
            "value": "Orchestration Test"
         },
         {
            "name": "Winery",
            "value": "W10"
         },
         {
            "name": "VesselNumber",
            "value": "W10-1"
         },
         {
            "name": "TestID",
            "value": "BRIX"
         },
     ]
}