Six steps to troubleshoot JDE orchestrations
JD Edwards EnterpriseOne Orchestrator was designed with business analysts in mind. The low-code tool makes it easy to integrate data from external tools, systems, and applications with JDE. Yet, troubleshooting orchestrations can be tough.
As an ERP Suites Orchestrator consultant and trainer, I’ve built orchestrations to automate processes, sync data collectors, enable mobility, and more. The more steps in the orchestration, the greater the chance of hitting a roadblock. Here are six steps I picked up along the way to troubleshoot orchestrations and keep data flowing:
Step 1: Make sure all connections are secure.
Internet securities, VPN, and authorizations must be in place to allow the user to connect to the network and appropriate URLs.
Step 2: Check JSON return and AIS logs.
If there is a JDE error, it’s returned in JSON output. Look here to rule out system issues that could be impacting your orchestrations. You can also check the AIS logs in Server Manager for lockouts or AIS errors.
Step 3: Review the JSON input.
Verify the JSON has the correct syntax and name/key values. It’s easy to miss small but crucial components when copying and pasting.
Step 4: Check securities.
Check the user’s Action and View Security if JSON output shows that their ID is missing permissions. Remember, Action Security only allows users to create, modify, and publish. On the other hand, View Security allows access to orchestrations and their parts.
Step 5: Review the manual process and orchestration setup.
Manually enter your process if you aren’t sure what is causing an error. Make sure you mirror the steps used in Orchestrator to verify that the setup and orchestration are correct. Perhaps a required field is missing, or the order of execution is wrong.
Step 6: Check for sub-forms and background automation.
Sub-forms can cause errors because they connect to multiple forms. While automation errors occur if an orchestration is calling an application, form, or version that Orchestrator can’t follow. Remember, Orchestrator can only perform the steps defined in the order of execution.
For example, let’s say a custom program is set up to enter a sales order. It does a background verification call by jumping to another form and back. Then, it allows the user to submit the order. Since the verification check is in the background, the user can’t see it. Neither can Orchestrator.
For more help building and troubleshooting orchestrations, visit erpsuites.com.
2019 winner of the JD Edwards Distinguished Partner Award for Successful Adoption of Orchestrator