Search Results header_attribute1

Overview

ICX_SHOPPING_CARTS_V is a view owned by the APPS schema in Oracle E-Business Suite and is documented under the ICX product family, which covers Oracle iProcurement. Its documented description is "Web Requisitions Header View," identifying it as a reporting and integration access point for the header-level information associated with internet shopping carts that have not yet been submitted as requisitions in Purchasing. Because iProcurement builds requisitions in a staging area — the shopping cart — before final submission to Oracle Purchasing, this view exposes the editable cart header data, including descriptive flexfield context and segment columns, so that reports, extensions, and interfaces can query cart contents without tightly coupling to the transactional cart tables.

Underlying Base Objects

The view is defined as a join over two documented base objects, both referenced through synonyms in the APPS schema:

• ICX_SHOPPING_CARTS — the primary cart header entity, aliased ISC in the view text, supplying cart identity, shopper information, saved and emergency flags, approver details, requisition numbering, reserved purchase order number, header description, header attribute columns, note-to-buyer text, destination attributes, need-by date, deliver-to information, and ORG_ID.
• ICX_CART_DISTRIBUTIONS — the cart distribution/accounting entity, aliased ICD, supplying the distribution identifier and the thirty generic charge account segment columns (CHARGE_ACCOUNT_SEGMENT1 through CHARGE_ACCOUNT_SEGMENT30).

The join ties distribution lines to their parent shopping cart, so each row of the view represents a cart header combined with one of its distributions. Consumers should therefore be aware that a single logical shopping cart may appear on multiple rows when more than one distribution exists.

Key Columns

• CART_ID / SHOPPER_ID — the unique cart identifier and the user who owns the cart.
• SAVED_FLAG / EMERGENCY_FLAG — indicators for saved carts and emergency (non-catalog) requisitions.
• APPROVER_ID / APPROVER_NAME / NOTE_TO_APPROVER — approval routing information captured at the cart header.
• REQ_NUMBER_SEGMENT1 / RESERVED_PO_NUM — requisition number segment and reserved purchase order number reserved against the cart.
• HEADER_DESCRIPTION / NOTE_TO_BUYER — header-level free text passed to the requisition and buyer.
• HEADER_ATTRIBUTE_CATEGORY and HEADER_ATTRIBUTE1 through HEADER_ATTRIBUTE15 — the descriptive flexfield context and segment values for the requisition header. HEADER_ATTRIBUTE1 is the first of these fifteen segments and is the column most frequently referenced by users searching for customized header DFF data.
• DESTINATION_TYPE_CODE / DESTINATION_ORGANIZATION_ID / DELIVER_TO_LOCATION_ID / DELIVER_TO_LOCATION / DELIVER_TO_REQUESTOR_ID / DELIVER_TO_REQUESTOR — destination and deliver-to resolution for the eventual requisition.
• NEED_BY_DATE — requested need-by date.
• DISTRIBUTION_ID and CHARGE_ACCOUNT_SEGMENT1–30 — distribution identity and the account segments used to build the charge account.
• ORG_ID — the operating unit owning the cart row.

Common Use Cases and Queries

Typical uses include auditing incomplete or saved carts, verifying that a descriptive flexfield segment such as HEADER_ATTRIBUTE1 has been populated before submission, reconciling cart distributions to accounting flexfield values, and building custom reports or interfaces over requisition staging data. Because ORG_ID is exposed, queries should be constrained by operating unit.

A representative query listing carts for an operating unit with their first header DFF segment:

• SELECT cart_id, shopper_id, req_number_segment1, header_attribute_category, header_attribute1, need_by_date FROM apps.icx_shopping_carts_v WHERE org_id = :p_org_id AND saved_flag = 'Y' ORDER BY creation_date DESC;

To isolate carts where the first header DFF segment is populated:

• SELECT cart_id, shopper_id, header_attribute1 FROM apps.icx_shopping_carts_v WHERE header_attribute1 IS NOT NULL;

To correlate a cart with its charge account segments:

• SELECT cart_id, distribution_id, charge_account_segment1, charge_account_segment2, charge_account_segment3 FROM apps.icx_shopping_carts_v WHERE cart_id = :p_cart_id;

Because the underlying structures are owned by iProcurement and may change across patch levels, custom code should reference the view rather than the base tables and should avoid assumptions about the number of distribution rows returned per cart.