Results for “charge_account_segment1”

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

Overview

ICX_CART_LINE_DISTRIBUTIONS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, classified under the ICX product family (Oracle iProcurement). ETRM documents it as the "Web Requisitions Line Distributions View." Its purpose is to expose the account distribution detail associated with shopping cart lines — the pre-requisition artifacts created through iProcurement that ultimately flow into Oracle Purchasing requisitions. Because the cart-line distribution records are the authoritative source for how a requisition line will be charged across accounting flexfield segments, the view serves as a stable read interface for both reporting and integration logic.

In the 12.1.1 and 12.2.2 release streams, this view is particularly relevant to developers who locate requisition accounting information by way of a cart_line_id. The view preserves the standard EBS audit and WHO-style columns while flattening the accounting flexfield into individually addressable segments, making it convenient for SQL-based reporting without requiring a join to FND_FLEX_VALUES_VL or similar construct. The object is documented as VALID in the ETRM repository.

Underlying Base Objects

Per the documented metadata, the view's single referenced base object is ICX_CART_LINE_DISTRIBUTIONS, exposed to APPS through a synonym. The view definition is a direct SELECT over that table with no joins, unions, or aggregation. Every column listed in the view text maps one-to-one to a column of the base distribution table, which means no derived or transformed values are introduced at the view layer.

The consequence for support and tuning purposes is straightforward: all column data types, the presence of the 30 charge-account segments, and the fifteen distribution attribute columns are inherited unchanged. Because the base object is referenced as a synonym rather than with a fully qualified schema prefix, the view resolves within the APPS naming context, consistent with the convention used throughout the ICX schema objects. The documentation does not identify any additional functions or sub-views beneath the definition.

Key Columns

• CART_LINE_ID — The primary linkage column requested in the originating search. Joins the distribution row to its parent iProcurement cart line; this is the key used to retrieve all distributions for a given line.
• DISTRIBUTION_ID / DISTRIBUTION_NUM — Surrogate and ordinal identifiers for the distribution itself, allowing multiple distributions to be distinguished within one cart line.
• CHARGE_ACCOUNT_ID — The full accounting flexfield combination identifier, which can be resolved against the code combination table.
• CHARGE_ACCOUNT_SEGMENT1 ... CHARGE_ACCOUNT_SEGMENT30 — The individually flattened accounting flexfield segments. The presence of thirty segments reflects a flexible chart-of-accounts configuration rather than a fixed structure.
• CHARGE_ACCOUNT_NUM — A formatted or concatenated representation of the charge account, useful for display without segment assembly.
• DIST_ATTRIBUTE_CATEGORY / DISTRIBUTION_ATTRIBUTE1 ... 15 — Descriptive flexfield context and attribute values captured at distribution level.
• ACCRUAL_ACCOUNT_ID, VARIANCE_ACCOUNT_ID, BUDGET_ACCOUNT_ID — Secondary accounting identifiers supporting accrual, variance, and budgetary accounting treatment.
• CART_ID / ORG_ID — Parent cart identifier and the operating unit or inventory organization context.
• ALLOCATION_TYPE, ALLOCATION_VALUE, ALLOCATION_QUANTITY — Fields describing how quantity or amount is apportioned to the distribution.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical usage centers on retrieving the accounting distributions associated with a specific cart line, either for reporting validation, data migration, or troubleshooting why a requisition carried unexpected account segments. The simplest access pattern filters on the cart_line_id.

SELECT cart_line_id, distribution_id, distribution_num, charge_account_id, charge_account_segment1, charge_account_segment2, charge_account_num, allocation_type, allocation_value
FROM apps.icx_cart_line_distributions_v
WHERE cart_line_id = :p_cart_line_id
ORDER BY distribution_num;

A second common pattern aggregates distributions by cart to validate allocation totals against the parent cart amount, or joins the view to ICX_CART_LINES to reconcile line-level and distribution-level information. Analysts also query by ORG_ID and CREATION_DATE to extract distribution activity for a period. Because the view performs no filtering of its own, any predicate such as org context or date range must be supplied explicitly by the calling query.