Results for “num_setup_checks”

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

Overview

AP_CHECK_STOCKS_ALL is a Payables (AP) module table in the AP schema that historically stored check stock definitions — the physical or electronic media, formats, and numbering rules used to generate payment documents. The table defines a "check stock" record that links a bank account to a check format, tracking the last document number issued, the last available document number, setup check counts, and the general ledger accounts used for bank charges, bank errors, cash clearing, and future-dated payments.

In Oracle EBS 12.1.1 and 12.2.2, the object is documented by Oracle as "No Longer Used." This is a critical fact: the table remains physically present in the AP schema (42 columns, status VALID) and retains its constraints and foreign key relationships, but Oracle no longer populates or actively uses it in current payment processing flows. Payment document sequencing in modern EBS releases is handled through the payment process request and payment document infrastructure rather than through AP_CHECK_STOCKS_ALL. The table therefore survives primarily as a legacy artefact retained for backward compatibility, archival data, and referential integrity with historic rows.

From a heuristic Data Vault modeling perspective, the table's structure is satellite-leaning. Its primary key, CHECK_STOCK_ID, is a surrogate key, and the bulk of the columns are descriptive attributes (format, numbering counters, flags, and code combination references) that evolve over time, which is characteristic of a satellite attached to a bank account hub.

Key Information Stored

The table is anchored by the surrogate primary key CHECK_STOCK_ID (AP_CHECK_STOCKS_PK). Two unique indexes act as business-key candidates: AP_CHECK_STOCKS_U1 on CHECK_STOCK_ID and AP_CHECK_STOCKS_U2 on the combination of BANK_ACCOUNT_ID and NAME, indicating that a check stock is uniquely identified within a bank account by its name.

• BANK_ACCOUNT_ID — foreign key to AP_BANK_ACCOUNTS_ALL; the disbursement bank account the stock belongs to.
• NAME — user-defined identifier for the check stock, part of the unique business key.
• CHECK_FORMAT_ID — foreign key to AP_CHECK_FORMATS; the print format template applied to the stock.
• DISBURSEMENT_TYPE_LOOKUP_CODE — disbursement method classification for the stock.
• LAST_DOCUMENT_NUM and LAST_AVAILABLE_DOCUMENT_NUM — trailing and ceiling document numbers used for sequencing.
• NUM_SETUP_CHECKS — count of setup/alignment checks reserved for the stock.
• SEQUENTIAL_FLAG and FUTURE_DATED_PAYMENTS_FLAG — control flags governing numbering and future-dated payment behaviour.
• INACTIVE_DATE — the date the stock was retired from use.
• FUTURE_PAY_CODE_COMBINATION_ID, BANK_CHARGES_CCID, BANK_ERRORS_CCID, and CASH_CLEARING_CCID — foreign keys to GL_CODE_COMBINATIONS defining accounting for future payments, charges, errors, and clearing.
• CLEARING_DAYS, DOC_CATEGORY_CODE, TRANSMISSION_CODE, and ORG_ID — clearing window, document category, transmission type, and multi-org partitioning.
• Descriptive attributes (ATTRIBUTE_CATEGORY, ATTRIBUTE1–15) support flexfield-style extension data.

Common Use Cases and Queries

Because the table is marked "No Longer Used," primary use cases are historical reporting, data migration archaeology, and integrity reconciliation rather than transactional processing. Analysts reconciling legacy payment numbering may query it as follows:

• Retrieve all check stocks for a given bank account: SELECT check_stock_id, name, last_document_num, last_available_document_num FROM ap_check_stocks_all WHERE bank_account_id = :p_account_id;
• Identify retired stocks by inactivity: SELECT check_stock_id, name, inactive_date FROM ap_check_stocks_all WHERE inactive_date IS NOT NULL ORDER BY inactive_date DESC;
• Join to historical payments via AP_CHECKS_ALL.CHECK_STOCK_ID to attribute issued documents to a stock and format.
• Join to GL_CODE_COMBINATIONS on the CCID columns to reconstruct the accounting configuration in force when the stock was active.
• Cross-reference AP_INV_SELECTION_CRITERIA_ALL and AP_PBATCH_SET_LINES_ALL, both of which carry a CHECK_STOCK_ID foreign key, to trace which selection or batch criteria referenced a stock.

Reporting should treat the table as read-only historical reference and avoid any reliance on it for current document sequencing logic, since Oracle has superseded this mechanism.

Related Objects

The most significant related objects, per the documented foreign key graph, are as follows:

• AP_BANK_ACCOUNTS_ALL — parent of BANK_ACCOUNT_ID; the bank account owning the check stock.
• AP_CHECK_FORMATS — referenced via CHECK_FORMAT_ID; defines the print format.
• GL_CODE_COMBINATIONS — referenced four times, by FUTURE_PAY_CODE_COMBINATION_ID, BANK_CHARGES_CCID, BANK_ERRORS_CCID, and CASH_CLEARING_CCID.
• AP_CHECKS_ALL — child table carrying CHECK_STOCK_ID; the primary historical link to issued payments.
• AP_INV_SELECTION_CRITERIA_ALL — child table carrying CHECK_STOCK_ID.
• AP_PBATCH_SET_LINES_ALL — child table carrying CHECK_STOCK_ID.