My Oracle Support Banner

P2 Item Attribute Sets Default Value On Subclass Where Not-visible, Displays Value In P2 Read-thru (Doc ID 2982303.1)

Last updated on OCTOBER 27, 2023

Applies to:

Oracle Agile Product Collaboration - Version and later
Information in this document applies to any platform.


On : RUP 19 version, Administration/Configuration

P2 Item attribute still get default value set in the subclass that has that attribute set to invisible.

A page two list attribute defined on items. It is configured with a default list value. The field is set visible at the class level. The field is visible on one subclass and not visible on another subclass. The field is displayed as a read-through field on the BOM. The problem is that for the subclass where the field is not visible the default value is showing through on the BOM tab Page Two read through field.

Part Class has field enabled and is set to use a default value (List13). The field is configured as a read-through field on the BOM tab.
Part subclass A has the field as visible
Part subclass B has the field as not visible.
In an Assembly that has Part subclass A and Part subclass B. On the BOM tab of the assembly the read-through field is showing the default value.

The expectation is that no value is displayed in the read-through field for Part subclass B




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

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