My Oracle Support Banner

E1: ORCH: Exception in Orchestration Output When Using Form Request Row Filtering in the Grid for a Date Column (Doc ID 2973792.1)

Last updated on JANUARY 18, 2024

Applies to:

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

Symptoms

When attempting to run an orchestration based on a form request which uses the "Filter" option for the non-QBE (Query By Example) columns for grid, the following exception occurs if the filter is for a date column.

It is observed that the input string appearing in the output corresponds to the Epoch Unix Timestamp for the date value in the first row in the grid. For example, "1693958400000" appearing in the above output is "Wed Sep 06 2023 00:00:00 GMT+0000".

Steps to replicate:

  1. Login to the orchestrator studio
  2. Create a form request with the below steps:

    - P4106|W4106J (Work With Preference Base Price) - Filter for an Item Number (eg: 210) and Branch Plant (30), click Find
    - Select the first grid record and click Select
    - P4106|W4106K (Base Price Revisions) - Select Update Row Filter check box and click on the icon under Input column
    - In the pop-up screen, setup a filter for "Eff Date Thru" and close it
    - Set "Eff Date Thru" with the new required value
    - Click OK
    - P4106|W4106J (Work With Preference Base Price) - Click Close

  3. Add the above form request to an Orchestration and run the orchestration

Changes

Updated the tools release to 9.2.7.3 or above.

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.