Results for “view_options_code”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

ZX_MCO_CHECK_ACCESS_V is an Oracle E-Business Suite view owned by the APPS schema, classified under the FND — Application Object Library product family, and documented as VALID in ETRM 12.2.2 (compatible with 12.1.1). The view belongs to the Oracle E-Business Tax (ZX) regime and supports Multi-Country Operations (MCO) functionality by determining whether the currently logged-in operating unit holds access rights to specific tax regime and first-party organization combinations stored in subscription details. Rather than exposing raw subscription rows, the view computes two derived boolean-style flags — UPDATE_ACCESS and DUPLICATE_ACCESS — and reduces multiple subscription rows to a single authoritative row per regime/first-party pairing. This makes it a decision-support object consumed by ETRM configuration, tax regime setup, and multi-country subscription maintenance screens rather than a standalone reporting table. Because it references FND_PROFILE.VALUE, its output is session-dependent: results differ based on the ZX_GCO_WRITE_ACCESS profile option value for the current responsibility and user.

Underlying Base Objects

The view is defined over two documented base objects:

• ZX_SUBSCRIPTION_DETAILS (SYNONYM): the primary source of subscription data, supplying PARENT_FIRST_PTY_ORG_ID, TAX_REGIME_CODE, VIEW_OPTIONS_CODE, and FIRST_PTY_ORG_ID. A synonym resolves this to the underlying ZX subscription detail entity.
• FND_PROFILE (PACKAGE): invoked as FND_PROFILE.VALUE('ZX_GCO_WRITE_ACCESS') to determine whether the current session carries global write access for tax configuration.

The view's logic is layered. An inner query filters ZX_SUBSCRIPTION_DETAILS using a WHERE clause that admits all rows where FIRST_PTY_ORG_ID <> -99, plus rows where FIRST_PTY_ORG_ID = -99 only when the write-access profile is 'Y'. It then derives UPDATE_ACCESS and DUPLICATE_ACCESS via DECODE expressions, and assigns PFPO_NUM using ROW_NUMBER() OVER (PARTITION BY TAX_REGIME_CODE, PARENT_FIRST_PTY_ORG_ID ORDER BY VIEW_OPTIONS_CODE DESC). The outer query retains only rows where PFPO_NUM = 1, guaranteeing one result row per regime/parent first-party organization key.

Key Columns

• PARENT_FIRST_PTY_ORG_ID: the parent first-party organization identifier (legally the operating unit or legal entity); value -99 denotes the global/shared regime context reserved for users with write access.
• TAX_REGIME_CODE: the tax regime code (e.g., the country-specific regime) — the primary functional key users search on.
• VIEW_OPTIONS_CODE: the subscription option driving access semantics; documented literals include VFC (view full configuration), VFD (view full data), and VFR (view full reference).
• UPDATE_ACCESS: 'Y' when -99 global context coincides with the ZX_GCO_WRITE_ACCESS profile of 'Y', otherwise 'Y' only when VIEW_OPTIONS_CODE = 'VFC'; 'N' otherwise. Indicates the session may modify regime subscription data.
• DUPLICATE_ACCESS: 'Y' only for the global -99 context when VIEW_OPTIONS_CODE is VFD or VFR; 'N' otherwise. Signals authority to copy/duplicate regime setup.
• PFPO_NUM: the analytic row number used internally to collapse duplicates; always 1 in returned rows.

Common Use Cases and Queries

The view is typically joined to regime and first-party organization lookups to render access-controlled setup lists and to gate write operations in MCO maintenance forms. A representative query filtering by the searched token follows:

SELECT tax_regime_code,
       parent_first_pty_org_id,
       view_options_code,
       update_access,
       duplicate_access
  FROM apps.zx_mco_check_access_v
 WHERE tax_regime_code = :p_regime_code
   AND update_access = 'Y';

To enumerate regimes a session can duplicate:

SELECT tax_regime_code
  FROM apps.zx_mco_check_access_v
 WHERE duplicate_access = 'Y'
 ORDER BY tax_regime_code;

Because results depend on FND_PROFILE.VALUE('ZX_GCO_WRITE_ACCESS'), queries must be executed within an initialized EBS session (same responsibility and user) for meaningful output; direct SQL*Plus access without profile context yields only the -99-excluded rows. The view is read-only by design and should not be updated directly.