My Oracle Support Banner

E1: ORCH: Orchestrator Monitor Skips Records For Orchestrations Called Via REST APIs If the Environment Name is Passed in Lower Case (Doc ID 2995751.1)

Last updated on JANUARY 05, 2024

Applies to:

JD Edwards EnterpriseOne Tools - Version 9.2 to 9.2 [Release 9.2]
Information in this document applies to any platform.

Symptoms

If we use REST APIs to call a JDE Orchestration, it is possible that the environment name is passed in Lower/Small case letters. This does not affect the execution of orchestration. However, for such calls the entries in F980060 OR  F980061 OR F980062 tables also record the environment name in lower case. This creates problem in Orchestrator Monitor when trying to filter the records based on environment name. If we try to search records in orchestrator monitor using search criteria environment in lower case e.g  'jps920', the records do not appear in the monitor. The orchestrator monitor application will only show records that have environment value in uppercase only, irrespective of whether we search for 'jps920' or 'JPS920'. In both the scenarios, only JPS920 records appear and jps920 are filtered out. It is not possible to find records which were submitted with lower case environment.

This issue may be replicated using the steps below:

  1. Use postman to call an orchestration and pass the environment name in small case.
  2. Notice that call is successful.
  3. Open orchestrator monitor through E1 Page Navigation or Type P980060X in fast path.
  4. Enter search criteria so that environment name is in small case.
  5. Notice the record with small case environment name is not displayed.
  6. Run the same orchestration using postman but the environment name in upper case.
  7. Open Orchestrator monitor again and filter using upper case environment. Notice the record due to step 6 appears in the result .
  8. Try to filter again using small case environment name. Notice that only record with upper case environment name (Step 6) appears in result and record due to step 1 is filtered out ( does not appear in result).

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.