Search Results icx_cart_line_distributions




Overview
Explore in AI Chat

Overview

The ICX_CART_LINE_DISTRIBUTIONS table is a core data object within the Oracle iProcurement (ICX) module of Oracle E-Business Suite (EBS) releases 12.1.1 and 12.2.2. It functions as the transactional repository for accounting distribution lines associated with items in a web-based shopping cart or requisition. When a requester adds items to a cart in iProcurement, the system creates one or more distribution records for each cart line to define the accounting charge. This table is essential for capturing the financial dimensions of a requisition before it is converted into a standard Purchase Requisition in the Purchasing (PO) module, ensuring proper accounting validation and fund checking during the requisitioning process.

Key Information Stored

The table's primary purpose is to store accounting distribution details for requisition lines. Its structure is defined by key columns that link to other master and transactional entities. The primary identifier is DISTRIBUTION_ID, a unique system-generated sequence. The DISTRIBUTION_NUM, combined with the CART_LINE_ID, forms a unique key (ICX_CART_LINE_DISTRIBUTION_UK1) to identify a specific distribution within a cart line. The most critical foreign key relationship is through the CART_LINE_ID, which links each distribution to its parent record in the ICX_SHOPPING_CART_LINES table. The accounting flexfield details are stored via the CHARGE_ACCOUNT_ID, which references the GL_CODE_COMBINATIONS table. Other typical columns, inferred from standard EBS distribution models, would include amounts (e.g., DISTRIBUTION_AMOUNT), percentages, and project accounting references (like TASK_ID, EXPENDITURE_TYPE), though these are not explicitly listed in the provided metadata.

Common Use Cases and Queries

This table is central to troubleshooting, reporting, and data validation for iProcurement transactions. A common use case is investigating requisitions that fail to import into Purchasing due to invalid accounting data. The link to the ICX_REQ_CART_ERRORS table, as shown in the metadata, is critical for this analysis. Database administrators and functional consultants often query this table to analyze distribution patterns or reconcile data. A sample query to retrieve distribution details for a specific cart would be:

  • SELECT d.distribution_num, d.distribution_amount, g.segment1, g.segment2
  • FROM icx_cart_line_distributions d,
  • gl_code_combinations g,
  • icx_shopping_cart_lines l
  • WHERE d.cart_line_id = l.cart_line_id
  • AND d.charge_account_id = g.code_combination_id
  • AND l.cart_id = :p_cart_id;

Reporting use cases include auditing charge account usage and analyzing requisition spending by accounting segment prior to PO creation.

Related Objects

The ICX_CART_LINE_DISTRIBUTIONS table has integral relationships with several other EBS objects, as confirmed by the foreign key metadata. The primary parent table is ICX_SHOPPING_CART_LINES, which holds the header information for each item in the cart. All distributions for a cart line are children of a single record in this table. For accounting validation, it references the GL_CODE_COMBINATIONS table via the CHARGE_ACCOUNT_ID column. Furthermore, errors encountered during the processing or validation of these distributions are logged in the ICX_REQ_CART_ERRORS table, which uses the DISTRIBUTION_NUM and CART_LINE_ID as a foreign key. This table's data is ultimately consumed by the requisition import process, which creates standard distributions in the PO_REQ_DISTRIBUTIONS_ALL table.