Search Results header_numeric1




Overview
Explore in AI Chat

Overview

APPS.ZX_SYNC_HDR_INPUT_V is a public synonym-backed view residing in the APPS schema and registered under the Oracle E-Business Tax (EBTax) module, whose underlying technology stack is delivered by the ETRM (E-Business Tax Repository Management) product. The object carries FND Design Data reference FND.ZX_SYNC_HDR_INPUT_V and reports a status of VALID, indicating that it compiles cleanly against its referenced base objects. Functionally, the view serves as a header-level staging and pass-through interface for tax synchronization processing. It exposes a normalized set of header attributes — organization and legal entity identifiers, establishment numbers, document type, transaction identifiers, and application context — alongside a wide generic attribute block consisting of thirty character columns, ten numeric columns, and five date columns.

The view is designed to feed downstream tax determination and tax line generation logic, particularly where header-level context must be captured before line-level detail factors are applied. It is typically consumed by integration and reporting components that need to flatten heterogeneous header structures into a single, uniform shape.

Underlying Base Objects

The documented base objects referenced by ZX_SYNC_HDR_INPUT_V are ZX_LINES_DET_FACTORS, ZX_PRVDR_HDR_EXTNS_GT, and ZX_TRX_PRE_PROC_OPTIONS_GT. ZX_LINES_DET_FACTORS supplies the transaction and document classification context used in tax determination; it is the principal persistent source for line-level determinant values that the header view associates with its transaction identifier. ZX_PRVDR_HDR_EXTNS_GT is a global temporary table holding provider-specific header extension values, and ZX_TRX_PRE_PROC_OPTIONS_GT stores pre-processing options applied to a transaction before tax calculation. The presence of two global temporary tables confirms that the view is session-scoped in practice: rows reflect data staged by the current session for the transaction being synchronized, not a persistent snapshot.

Key Columns

Common Use Cases and Queries

Typical usage patterns include diagnosing why a tax header did not synchronize, validating staged provider extension values, and extracting header context for reconciliation reports.

  • Inspect staged header synchronization input for a transaction: 
    SELECT transaction_id, application_code, document_level_action,
       transaction_number, transaction_due_date
  FROM apps.zx_sync_hdr_input_v
 WHERE transaction_id = :p_trx_id;
  • Review provider extension attributes carried through the header: 
    SELECT internal_organization_id, legal_entity_number,
       header_char1, header_char2, header_numeric1
  FROM apps.zx_sync_hdr_input_v
 WHERE application_code = 'AR'
   AND document_level_action = 'CREATE';
  • Audit by legal entity and establishment: 
    SELECT legal_entity_number, establishment_number,
       COUNT(*) staged_rows
  FROM apps.zx_sync_hdr_input_v
 GROUP BY legal_entity_number, establishment_number;

Because two of the three base objects are global temporary tables, results are meaningful only within the session that populated them; queries executed from a separate session will generally return no rows.