My Oracle Support Banner

WS: 30: P30601 Integrity Analysis Not Reporting Missing F4102 and F41021 Records A9.2.1 and A9.3.1 (Doc ID 1684416.1)

Last updated on JULY 21, 2020

Applies to:

JD Edwards World Product Data Management - Version A9.2 cume 1 to A9.3 cume 1 [Release A9.2 to A9.3]
Information in this document applies to any platform.

Symptoms

Records containing item numbers were erroneously removed from two data files by using a data file utility (DFU) tool. The files affected are the Item Branch File (F4102) and the Item Location File (F41021). The field LLX (low level code) is stored in the Item Branch File (F4102) for each Item Branch record that resides on a BOM (bill of material). To ensure that the LLX code for the Item Branch records is set correctly, JDE recommends running the Integrity Analysis (P30601) program prior to launching a cost roll (P30820/P30835). The LLX assists in determining the physical location of the item within the BOM structure.        

The Integrity Analysis report (R30601) is designed to report situations where short item numbers (ITM) are compared between the Item Master (F4101) and Item Branch (F4102) files, with the Item Branch (F4102) being the predominate file. Currently, the Integrity Analysis report does not print an error message when a component item used in a BOM does not exist in the Item Branch (F4102) file. Additionally, when a primary location record is removed from the Item Location (F41021) file, Integrity Analysis should report that the primary location record is missing.

                                         

Changes

 Integrity Analysis (P30601) is also known as Bill of Material Structure Analysis (P30601).

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.