Search Results lookup_code_fk

Overview

EDW_LOOKUP_PKG is an Oracle E-Business Suite PL/SQL package owned by the APPS schema and classified under the ETRM registry as an "OTHER" API type. Its name associates it with the Enterprise Data Warehouse (EDW) layer of EBS, where PL/SQL packages prefixed with EDW are used to resolve and standardise reference data before it is presented to downstream reporting and analytics objects. In practice, the package serves as a centralised lookup resolution utility: it abstracts the mechanics of retrieving codes and meanings from EBS lookup types so that consuming packages do not embed their own decoding logic. Status is documented as VALID, confirming the package compiles cleanly and is available at runtime.

The user search term "opi_edw_cogs_fcv" is directly relevant here. OPI_EDW_COGS_FCV is one of five documented dependents of EDW_LOOKUP_PKG, indicating that the COGS (Cost of Goods Sold) fact collection view relies on this package for lookup translation.

Key Procedures and Functions

The ETRM documentation records two procedures or functions for this package, of which the named member is LOOKUP_CODE_FK. The "FK" suffix conventionally denotes a foreign-key style resolver, and the naming pattern indicates the routine accepts a lookup type and lookup code and returns the corresponding decoded value or surrogate key. A second documented member exists but is not individually named in the available excerpt; its existence indicates the package exposes at least one companion utility alongside LOOKUP_CODE_FK.

It must be emphasised that the ETRM metadata does not publish parameter lists, return types, or datatype signatures for these members. Consequently, no parameter signature is asserted here. Consumers should inspect the package source directly, or query ALL_ARGUMENTS filtered on package_name = 'EDW_LOOKUP_PKG', before invoking any member from custom code.

Tables Accessed

The ETRM metadata records no tables referenced via APPS synonyms for EDW_LOOKUP_PKG. This is a notable characteristic. When a PL/SQL unit lists no synonym-based table dependencies, the routine commonly operates purely on its input arguments, on PL/SQL constructs such as collections or records, or on SYS-owned dictionary views and STANDARD-supplied built-ins. The documented dependency list explicitly names SYS and STANDARD, which corroborates this: SYS provides the data dictionary infrastructure, while STANDARD provides the base PL/SQL environment functions. Any underlying lookup table access may therefore occur indirectly, for example through an intermediate view or a dynamically referenced object not surfaced in the dependency listing.

Usage Notes

EDW_LOOKUP_PKG is referenced by five packages, all of which are EDW fact collection views (FCVs): OPI_EDW_COGS_FCV, POABV_EDW_RECEIVING_TXN_FCV, POABV_EDW_SUPPLIER_PERFORM_FCV, POA_EDW_RECEIVING_TXN_FCV, and POA_EDW_SUPPLIER_PERFORM_FCV. It is also referenced by itself, indicating internal recursive calls between its own members.

Typical invocation is therefore not from an Oracle Forms screen or a standard concurrent program, but from within the PL/SQL bodies of these EDW collection views during data extraction, transformation, and load processing. Analysts querying or customising OPI_EDW_COGS_FCV, or the supplier performance and receiving transaction FCVs, will encounter this package one level beneath the surface. Because the package is an internal EDW utility rather than a supported public API, customer extensions should avoid direct dependency on its members; instead, replicate the lookup resolution logic locally or use supported public lookup APIs, so that future EBS patching does not break custom code.