Results for “status_lookup_code”

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

Overview

AP_PERIOD_CLOSE_EXCPS_GT is a Payables module table owned by the AP schema in Oracle E-Business Suite 12.1.1 and 12.2.2. The _GT suffix identifies it as a global temporary table (GTT), meaning rows are session-scoped and typically used as a staging or collection structure during the Payables period-close process. The table surfaces exceptions encountered while validating and closing an accounting period, capturing invoice, distribution, payment, and check-level details that prevent a clean close. In the standard Payables flow, the Period Close Exceptions program or concurrent request populates this GTT, and a downstream report or form reads it back to present the exceptions to the user.

Under the heuristic Data Vault classification mined from its foreign key structure, this table is modeled as a standalone object. It contains no parent hub or link dependencies that would qualify it as a hub, link, or satellite, so it functions as a transient staging artifact rather than a durable dimensional entity.

Key Information Stored

The documented physical schema contains 39 columns. The most operationally significant include:

• INVOICE_ID, INVOICE_DISTRIBUTION_ID, INVOICE_LINE_NUMBER — identify the invoice and distribution line in exception.
• INVOICE_NUM, VOUCHER_NUM, DOC_SEQUENCE_VALUE — business-key identifiers for the invoice document.
• ACCOUNTING_DATE, INVOICE_DATE, CANCELLED_DATE — period-relevant dates driving close validation.
• INVOICE_AMOUNT, PAYMENT_AMOUNT, CHECK_AMOUNT, AMOUNT — monetary values used in reconciliation checks.
• INVOICE_PAYMENT_ID, PAYMENT_HISTORY_ID, CHECK_ID — link the exception to a payment or check record.
• LEGAL_ENTITY_ID, ORG_ID — multi-org and legal-entity context for the exception.
• MATCH_STATUS_FLAG, RECON_ACCOUNTING_FLAG, PROCESS_STATUS_FLAG — status flags indicating why the record is an exception.
• TRANSACTION_TYPE, EVENT_TYPE_CODE, ENTITY_CODE, SOURCE_TYPE, SOURCE_TABLE_NAME — classify the origin and nature of the exception.

No explicit surrogate primary key is documented; identity is implied by the combination of invoice, distribution, and payment identifiers. Business-key candidates include INVOICE_ID/INVOICE_DISTRIBUTION_ID and INVOICE_PAYMENT_ID. The two documented foreign keys are INVOICE_PAYMENT_ID → AP_INVOICE_PAYMENTS_ALL and LEGAL_ENTITY_ID → FV_LEGAL_ENTITIES.

Common Use Cases and Queries

Typical scenarios include troubleshooting a failed period close, generating an exceptions report, and reconciling payment or check amounts against invoices. A representative query joins the exception to the payment table and legal entity:

• List all open exceptions for a given accounting period:
  SELECT e.invoice_num, e.accounting_date, e.invoice_amount, e.mat...ch_status_flag
• Join to AP_INVOICE_PAYMENTS_ALL on INVOICE_PAYMENT_ID to retrieve payment detail for exceptions tied to payments.
• Join to FV_LEGAL_ENTITIES on LEGAL_ENTITY_ID to group exceptions by legal entity.
• Filter on PROCESS_STATUS_FLAG or RECON_ACCOUNTING_FLAG to isolate unresolved items.

Because this is a global temporary table, queries must run within the same session that populated it, typically immediately after the period-close exception program completes.

Related Objects

• AP_INVOICE_PAYMENTS_ALL — joined via INVOICE_PAYMENT_ID.
• FV_LEGAL_ENTITIES — joined via LEGAL_ENTITY_ID.
• AP_INVOICES_ALL — source of INVOICE_ID and invoice-level attributes.
• AP_INVOICE_DISTRIBUTIONS_ALL — source of INVOICE_DISTRIBUTION_ID.
• AP_CHECKS_ALL — referenced through CHECK_ID and check-related columns.
• AP_PAYMENT_HISTORY_ALL — referenced through PAYMENT_HISTORY_ID.
• Payables period-close concurrent programs and exception reports that populate and consume this GTT.