Results for “order_source_id”

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

Overview

ICX_WEB_STORE_OPTIONS is an Oracle iProcurement (ICX product family) configuration table owned by the ICX schema. As its ETRM description states, it stores "default values for Web Store system configurable options per operating unit." In effect, it is the authoritative repository of storefront-level defaults that iProcurement consults when rendering the Web Store, resolving pricing, order sourcing, and purchasing behavior for a given operating unit (ORG_ID). Because the Web Store behaves differently across organizations, this table provides the per-OU override layer that governs how requisitions are priced, which order types and sources apply, and how guest or credit-card purchasing is handled.

From a Data Vault modeling perspective, the heuristic classification mined from the foreign-key structure is link. This is a reasonable suggestion: the table's identity is anchored by a single primary key column (ORG_ID, via ICX_WEB_STORE_OPTIONS_PK) that ties a configuration record to an operating unit, and its many outbound foreign keys connect that record to price lists, order sources, order types, category sets, receipt methods, and items. It therefore functions more as a relationship/association record binding configuration attributes to an operating unit than as a pure descriptive satellite.

Key Information Stored

The table contains 34 documented columns. The most operationally significant include:

• ORG_ID — The operating unit, and the sole column of the primary key ICX_WEB_STORE_OPTIONS_PK. It is the business-key anchor that makes every other setting OU-specific.
• PRICE_LIST_ID — The default price list for the storefront (FK to SO_PRICE_LISTS_B).
• GUEST_PRICE_LIST_ID, GUEST_USERNAME, GUEST_PASSWORD — Guest-shopping configuration and pricing.
• ORDER_TYPE_ID, ORDER_SOURCE_ID, USE_WEB_ORDER_TYPE, USE_WEB_PRICE_LIST — Order sourcing/typing defaults and toggles controlling whether web order types and price lists are honored.
• CATEGORY_SET_ID — Default category set (FK to MTL_CATEGORY_SETS_B) used for catalog browsing.
• NON_SHIPITEM_ID — Item used for non-shippable lines (FK to MTL_SYSTEM_ITEMS_B).
• USE_ORDER_IMPORT_PRICING_RULES, FREIGHT_AMT, FREIGHT_FLAG — Pricing-rule and freight defaults.
• CONSUMER_ALLOW_CREDIT_CARDS, PARTNER_ALLOW_CREDIT_CARDS, CREDIT_CARD_ORDER_TYPE_ID, RECEIPT_METHOD_ID — Credit-card and receipt-method controls.
• ENABLE_EMAIL, ENABLE_CALL_BACK, DEFAULT_EMAIL_ADDRESS, EMAIL_CARTRIDGE_PATH, OTS_CARTRIDGE_PATH — Notification and cartridge configuration.
• ITEM_TEMPLATE, CATEGORY_TEMPLATE, ITEM_DESC, DEFAULT_UOM, FCURRENCY_CODE, COMPANY_HOME_PAGE_URL — Display and defaulting attributes.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns.

ORG_ID serves as the surrogate/primary key, while the remaining configuration columns are descriptive business attributes rather than standalone unique keys.

Common Use Cases and Queries

The most frequent use is retrieving the effective storefront configuration for a single operating unit during troubleshooting or setup validation:

SELECT ORG_ID, PRICE_LIST_ID, GUEST_PRICE_LIST_ID, ORDER_TYPE_ID,
       ORDER_SOURCE_ID, CATEGORY_SET_ID, NON_SHIPITEM_ID,
       CONSUMER_ALLOW_CREDIT_CARDS, PARTNER_ALLOW_CREDIT_CARDS,
       USE_WEB_PRICE_LIST, USE_WEB_ORDER_TYPE
FROM   ICX.ICX_WEB_STORE_OPTIONS
WHERE  ORG_ID = :p_org_id;

Reporting scenarios include auditing which OUs share a common price list or order source, comparing guest versus registered pricing configurations, and confirming credit-card enablement across organizations. Joining to SO_PRICE_LISTS_B, SO_ORDER_TYPES_115_ALL, and MTL_CATEGORY_SETS_B produces a human-readable configuration matrix, and the WHO columns support change-tracking audits.

Related Objects

• SO_PRICE_LISTS_B — referenced twice via PRICE_LIST_ID and GUEST_PRICE_LIST_ID.
• SO_ORDER_SOURCES_115 — via ORDER_SOURCE_ID.
• SO_ORDER_TYPES_115_ALL — via ORDER_TYPE_ID (and CREDIT_CARD_ORDER_TYPE_ID).
• MTL_SYSTEM_ITEMS_B — via NON_SHIPITEM_ID.
• MTL_CATEGORY_SETS_B — via CATEGORY_SET_ID.
• AR_RECEIPT_METHODS — via RECEIPT_METHOD_ID.

These foreign-key relationships confirm that ICX_WEB_STORE_OPTIONS acts as the configuration hub binding each operating unit to its pricing, sourcing, catalog, and payment dependencies within iProcurement.