Search Results get_initial_sort_code




Overview
Explore in AI Chat

Overview

APPS.BOM_COMMON_DEFINITIONS is a small PL/SQL package body in the Oracle E-Business Suite Bills of Material (BOM) module. Its role is to centralize and expose a set of common, session-level definition values that are used throughout the BOM feature set. The package does not itself perform complex business logic; rather, it acts as a lightweight access layer over package global variables that are initialized once and then queried repeatedly by other BOM components. By funneling these values through dedicated functions, Oracle ensures that consuming programs obtain a consistent "sort code" and "source system" identifier without duplicating initialization logic or hard-coding constants. The source header identifies the file as BOMCONSB.pls (revision 120.1, dated 2005/08/15), with initial creation dating to 1996, indicating the package has been a stable part of the BOM architecture across many releases. It is classified in the ETRM metadata as an "OTHER" API, meaning it is an internal utility rather than a public, documented integration API.

Key Procedures and Functions

The documented package exposes two functions:

  • GET_INITIAL_SORT_CODE — Returns a VARCHAR2 value that reflects the initial sort code used by the BOM explosion and inquiry processes. This is the function most relevant to the user's search term. It simply returns the package global G_Bom_Init_SortCode, which is established when the package is loaded or initialized. The sort code governs the default ordering applied to exploded bill-of-material component lists.
  • GET_PDH_SRCSYS_CODE — Returns a NUMBER value representing the "PDH" (Product Data Hub) source system identifier. It returns the package global G_BOM_PDH_SRCSYS_ID. This value is used to distinguish records originating from the source system, supporting integration between BOM structures and product data management flows.

Both functions accept no parameters, consistent with their role as simple getters over pre-seeded globals. The entire package body is only 27 lines, underscoring its narrow, utility purpose.

Tables Accessed

The ETRM metadata documents a reference to the APPS synonym for BOM_EXPLOSIONS. In practice, the functions shown in the excerpt do not issue explicit SQL; the association with BOM_EXPLOSIONS arises from the broader context in which the package's global values are derived and consumed, particularly around exploded BOM querying and where-used reporting. The package is best understood as supporting data retrieved from the bill-of-material explosion view rather than directly manipulating it. No inserts, updates, or deletes are associated with the documented functions.

Usage Notes

Because the package is labeled an internal ("OTHER") component and is referenced by 17 other packages, it is typically invoked indirectly rather than called directly by end users. Within Oracle EBS 12.1.1 and 12.2.2, the most probable call paths include BOM inquiry forms, BOM explosion concurrent programs, and the various BOM_* packages that assemble component and where-used data. Custom code that needs to honor the same default sorting applied by standard BOM explosion screens can call GET_INITIAL_SORT_CODE to remain consistent with the delivered behavior, and code integrating with product data management can call GET_PDH_SRCSYS_CODE to obtain the correct source system identifier. Developers should treat the returned values as read-only session settings and should not attempt to use the package to set or persist these values, since no setters are exposed.