Results for “ac_attribute2”

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

Overview

ECE_CDMO_ALLOWANCE_CHARGES_V is a private APPS-schema view in Oracle E-Business Suite, owned by the e-Commerce Gateway (EC) product. It extracts allowance and charge information for the outbound Credit/Debit Memo transaction — the 812 document, encompassing the CREADV and DEBADV message variants. The view is consumed both at the header level and at the line level of the outbound memo, providing the EDI translator with the special charge and allowance segments required by the 812 mapping. The @rep annotations in the metadata mark it as private scope under the AR product lineage, meaning it is an internal implementation object rather than a general-purpose reporting view, and it should not be treated as a stable public interface. It is defined over RA_CUSTOMER_TRX_LINES and is read when e-Commerce Gateway builds outbound credit and debit memo extracts.

Underlying Base Objects

The view is defined exclusively over RA_CUSTOMER_TRX_LINES, referenced through its APPS synonym. The driving query selects columns from that table and filters the result set on LINE_TYPE = 'FREIGHT', so only freight lines qualify as the allowance/charge source rows. Every transactional column in the projection is inherited directly from RA_CUSTOMER_TRX_LINES: the transaction identifier, line number, line type, customer transaction line identifier, and the link-to-customer-trxn-line identifier (coalesced to 0 via NVL). No other base tables, views, or joins appear in the documented SQL, and no aggregation or outer join is present.

Key Columns

The view exposes a fixed, wide projection. The populated columns are:

• TRANSACTION_ID — sourced from RCTL.CUSTOMER_TRX_ID; identifies the parent credit or debit memo.
• LINE_NUMBER and LINE_TYPE — the line sequence and the line type, which is always FREIGHT given the WHERE clause.
• CUSTOMER_TRX_LINE_ID — the unique line identifier.
• LINK_TO_CUST_TRX_LINE_ID — the associated line, returned as 0 when null.

The remaining columns — HEADER_DETAIL_INDICATOR, ALLOWANCE_CHARGE_INDICATOR, ALLOWANCE_CHARGE_AMOUNT, SPECIAL_CHARGES_CODE, SPECIAL_SERVICES_CODE, METHOD_HANDLING_CODE, ALLOWANCE_CHARGE_DESC, AGENCY_QUALIFIER_CODE, ALLOWANCE_CHARGE_RATE, ALLOWANCE_CHARGE_PCT_QUALIFIER, ALLOWANCE_CHARGE_PCT, ALLOWANCE_CHARGE_UOM_CODE, ALLOWANCE_CHARGE_QUANTITY, and the AC_ATTRIBUTE_CATEGORY plus AC_ATTRIBUTE1 through AC_ATTRIBUTE15 flexfield columns — are all projected as typed NULLs (TO_CHAR(NULL) or TO_NUMBER(NULL)). This placeholder technique preserves the expected 812 output column signature for the e-Commerce Gateway mapping while the substantive allowance/charge data is not sourced from the base table in this definition. Users searching on ac_attribute_category will find that column present but always null, since it is a placeholder for a descriptive flexfield category that is not populated by the documented SQL.

Common Use Cases and Queries

The view is used by the outbound 812 CREADV/DEBADV extract in e-Commerce Gateway and is typically queried by transaction to enumerate freight-related allowance and charge rows:

• Retrieve all allowance/charge lines for a specific memo: SELECT transaction_id, line_number, line_type, customer_trx_line_id, link_to_cust_trx_line_id FROM apps.ece_cdmo_allowance_charges_v WHERE transaction_id = :p_trx_id ORDER BY line_number;

• Inspect placeholder flexfield columns when diagnosing mapping expectations: SELECT customer_trx_line_id, ac_attribute_category, ac_attribute1 FROM apps.ece_cdmo_allowance_charges_v WHERE transaction_id = :p_trx_id;

Because the view is private and returns typed NULL placeholders for most business columns, it should be used only in the context of the e-Commerce Gateway outbound extract, and any custom query relying on the AC_ATTRIBUTE columns or allowance amounts should be validated against RA_CUSTOMER_TRX_LINES directly.