Results for “invoke_events”
4 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
APPS.BOM_DELETE_GROUPS_API is a PL/SQL package body within the Oracle E-Business Suite Bills of Material module. Its principal responsibility is the programmatic deletion of bill of material groups and related entities, including assemblies, components, alternate designators, and operation sequences. The package encapsulates the complex referential logic required to remove manufacturing structures while preserving transactional and cost integrity across inventory, work in process, and costing subsystems.
In both Release 12.1.1 and 12.2.2, the package is classified as an API and is stored under the APPS schema. The underlying source file is BOMPDELB.pls (version 120.9), originally created in September 2002. Although the package is not documented as a public, user-facing interface in the same manner as certain other BOM APIs, it is referenced internally by other packages and provides the procedural foundation for controlled deletion of bill structures.
Key Procedures and Functions
The documented package exposes two procedures/functions, one of which is DELETE_GROUPS. This is the principal entry point and orchestrates the removal of the requested bill structure according to the parameters supplied by the caller. It validates the target entities, performs the deletion, and returns a status indicating success or a SQL exception condition.
Although the ETRM metadata lists DELETE_GROUPS as the documented procedure, the source excerpt reveals a supporting function named INVOKE_EVENTS. This function is central to the package's integration with Oracle Workflow Business Events. Based on the parameters passed to it—action type, organization, assembly, alternate, item name, description, bill identifier, component identifier, and delete type—INVOKE_EVENTS raises the appropriate business event to notify subscribing applications of the deletion activity. The function returns zero on success or a non-zero value when a SQL exception occurs, and it returns error text through an OUT NOCOPY parameter.
A second supporting function, WRITE_LOG, records diagnostic information to the concurrent manager log. Its inputs include alternate designator, organization name, item name, component name, effective date, operation sequence, and delete type, together with an error text output parameter. This logging behavior supports troubleshooting of failed or partial deletions.
Tables Accessed
The package reads and writes a range of documented tables through APPS synonyms. The primary working tables are BOM_DELETE_ENTITIES, BOM_DELETE_SUB_ENTITIES, BOM_DELETE_SQL_STATEMENTS, and BOM_DELETE_ERRORS, which together form the deletion staging and error-capture framework. BOM_OPERATIONAL_ROUTINGS and BOM_OPERATION_SEQUENCES are accessed to remove routing and operation sequence data associated with deleted assemblies.
Inventory and item master data are referenced through MTL_SYSTEM_ITEMS, while MTL_PARAMETERS supplies organization-level defaults. Transactional and cost records are handled through MTL_MATERIAL_TRANSACTIONS, MTL_TRANSACTION_ACCOUNTS, MTL_TRANSACTION_LOT_NUMBERS, MTL_UNIT_TRANSACTIONS, and WIP_COST_TXN_INTERFACE, ensuring that deletion activity is reflected in inventory and cost interfaces. BOM_PARAMETERS provides module-level configuration, and FND_ORACLE_USERID is used for session or audit identification.
Usage Notes
BOM_DELETE_GROUPS_API is typically invoked from Oracle Forms within the Bills of Material responsibility, from concurrent programs that process mass deletions, or from custom PL/SQL code that must remove bill structures through a supported interface rather than direct DML. Because it is referenced by at least one other package, it may also be called as a subordinate routine during higher-level deletion processes. Developers using the package should account for its business event invocation and log-writing behavior, and should handle the returned status and error text to detect SQL exceptions. In R12.1.1 and R12.2.2 the package remains available under the APPS schema and should be called with the appropriate organization and entity identifiers.