Search Results g_first_party_org_id




Overview

ZX_SECURITY is the PL/SQL security enforcement package for the Oracle E-Business Tax (EBTax) module within Oracle EBS 12.1.1 and 12.2.2. Its principal business function is to implement and enforce first-party organization security policies that govern read and write access to tax configuration data — including tax rules, formulas, subscriptions, and exception records. The package operates as a supporting security layer behind Oracle Virtual Private Database (VPD) or Application Context mechanisms, returning predicate strings that restrict visibility of rows in EBTax setup tables according to the currently established security context.

A central element of its design is the runtime session context. Security predicates reference values exposed through SYS_CONTEXT('my_ctx', ...), notably EFFECTIVEDATE and FIRSTPTYORGID. The package therefore provides both the functions that generate access predicates and the routines that populate that session context before EBTax queries execute.

Key Procedures and Functions

The package exposes sixteen documented procedures and functions, grouped by purpose:

The documented source excerpt confirms SINGLE_READ_ACCESS builds a predicate comparing (content_owner_id, tax_regime_code) against ZX_SUBSCRIPTION_DETAILS rows where view options are NONE, VFC, or VFR, filtered by the effective date and the session's first-party organization identifier.

Tables Accessed

Two tables are documented as referenced through APPS synonyms:

  • ZX_SUBSCRIPTION_DETAILS — the primary source for security filtering. It links first-party organizations to tax regimes and subscription view options, and supplies the parent organization and regime values against which access predicates are matched.
  • DBMS_SESSION — used to set and manage the application context (my_ctx) that carries effective date and first-party organization values for the duration of the session.

Usage Notes

ZX_SECURITY is invoked indirectly rather than directly by end users. EBTax configuration forms and concurrent programs call SET_SECURITY_CONTEXT (or SET_SECURITY_CONTEXT_UI for user-interface flows) before issuing queries, after which database policies reference the predicate functions. The package is referenced by nine other packages, reflecting its role as a shared security foundation. Custom code or extensions that must respect EBTax security should establish the context first, then rely on the predicate functions rather than querying the underlying tables directly. In 12.2.x, the same package continues to serve this function, with the version header indicating maintenance through the 12.1.1 family.