Search Results zx_user_proc_input_v




Overview
Explore in AI Chat

Overview

ZX_USER_PROC_INPUT_V is a VALID view owned by the APPS schema within the FND - Application Object Library product group in Oracle E-Business Suite, documented under ETRM for releases 12.1.1 and 12.2.2. The view exposes the pre-processing input parameters captured for user-defined tax processing in the E-Business Tax (ZX) module. Its name reflects its purpose: it presents the "user processing input" values that Oracle's tax engine consumes before the tax determination and calculation routines execute for a transaction.

In Oracle EBS reporting and integration contexts, this view functions as a lightweight, denormalized access point into a global temporary table used during tax pre-processing. Rather than exposing the entire GT structure, the view projects a focused set of identifying and configuration columns, allowing external programs, concurrent reports, and custom SQL to read the pre-processing options associated with a transaction. Because it is a view over a session-scoped temporary table, the rows visible to any query are limited to those populated by the current session's tax processing activity.

Underlying Base Objects

According to the documented ETRM metadata for 12.2.2, the view is defined over a single referenced base object: ZX_TRX_PRE_PROC_OPTIONS_GT, which is registered in the APPS schema as a synonym. The documented view text confirms this directly:

ZX_TRX_PRE_PROC_OPTIONS_GT is a global temporary table (GT) that holds transaction pre-processing options during E-Business Tax processing. Because ZX_USER_PROC_INPUT_V selects from the GT without joins, filters, or aggregations, it is a direct pass-through view. It does not persist data of its own; all content is transient and scoped to the session and transaction context in which the underlying GT is populated. This design means the view does not participate in row-level security or partitioning logic beyond what the GT itself enforces.

Key Columns

The view exposes seven columns, each carrying transactional or tax-configuration context:

  • INTERNAL_ORGANIZATION_ID — Identifies the internal organization (operating unit or inventory organization) associated with the transaction, anchoring the tax event to a legal and business context.
  • APPLICATION_ID — The application identifier (FND_APPLICATION.APPLICATION_ID) of the source application, distinguishing tax processing for Receivables, Payables, Purchasing, and other modules.
  • ENTITY_CODE — The application entity code representing the type of tax event or business entity being processed.
  • EVENT_CLASS_CODE — Classifies the event driving tax processing, such as a customer invoice, purchase order, or credit memo.
  • TRX_ID — The transaction identifier linking the pre-processing input row to the specific document under tax evaluation.
  • TAX_PROVIDER_ID — The tax provider identifier, indicating which provider or service supplies or overrides tax calculation for the transaction.
  • TAX_REGIME_CODE — The tax regime code, identifying the tax regime (for example, a country-specific VAT or sales tax regime) applied to the transaction.

Common Use Cases and Queries

Typical usage centers on diagnostics, integration extraction, and reporting on tax pre-processing behavior. A common pattern is to retrieve the options captured for a specific transaction within the active session:

  • Transaction-level inspection: Select all columns from ZX_USER_PROC_INPUT_V where TRX_ID equals the document number in question, to verify which tax provider and regime were supplied before calculation.
  • By organization or application: Filter on INTERNAL_ORGANIZATION_ID or APPLICATION_ID to analyze pre-processing options across an operating unit or module.
  • Event classification: Aggregate rows by EVENT_CLASS_CODE or ENTITY_CODE to understand how tax pre-processing inputs differ across document types.
  • Integration extraction: Programs integrating with external tax engines can read this view to synchronize the provider and regime parameters used for each transaction.

Because the underlying object is a global temporary table, queries outside the processing session may return no rows. Analysts should invoke the view within the same session or concurrent request that populates ZX_TRX_PRE_PROC_OPTIONS_GT, which is why the view is best suited to in-process diagnostics and point-in-time reporting rather than historical analysis. For historical tax data, base transactional tax tables should be queried instead.