Search Results pv_vend_contact_id

Overview

APPS.ICX_SEC is the Oracle E-Business Suite security and session management package used by the Oracle iProcurement and Internet Computing Architecture (ICX) framework. Its primary business function is to establish, validate, and tear down authenticated user sessions in the self-service web tier, and to maintain the associated session context that governs which responsibility, organization, function, and user attributes apply during a given web interaction. The package is classified as OTHER within the ETRM registry for 12.2.2 and is owned by APPS. It is a foundational component: the metadata records that it is referenced by 166 other packages, confirming that session lifecycle handling is a shared service consumed broadly across the EBS web stack. The script header (ICXSESES.pls, version 120.0, dated 2005/10/07) indicates a long-stable implementation that has been carried forward through 12.1.1 and 12.2.2 environments without structural change.

Key Procedures and Functions

The ETRM registry documents 49 procedures and functions, of which the following are named in the excerpt. These are organized by role rather than by call order.

• Session lifecycle: CREATESESSION establishes a new session record; NEWSESSION performs the higher-level creation of a session together with its context; PSEUDOSESSION creates a non-authenticated or provisional session context used for pre-login presentation; VALIDATESESSION, VALIDATESESSIONPRIVATE, and VALIDATEPLUGSESSION verify that an existing session is still valid and authorized for the requested access; DISABLEUSERSESSION terminates an active session; and SETSESSIONPUBLIC / SETSESSIONPRIVATE set the visibility scope of session data.
• Authentication and audit: VALIDATEPASSWORD performs credential verification against the FND_USER repository. WRITEAUDIT records security-relevant events. REMOVECOOKIE clears the client-side session cookie. CREATESESSIONCOOKIE issues the cookie associated with a new session.
• Transaction and context handling: CREATETRANSACTION and REMOVETRANSACTION manage transaction records used to correlate a logical unit of web work. SET_ORG_CONTEXT applies the operating unit (ORG_ID) to the session.
• Attribute and accessor functions: GETID retrieves session attribute values by identifier; PUTSESSIONATTRIBUTEVALUE writes a named attribute into the session store; GETRESPONSIBILITYLIST returns the responsibilities available to the current user; SERVERLEVEL exposes server-level session status information.

The package defines table types (g_char_tbl_type, g_date_tbl_type, g_num_tbl_type) indexed by BINARY_INTEGER for passing collections, and global variables that mirror ICX_SESSIONS columns, including g_session_id, g_responsibility_id, g_org_id, g_function_id, g_function_type, g_language_code, g_date_format, and g_login_id.

Tables Accessed

The package reads and writes session state and security configuration through APPS synonyms.

• Session storage: ICX_SESSIONS holds the master session record; ICX_SESSION_ATTRIBUTES stores per-session key/value attributes; ICX_TRANSACTIONS records transaction correlation data; ICX_SESSION_ATTRIBUTES and ICX_PARAMETERS supply configuration defaults.
• Security and personalization: FND_USER provides user identity and password data; FND_RESP_FUNCTIONS and FND_MENU_ENTRIES resolve responsibility-to-function and menu navigation; FND_FORM_FUNCTIONS supplies function metadata; AK_WEB_USER_SEC_ATTR_VALUES stores web user security attribute values.
• Infrastructure and diagnostics: FND_NODES identifies the application node serving the session; FND_PRODUCT_GROUPS frames the environment; FND_LANGUAGES supports language and NLS resolution; ICX_PAGE_PLUGS maps pages to pluggable regions; ICX_FAILURES and WF_EVENT_T capture failures and raise workflow events.

The constant PV_USER_REQ_TEMPLATE (value 25) is one of a block of session attribute identifiers. It labels the session attribute that carries the user's preferred requirement (requisition) template, alongside PV_USER_REQ_OVERRIDE_REQUESTOR, PV_USER_REQ_OVERRIDE_LOC_FLAG, and PV_USER_REQ_DAYS_NEEDED_BY. These constants allow calling code to read and write those preferences through GETID and PUTSESSIONATTRIBUTEVALUE rather than by hard-coding numbers. Related constants include PV_CUST_CONTACT_ID (7), PV_VEND_CONTACT_ID (8), PV_INT_CONTACT_ID (9), PV_WEB_USER_ID / PV_USER_ID (10), PV_LANGUAGE_CODE (21), PV_DATE_FORMAT (22), PV_SESSION_ID (23), PV_RESPONSIBILITY_ID (24), PV_ORG_ID (29), PV_SESSION_MODE (30), PV_FUNCTION_ID (31), PV_FUNCTION_TYPE (32), and PV_USERNAME / PV_USER_NAME (99).

Usage Notes

ICX_SEC is invoked implicitly by the ICX framework rather than called directly by end users. Typical invocation points include iProcurement and self-service login flows, JSP and Java servlet authentication handlers, and forms that participate in the web session model. Because the package maintains session globals within a database session, callers must be aware of connection pooling behavior in the middle tier: state is scoped to the database session, and stale values can persist if a pooled connection is reused without reinitialization. Custom code extending the framework should reference the PV_* constants instead of literal identifiers to remain compatible across patch levels, and should treat SETSESSIONPUBLIC and SETSESSIONPRIVATE as scope controls that must be balanced. The metadata does not enumerate parameter lists, so integrators should inspect the package specification in the target instance before writing dependent code. Given its 166 dependent packages, any customization should be confined to wrapper code rather than modification of ICX_SEC itself, preserving upgrade safety across 12.1.1 and 12.2.2.