Results for “interface_attribute1”

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

Overview

ECE_CDMO_HEADER_1_V is a private APPS-owned view in the Oracle E-Business Suite 12.1.1 and 12.2.2 environments, registered under the e-Commerce Gateway product (EC). Its documented purpose is to extract additional header information for the outbound Credit/Debit Memo transaction, identified by the EDI transaction set 812 with the CREADV and DEBADV business document codes. Within the Credit/Debit Memo outbound extraction flow, the primary header data is derived from RA_CUSTOMER_TRX; this view supplies the supplementary header attributes — shipping, equipment, packing, and interface attribute segments — that the standard 812 mapping does not retrieve from the base transaction tables alone. The view is marked with a lifecycle status of active and a scope of private, meaning it is an internal implementation object referenced by the e-Commerce Gateway extraction logic rather than a publicly documented dictionary object. Its display name in the repository is "Credit/Debit Memo Header Attributes View," reflecting its role as a header-level attribute supplement for the 812 outbound process.

Underlying Base Objects

The documented base objects for this view span Accounts Receivable, Shipping Execution, and general reference data. The view joins RA_CUSTOMER_TRX and RA_CUSTOMER_TRX_LINES (aliased RCT and RCTL in the view text) to supply the transaction identifier, line identifier, line type, and the interface and descriptive flexfield attribute columns. Shipping data is sourced from WSH_DELIVERY_DETAILS, WSH_DELIVERY_LEGS, WSH_DOCUMENT_INSTANCES, WSH_TRIPS, and WSH_TRIP_STOPS, which are used to derive the delivery detail identifier, the packing slip sequence number, and the equipment and routing attributes carried on the trip. Organization context is resolved through MTL_PARAMETERS, HR_ALL_ORGANIZATION_UNITS, HR_ALL_ORGANIZATION_UNITS_TL, and HR_ORGANIZATION_INFORMATION, exposed as the ship-from organization code. HR_SECURITY is referenced as a package to enforce organization-level access restrictions on the organization data. GL_SETS_OF_BOOKS is included among the referenced objects, consistent with ledger context used in the broader Credit/Debit Memo extraction. The view therefore depends on the AR transaction schema, the WSH trip and delivery schema, and standard HR/MTL organization tables, joined on transaction, delivery detail, trip stop, and organization keys.

Key Columns

The view exposes transaction keys and attribute segments alongside shipping-specific columns. The user's search term, equipment_number, maps directly to the EQUIPMENT_NUMBER column, which is derived as SUBSTR(WTP.VEHICLE_NUMBER, NVL(LENGTH(RTRIM(WTP.VEHICLE_NUMBER,'0123456789')),0)+1). In effect, the view separates a vehicle number into a non-numeric prefix and a numeric component: EQUIPMENT_PREFIX holds RTRIM(WTP.VEHICLE_NUMBER,'0123456789') and EQUIPMENT_NUMBER holds the remaining numeric portion beginning at the first digit. This is significant when populating EDI equipment identification fields, where the standard distinguishes an equipment prefix (often the owning carrier's alpha code) from the equipment number itself. Other notable columns include TRANSACTION_ID and CUSTOMER_TRX_LINE_ID from RA_CUSTOMER_TRX and RA_CUSTOMER_TRX_LINES, SHIP_FROM_CODE_INT from the organization code, ROUTING_INSTRUCTIONS truncated to 150 characters, PACKING_SLIP_NUMBER as the delivery detail sequence, PICKING_LINE_ID as the delivery detail identifier, and INTERFACE_ATTRIBUTE_CATEGORY with INTERFACE_ATTRIBUTE1 through INTERFACE_ATTRIBUTE15 from RA_CUSTOMER_TRX interface columns. TRANSACTION_ATTRIBUTE_CATEGORY and the TRANSACTION_ATTRIBUTE1 through n columns carry the descriptive flexfield values defined on the transaction header.

Common Use Cases and Queries

This view is typically consumed by the e-Commerce Gateway 812 outbound extraction, by diagnostic queries that verify what attribute data will be transmitted for a given credit or debit memo, and by extension and mapping work where additional header attributes are added to the outbound document. A representative query to inspect equipment and routing values for a transaction follows:

• SELECT transaction_id, ship_from_code_int, equipment_prefix, equipment_number, routing_instructions, packing_slip_number FROM apps.ece_cdmo_header_1_v WHERE transaction_id = :customer_trx_id;
• SELECT transaction_id, interface_attribute_category, interface_attribute1, interface_attribute2, transaction_attribute_category, transaction_attribute1 FROM apps.ece_cdmo_header_1_v WHERE transaction_id = :customer_trx_id;
• SELECT equipment_prefix, equipment_number, packing_slip_number, ship_from_code_int FROM apps.ece_cdmo_header_1_v WHERE equipment_number IS NOT NULL ORDER BY transaction_id;

Because the view is private, it should be treated as an implementation detail of the Credit/Debit Memo extraction rather than a stable public interface, and any customer extension should account for potential changes to its definition during patching or upgrade.