Search Results get_territory
Overview
FND_REQUEST_INFO is a public PL/SQL package owned by APPS that provides Multi-Lingual Support (MLS) functions with runtime information about the concurrent request currently being executed. Its declared purpose, per the package header comments, is to allow an MLS function to retrieve the concurrent program application short name, the concurrent program short name, and the concurrent request parameters as needed. Because MLS functions execute in the context of a specific concurrent request, the package exposes a controlled set of accessors rather than requiring calling code to query the underlying request tables directly.
The package is declared with AUTHID CURRENT_USER, meaning its SQL statements execute with the privileges of the invoking user rather than the package owner. It is classified as an OTHER API in the ETRM repository, carries an active lifecycle status, and is marked as supported (compatibility S). Its business entity category is FND_CP_REQUEST, and its product is FND. The latest header revision documented is 120.4, dated 2006.
Key Procedures and Functions
- INITIALIZE — Initializes the global variables held by the package for the current request. This routine establishes the session-level context that the remaining accessors depend upon.
- GET_REQUEST_ID — Returns the request ID of the current concurrent request as a number.
- GET_PARAM_INFO — Retrieves the parameter name corresponding to a given parameter number for the request's concurrent program. Returns -1 when the parameter information cannot be retrieved.
- GET_PARAM_NUMBER — Performs the inverse lookup, returning the parameter number for a supplied parameter name.
- GET_PROGRAM — Returns the concurrent program short name associated with the current request, enabling the MLS function to identify which program is executing.
- GET_PARAMETER — Returns the value of a concurrent request parameter, allowing the MLS function to adapt its behaviour based on the arguments supplied by the user at submission time.
- GET_TERRITORY — Returns territory information for the current request. This routine supports implementations that must resolve territory context when translating or formatting request output, and it is the entry point most commonly referenced by users searching for territory-related request metadata.
Both GET_REQUEST_ID and GET_PARAM_INFO carry PRAGMA RESTRICT_REFERENCES declarations of WNDS and WNPS, indicating they do not write database state or package state and can therefore be called from SQL contexts.
Tables Accessed
- FND_APPLICATION — Resolves application short names, supporting the requirement to return the concurrent program's application short name.
- FND_CONCURRENT_PROGRAMS — Supplies concurrent program definition details, including the program short name and parameter definitions used by the parameter lookup routines.
- FND_RUN_REQUESTS — Stores the runtime request record from which the current request ID and parameter values are derived.
Access is performed through APPS synonyms. The package reads FND_APPLICATION and FND_RUN_REQUESTS from the APPS schema and FND_CONCURRENT_PROGRAMS from the FND schema.
Usage Notes
FND_REQUEST_INFO is intended for consumption by MLS functions registered against concurrent programs, but it is equally applicable to any custom PL/SQL executed within a concurrent request. Typical invocation begins with INITIALIZE to populate the session globals, followed by calls to the individual accessors. The package is referenced by ten other packages documented in the ETRM repository, indicating it is embedded in standard Oracle functionality rather than being a standalone utility.
Because all accessors depend on invocation inside a running concurrent request, calling the package from an interactive Forms session or from outside the concurrent manager is not supported. The GET_TERRITORY routine in particular should be invoked only after INITIALIZE has completed, and its result should be validated before being used to drive territory-specific logic. The -1 return convention on GET_PARAM_INFO means callers must explicitly test for failure rather than assuming a valid value.
-
PACKAGE: APPS.FND_REQUEST_INFO
12.2.2
-
PACKAGE: APPS.FND_REQUEST_INFO
12.1.1
-
PACKAGE: APPS.ARPT_SQL_FUNC_UTIL
12.1.1
-
PACKAGE: APPS.ARPT_SQL_FUNC_UTIL
12.2.2
-
PACKAGE BODY: APPS.FND_REQUEST_INFO
12.1.1
-
PACKAGE BODY: APPS.FND_REQUEST_INFO
12.2.2
-
APPS.ORACLEAPPS dependencies on V$NLS_VALID_VALUES
12.1.1
-
APPS.ORACLEAPPS dependencies on FND_TERRITORIES_VL
12.2.2
-
APPS.ORACLEAPPS dependencies on V$NLS_VALID_VALUES
12.2.2
-
APPS.ORACLEAPPS dependencies on FND_TERRITORIES_VL
12.1.1
-
APPS.ARPT_SQL_FUNC_UTIL dependencies on FND_TERRITORIES_VL
12.1.1
-
APPS.ORACLEAPPS dependencies on FND_DM_NODES
12.1.1
-
APPS.ORACLEAPPS dependencies on FND_DM_NODES
12.2.2
-
APPS.ARPT_SQL_FUNC_UTIL dependencies on FND_TERRITORIES_VL
12.2.2
-
PACKAGE BODY: APPS.ARPT_SQL_FUNC_UTIL
12.1.1
-
PACKAGE BODY: APPS.ARPT_SQL_FUNC_UTIL
12.2.2
-
APPS.ARPT_SQL_FUNC_UTIL dependencies on RA_CUSTOMER_TRX
12.2.2
-
APPS.ARPT_SQL_FUNC_UTIL dependencies on RA_CUSTOMER_TRX
12.1.1
-
PACKAGE BODY: APPS.ORACLEAPPS
12.2.2
-
PACKAGE BODY: APPS.ORACLEAPPS
12.1.1
-
APPS.ORACLEAPPS dependencies on HTP
12.1.1
-
APPS.ORACLEAPPS dependencies on HTP
12.2.2