Search Results document_sequence_id

Overview

CE_DOCUMENTS_PAYABLE is a Cash Management (CE) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents payment-related transaction records in the canonical "documents payable" format required by the Oracle Payments payment instruction and document submission model. Rather than storing data itself, the view projects rows from the Cash Management payment transaction table into a normalized structure that the payment engine can consume when building payment instructions.

In practice the view acts as an integration and reporting bridge. It exposes a consistent set of payee, bank, currency, amount, and remittance attributes sourced from Cash Management transactions, which downstream processes, custom reports, and reconciliation queries can read without having to join the underlying CE tables directly. The view filters and re-labels columns so that Cash Management-originated payments appear as payable documents with an application ID of 260 (Cash Management) and a payment function of CASH_PAYMENT.

Underlying Base Objects

Per the documented ETRM metadata, the sole referenced base object is CE_PAYMENT_TRANSACTIONS, accessed through a synonym. The view text selects from this table using the alias I, mapping its columns into the standardized document layout. Because the definition is a straight projection with literal constants and NULL placeholders rather than a join, the view remains tightly coupled to the CE_PAYMENT_TRANSACTIONS structure. Columns that exist in the generic document contract but have no Cash Management analogue (for example PO_NUMBER, DISCOUNT_DATE, INTEREST_RATE, and SETTLEMENT_PRIORITY) are exposed as NULL to preserve column parity with the broader documents-payable interface.

Key Columns

• CALLING_APP_ID — hard-coded to '260', identifying Cash Management as the originating application.
• CALLING_APP_UNIQUE_REF1 / CALLING_APP_DOC_REF_NUMBER — both map to TRXN_REFERENCE_NUMBER, providing the unique transaction reference.
• PAYMENT_AMOUNT / DOCUMENT_AMOUNT — derived from I.PAYMENT_AMOUNT and I.PAYMENT_CURRENCY_CODE.
• PAYMENT_DATE / DOCUMENT_DATE — sourced from I.TRANSACTION_DATE; ANTICIPATED_VALUE_DATE maps to I.ANTICIPATED_VALUE_DATE.
• INTERNAL_BANK_ACCOUNT_ID / EXTERNAL_BANK_ACCOUNT_ID — from I.SOURCE_BANK_ACCOUNT_ID and I.EXT_BANK_ACCOUNT_ID.
• PAYEE_PARTY_ID / PARTY_SITE_ID — from I.DESTINATION_PARTY_ID and I.DESTINATION_PARTY_SITE_ID.
• ORG_ID / LEGAL_ENTITY_ID — both set to I.SOURCE_LEGAL_ENTITY_ID, with ORG_TYPE as 'LEGAL_ENTITY'.
• REMITTANCE_MESSAGE1..3 — carried straight from the base table for payment advice text.

Note that the view does not expose a REMIT_TO_LOCATION_ID column. Users searching on that identifier will not find it here; the closest party/location attributes are PAYEE_PARTY_ID and PARTY_SITE_ID. Remit-to location data resides in supplier and party site tables rather than in this Cash Management document projection.

Common Use Cases and Queries

Typical scenarios include auditing Cash Management payment documents, feeding payment instructions, and reconciling transaction references. A representative query is:

• SELECT calling_app_doc_ref_number, payment_amount, payment_currency_code, payment_date FROM ce_documents_payable WHERE payment_date BETWEEN :start_date AND :end_date;
• SELECT payee_party_id, party_site_id, payment_amount FROM ce_documents_payable WHERE internal_bank_account_id = :bank_account_id;

Because the view carries no remit-to location, obtaining that attribute requires joining to supplier site or party site tables on PAYEE_PARTY_ID and PARTY_SITE_ID.