Search Results p_group_to




Overview
Explore in AI Chat

Overview

APPS.BOM_BOMRDDEL_XMLP_PKG is the generated PL/SQL package body that backs the Oracle EBS concurrent program "Delete Bill of Material and Routing" (short name BOMRDDEL). The package embodies the report logic for a mass-deletion utility that removes Bill of Material (BOM) and routing records recorded in the Delete Group and Delete Entity staging tables. Its principal business function is to accept user-supplied selection criteria at the concurrent program parameter screen — such as delete group ranges, delete entity statuses, and object type flags — and translate those criteria into dynamic SQL WHERE-clause fragments that filter the deletion set. In Oracle EBS 12.1.1 and 12.2.2, the package follows the standard Oracle Reports XML Publisher (XMLP) wrapper pattern: report-level trigger logic is exposed as package functions invoked by the report, while the actual data selection is parameterised through helper functions that return VARCHAR2 predicate strings. The package is generated and owned by APPS and is classified as OTHER in the ETRM repository, indicating it is not a public API but an internal support unit.

Key Procedures and Functions

  • BEFOREREPORT — Retains the concurrent request identifier from FND_GLOBAL.CONC_REQUEST_ID and performs standard report initialisation before data retrieval. The historical FND SRWINIT user exit call is commented out, reflecting the XMLP architecture.
  • AFTERREPORT — Terminates report execution cleanly. In this package it simply returns TRUE.
  • WHERE_GROUP — Builds the predicate restricting the deletion set to a range of delete group names. It handles three cases: both FROM and TO supplied (BETWEEN), only FROM (LIKE), only TO (LIKE), or neither (no predicate).
  • WHERE_TYPE — Constructs the DELETE_TYPE IN (...) predicate. Each BOM/routing object category (item, bill, routing, component, operation, bill reference, item bill reference) is mapped to a numeric type code when its corresponding parameter flag equals 1; otherwise the code resolves to 0 and the category is excluded.
  • WHERE_TYPE1 — A companion type-filter function, typically used elsewhere in the report layout where a second, independently parameterised type clause is required.
  • WHERE_ENTITY_STATUS — Generates the predicate for the delete-entity status filter applied to the primary entity records.
  • WHERE_SUB_ENTITY_STATUS — Generates the equivalent status predicate for subordinate (sub-entity) records, allowing distinct status treatment across parent and child rows.
  • BEFOREPFORM — Pre-form trigger logic executed before the main report body is formatted.
  • C_ENG_FLAG_WHEREFORMULA — A computed/format-trigger helper that exposes the engineering-change flag predicate for formula columns in the report template.
  • GET_MESSAGE, GET_MESSAGE2, GET_MESSAGE3 — Retrieve predefined message text, generally used to populate warning or informational output embedded in the report body.

Tables Accessed

The ETRM metadata does not enumerate base tables directly, but the generated predicates reference the alias bdg, which corresponds to the delete-group staging table (BOM_DELETE_GROUPS). Predicates such as bdg.DELETE_GROUP_NAME and bdg.DELETE_TYPE confirm that the package filters this staging table. Related delete-entity records (BOM_DELETE_ENTITIES) supply the status columns filtered by WHERE_ENTITY_STATUS and WHERE_SUB_ENTITY_STATUS. The package reads these staging tables to isolate the records the deletion process will later purge; it does not itself perform the destructive delete, which is handled by the underlying concurrent program and its associated logic.

Usage Notes

This package is invoked exclusively through the BOMRDDEL concurrent program. When a user submits the program, the Oracle Reports runtime calls BEFOREREPORT, evaluates the WHERE_* functions to assemble the dynamic SQL predicate, formats the report via BEFOREPFORM, extracts messages through the GET_MESSAGE family, and finalises with AFTERREPORT. The BR_TYPE variable referenced in WHERE_TYPE corresponds to the bill-reference category (P_BR_FLAG), one of the seven object classes the deletion utility can target. Because the package body is generated and classified as OTHER, it must not be called directly from custom code; customisations should instead wrap the concurrent program submission or use supported BOM APIs. Users investigating the "br_type" search term should note it is an internal local variable used solely to translate the bill-reference parameter flag into the numeric DELETE_TYPE code 6 within the DELETE_TYPE IN (...) clause produced by WHERE_TYPE.