Results for “zx_user_proc_hdr_input_v”

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

Overview

The ZX_USER_PROC_HDR_INPUT_V view is a reporting and integration object owned by the APPS schema within Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the FND – Application Object Library product grouping and is classified as a VALID view. Its role within the E-Business Tax (ETRM/ZX) subsystem is to expose a consolidated, header-level projection of transaction data that the tax determination engine requires as input. Specifically, the view joins detail-level tax determination factors with the transaction pre-processing options captured at runtime, producing a set of rows that pair each transaction with its applicable tax provider and tax regime context.

This object is commonly encountered during diagnostics of tax determination and tax calculation pipelines, particularly when the underlying ZX_LINES_DET_FACTORS data must be reconciled against the options selected in the transaction pre-processing step. Because it is a view rather than a table, it does not store data; it derives its output dynamically from its referenced base objects at query time.

Underlying Base Objects

According to the documented view definition, ZX_USER_PROC_HDR_INPUT_V is defined over two referenced base objects, both represented in the metadata as synonyms:

• ZX_LINES_DET_FACTORS (aliased as ZX_DET_FACT) – the primary detail factors source, supplying organization, application, entity, event class, transaction, date, and receivables transaction type information.
• ZX_TRX_PRE_PROC_OPTIONS_GT (aliased as ZX_PRE_REC_OPT) – a global temporary table holding transaction pre-processing options such as tax provider and tax regime code.

The two sources are joined on five key attributes: INTERNAL_ORGANIZATION_ID, APPLICATION_ID, EVENT_CLASS_CODE, ENTITY_CODE, and TRX_ID. This composite join ensures that each transaction's determination factors are matched to the corresponding pre-processing option record for the same organizational and event context.

Key Columns

The view projects the following columns, which constitute its exposed interface:

• INTERNAL_ORGANIZATION_ID – the operating unit or organization identifier for the transaction.
• APPLICATION_ID – the owning application (for example, Receivables) associated with the transaction.
• ENTITY_CODE – the entity classification used by tax determination, such as a transaction entity.
• EVENT_CLASS_CODE – the event class driving tax determination (e.g., invoice, credit memo).
• TRX_ID – the transaction identifier, serving as the join key to the pre-processing options.
• TAX_PROVIDER_ID – the tax provider selected for the transaction, sourced from the pre-processing options.
• TAX_REGIME_CODE – the tax regime applicable to the transaction.
• TRX_DATE – the transaction date from the detail factors.
• TRX_TYPE_ID – exposed as the receivables transaction type identifier (RECEIVABLES_TRX_TYPE_ID in the underlying source).

Common Use Cases and Queries

This view is typically used to validate that the correct tax provider and regime are being applied to a given transaction, and to trace determination inputs during tax calculation troubleshooting. A representative query retrieves header input context for a specific transaction:

• SELECT trx_id, entity_code, event_class_code, tax_provider_id, tax_regime_code, trx_date FROM zx_user_proc_hdr_input_v WHERE trx_id = :p_trx_id;
• SELECT internal_organization_id, application_id, COUNT(*) FROM zx_user_proc_hdr_input_v GROUP BY internal_organization_id, application_id; – to audit determination input volumes by organization.
• SELECT h.trx_id, h.tax_regime_code, h.tax_provider_id FROM zx_user_proc_hdr_input_v h WHERE h.trx_date BETWEEN :p_from AND :p_to; – to analyze tax regime distribution across a date range.

Because the view depends on a global temporary table (ZX_TRX_PRE_PROC_OPTIONS_GT), query results are meaningful only within a session where the pre-processing options have been populated. Queries executed outside such a session may return no rows or incomplete results, which is an important consideration during diagnostic work.