Results for “pay_group_option”

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

Overview

AP_PAYMENT_TEMPLATES is a Payables (AP) owned table that stores user-defined Payment Process Request Templates in Oracle E-Business Suite 12.1.1 and 12.2.2. These templates capture the reusable selection criteria, grouping rules, and processing options that drive a Payment Process Request (PPR). Rather than re-entering the same parameters each time a payment run is submitted, an AP user creates a template once and applies it repeatedly, achieving consistency across payment batches and reducing data-entry error. The table is therefore central to the automated payment workflow, sitting between the configuration of payment attributes and the execution of individual payment instructions.

From a data-modeling perspective, the mined foreign-key structure suggests a hub-leaning classification. The table is referenced by four dependent grouping tables that all point back to it through TEMPLATE_ID, and it carries a surrogate primary key (TEMPLATE_ID) with no natural composite business key. This pattern is consistent with a hub entity in a Data Vault model, where the template identity is the durable anchor and the surrounding attributes would be split into satellites. This is offered as a modeling suggestion only; in native EBS it is a standard transactional/configuration table.

Key Information Stored

The table contains 59 documented columns in 12.2.2. The primary key is the system-generated surrogate column TEMPLATE_ID, backed by the unique index AP_PAYMENT_TEMPLATES_U1. No separate multi-column business key is documented; the closest business identifier is TEMPLATE_NAME, which is what users see and select at runtime.

• TEMPLATE_ID — Surrogate primary key; the join column to all dependent group tables.
• TEMPLATE_NAME — User-visible name of the Payment Process Request Template.
• TEMPLATE_TYPE — Classifies the template variant.
• DESCRIPTION and INACTIVE_DATE — Free-text description and the date after which the template is no longer selectable.
• PAYMENT_METHOD_CODE — Determines the payment instrument (for example, check, wire, or electronic).
• PAY_ONLY_WHEN_DUE_FLAG, ADDL_PAYMENT_DAYS, ADDL_PAY_FROM_DAYS, ADDL_PAY_THRU_DAYS — Control the due-date window for payment selection.
• HI_PAYMENT_PRIORITY and LOW_PAYMENT_PRIORITY — Bound the payment priority range included in the run.
• BANK_ACCOUNT_ID and PAYMENT_PROFILE_ID — Disbursement account and payment profile. PAYMENT_PROFILE_ID references IBY_ACCT_PMT_PROFILES_B.
• VENDOR_ID, PARTY_ID, and VENDOR_TYPE_LOOKUP_CODE — Restrict the template to specific suppliers or supplier types; PARTY_ID references HZ_PARTIES.
• PAY_GROUP_OPTION, CURRENCY_GROUP_OPTION, LE_GROUP_OPTION, OU_GROUP_OPTION — Define how payments are grouped by pay group, currency, legal entity, and operating unit.
• PAYMENT_DATE_OPTION, PAYABLES_REVIEW_SETTINGS, PAYMENTS_REVIEW_SETTINGS, CREATE_INSTRS_FLAG, RESUBMIT_FLAG — Govern scheduling, review gates, and instruction creation.
• ATTRIBUTE_CATEGORY through ATTRIBUTE15 and the standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) — Descriptive flexfield segments and audit trail.

Common Use Cases and Queries

Typical usage centers on identifying active templates, auditing the payment criteria embedded in a template, and tracing the grouping configuration attached to each template.

• List active templates: SELECT TEMPLATE_ID, TEMPLATE_NAME, PAYMENT_METHOD_CODE FROM AP_PAYMENT_TEMPLATES WHERE INACTIVE_DATE IS NULL OR INACTIVE_DATE > SYSDATE;
• Inspect payment restrictions for a named template: query HI_PAYMENT_PRIORITY, LOW_PAYMENT_PRIORITY, PAY_ONLY_WHEN_DUE_FLAG, and ADDL_PAYMENT_DAYS to document the selection window.
• Trace supplier-scoped templates: join PARTY_ID to HZ_PARTIES.PARTY_ID to resolve the supplier name behind vendor-specific templates.
• Audit disbursement configuration: join PAYMENT_PROFILE_ID to IBY_ACCT_PMT_PROFILES_B to confirm the bank account and profile used.
• Grouping analysis: join to AP_PAY_GROUP, AP_CURRENCY_GROUP, AP_LE_GROUP, and AP_OU_GROUP on TEMPLATE_ID to report which grouping rules a template applies.

These queries support month-end reporting, segregation-of-duties review, and migration of template configuration between environments.

Related Objects

The following objects most significantly reference or are referenced by AP_PAYMENT_TEMPLATES, based on the documented relationships:

• AP_PAY_GROUP — joins on TEMPLATE_ID; holds pay group assignments for the template.
• AP_CURRENCY_GROUP — joins on TEMPLATE_ID; holds currency grouping configuration.
• AP_LE_GROUP — joins on TEMPLATE_ID; holds legal entity grouping configuration.
• AP_OU_GROUP — joins on TEMPLATE_ID; holds operating unit grouping configuration.
• HZ_PARTIES — referenced by AP_PAYMENT_TEMPLATES.PARTY_ID; resolves supplier party identity.
• IBY_ACCT_PMT_PROFILES_B — referenced by PAYMENT_PROFILE_ID; stores the payment profile and account definition.

Collectively these linkages establish AP_PAYMENT_TEMPLATES as the configuration anchor for Payment Process Requests in Oracle Payables.