Search Results jg_zz_ap_wht_itf




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

Overview

JG_ZZ_AP_WHT_ITF is a table owned by the JG schema (JG – Regional Localizations) in Oracle E-Business Suite, documented as the Korean Withholding Tax Extract Table. It is a regional localization object rather than a core payables entity. Its function is to store a denormalized, extract-ready snapshot of withholding tax (WHT) information associated with supplier invoices and payments, so that Korean statutory reporting and tax remittance processes can be produced from a single consolidated source instead of joining across Payables, Purchasing, and Suppliers in real time.

The table is delivered with the status VALID and carries 262 documented columns in the 12.2.2 physical schema, confirming it is a wide, flattened reporting table. In the heuristic Data Vault classification supplied in the metadata, the object is marked standalone. From a modeling perspective, this should be read as: it behaves neither as a pure hub, link, nor satellite, but as an extract or staging structure. It contains one foreign key to AP_INVOICE_PAYMENTS_ALL.INVOICE_PAYMENT_ID, which supplies its only documented link to the transactional core. All remaining payload is descriptive and attribute-driven.

Key Information Stored

The columns fall into several recognizable families. The transactional identifiers are the most operationally significant: INVOICE_PAYMENT_ID (the documented foreign key back to AP_INVOICE_PAYMENTS_ALL), INVOICE_ID, INVOICE_DISTRIBUTION_ID, CHECK_ID, and PAYMENT_NUMBER / CHECK_NUMBER. These are the business-key candidates used to trace an extract row back to its source document; the metadata does not document a surrogate or primary key column, so joins should always be driven from these identifiers and REQUEST_ID.

Columns prefixed PV_, PVS_, INV_, IND_, ATC_, and HR_/HRL_ represent descriptive flexfield attribute segments for the supplier, supplier site, invoice, invoice distribution, tax rate, and location/legal entity respectively, with corresponding _GA_CATEGORY columns holding the context value.

Common Use Cases and Queries

The primary use case is Korean withholding tax reporting — generating the resident and non-resident withholding reports required by Korean tax authorities, reconciling them against Payables, and auditing that the correct tax rate was applied to each payment. A second use case is statutory file generation for a given extract run, and a third is diagnostic analysis of withholding discrepancies between the tax computed and the amount withheld.

Because rows are produced by a concurrent extract keyed by REQUEST_ID, the most common access pattern is filtering by request and reporting period:

  • Extract for a specific run: SELECT * FROM jg.jg_zz_ap_wht_itf WHERE request_id = :p_request_id;
  • WHT summary by supplier: aggregate TOTAL_WHT_AMOUNT, INCOME_TAX, and RESIDENT_TAX grouped by SUPPLIER_NAME and TAX_AUTHORITY_NAME, constrained by ACCOUNTING_DATE.
  • Reconciliation to payments: SELECT i.invoice_payment_id, i.payment_number, i.total_wht_amount FROM jg_zz_ap_wht_itf i WHERE i.payment_date BETWEEN :from_date AND :to_date;
  • Trace to source: join on INVOICE_PAYMENT_ID to AP_INVOICE_PAYMENTS_ALL and onward to AP_INVOICES_ALL to validate the extracted amounts against the live transaction.
  • Legal entity roll-up: group by LEGAL_ENTITY_NAME, REPORTING_ENTITY_NAME, and SOB_ID for management and statutory reporting.

Because the table is an extract target, it is normally treated as read-only during reporting; rows should not be manually updated, and analysis should be scoped to the latest REQUEST_ID for the period to avoid double counting across historical extract runs.

Related Objects

The documented foreign key relationship — INVOICE_PAYMENT_ID → AP_INVOICE_PAYMENTS_ALL.INVOICE_PAYMENT_ID — anchors the extract to the Payables payment record. The most significant related objects are:

  • AP_INVOICE_PAYMENTS_ALL — joined on INVOICE_PAYMENT_ID; the authoritative source for payment amounts, dates, and check references.
  • AP_INVOICES_ALL — referenced via INVOICE_ID for invoice amounts, dates, and supplier context.
  • AP_INVOICE_DISTRIBUTIONS_ALL — referenced via INVOICE_DISTRIBUTION_ID; holds the accounted distributions and code combination behind DIST_CODE_COMBINATION_ID.
  • AP_SUPPLIERS / AP_SUPPLIER_SITES_ALL — joined on SUPPLIER_ID and SUPPLIER_SITE_ID for supplier master and site attributes.
  • AP_CHECKS_ALL — linked via CHECK_ID and CHECK_NUMBER for payment document reconciliation.
  • AP_TAX_CODES_ALL — matched on TAX_CODE / TAX_ID for validation of withholding tax codes.
  • AP_AWT_TAX_RATES (withholding tax rate definitions) — aligned through TAX_RATE_ID and TAX_RATE to verify the rate applied.
  • FND_CONCURRENT_REQUESTS — joined on REQUEST_ID for extract run identification and status.
  • GL_CODE_COMBINATIONS — joined on DIST_CODE_COMBINATION_ID to resolve ACCOUNTING_FLEXFIELD.
  • HR_OPERATING_UNITS / HR_LOCATIONS_ALL — the source of the HRL_* and LOCATION_* columns used for legal entity and location reporting.