Search Results entity_attribute_defaulting

Overview

BOM_DEFAULT_RTG_REVISION is an Oracle EBS Bills of Material (BOM) package body owned by the APPS schema that provides attribute defaulting services for routing revision records. Within the EBS 12.1.1 and 12.2.2 codebases the package is responsible for translating the sentinel value FND_API.G_MISS_CHAR into meaningful defaults, or NULL, before a routing revision record is validated and persisted. The source header, BOMDRRVB.pls (version 115.3, last shipped 2002/11/21), identifies the body as the implementation of package BOM_Default_Rtg_Revision, with an initial creation date of 07-AUG-00. The functionality is significant to users who searched on "entity_attribute_defaulting" because the package encapsulates the descriptive flexfield attribute handling for routing revisions, a classic example of the attribute defaulting pattern used across the EBS public APIs.

Key Procedures and Functions

• ATTRIBUTE_DEFAULTING — Applies defaulting logic to the descriptive attribute columns of a routing revision record. It exists so that callers can pass partially populated records and have the remaining attributes resolved to a consistent state.
• ENTITY_ATTRIBUTE_DEFAULTING — The entity-level counterpart to ATTRIBUTE_DEFAULTING. This procedure coordinates defaulting across the full routing revision entity rather than a single attribute, matching the naming convention used by the "entity_attribute_defaulting" search term.
• POPULATE_NULL_COLUMNS — Normalizes columns received as FND_API.G_MISS_CHAR into NULL or other appropriate values. The visible excerpt of BOMDRRVB.pls demonstrates this behavior in the private helper Get_Flex_Rtg_revision, which copies the incoming record and converts G_MISS_CHAR values in attribute_category and attribute2 through attribute9 to NULL.

Parameter lists are not documented in the available metadata and should be confirmed against the deployed package specification in the target instance.

Tables Accessed

No tables are documented as referenced through APPS synonyms in the ETRM metadata. The logic observed in the source excerpt operates purely on the in-memory record types Bom_Rtg_Pub.Rtg_Revision_Rec_Type; no DML against BOM_ROUTING_REVISIONS or the descriptive flexfield tables is evidenced by the documented procedures. Persistence is therefore the responsibility of the calling public API, not of this defaulting package.

Usage Notes

The package sits in the supporting layer beneath Bom_Rtg_Pub and is invoked during routing revision creation and update flows. Typical callers are BOM public API routines, Oracle Forms based routing maintenance screens, and custom integrations that build a Rtg_Revision_Rec_Type, pass it through BOM_Default_Rtg_Revision for attribute normalization, and then hand the resulting record to the public API for validation and commit. The ETRM metadata records that the package is referenced by one other package, which reinforces its role as a utility consumed by a peer API rather than a standalone entry point. Custom code should call the public API rather than invoke BOM_Default_Rtg_Revision directly, since the defaulting logic is internal to the BOM transaction model.