E1: 30A: R30812 / P30206 to Use F4105 Costs if There Are no Existing BOMs for a Manufactured Parent (Doc ID 2105751.1)

Last updated on FEBRUARY 11, 2016

Applies to:

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

Symptoms

For a stocking type "M" item, R30812 is using BOM to roll up the costs for top parent mfg item and for stocking type "P", it uses the F4105 cost.

However, for two level BOM structure:
- Item A is the top parent, level 1 (stocking type "M"), having a BOM defined
- Item B is a component for item A, level 2 (stocking type 'M'), NOT having a BOM defined yet but having a 07 Cost in F4105.
When Simulate is run over item A, the costed bill inquiry screen shows item B with zero cost due to missing BOM record. Why is this happening? The expectation was that if a BOM is not defined for the sub-assembly, then the Simulate Roll-up UBE to consider the F4105 07 costs (different than zero).

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms