Results for “cart_line_id”

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

Overview

ICX_CART_LINE_DISTRIBUTIONS is the distribution-level detail table for Oracle iProcurement web requisitions, residing in the ICX schema. While a shopping cart line records what a requester intends to buy, this table records how the cost of that line is allocated across accounting distributions: charge accounts, accrual, variance, and budget accounts, allocation methods, and supporting descriptive flexfield context. In Oracle EBS 12.1.1 and 12.2.2 it is a core staging object for iProcurement checkout, holding requisition distribution data before it is transferred into the purchasing and General Ledger account structures.

Roughly 64 columns are documented physically, reflecting the wide account-segment and DFF storage typical of EBS distribution tables. Based on the foreign key topology — a mandatory parent reference to ICX_SHOPPING_CART_LINES plus references outward to GL_CODE_COMBINATIONS — the heuristic Data Vault classification is satellite-leaning. It should be treated as a dependent detail entity whose grain is one row per distribution of a cart line.

Key Information Stored

• DISTRIBUTION_ID — surrogate primary key of the row (ICX_CART_LINE_DISTRIBUTION_PK1).
• CART_LINE_ID — foreign key to ICX_SHOPPING_CART_LINES identifying the parent cart line; part of the unique key ICX_CART_LINE_DISTRIBUTIONS_U1 (CART_LINE_ID, DISTRIBUTION_ID).
• DISTRIBUTION_NUM — business-key candidate (ICX_CART_LINE_DISTRIBUTION_UK1) that sequences distributions within a line and is also referenced by ICX_REQ_CART_ERRORS.
• CHARGE_ACCOUNT_ID — foreign key to GL_CODE_COMBINATIONS for the primary charge account.
• CHARGE_ACCOUNT_SEGMENT1 … SEGMENT30 — denormalized account segment values that mirror the code combination at entry time.
• ACCRUAL_ACCOUNT_ID, VARIANCE_ACCOUNT_ID, BUDGET_ACCOUNT_ID — alternative accounting references used for accrual, variance, and budgetary postings.
• ORG_ID — operating unit, enabling multi-org (MOAC) querying and security.
• CART_ID — the parent shopping cart, useful for cart-level reporting without joining through the line table.
• ALLOCATION_TYPE, ALLOCATION_VALUE, ALLOCATION_QUANTITY — how quantity or amount is split across distributions (percentage, amount, or quantity based).
• DIST_ATTRIBUTE_CATEGORY and DISTRIBUTION_ATTRIBUTE1 … ATTRIBUTE15 — descriptive flexfield context and values for distribution-level DFF data.
• CHARGE_ACCOUNT_NUM — the concatenated charge account string.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns for row provenance and change tracking.

Common Use Cases and Queries

Typical reporting scenarios include requisition distribution detail for cost-center chargeback, validation of account data before requisition import, and troubleshooting failed iProcurement submissions using error rows in ICX_REQ_CART_ERRORS.

A common query joins distributions to their cart line and operating unit:

• SELECT d.CART_LINE_ID, l.CART_ID, d.DISTRIBUTION_NUM, d.CHARGE_ACCOUNT_NUM, d.ALLOCATION_TYPE, d.ALLOCATION_VALUE FROM ICX_CART_LINE_DISTRIBUTIONS d, ICX_SHOPPING_CART_LINES l WHERE d.CART_LINE_ID = l.CART_LINE_ID AND d.ORG_ID = :p_org_id
• To validate that a charge account is a valid GL combination: join d.CHARGE_ACCOUNT_ID to GL_CODE_COMBINATIONS.CODE_COMBINATION_ID.
• To isolate checkout failures: join ICX_REQ_CART_ERRORS on CART_LINE_ID = CART_LINE_ID and DISTRIBUTION_NUM = DISTRIBUTION_NUM.

Related Objects

• ICX_SHOPPING_CART_LINES — parent table; join on CART_LINE_ID.
• GL_CODE_COMBINATIONS — account validation reference; join on CHARGE_ACCOUNT_ID.
• ICX_REQ_CART_ERRORS — error logging table referencing this table via CART_LINE_ID and DISTRIBUTION_NUM.
• PO_REQUISITION_HEADERS_ALL / PO_REQUISITION_LINES_ALL / PO_REQ_DISTRIBUTIONS_ALL — downstream purchasing tables populated once a checkout succeeds.
• ICX_CART_LINES — cart line context in the iProcurement schema used during requisition creation.
• PO_APPROVAL / iProcurement Requisition APIs — processes consuming the distribution rows during submission and approval.