My Oracle Support Banner

E1: 31: EDSP flag is back from Y to N by R31113Z1I (Doc ID 2590294.1)

Last updated on SEPTEMBER 19, 2019

Applies to:

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

Symptoms


ACTUAL BEHAVIOR
----------------------

R31113Z1I updates transaction processing flag; EDSP from Y to N. Next

execution of R31113Z1I updates the EDSP from N to Y and creates IM transaction in Item Ledger and issued inventory. It causes unexpected over issue.


EXPECTED BEHAVIOR
-----------------------
EDSP=Y should not be updated to N unexpectedly.



STEPS
-----------------------
The issue can be reproduced at will with the following steps:

 

1.Add 3 work orders and attach parts list (P48013). All 3 work order headers are same.

For WO#1 and #2, component A is in component line (CPNB) #1.00. And component B is in component line (CPNB) #2.00

For WO#3, component B is in first component line. Next is component A.

2.Populate data in F3111Z1. To create ERROR (EDSP=N) records, populate wrong short item number in WO#1/Line#2, WO#2/Line#2 and WO#3/Line#1 that have component B. Other lines have correct data processed.

3.Run R31113Z1I.

Data selection:

Type-Transaction(F3111Z1.TYTN) is equal to JDEII

Direction Indicator (F3111Z1.DRIN) is equal to 1

EDI-Successfully Processed (F3111Z1.EDSP) is not equal to Y

EDI-User ID (F3111Z1.EDUS) is equal to xxxxx

4.Check F3111Z1.

EDSP of WO#1/Line#2, WO#2/Line#2 and WO#3/Line#1 are N. Other 3 lines (WO#1/Line#1, WO#2/Line#1 and WO#3/Line#2)have Y in EDSP. R31113Z1I works correctly.

5.Run R31113Z1I again without any changes.

6.In PDF report; R31113Z1I, errors occur for 3 lines; WO#1/Line#2, WO#2/Line#2 and WO#3/Line#1. This is correct.

7.Check F3111Z1. EDSP in WO#2/Line#1 is updated from Y to N. This is the issue. EDSP should not be updated from Y to N.

8.Run R31113Z1I again without any changes. EDSP in WO#2/Line#1 is updated from N to Y. And also IM record is added in Item Ledger (F4111). It means unexpected over-issue.

 

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
The issue causes over issues and incorrect on hand inventory information.

POTENTIAL WORKAROUNDS

------------------------------

No workaround

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.