Results for “get_context_value”
36 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
FF_ARCHIVE_UTILS is an Oracle E-Business Suite PL/SQL package owned by the APPS schema. Its header identifies the source file as ffarcutl.pkh and the initial version as 115.0, created on 11-JUN-2002 by author "pganguly." It is declared with AUTHID CURRENT_USER, meaning its SQL statements execute under the privileges of the invoking user rather than the package owner, which is consistent with a utility package intended to be called from a wide range of application and custom contexts.
The package occupies an unusual position in the EBS architecture. Despite its name, which suggests a role in archive or purge processing, the three documented functions are entirely concerned with resolving org context and legislation information. In the Oracle EBS 11i/12.1.1/12.2.2 lineage, the "FF" prefix denotes the Financials family of products, and this package serves as a lightweight resolver that bridges a business group identifier to a legislation code and normalizes context values used by globalization and jurisdiction logic. It is classified in the ETRM 12.2.2 metadata as API classification OTHER, reflecting that it is a supporting utility rather than a public, commit-bearing business API.
Key Procedures and Functions
The package exposes three documented functions, all declared in the package specification:
- GET_CONTEXT_VALUE — Accepts a legislation code, a context name, and a context value, and returns a VARCHAR2. It resolves a specific context value within the framework of the specified legislation, effectively performing a lookup against the context definitions used by the Financials product family.
- GET_LEGISLATION_CODE — Accepts a business group identifier and returns the corresponding legislation code as a VARCHAR2. This is the most commonly referenced function, because business group to legislation mapping is a prerequisite for nearly all globalization-aware processing in Oracle Financials.
- US_JURISDICTION_CODE — Accepts a context value and returns a jurisdiction code. It is the single legislation-specific helper in the package, scoped to United States jurisdiction determination.
The ETRM metadata does not document parameter defaults or return semantics beyond the types above, so callers should treat all three as deterministic lookups with VARCHAR2 returns.
Tables Accessed
The documented table reference for this package is DBMS_SQL accessed through APPS synonyms. This is significant: rather than relying on a fixed set of base tables, FF_ARCHIVE_UTILS performs dynamic SQL construction and execution via the DBMS_SQL built-in. This design permits the package to resolve context and legislation values against tables whose names are determined at runtime, which is typical of globalization utilities that must address legislation-specific or context-specific structures without hard-coding object names. Because no conventional base tables are documented, the package should be regarded as a metadata-driven resolver rather than a data-maintenance package.
Usage Notes
FF_ARCHIVE_UTILS is referenced by one other documented package, indicating that it is an internal dependency of the Financials stack rather than a directly exposed user-facing component. In practice, calls to GET_LEGISLATION_CODE originate from forms-based logic and concurrent programs that must determine the legal environment of a business group before applying jurisdiction-sensitive rules. GET_CONTEXT_VALUE and US_JURISDICTION_CODE are typically reached indirectly, through the dependent package, as part of context resolution during fiscal and statutory processing. Custom code that requires the legislation code for a business group may call the function directly, but should account for the AUTHID CURRENT_USER declaration: the invoking schema must hold the necessary privileges on the underlying objects and on DBMS_SQL itself. Because the package performs dynamic SQL, integrators should also expect a compilation and execution cost profile heavier than that of simple static lookups. As a legacy utility shipped in the 11i code line and retained through 12.1.1 and 12.2.2, it carries no documented public API guarantees; it is best invoked through the Oracle-maintained packages that already depend on it.
-
PACKAGE BODY: APPS.HR_COST 12.2.2
-
PACKAGE BODY: APPS.HR_COST 12.1.1
-
PACKAGE: APPS.HR_COST 12.2.2
-
PACKAGE: APPS.HR_COST 12.1.1
-
PACKAGE: APPS.HR_COST 12.2.2
-
PACKAGE: APPS.HR_COST 12.1.1
-
PACKAGE BODY: APPS.HR_COST 12.2.2
-
PACKAGE BODY: APPS.HR_COST 12.1.1