Search Results printing_pending




Overview
Explore in AI Chat

Overview

The view APPS.ECE_CDMO_TRX_NUMBER_V exposes a filtered, joined set of Oracle Receivables transactions that are eligible for the Oracle E-Commerce Gateway (ECE) outbound transaction-number process. Its most distinguishing filter, and the column most frequently searched in this context, is RA_CUSTOMER_TRX.PRINTING_PENDING = 'Y'. The view therefore answers the operational question of which credit memos and debit memos are complete, have printing pending, are assigned the PRI printing option, and are configured for EDI processing through the CDMO (Customer Direct Debit Memo / credit-debit memo) document definition.

Within EBS 12.1.1 and 12.2.2, this object serves as a read-only reporting and integration source. It is referenced by ECE code that generates outbound transaction-number data for trading partners, allowing the interface layer to identify documents that must still be printed and transmitted. Because it is a view and not a table, it holds no data of its own; all values are derived at query time from the underlying Receivables and ECE tables.

Underlying Base Objects

The ETRM 12.2.2 metadata documents the view as owned by APPS and defined over the following referenced base objects, each exposed through a synonym:

The joins bind each Receivables transaction to its customer account, party name, bill-to site use, and transaction type, then link the customer account site to a trading-partner header and detail record. The ECE detail record supplies the DOCUMENT_ID = 'CDMO' constraint, the EDI_FLAG = 'Y' condition, and the document-type match against RA_CUST_TRX_TYPES.TYPE.

Key Columns

  • TRX_NUMBER — the user-visible Receivables transaction number.
  • CUSTOMER_TRX_ID — the internal primary key of the transaction, used for drill-down to RA_CUSTOMER_TRX.
  • DOCUMENT_TYPE — the transaction type code from RA_CUST_TRX_TYPES.TYPE; the view restricts this to DM (debit memo) and CM (credit memo).
  • CUSTOMER_ID — the bill-to customer account identifier from HZ_CUST_ACCOUNTS.CUST_ACCOUNT_ID.
  • CUSTOMER_NAME — the party name from HZ_PARTIES.PARTY_NAME.

Common Use Cases and Queries

The canonical use case is identifying transactions awaiting print and EDI transmission. A direct inspection of pending items uses:

  • SELECT trx_number, customer_trx_id, document_type, customer_id, customer_name FROM apps.ece_cdmo_trx_number_v;
  • Joining CUSTOMER_TRX_ID back to RA_CUSTOMER_TRX to retrieve amounts, currency, and dates.
  • Grouping by DOCUMENT_TYPE or CUSTOMER_NAME to size pending outbound volumes.
  • Comparing the view output against the ECE outbound interface tables to reconcile documents not yet transmitted.

Because the view already enforces COMPLETE_FLAG = 'Y', PRINTING_PENDING = 'Y', and the EDI status conditions, queries against it should not re-apply those predicates unless the intent is to diagnose why a specific transaction is excluded.