Search Results bom_bill_of_material

Overview

BOM_GLOBALS is a private, utility-oriented PL/SQL package in the Oracle E-Business Suite Bills of Material (BOM) product. Its stated purpose, per the package specification header, is to populate the System Information Record with global data — user identifier, login identifier, program application identifier, program identifier, and related session attributes — that the BOM APIs use when validating a user's access privileges to the business object being processed. The package also maintains a set of operational and status flags (for example, ECO implementation and cancellation indicators) used to set and track the status of a business object and its components. It is not a business-facing API; the annotation @rep:scope private confirms that it is intended for internal consumption by other BOM components rather than direct customer invocation. Its compatibility rating is S (supported) and its lifecycle is active, and it has been present since the initial creation of the BOM server-side global utilities in 1999, with later enhancements for EAM in 2001 and additional accessor functions added in 2003.

Key Procedures and Functions

The documented interface comprises 124 procedures and functions, organized around session state and contextual attributes:

• System Information Record management: INIT_SYSTEM_INFO_REC, GET_SYSTEM_INFORMATION, and SET_SYSTEM_INFORMATION initialize and manage the global record that carries session context.
• Bill sequence context: SET_BILL_SEQUENCE_ID and GET_BILL_SEQUENCE_ID store and retrieve the bill sequence identifier for the structure being processed.
• Entity context: SET_ENTITY and GET_ENTITY manage the current business entity associated with the operation.
• Organization context: SET_ORG_ID and GET_ORG_ID manage the operating unit/inventory organization identifier.
• ECO context: SET_ECO_NAME and GET_ECO_NAME carry the engineering change order name in effect for the transaction.
• User and session identity: SET_USER_ID/GET_USER_ID, SET_LOGIN_ID/GET_LOGIN_ID, SET_PROG_APPID/GET_PROG_APPID, SET_PROG_ID/GET_PROG_ID, and SET_REQUEST_ID establish the identity and concurrent request context used for access checking.

Each setter/getter pair follows a consistent pattern: the setter records a value into the package's global state for the duration of a processing call, and the getter exposes it to downstream logic. This design lets the BOM business logic validate privileges without repeatedly querying session environment views.

Tables Accessed

Through APPS synonyms, the package touches a broad set of BOM and related objects. The primary BOM structures are BOM_STRUCTURES_B, BOM_STRUCTURE_TYPES_B, BOM_COMPONENTS_B, BOM_COMPONENT_OPERATIONS, BOM_COMPONENT_OPERATIONS_S, BOM_INVENTORY_COMPONENTS_S, BOM_REFERENCE_DESIGNATORS, and BOM_SUBSTITUTE_COMPONENTS. Engineering change and lifecycle context draws on ENG_ENGINEERING_CHANGES, ENG_REVISED_ITEMS, ENG_CHANGE_TYPE_PROCESSES, EGO_DATA_LEVEL_B, and EGO_OBJ_TYPE_LIFECYCLES. Metadata and lookup resolution rely on FND_LOOKUP_VALUES and FND_OBJECTS. These reads support access-privilege checks and the resolution of flags controlling ECO implementation, cancellation, and object status transitions.

Usage Notes

BOM_GLOBALS is invoked indirectly. It is referenced by 78 other packages, making it a foundational dependency for the BOM bill-of-material processing stack. Typical invocation occurs when a BOM API, a Bills of Material form, or a concurrent program begins processing — the caller initializes the System Information Record, sets the applicable organization, entity, ECO, and bill sequence context, and then proceeds with the operation, relying on the package's getters for access validation. Custom code should not call this package directly, since its interface is private and its state is scoped to the current database session; customizations should instead use the documented public BOM APIs. Administrators and developers diagnosing bill-of-material issues should treat BOM_GLOBALS as an internal context holder whose values reflect the session state under which the current BOM operation is executing.