Search Results cash_payment

Overview

APPS.CE_DOCUMENTS_PAYABLE is a Cash Management (CE) view that presents payment transactions in the standardized Oracle Payments "document payable" format. Its principal purpose is to expose records from the Cash Management payment transactions table to the Oracle Payments funds capture and disbursement engine, exposing each row as a payable document with the calling application identified as "260". The view maps Cash Management transaction attributes onto the generic Payments interface columns — calling application identifiers, payment function, payment date, currency, amount, payment method, bank accounts, and remittance detail — so that the payment instruction subsystem can process cash payments uniformly alongside invoices, expense reports, and other payable sources.

Because the transaction reference number is projected into CALLING_APP_UNIQUE_REF1 and CALLING_APP_DOC_REF_NUMBER, the view supports traceability back to the originating Cash Management transaction. The fixed literal 'CASH_PAYMENT' in the PAYMENT_FUNCTION column is the distinguishing marker that identifies this view as the cash payment integration point; applications and concurrent programs filter on this value to isolate cash payments from other payable document types.

Underlying Base Objects

The view's documented base object is the synonym CE_PAYMENT_TRANSACTIONS, which resolves to the Cash Management payment transactions table in the APPS schema. The view is a straightforward SELECT — it contains no joins to supplier, purchase order, or payment profile tables. Columns that have no Cash Management counterpart, such as PO_NUMBER, DISCOUNT_DATE, PAYMENT_DUE_DATE, SUPPLIER_SITE_ID, and UNIQUE_REMITTANCE_IDENTIFIER, are populated with NULL so that the projected row set conforms exactly to the Payments document payable interface expected by the calling application.

Key Columns

• PAY_PROC_TRXN_TYPE_CODE — sourced from I.TRANSACTION_TYPE; identifies the payment processing transaction type.
• CALLING_APP_ID — hard-coded to '260', the Oracle Payments calling application identifier for Cash Management.
• CALLING_APP_UNIQUE_REF1 / CALLING_APP_DOC_REF_NUMBER — both hold I.TRXN_REFERENCE_NUMBER, providing the unique document reference.
• CALL_APP_PAY_SERVICE_REQ_CODE — the Cash Management payment request number.
• PAYMENT_FUNCTION — literal 'CASH_PAYMENT'; the key discriminator for this view.
• PAYMENT_DATE / DOCUMENT_DATE — both derived from I.TRANSACTION_DATE; ANTICIPATED_VALUE_DATE carries I.ANTICIPATED_VALUE_DATE.
• DOCUMENT_TYPE / DOCUMENT_DESCRIPTION — from I.TRANSACTION_TYPE and I.TRANSACTION_DESCRIPTION.
• DOCUMENT_CURRENCY_CODE / PAYMENT_CURRENCY_CODE — both I.PAYMENT_CURRENCY_CODE.
• DOCUMENT_AMOUNT / PAYMENT_AMOUNT — both I.PAYMENT_AMOUNT, so no withholding, discount, or charge amounts are expressed.
• PAYMENT_METHOD_CODE — I.PAYMENT_METHOD_CODE; PAYMENT_PROFILE_ID is NULL.
• EXCLUSIVE_PAYMENT_FLAG — literal 'Y'.
• INTERNAL_BANK_ACCOUNT_ID / EXTERNAL_BANK_ACCOUNT_ID — the source and external bank accounts on the transaction.
• PAYEE_PARTY_ID / PARTY_SITE_ID — destination party and party site; SUPPLIER_SITE_ID is NULL.
• ORG_ID / LEGAL_ENTITY_ID — both I.SOURCE_LEGAL_ENTITY_ID; ORG_TYPE is the literal 'LEGAL_ENTITY'.
• BANK_CHARGE_BEARER, PAYMENT_REASON_CODE, PAYMENT_REASON_COMMENTS — carried directly from the transaction.
• REMITTANCE_MESSAGE1..3 — remittance information passed through to the payment.
• DOC_SEQUENCE_ID — the document sequence identifier for the transaction.

Common Use Cases and Queries

Typical uses include reconciling cash payments fed to Oracle Payments, validating the mapped amounts and dates before payment processing, and building custom reports on cash payment activity by legal entity or bank account.

Listing cash payment documents by currency and legal entity:

SELECT calling_app_unique_ref1, payment_date, payment_currency_code,
       payment_amount, payment_method_code, legal_entity_id
FROM   apps.ce_documents_payable
WHERE  payment_function = 'CASH_PAYMENT'
ORDER BY payment_date;

Auditing the bank account and payee mapping for a specific transaction reference:

SELECT calling_app_unique_ref1, internal_bank_account_id,
       external_bank_account_id, payee_party_id, party_site_id,
       anticipated_value_date
FROM   apps.ce_documents_payable
WHERE  calling_app_id = '260'
AND    calling_app_unique_ref1 = :trxn_reference_number;

Because DOCUMENT_AMOUNT and PAYMENT_AMOUNT are identical and the withholding, discount, and charge columns are NULL, any reconciliation query must source those components from the underlying Cash Management transaction rather than from this view.