Results for “check_payment_method”

42 results




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

Overview

The ARP_PROCESS_CREDIT_UTIL package body in the APPS schema is a utility package within the Oracle E-Business Suite Receivables (AR) module. It provides the shared PL/SQL logic used to process and validate credit transactions — specifically credit memos, on-account credits, and adjustments — against open receivables. Its central role is to determine how much of a customer's outstanding balance can be offset by credit, to derive the defaulting rules that a credit transaction inherits from its originating transaction and transaction type, and to validate the receipt, payment method, bank account, and transaction type attributes that govern how a credit is applied or refunded.

In ETRM classification terms this object is listed as a UTIL package: it exposes reusable calculation and validation routines rather than a business flow of its own. It is not referenced by any database object, meaning it is a leaf dependency — invoked by forms, concurrent programs, and other AR packages but not depended upon structurally at the database level. It does, however, reference a broad set of AR and Receivables foundation APIs, indicating that its purpose is to centralize credit-processing rules that would otherwise be duplicated across credit memo entry and adjustment workflows.

Key Procedures and Functions

Nine documented procedures and functions are exposed by the package. The utility falls into three logical groups: credit amount derivation, header defaulting, and validation.

  • GET_COMMITMENT_ADJUSTMENTS — Retrieves adjustment records associated with a commitment, used when credit must be reconciled against committed or applied amounts.
  • GET_COMMITMENT_ADJ_DETAIL — Returns the detailed attributes of a specific commitment adjustment for use in downstream credit calculations.
  • GET_CREDITED_TRX_DETAILS — Fetches the details of the transaction that has been credited, providing the reference data needed to build a credit memo line or adjustment.
  • GET_CREDIT_MEMO_AMOUNTS — Computes the amounts available for credit memo creation, including the creditable balance remaining on the source transaction.
  • GET_CM_HEADER_DEFAULTS — Derives the default header attribute values (transaction type, batch source, terms, currency, and related attributes) for a new credit memo, using transaction default APIs.
  • CHECK_PAYMENT_METHOD — Validates that the selected receipt method is permitted for the credit or refund being processed.
  • CHECK_BANK_ACCOUNT — Confirms that the specified bank account is valid and usable for the payment method and operating unit.
  • CHECK_CM_TRXTYPE — Verifies that the transaction type supplied for a credit memo is valid and appropriate for credit processing.
  • INIT — Initializes package-level state, typically caching profile options and system parameter values for the duration of the session.

Tables Accessed

The package reads and writes against the core Receivables and Credit-to-Cash tables through APPS synonyms. Customer and site data is obtained from HZ_CUST_ACCOUNTS, HZ_CUST_ACCOUNT_ROLES, HZ_CUST_ACCT_SITES, and HZ_CUST_SITE_USES. Transaction data is drawn from RA_CUSTOMER_TRX, RA_CUSTOMER_TRX_LINES, RA_CUST_TRX_LINE_GL_DIST, and RA_CUST_TRX_TYPES, with commitments and related exposure tracked via AR_PAYMENT_SCHEDULES and AR_ADJUSTMENTS. Refund and receipt configuration is validated against AR_RECEIPT_CLASSES, AR_RECEIPT_METHODS, AR_RECEIPT_METHOD_ACCOUNTS, RA_CUST_RECEIPT_METHODS, CE_BANK_ACCOUNTS, CE_BANK_ACCT_USES, and CE_BANK_BRANCHES_V. Batch and defaulting context is provided by RA_BATCHES, RA_BATCH_SOURCES, RA_TERMS, RA_SALESREPS, AR_SYSTEM_PARAMETERS, FND_CURRENCIES, and AR_LOOKUPS.

Usage Notes

ARP_PROCESS_CREDIT_UTIL is invoked indirectly by Receivables credit memo and adjustment forms, by the Credit Memo and AutoInvoice-related concurrent programs, and by custom extensions that need to reproduce standard credit-processing rules. Because it is classified as a utility and is not referenced by other database objects, it should be treated as a supporting library rather than a public API: custom code calling it directly must be aware that its interface is internal to Oracle and may change between patch levels. Its dependency on profile options and system parameters means the package must be initialized in the correct operating-unit context before its validation and defaulting routines return meaningful values.