My Oracle Support Banner

E1: 41: Implication of Bug 25920841/25913248 - Changes Foreign Key in F4111.JELN (Doc ID 2402413.1)

Last updated on JULY 18, 2018

Applies to:

JD Edwards EnterpriseOne Inventory Management - Version 9.1 and later
Information in this document applies to any platform.

Purpose

 

This document describes the implication of <Bug 25920841> - P4112 IS NOT PROPERLY RECORDING JELN IN F4111 WHEN ISSUING MULTIPLE LINES and <Bug 25913248>: P4112 IS NOT PROPERLY RECORDING JELN IN F4111 WHEN ISSUING MULTIPLE LINES in EnterpriseOne Application Release 9.1 and 9.2. 

The application of this Bug will change the way it sets F4111.JELN (Item Ledger. Journal Entry Line Number).

 

Supposing that there is a single line of F4111, the JELN gets assigned as below,

P4112 - Inventory Issue
    |--- F4114EditLine
           |--- F4111EditLine
                  |--- 1. Get Account on DMAAI 4122
                  |--- 1. F0911FSEditLine > Assign JELN 1.0 for F0911
                  |--- 2. Get Account on DMAAI 4124
                  |--- 2. F0911FSEditLine > Assign JELN 2.0 for F0911
                  |--- 3. Assign JELN for F4111 based on actual JELN assigned to F0911
                           * Before this bug: F4111.JELN = 1.0, 3.0, 5.0, and so forth (Odd Numbers).
                           * After this bug: F4111.JELN = 2.0, 4.0, 6.0, and so on (Even Numbers).

Note:

  • Across document, the data dictionary alias JELN is used to describe Journal Entry Line Number. JELN in F0911 is a member of the primary key of F0911, and JELN in F4111 is a member of Foreign Key. This foreign key is used to read data from F0911
  • The bug in this document, synchronize the account information between F4111 and F0911 where the relationship between F4111 to F0911 is 1 : 2, or 1 : 4
  • There no standard option to correct F4111.JELN
  • This bug affects both P4112 and XT4111Z1
    • After: P4112 does not add ( F4111.JELN + 1 ) to get corresponding cost object from F0911 and XT4111Z1 assigns F4111.JELN the last JELN of F0911

 

Troubleshooting Steps

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
Purpose
Troubleshooting Steps
 DMAAI settings
 Representation in P4112 (Inventory Issue)
 Data Representation from F4111
 Data representation from F0911 - No change
 Reversal Inventory Issue when
 Workaround
 Summary
References


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