Results for “ap_payment_programs”

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

Overview

AP_PAYMENT_PROGRAMS is a Payables-owned reference table that stores the payment programs available for defining payment formats in Oracle E-Business Suite 12.1.1 and 12.2.2. Although it is created and maintained by the Payables (AP) product, the table functions as a shared cross-product registry: Receivables, Banks, and the Brazilian localizations (JL_BR) all point to the same rows to designate the concurrent programs that print, transmit, build, or format payment and receipt output. Each row identifies a specific program and classifies the program type, allowing Oracle EBS to resolve the correct executable when a payment format, receipt method, or bank branch is used.

From a Data Vault modeling perspective, the mined foreign-key structure classifies AP_PAYMENT_PROGRAMS as a hub. This is a modeling suggestion rather than a physical design: the table supplies a stable, unique business key (the program) that numerous other tables reference. In practice, it behaves as a low-volume, slowly-changing reference/lookup table rather than a transactional entity.

Key Information Stored

The documented physical schema contains 11 columns. The columns of greatest operational importance are:

• PROGRAM_ID — Surrogate primary key, enforced by AP_PAYMENT_PROGRAMS_PK. This is the value stored in every dependent foreign key column across AP, AR, and JL_BR tables.
• PROGRAM_NAME — The executable/concurrent program name the row represents.
• PROGRAM_TYPE — The classification of the program (for example, print, transmission, or format categories), which determines how the program is applied to a payment format or receipt method.
• FRIENDLY_NAME — The user-facing display name presented in Oracle EBS setup windows; it is also a business-key candidate via AP_PAYMENT_PROGRAMS_UK1 and the unique index AP_PAYMENT_PROGRAMS_U2 (FRIENDLY_NAME, ZD_EDITION_NAME).
• TRANSMISSIONS_ENABLED — Flag indicating whether the program supports electronic transmission, used to filter eligible transmission programs.
• ZD_EDITION_NAME — Editioning column reflecting the 12.2 online patching (adop) architecture; it participates in both unique indexes AP_PAYMENT_PROGRAMS_U1 (PROGRAM_ID, ZD_EDITION_NAME) and AP_PAYMENT_PROGRAMS_U2.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN capture standard who-column audit information.

The surrogate primary key is PROGRAM_ID; the business-key candidates are PROGRAM_ID/FRIENDLY_NAME qualified by ZD_EDITION_NAME. Note that in 12.2, any query against this table should generally be edition-aware.

Common Use Cases and Queries

Typical use cases include identifying which program is assigned to a payment format or receipt method, listing all transmission-capable programs, and resolving a foreign key back to a friendly name for reporting. A representative lookup is:

• Resolving a bank branch's printing or transmission program:
  SELECT p.friendly_name, p.program_name, p.program_type FROM ap.ap_payment_programs p, ap.ap_bank_branches b WHERE b.printing_program_id = p.program_id AND b.branch_id = :branch;
• Listing transmission-enabled programs:
  SELECT program_id, friendly_name FROM ap.ap_payment_programs WHERE transmissions_enabled = 'Y';
• Finding the format program referenced by a Brazilian receipt-method account extension:
  SELECT p.friendly_name FROM ap.ap_payment_programs p, jl_br_ar_rec_met_accts_ext_all j WHERE j.factor_format_pgm_id = p.program_id;

Related Objects

The most significant dependents, joined on the documented foreign key columns, are:

• AP_CHECK_FORMATS — references BUILD_PAYMENTS_PROGRAM_ID, FORMAT_PAYMENTS_PROGRAM_ID, and REMITTANCE_ADVICE_PROGRAM_ID.
• AP_BANK_BRANCHES — references TRANSMISSION_PROGRAM_ID and PRINTING_PROGRAM_ID.
• AR_RECEIPT_METHODS — references AUTO_PRINT_PROGRAM_ID.
• AR_RECEIPT_METHOD_ACCOUNTS_ALL — references FACTOR_PRINT_PROGRAM_ID, FACTOR_TRANSMISSION_PROGRAM_ID, REMIT_PRINT_PROGRAM_ID, and REMIT_TRANSMISSION_PROGRAM_ID.
• AR_BATCHES_ALL — references AUTO_PRINT_PROGRAM_ID and AUTO_TRANS_PROGRAM_ID.
• JL_BR_AR_REC_MET_ACCTS_EXT_ALL — references FACTOR_FORMAT_PGM_ID and COLL_FORMAT_PGM_ID; this table is directly relevant to the user's search term.
• JL_BR_AR_REMIT_BORDEROS_ALL — references OUTPUT_PROGRAM_ID.

Because AP_PAYMENT_PROGRAMS is a hub, its PROGRAM_ID is the single join column that provisions program resolution across all of these Payables, Receivables, Bank, and localization objects.