Search Results zx_sync_hdr_input_v




Overview
Explore in AI Chat

Overview

ZX_SYNC_HDR_INPUT_V is a seeded Oracle E-Business Suite view owned by the APPS schema and registered under the FND – Application Object Library product. Its status is VALID in both 12.1.1 and 12.2.2 environments. Despite the FND ownership classification, the view is functionally part of the E-Business Tax (ZX) synchronization infrastructure: the "SYNC_HDR_INPUT" naming convention indicates it serves as a header-level input staging view for the tax synchronization engine that moves transaction tax data between the ETRM and the transaction tables.

The view presents a unified header projection combining tax determinants, transaction identifiers, and a wide set of provider-specific header extension attributes. Rather than exposing foreign keys alone, it flattens pre-processing context and external provider metadata into a single consumable structure. This makes it suitable for downstream concurrent programs, tax synchronization flows, and diagnostic reporting where a consolidated header record is required without repeated joins.

Underlying Base Objects

The documented view metadata identifies three referenced base objects, all exposed to APPS as synonyms:

  • ZX_LINES_DET_FACTORS – Supplies line-level tax determinant factors such as internal organization, event class mapping, transaction identifiers, tax event type, and document sequencing values.
  • ZX_PRVDR_HDR_EXTNS_GT – A global temporary table holding external tax provider header extension values, including the numbered varchar, number, and date attribute columns.
  • ZX_TRX_PRE_PROC_OPTIONS_GT – A global temporary table carrying tax pre-processing options, contributing legal entity and establishment identifiers along with application short name context.

Because two of the three sources are global temporary tables, the view is session-scoped in practice: rows are only meaningful within the session that populated the temporary tables, typically a tax synchronization concurrent request. The join aligns transaction header determinants with provider extensions and pre-processing option values on common keys such as TRX_ID and EVENT_CLASS_MAPPING_ID.

Key Columns

Common Use Cases and Queries

Typical uses include debugging tax synchronization runs, validating that header extensions are correctly passed from the provider interface, and auditing determinant values applied to a transaction.

To inspect header determinants for a specific transaction:

  • SELECT trx_number, tax_event_type_code, legal_entity_number, establishment_number FROM zx_sync_hdr_input_v WHERE trx_id = :p_trx_id;

To review provider header extensions:

  • SELECT trx_id, header_ext_varchar_attribute1, header_ext_number_attribute1 FROM zx_sync_hdr_input_v WHERE internal_organization_id = :p_org_id;

Because the view depends on session-level global temporary tables, queries outside the populating session generally return no rows; it should therefore be used within the synchronization flow or immediately after the driving request completes in the same session.