Search Results cn_sca_headers_interface_u1




Overview
Explore in AI Chat

Overview

CN.CN_SCA_HEADERS_INTERFACE_ALL is the Sales Credit Assignment (SCA) header interface table owned by the CN (Sales Crediting) schema in Oracle E-Business Suite, documented as VALID in the ETRM repository for releases 12.1.1 and 12.2.2. Its stated purpose is to hold transactions that require processing by the Sales Credit Engine. Rows are staged here before the crediting engine evaluates transaction lines against credit rules and assigns sales credit splits. The table stores 118 columns in total and resides in the APPS_TS_TX_DATA tablespace with a PCTFREE of 10, which reflects its role as a high-volume transactional staging object rather than a reference table.

The heuristic Data Vault classification mined from the foreign-key structure is standalone, meaning the object has no upstream parent hub relationships beyond a security-group reference and is best modeled as an independent staging or keyed table rather than as a link or satellite. Its uniqueness is enforced by two unique indexes, so it functions as its own grain definition.

Key Information Stored

The physical primary key is the surrogate identifier SCA_HEADERS_INTERFACE_ID, a NUMBER column described as the unique identifier. Two business-key candidates are enforced by unique indexes:

Other business columns of note include TRANSACTION_SOURCE (a lookup code from SCA_TRX_SOURCES; for Order Information Center the value is CN), SOURCE_TYPE (ORD for an order or INV for an invoice), SOURCE_ID (the order or invoice number), SOURCE_LINE_ID (the corresponding order or invoice line number), TRANSACTION_AMOUNT (the aggregate amount at order or invoice line level), and CREDIT_RULE_ID, which points to the credit rule applied. Control columns drive the processing lifecycle: PROCESSED_DATE, PROCESS_STATUS, and TRANSACTION_STATUS. Standard EBS who-columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER), ORG_ID, and SECURITY_GROUP_ID are also present. ATTRIBUTE1 through ATTRIBUTE100 provide descriptive flexfield segments.

Common Use Cases and Queries

Typical usage centers on monitoring the crediting backlog and reconciling source transactions to credit assignments. The non-unique indexes support the common access paths directly: N1 on PROCESSED_DATE, N2 on TRANSACTION_STATUS, and N3 on PROCESS_STATUS. A frequent pattern is a status-driven backlog report:

  • Select unprocessed rows: SELECT source_type, source_id, source_line_id, transaction_amount FROM cn_sca_headers_interface_all WHERE process_status = 'UNPROCESSED' AND org_id = :p_org_id.
  • Reconcile a specific source line using the U2 business key: WHERE source_type = 'ORD' AND source_id = :order_number AND source_line_id = :line_number.
  • Ageing of pending credit: filter on processed_date IS NULL and group by TRANSACTION_STATUS.

Administrators also query the table after running the Sales Credit Engine concurrent program to confirm that the expected transaction lines were consumed, and to diagnose rows that remain staged due to missing or invalid credit rules.

Related Objects

The documented foreign key SECURITY_GROUP_ID references FND_SECURITY_GROUPS, tying each row to a security group for multi-tenant data isolation. TRANSACTION_SOURCE values are validated against the SCA_TRX_SOURCES lookup table, and CREDIT_RULE_ID resolves to the credit rule definitions used by the Sales Credit Engine (the CN_SCA_RULES domain). The source transactions themselves originate in OE_ORDER_HEADERS_ALL and OE_ORDER_LINES_ALL for order-based feeds (SOURCE_TYPE = ORD) and in RA_CUSTOMER_TRX_ALL and RA_CUSTOMER_TRX_LINES_ALL for invoice-based feeds (SOURCE_TYPE = INV), joined on the SOURCE_ID and SOURCE_LINE_ID business key. Downstream, processed rows drive the Sales Credit Engine's assignment output and are commonly reconciled against CN_SALES_CREDITS_ALL. Column-level traceability is provided by the FND design data repository entry CN.CN_SCA_HEADERS_INTERFACE_ALL.