Search Results set_apps_context

Overview

JTF_EBI_UTIL is a utility package owned by APPS in the Oracle E-Business Suite, classified under the UTIL API category within ETRM. Its primary responsibility is to establish a valid Oracle EBS runtime session context for external or embedded callers that do not already inherit an FND session. In practice, this package bridges the gap between a plain database connection and the fully initialized environment required by Oracle Application Framework (OAF), EBI (Enterprise Business Intelligence) publisher integrations, and other programmatic entry points that must operate under a specific EBS user, responsibility, and security group.

The header comment ($Header: JTFEIUTB.pls 120.1 2011/03/23 16:48:53 agunnam noship $) confirms the file is a nonshipped (noship) PL/SQL library, meaning it is delivered or applied outside the standard product shipping manifest. Despite this, the package remains part of the APPS schema and is referenced by at least one other package, indicating its use in supported integration flows.

Key Procedures and Functions

• SET_APPS_CONTEXT — The central procedure and the object most frequently associated with the search term "set_apps_context." It accepts a user name and a responsibility name, resolves the corresponding USER_ID, RESPONSIBILITY_ID, RESPONSIBILITY_APPLICATION_ID, and SECURITY_GROUP_ID, and then calls FND_GLOBAL.APPS_INITIALIZE to populate the FND global context. It also declares local variables for language, language code, date format, date language, numeric characters, NLS sort, NLS territory, limit time, limit connects, organization ID, and timeout, reflecting a typical profile-option initialization pattern. The user/responsibility lookup is wrapped in an exception handler that suppresses errors, so the procedure fails silently if the values cannot be resolved.
• IS_RESOURCE_ERROR_EXISTS — A validation function that inspects resource-related interface data to determine whether error records are present. It is used in conjunction with the JTF resource interface tables to gate downstream processing.
• IS_SALESREP_ERROR_EXISTS — A parallel validation function for sales representative interface data, returning whether salesrep-level errors exist. Both functions support error-checking before commit or reprocessing.

Tables Accessed

• FND_USER — Source of USER_ID resolution from the supplied user name.
• FND_RESPONSIBILITY_TL — Provides RESPONSIBILITY_ID and APPLICATION_ID from the responsibility name.
• FND_USER_RESP_GROUPS — Supplies the SECURITY_GROUP_ID tied to the user/responsibility pairing (referenced as FND_USER_RESP_GROUPS via the FURG alias).
• FND_PROFILE_OPTION_VALUES — Source of NLS, date, language, and numeric profile values loaded during context setup.
• JTF_RS_RESOURCE_EXTNS_INT and JTF_RS_SALESREPS_INT — Interface tables examined by IS_RESOURCE_ERROR_EXISTS and IS_SALESREP_ERROR_EXISTS to detect error rows.

Usage Notes

SET_APPS_CONTEXT is typically invoked from custom concurrent programs, OAF extensions, BPEL/EBI callers, or standalone PL/SQL that connects to the APPS schema without an initialized session. Calling it before any FND-dependent API ensures that FND_GLOBAL values are populated and that profile options resolve correctly. Because the user/responsibility lookup uses UPPER() comparisons and silently swallows lookup failures, callers should verify FND_GLOBAL.USER_ID after invocation. The IS_*_ERROR_EXISTS functions are used within resource and salesrep import/validation routines to decide whether error handling is required prior to commit. As a noship utility, JTF_EBI_UTIL should be treated as an internal helper rather than a supported public API, and customizations should avoid modifying its body.