My Oracle Support Banner

E1: ORCH: Orchestration Doesn't Throw Error When There Is an Error in E1 Application. (Doc ID 2732493.1)

Last updated on JULY 14, 2021

Applies to:

JD Edwards EnterpriseOne Orchestrator - Version 9.2 and later
Information in this document applies to any platform.

Symptoms

Symptom 1:  P03B102 with an invalid Doc Number

 

When processing Receipts using P03B102, if the Doc number is invalid, then it throws "No Grid Record Selected" error.  However, orchestration processes without a valid doc number even though it is set to "Abort on Error".


E1 application Flow:

P03B102->Add->OK (Batch Control)->CO(00001) and Payor(4242)->From::Select->Enter and invalid Doc Number

Row Exit ::Select/Deselect

Error:





Symptom 2:  P4310:  Enter an invalid "Cost Center/Business Unit"  for a line item.  If you have only 1 line, there is no error.  If you have 2 lines, then error is thrown. 

 

A single line failed (no error):

Input: 

 

 

 

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
 Symptom 1:  P03B102 with an invalid Doc Number
 Symptom 2:  P4310:  Enter an invalid "Cost Center/Business Unit"  for a line item.  If you have only 1 line, there is no error.  If you have 2 lines, then error is thrown. 
Changes
Cause
Solution


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