Search Results ece_cdmo_trx_number_v




Overview
Explore in AI Chat

Overview

ECE_CDMO_TRX_NUMBER_V is a reporting view owned by the APPS schema within the Oracle E-Business Suite e-Commerce Gateway (EC) module. It exposes the credit and debit memo transaction numbers that are pending outbound transmission to customers through the Credit/Debit Memo (812 - CREADV / DEBADV) EDI transaction set. The view functions as a bridge between Receivables transaction data and the trading partner configuration held in the e-Commerce Gateway tables, isolating only those records that are complete, marked for printing, and not yet processed through the EDI pipeline.

Because the view is keyed on the RA_CUSTOMER_TRX.PRINTING_PENDING column, it is frequently consulted during the credit memo printing cycle. Users searching the term "printing_pending" are typically diagnosing why a memo has not appeared on an outbound 812 file, or why it remains visible to the printing process. This view answers that question by returning every qualifying memo whose PRINTING_PENDING flag is 'Y', whose PRINTING_OPTION is 'PRI', and whose EDI processed status is still open (ED, PR, or EP) with the EDI processed flag clear.

Underlying Base Objects

The view is defined over eight base objects, all referenced in the APPS schema as synonyms:

Joins flow from the transaction to the customer hierarchy, then through the account site to the trading partner header, and finally to the trading partner detail row matching the transaction type.

Key Columns

  • TRX_NUMBER — the visible credit or debit memo number presented to the customer.
  • CUSTOMER_TRX_ID — the internal primary key of the Receivables transaction, used to drill back to RA_CUSTOMER_TRX.
  • DOCUMENT_TYPE — the transaction type code (CM or DM), derived from RA_CUST_TRX_TYPES.TYPE.
  • CUSTOMER_ID — the bill-to customer account identifier from HZ_CUST_ACCOUNTS.
  • CUSTOMER_NAME — the bill-to party name from HZ_PARTIES.

Common Use Cases and Queries

Typical uses include verifying which memos are queued for the 812 outbound extract, reconciling printing_pending records that never reach the EDI interface, and confirming trading partner enablement for CM/DM document types.

A basic listing of pending outbound memos:

  • SELECT trx_number, document_type, customer_name FROM ece_cdmo_trx_number_v ORDER BY trx_number;
  • SELECT customer_trx_id, trx_number FROM ece_cdmo_trx_number_v WHERE document_type = 'CM';

To investigate a memo that remains pending, join the view back to RA_CUSTOMER_TRX on CUSTOMER_TRX_ID and inspect the EDI_PROCESSED_STATUS, EDI_PROCESSED_FLAG and PRINTING_OPTION values. If the row is absent from the view despite PRINTING_PENDING = 'Y', the cause is usually a missing ECE_TP_DETAILS row, EDI_FLAG not set to 'Y', or a document type not matching CM/DM.