Results for “ord_oneclick_id”

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

Overview

IBE.IBE_ORD_ONECLICK_ALL is an Oracle E-Business Suite table that stores express checkout, or "one-click," settings for registered customers of the iStore (IBE) module. In Oracle EBS 12.1.1 and 12.2.2, IBE provides the Oracle iStore storefront application, and this table persists the preferences that allow a recognized, logged-in customer to bypass repetitive entry of shipping, billing, and payment information during order submission. Each row represents a stored express-checkout configuration tied to a specific customer account and party, scoped to a given operating unit through ORG_ID.

From a data-modeling perspective, the mined Data Vault classification for this object is link. This heuristic reflects the table's role as an associative entity that connects a party, a customer account, and party sites (bill-to and ship-to) rather than serving as a standalone hub of business keys or a descriptive satellite. The link classification is a modeling suggestion derived from the foreign-key structure, not a formally declared Data Vault design.

Key Information Stored

The table is owned by the IBE schema and contains 36 documented columns. The most significant are summarized below.

• ORD_ONECLICK_ID — the surrogate primary key, enforced by IBE_ORD_ONECLICK_PK. It uniquely identifies each express-checkout record.
• CUST_ACCOUNT_ID and PARTY_ID — together with ORG_ID, these form the business-key candidate captured by the unique index IBE_ORD_ONECLICK_U1. They identify the customer account and the underlying party that owns the setting.
• ORG_ID — the operating unit that scopes the record for multi-org security and reporting.
• ENABLED_FLAG — indicates whether express checkout is active for the customer.
• BILL_TO_PTY_SITE_ID and SHIP_TO_PTY_SITE_ID — the default bill-to and ship-to party sites to be applied during one-click checkout.
• PAYMENT_ID — references the stored payment preference used for the express flow.
• FREIGHT_CODE — the default freight or shipping method associated with the setting.
• SECURITY_GROUP_ID — the security group reference used in multi-tenant or hosted deployments.
• OBJECT_VERSION_NUMBER — supports optimistic locking during concurrent updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns.
• REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE — concurrent program and request tracking columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the standard DFF-ready descriptive flexfield columns.

Common Use Cases and Queries

Application logic and reporting typically retrieve express-checkout settings during storefront session initialization and order submission, ensuring the correct defaults are applied for the registered customer.

• Retrieve a customer's one-click setting: SELECT * FROM IBE.IBE_ORD_ONECLICK_ALL WHERE CUST_ACCOUNT_ID = :cust_id AND PARTY_ID = :party_id AND ORG_ID = :org_id AND ENABLED_FLAG = 'Y';
• List enabled express users by operating unit: filter on ENABLED_FLAG = 'Y' grouped by ORG_ID for adoption reporting.
• Validate default sites and payment: join BILL_TO_PTY_SITE_ID, SHIP_TO_PTY_SITE_ID, and PAYMENT_ID to confirm referenced entities remain valid.
• Audit changes: use LAST_UPDATED_BY and LAST_UPDATE_DATE to trace modifications to customer preferences.
• DFF extraction: query ATTRIBUTE_CATEGORY and the ATTRIBUTE1–15 columns where custom checkout attributes are configured.

Related Objects

• HZ_PARTIES — joined via PARTY_ID; identifies the owning party of the express setting.
• HZ_CUST_ACCOUNTS — joined via CUST_ACCOUNT_ID; identifies the customer account.
• HZ_PARTY_SITES — referenced twice, via BILL_TO_PTY_SITE_ID and SHIP_TO_PTY_SITE_ID, for default addresses.
• FND_SECURITY_GROUPS — joined via SECURITY_GROUP_ID for security group scoping.
• IBE_ORD_ONECLICK_PK / IBE_ORD_ONECLICK_U1 — the primary key constraint and the business-key unique index (CUST_ACCOUNT_ID, PARTY_ID, ORG_ID) that govern record uniqueness.