E1: ORCH: While Running an Orchestration the Nested Iterating Steps, That is After a Rule Doesn't Update the Status for All Lines.
(Doc ID 2767225.1)
Last updated on DECEMBER 27, 2022
Applies to:
JD Edwards EnterpriseOne Orchestrator - Version 9.2 and laterInformation in this document applies to any platform.
Symptoms
When running the orchestration, After the rule the nested iterate over steps fails to update the status for all the detail lines.
Example: If an Order that meets the status of 222-225, it will get the Log record type "R", Status "N" from the F4305 and update the status of the Log record
to a "Y". The Rule checks to see if a record count is 1 to found a record before following the True path in the Flow. It then performs a Data Request of F4311 to get the detail lines and will update the lines to a Status 225 - 400. When running the Orchestration, only one line gets updates to the status, which means Iterate Over fails update on the F4311. If the rule is removed and execute the orchestration then both lines get the status updated.
Changes
Upgraded tools release to 9.2.5.1
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 |