Results for “ap_check_formats_u1”

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

Overview

AP.AP_CHECK_FORMATS is an Oracle Payables reference table that stores the payment format definitions used to produce payment documents such as checks, EFT files, and separate remittance advices. Each row represents a single payment format that a Payables installation can select when creating payments to suppliers, and the table corresponds directly to the Payment Formats window in the EBS Payables application. The table resides in the APPS_TS_SEED tablespace, reflecting its role as a seed and configuration object rather than a high-volume transactional table.

From a dimensional modeling perspective, the documented foreign key structure suggests a satellite-leaning classification. The table carries a surrogate primary key and multiple descriptive and control attributes, while referencing AP_PAYMENT_PROGRAMS and FND_CURRENCIES. This heuristic classification is offered as a modeling suggestion rather than a documented fact, and reflects the table's role as a descriptive extension around payment program and currency references.

The table is present and valid in both EBS 12.1.1 and 12.2.2. In 12.2.2 the documented physical schema records 78 columns and adds the ZD_EDITION_NAME column, which participates in both unique indexes as part of the editioning and online patching architecture introduced in Release 12.2.

Key Information Stored

The most operationally significant columns are:

• CHECK_FORMAT_ID — the surrogate primary key of the table (AP_CHECK_FORMATS_PK) and the column referenced by downstream payment and check stock tables.
• NAME — the payment format name, limited to 30 characters; together with PAYMENT_METHOD_LOOKUP_CODE it forms the business-key candidate captured by index AP_CHECK_FORMATS_U2.
• PAYMENT_METHOD_LOOKUP_CODE — the payment method the format supports (for example check or EFT); the second component of AP_CHECK_FORMATS_U2.
• CURRENCY_CODE — the currency associated with the format, with a foreign key to FND_CURRENCIES; used in multi-currency configurations.
• CREATE_PAYMENTS_PROGRAM_ID, CONFIRM_PAYMENTS_PROGRAM_ID, BUILD_PAYMENTS_PROGRAM_ID, and FORMAT_PAYMENTS_PROGRAM_ID — concurrent program references into AP_PAYMENT_PROGRAMS that drive payment creation, confirmation, building, and formatting.
• REMITTANCE_ADVICE_PROGRAM_ID and SEPARATE_REMITTANCE_ADVICE — control whether a separate remittance advice program is invoked and which program it is.
• INVOICES_PER_STUB — the number of invoices printed on a check stub or separate remittance advice.
• PRINT_CHECK_STUB, MULTI_CURRENCY_FLAG, ZERO_AMOUNTS_ONLY, GROUP_BY_DUE_DATE, TRANSMISSIONS_FLAG, and BANK_FILE_CHARACTER_SET — behavioral flags governing stub printing, currency handling, zero-amount output, grouping, and bank file encoding.

Several legacy columns such as TYPE, STUB_FIRST_FLAG, CHECK_LENGTH, and the row-line positioning columns are documented as no longer used, and printable layout is now handled through XML Publisher templates rather than these fields. Standard WHO columns track creation and last update, and the ATTRIBUTE1–15 and GLOBAL_ATTRIBUTE1–20 descriptive flexfield columns allow customer-defined extensions.

Common Use Cases and Queries

The primary use case is configuration validation and payment processing diagnostics. A common query resolves the format assigned to a payment by joining AP_CHECKS_ALL to AP_CHECK_FORMATS on CHECK_FORMAT_ID. A related query lists all formats by payment method and currency to confirm which formats are available for a given operating unit:

• Join AP_CHECKS_ALL.CHECK_FORMAT_ID to AP_CHECK_FORMATS.CHECK_FORMAT_ID to report the format used on each payment.
• Join AP_CHECK_STOCKS_ALL.CHECK_FORMAT_ID to AP_CHECK_FORMATS.CHECK_FORMAT_ID to audit which check stocks are attached to each format.
• Query by NAME and PAYMENT_METHOD_LOOKUP_CODE to retrieve a specific format, exploiting index AP_CHECK_FORMATS_U2.
• Join CREATE_PAYMENTS_PROGRAM_ID, CONFIRM_PAYMENTS_PROGRAM_ID, and REMITTANCE_ADVICE_PROGRAM_ID to AP_PAYMENT_PROGRAMS to trace the concurrent programs executed during payment processing.

Typical reporting scenarios include reconciling payment output to its driving concurrent programs, verifying remittance advice configuration, and auditing multi-currency or EFT format usage.

Related Objects

• AP_PAYMENT_PROGRAMS — referenced multiple times from this table via BUILD_PAYMENTS_PROGRAM_ID, FORMAT_PAYMENTS_PROGRAM_ID, CREATE_PAYMENTS_PROGRAM_ID, CONFIRM_PAYMENTS_PROGRAM_ID, and REMITTANCE_ADVICE_PROGRAM_ID.
• FND_CURRENCIES — referenced through CURRENCY_CODE.
• AP_CHECKS_ALL — references AP_CHECK_FORMATS through CHECK_FORMAT_ID.
• AP_CHECK_STOCKS_ALL — references AP_CHECK_FORMATS through CHECK_FORMAT_ID.
• AP_PAYMENT_FORMATS and the Payment Formats window — the application and UI layers that maintain this seed data.
• FND_USER — referenced by the LAST_UPDATED_BY and CREATED_BY standard WHO columns.
• AP_PAYMENT_TEMPLATES — the XML Publisher templates associated with payment and remittance advice formatting.