Search Results add_icx_session_id




Overview
Explore in AI Chat

Overview

ZX_SECURITY is the row-level security policy package for Oracle E-Business Suite's E-Business Tax (EBTax) module, delivered under the APPS schema as an AUTHID CURRENT_USER definer package. Its header carries the revision marker $Header: zxifdtaccsecpvts.pls 120.11 2008/02/14 19:25:00 appradha ship $, indicating a component of the original EBTax security infrastructure introduced in Release 12. The package supplies the predicate-generating functions that Oracle Virtual Private Database (VPD) policies attach to tax configuration tables, evaluating whether the currently logged-in subscriber — the operating unit, first-party legal entity, or tax regime context established for the session — may read or write a given row.

Because EBTax configuration data (rules, formulas, exception setup, overrides, and subscription details) is partitioned by subscriber, ZX_SECURITY is the mechanism that prevents one operating unit from viewing or modifying another's tax setup. The package exposes global state used by those predicate functions, including G_FIRST_PARTY_ORG_ID, G_EFFECTIVE_DATE, and G_ICX_SESSION_ID, which record the resolved organization, effective date, and ICX session identity for the active security context.

Key Procedures and Functions

The package exposes sixteen documented program units, organized around single-subscriber and multi-subscriber access patterns:

  • GET_EFFECTIVE_DATE — returns the effective date used when evaluating date-effective tax configuration rows.
  • SINGLE_READ_ACCESS — security policy function controlling read access to rules and formula setup data for a single subscriber.
  • SINGLE_READ_ACCESS_FOR_EXCP — controls read access to exception setup data for a single first-party organization.
  • SINGLE_READ_ACCESS_FOR_OVRD — controls read access to tax setup data for a single first-party organization (override scenario).
  • MULTIPLE_READ_ACCESS — controls read access to tax setup data across multiple subscribers.
  • MULTIPLE_READ_ACCESS_FOR_EXCP — controls read access to exception setup data across multiple first-party organizations.
  • WRITE_ACCESS and WRITE_ACCESS_FOR_EXCP — enforce write authorization for setup and exception data respectively.
  • CHECK_WRITE_ACCESS — validation helper used to verify write authority before setup changes are persisted.
  • FIRST_PARTY_ORG_ACCESS — resolves and validates access for the first-party organization associated with the session.
  • SINGLE_REGIME_ACCESS — restricts access to a single tax regime configuration context.
  • ADD_ICX_SESSION_ID — registers the ICX session identifier so that security predicates can be correlated with the originating session.
  • SET_SECURITY_CONTEXT and SET_SECURITY_CONTEXT_UI — establish the global security context (organization, effective date, session) for programmatic and user-interface invocation paths respectively.
  • NAME_VALUE — utility function returning a name/value pair for the security context.

Each read-access function accepts the VPD-standard D1 (object schema) and D2 (object name) arguments and returns a VARCHAR2 predicate fragment.

Tables Accessed

The package references ZX_SUBSCRIPTION_DETAILS through an APPS synonym. This table records which subscribers (operating units and first-party legal entities) are entitled to which tax content; the security predicate functions join against it to derive the allowed organization set for read and write operations. The package also calls DBMS_SESSION, the Oracle-supplied PL/SQL package, to manage session-level context and client identifier settings rather than querying a tax table directly. No other base tables are documented in the ETRM metadata.

Usage Notes

ZX_SECURITY is not invoked directly by end users. It is called by Oracle VPD policy definitions attached to EBTax setup tables, and by the EBTax setup UI (OAF pages and forms) through SET_SECURITY_CONTEXT_UI when a user navigates tax configuration. Concurrent programs and integration interfaces that load or report on tax configuration invoke SET_SECURITY_CONTEXT before touching protected data so that predicates evaluate correctly. The package is referenced by nine other APPS packages, most of which supply the VPD policy handlers and the setup-processing logic layered on top of these predicates. Custom code operating on EBTax configuration tables in a multi-organization environment should likewise initialize the security context rather than bypassing these policies.