Search Results bmlupid_update_item_desc
Overview
BOMPLDCB is a public PL/SQL package owned by the APPS schema in Oracle E-Business Suite. Its name follows the convention used for Bill of Materials (BOM) loading and conversion routines, and its declared procedures confirm that it serves as a programmatic entry point for bulk data operations against the BOM interface tables. The package is defined with AUTHID CURRENT_USER, meaning its SQL statements execute with the privileges of the invoking session rather than the definer, a pattern that allows the calling user's security context to govern access to the underlying BOM objects. The header comment dates the source line to 2005, indicating that the package has been stable across the 11i and R12 releases, including 12.1.1 and 12.2.2.
Functionally, BOMPLDCB supports the BOM open interface workflow: staging records in interface tables, validating and converting them into the base BOM tables, and refreshing descriptive attributes on existing item and structure records. It is classified in the ETRM metadata as API classification OTHER, indicating it is a supporting utility rather than a fully documented public API, and it is not referenced by any other package, so it is normally invoked directly by concurrent programs, forms, or custom extension code.
Key Procedures and Functions
- BMLGGPN_GET_GROUP_NAME — Returns a group name for a supplied group identifier, using an IN OUT buffer for the group name and an error buffer for diagnostic output. It resolves the grouping label used when organizing BOM interface records.
- BMLUPID_UPDATE_ITEM_DESC — Updates the description information associated with a given item within a specified organization. This is the function referenced by the search term
bmlupid_update_item_desc. It accepts the item identifier and organization identifier and returns a status code, writing any failure detail into the error buffer. - BMLDBRT_LOAD_BOM_RTG — Loads bill of material and routing data, accepting an inheritance check flag and returning error message, message name, and table name through IN OUT buffers. It drives the conversion of staged interface rows into the production BOM and routing tables.
All three functions return an integer status, consistent with the standard BOM API convention where zero indicates success and non-zero values indicate warnings or errors.
Tables Accessed
The package reads and writes the full set of BOM interface and base tables. Interface tables include BOM_BILL_OF_MTLS_INTERFACE, BOM_INVENTORY_COMPS_INTERFACE, BOM_OP_ROUTINGS_INTERFACE, BOM_OP_SEQUENCES_INTERFACE, BOM_OP_RESOURCES_INTERFACE, and BOM_REF_DESGS_INTERFACE, which hold staged bill, component, routing, operation, resource, and reference designator rows prior to validation. Base tables such as BOM_INVENTORY_COMPONENTS_S, BOM_OPERATIONAL_ROUTINGS and its _S variant, BOM_OPERATION_SEQUENCES and its _S variant, BOM_OPERATION_RESOURCES, BOM_REFERENCE_DESIGNATORS, BOM_DEPENDENT_DESC_ELEMENTS, and BOM_OPERATIONAL_ROUTINGS receive the validated results. FND_ID_FLEX_STRUCTURES is referenced for key flexfield structure definitions used during validation of item and component segments. Access is through APPS synonyms.
Usage Notes
BMLUPID_UPDATE_ITEM_DESC is typically invoked when item descriptions must be synchronized onto BOM structures or interface rows, for example after an item master update or during a BOM copy or conversion cycle. The other two functions are invoked from the BOM open interface concurrent programs and from the Bill of Materials forms when loading or validating staged data. Because the package is not referenced by other packages and carries the OTHER classification, custom code should call these functions explicitly, always passing a correctly sized error buffer and checking the integer return value before committing. Test any invocation in a non-production environment, since BOM conversion routines write directly to production component and routing tables and are sensitive to concurrent open interface activity.
-
PACKAGE: APPS.BOMPLDCB
12.2.2
-
PACKAGE: APPS.BOMPLDCB
12.1.1
-
PACKAGE: APPS.CTO_UPDATE_BOM_RTG_PK
12.1.1
-
PACKAGE: APPS.CTO_UPDATE_BOM_RTG_PK
12.2.2
-
APPS.CTO_CONFIG_BOM_PK SQL Statements
12.1.1
-
APPS.CTO_CONFIG_BOM_PK SQL Statements
12.2.2
-
PACKAGE: APPS.CTO_CONFIG_BOM_PK
12.2.2
-
PACKAGE: APPS.CTO_CONFIG_BOM_PK
12.1.1
-
PACKAGE BODY: APPS.CTO_CONFIG_BOM_PK
12.1.1
-
APPS.CTO_UPDATE_BOM_RTG_PK SQL Statements
12.1.1
-
PACKAGE BODY: APPS.CTO_CONFIG_BOM_PK
12.2.2
-
APPS.BOMPLDCB SQL Statements
12.2.2
-
APPS.BOMPLDCB SQL Statements
12.1.1
-
APPS.CTO_UPDATE_BOM_RTG_PK SQL Statements
12.2.2
-
APPS.CTO_UPDATE_BOM_RTG_PK dependencies on FND_ID_FLEX_STRUCTURES
12.1.1
-
APPS.CTO_UPDATE_BOM_RTG_PK dependencies on FND_ID_FLEX_STRUCTURES
12.2.2
-
PACKAGE BODY: APPS.BOMPLDCB
12.1.1
-
PACKAGE BODY: APPS.BOMPLDCB
12.2.2
-
APPS.CTO_CONFIG_BOM_PK dependencies on FND_ID_FLEX_STRUCTURES
12.2.2
-
APPS.CTO_CONFIG_BOM_PK dependencies on FND_ID_FLEX_STRUCTURES
12.1.1
-
APPS.CTO_CONFIG_BOM_PK dependencies on CTO_MSG_PUB
12.1.1
-
PACKAGE BODY: APPS.CTO_UPDATE_BOM_RTG_PK
12.1.1
-
APPS.CTO_CONFIG_BOM_PK dependencies on CTO_MSG_PUB
12.2.2
-
PACKAGE BODY: APPS.CTO_UPDATE_BOM_RTG_PK
12.2.2
-
APPS.CTO_CONFIG_BOM_PK dependencies on OE_DEBUG_PUB
12.1.1
-
APPS.CTO_CONFIG_BOM_PK dependencies on OE_DEBUG_PUB
12.2.2
-
APPS.CTO_CONFIG_BOM_PK dependencies on FND_API
12.2.2
-
APPS.CTO_CONFIG_BOM_PK dependencies on FND_API
12.1.1