Results for “multi_currency_flag”

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

Overview

AP_CHECK_FORMATS is a Payables (AP) module table in the Oracle E-Business Suite 12.1.1 and 12.2.2 releases. Despite being marked VALID in the ETRM repository, its official description is "No Longer Used," meaning the table is retained for backward compatibility and historical data preservation but is not actively maintained by standard Payables functionality in current releases. In legacy configurations it defined the physical layout of printed payment documents — checks, stubs, and remittance advices — including line positioning for the check number, date, amount, amount in words, vendor name, vendor number, and invoice details.

From a Data Vault modeling perspective, the metadata classifies this object heuristically as satellite-leaning. This suggests it is best modelled as a descriptive satellite attached to a business key (the format name combined with payment method), rather than as a hub or link. The multiple foreign keys to AP_PAYMENT_PROGRAMS and a currency reference reinforce its role as a descriptive, configurable extension rather than a transactional core entity.

Key Information Stored

The table contains 78 documented columns. The surrogate primary key is CHECK_FORMAT_ID, defined by AP_CHECK_FORMATS_PK. Two unique indexes act as business-key candidates: AP_CHECK_FORMATS_UK1 / U2 on NAME and PAYMENT_METHOD_LOOKUP_CODE (and ZD_EDITION_NAME in 12.2.2), and AP_CHECK_FORMATS_U1 on CHECK_FORMAT_ID and ZD_EDITION_NAME. The most operationally significant columns include:

• CHECK_FORMAT_ID — surrogate primary key and the join column referenced by AP_CHECKS_ALL and AP_CHECK_STOCKS_ALL.
• NAME — the user-facing format name; part of the unique business key.
• PAYMENT_METHOD_LOOKUP_CODE — the payment method (for example, check or EFT) the format applies to.
• CURRENCY_CODE — restricts the format to a specific currency, referencing FND_CURRENCIES.
• CHECK_LENGTH, STUB_LENGTH, INVOICES_PER_STUB — physical layout dimensions of the printed document.
• STUB_FIRST_FLAG, PRINT_CHECK_STUB, OVERFLOW_RULE, PRE_NUMBERED_FLAG — control flags governing stub ordering and overflow behavior.
• DATE_ROW_LINE, AMOUNT_ROW_LINE, AMOUNT_WORDS_ROW_LINE, VENDOR_NAME_ROW_LINE, VENDOR_NUM_ROW_LINE — row-line coordinates for printing each data element.
• BUILD_PAYMENTS_PROGRAM_ID, FORMAT_PAYMENTS_PROGRAM_ID, REMITTANCE_ADVICE_PROGRAM_ID — foreign keys to AP_PAYMENT_PROGRAMS controlling which concurrent programs build, format, and produce remittance advice output.
• MULTI_CURRENCY_FLAG, ZERO_AMOUNTS_ONLY, GROUP_BY_DUE_DATE, EFT_TYPE, SEPARATE_REMITTANCE_ADVICE — behavioral options for payment processing.
• BANK_FILE_CHARACTER_SET, TRANSMISSIONS_FLAG — settings relevant to electronic payment file generation.

Common Use Cases and Queries

Because the table is functionally obsolete, primary use cases are historical reporting, data migration audits, and impact analysis before decommissioning or archiving. Analysts commonly join it to its dependent check tables to reconcile which format was applied to issued payments. A representative query pattern:

SELECT cf.name, cf.payment_method_lookup_code, c.check_number, c.amount
FROM ap_check_formats cf, ap_checks_all c
WHERE cf.check_format_id = c.check_format_id;

Other patterns include listing formats by payment method, auditing currency-specific configurations via the FND_CURRENCIES join, and verifying program associations against AP_PAYMENT_PROGRAMS. Reporting should treat the table as reference data rather than a live transactional source.

Related Objects

The most significant related objects, based on documented foreign key relationships, are:

• AP_CHECKS_ALL — references AP_CHECK_FORMATS via CHECK_FORMAT_ID; holds issued payment records.
• AP_CHECK_STOCKS_ALL — references AP_CHECK_FORMATS via CHECK_FORMAT_ID; tracks check stock inventory.
• AP_PAYMENT_PROGRAMS — referenced three times (BUILD_PAYMENTS_PROGRAM_ID, FORMAT_PAYMENTS_PROGRAM_ID, REMITTANCE_ADVICE_PROGRAM_ID).
• FND_CURRENCIES — referenced via CURRENCY_CODE for currency validation.

Together these objects define the historical linkage between payment formats and the payments, stock, and concurrent programs that consumed them.