Results for “zx_rep_actg_ext_t”

50+ results




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

Overview

ZX_REP_ACTG_EXT_T is a transient staging table owned by the ZX (E-Business Tax) schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the accounting information extracted by the tax extract program from each product transaction table, capturing one row for every row present in ZX_REP_TRX_DETAIL_T. The table acts as the accounting-detail extension of the reporting extract pipeline that feeds the Tax Reporting Ledger (ETRM/ZX reporting) processes, enabling downstream reporting, reconciliation, and General Ledger transfer of tax accounting entries.

From a Data Vault modeling perspective (heuristic, mined from the FK structure), the object classifies as standalone. It carries its own surrogate primary key, ZX_REP_ACTG_EXT_T_PK on ACTG_EXT_LINE_ID, and a foreign-key reference outward to ZX_REP_TRX_DETAIL_T, but no other tables reference it. This pattern is consistent with a satellite-like detail structure attached to the transaction-detail parent, supplying the accounting attributes associated with each extracted tax line.

Key Information Stored

The table documents 55 physical columns. The most significant are the following:

Common Use Cases and Queries

Primary use cases centre on reporting and reconciliation of extracted tax accounting data, and on diagnosing GL transfer activity.

  • Reporting accounting entries for a period: query by PERIOD_NAME and ACCOUNTING_DATE to aggregate ACTG_STAT_AMT by ACTG_CATEGORY_CODE or ACTG_EVENT_TYPE_CODE.
  • Reconciliation with transaction detail: join to ZX_REP_TRX_DETAIL_T on DETAIL_TAX_LINE_ID = DETAIL_TAX_LINE_ID to compare tax line amounts with accounting amounts.
  • GL transfer monitoring: filter on GL_TRANSFER_FLAG and GL_TRANSFER_RUN_ID to identify entries pending transfer or tied to a specific transfer run.
  • Account derivation review: inspect ACTG_LINE_CCID, ACCOUNT_FLEXFIELD, and the TRX_TAXABLE_* columns to verify segment derivation.
  • Extract-program troubleshooting: use REQUEST_ID and PROGRAM_ID to trace rows back to the concurrent request that generated them.

Typical SQL pattern:

  • SELECT a.ACTG_EXT_LINE_ID, a.DETAIL_TAX_LINE_ID, a.ACCOUNTING_DATE, a.PERIOD_NAME, a.ACTG_STAT_AMT, a.GL_TRANSFER_FLAG FROM ZX.ZX_REP_ACTG_EXT_T a WHERE a.PERIOD_NAME = :period;
  • SELECT a.ACTG_EXT_LINE_ID, d.* FROM ZX.ZX_REP_ACTG_EXT_T a JOIN ZX.ZX_REP_TRX_DETAIL_T d ON a.DETAIL_TAX_LINE_ID = d.DETAIL_TAX_LINE_ID;

Related Objects

  • ZX_REP_TRX_DETAIL_T — parent transaction-detail extract table; joined via DETAIL_TAX_LINE_ID.
  • ZX_REP_ACTG_EXT_T_PK / ZX_REP_ACTG_EXT_T_U1 — primary key constraint and unique index on ACTG_EXT_LINE_ID.
  • ZX_REP_TRX_DETAIL_T related lookup/reporting views consuming both tables for Tax Reporting Ledger output.
  • ZX_REP_ACTG_T and other ZX_REP_* extract tables generated by the same tax extract program, sharing REQUEST_ID and PROGRAM_ID context.
  • GL_JE_HEADERS / GL_JE_LINES — downstream destinations of the entries controlled by GL_TRANSFER_FLAG, GL_TRANSFER_RUN_ID, and GL_TRANSFER_CODE.