Search Results get_prog_id

Overview

BOM_RTG_GLOBALS is a specification-only PL/SQL package (AUTHID CURRENT_USER) in the APPS schema that serves as the shared globals and session-state repository for the Oracle Bills of Material and Engineering routing infrastructure. It was created in August 2000 by Biao Zhang and carries header version 120.1 (last modified 2006/06/14). The package does not implement business transactions itself; rather, it centralizes the constants, record types, and accessor procedures used by the routing APIs, ECO (Engineering Change Order) processing logic, and their dependent packages. Its constants define the operation modes (CREATE, UPDATE, DELETE, LOCK, CANCEL, NONE), record-found flags (F/N), planning types (MODEL, OPTION_CLASS, PLANNING, STANDARD, PRODUCT_FAMILY), routing types (FLOW, STANDARD, LOT), business object identifiers (ECO, BOM, RTG), asset group/activity/rebuildable enumerations, and event/process/line operation codes. It also declares record and table types such as Temp_Op_Rec_Type and Temp_Op_Rec_Tbl_Type for operation sequence/date comparisons, and SYSTEM_INFORMATION_REC_TYPE for session context. Because the routing API family spans many packages, BOM_RTG_GLOBALS enforces a single, consistent definition of these values instead of duplicating literals throughout the codebase.

Key Procedures and Functions

The package exposes 93 documented procedures and functions that fall into two categories: system-information initialisation and typed attribute accessors.

• INIT_SYSTEM_INFO_REC — initialises the system information record used to hold the current session's context before any routing operation.
• GET_SYSTEM_INFORMATION / SET_SYSTEM_INFORMATION — retrieve and populate the composite session-information record.
• SET_ROUTING_SEQUENCE_ID / GET_ROUTING_SEQUENCE_ID — store and return the routing sequence identifier for the operation in progress.
• SET_COMMON_RTG_SEQ_ID / GET_COMMON_RTG_SEQ_ID — manage the common routing sequence identifier shared across ECO or routing operations.
• SET_ENTITY / GET_ENTITY — manage the current business entity (such as ECO, BOM, or RTG) being processed.
• SET_ORG_ID / GET_ORG_ID — hold the inventory organisation context for the current call.
• SET_ECO_NAME / GET_ECO_NAME — store and return the ECO name (engineering change order) associated with the current routing or BOM operation, which is the specific attribute referenced by the user's search.
• SET_USER_ID / GET_USER_ID — maintain the current application user identifier for audit and validation.
• SET_LOGIN_ID / GET_LOGIN_ID — maintain the login identifier of the executing session.
• SET_PROG_APPID / GET_PROG_APPID — hold the application identifier of the calling concurrent program or form.
• SET_PROG_ID / GET_PROG_ID — hold the concurrent program or form identifier for the current invocation.

Tables Accessed

Through APPS synonyms, the package family accesses BOM_OPERATIONAL_ROUTINGS (routing headers and operation sequences), ENG_CHANGE_TYPE_PROCESSES and ENG_ENGINEERING_CHANGES (ECO definition and change-type processing), ENG_REVISED_ITEMS (item revisions affected by ECOs), MTL_SYSTEM_ITEMS (item master validation and context), and PLITBLM (a standard EBS temporary/scratch table used during record processing). The accessor procedures allow callers to program against the ECO name and organisation context without repeatedly querying ENG_ENGINEERING_CHANGES.

Usage Notes

BOM_RTG_GLOBALS is referenced by 35 other packages, making it an internal dependency rather than a customer-callable API (classification OTHER). It is invoked at the start of routing, BOM, and ECO workflows to initialise session state, set the ECO name and organisation context, then read those values back during validation and write logic. Typical entry points include the Engineering Change Order forms, routing maintenance forms, and concurrent programs that create or revise routings. Custom code should treat the package as read-mostly: use the GET_* functions to read context and the SET_* procedures only inside the same session thread, mirroring the pattern used by the standard routing APIs. Because the values are package globals, state is session-scoped and must be re-initialised per invocation.