Search Results ibe_ord_oneclick




Overview
Explore in AI Chat

Overview

IBE_ORD_ONECLICK is an Oracle iStore (IBE) application table that stores express checkout, or "one-click," configuration settings for registered customers. In the Oracle E-Business Suite 12.1.1 and 12.2.2 environments, iStore provides a self-service storefront where registered business customers authenticate and place orders against their negotiated pricing and payment terms. The one-click feature allows a returning registered user to bypass the standard multi-step checkout flow by pre-configuring default shipping, billing, and payment preferences. This table persists those defaults on a per-customer basis.

From a Data Vault modeling perspective, the metadata classifies this object heuristically as a link. This classification is consistent with the table's structure: it does not model a single business entity but rather records an association between a party (customer), their bill-to and ship-to addresses, a customer account, and a payment instrument. The link connects multiple hub-like business keys (party, customer account, party sites, bank account) into a single convenience record that the iStore checkout engine can resolve at runtime.

Key Information Stored

The primary key is defined by the constraint IBE_ORD_ONECLICK_PK, which is based on the surrogate column ORD_ONECLICK_ID. This surrogate identifier is the only guaranteed-unique column documented; no alternate unique index or natural business key is identified in the metadata, meaning uniqueness of a customer's one-click configuration is enforced through the combination of foreign key values rather than a single business column.

The most significant columns are the foreign key attributes that define the express checkout profile:

Together these columns capture the complete preference set required to construct an order without user re-entry, tying the identity of the buyer to their addresses and payment source.

Common Use Cases and Queries

The principal use case is the iStore express checkout flow, which reads this table when a registered user selects one-click ordering. Reporting and support scenarios typically join the profile back to the TCA (Trading Community Architecture) model. A representative query retrieving a customer's one-click defaults:

  • SELECT o.ord_oneclick_id, o.party_id, o.cust_account_id, o.bill_to_pty_site_id, o.ship_to_pty_site_id, o.payment_id FROM ibe_ord_oneclick o WHERE o.party_id = :p_party_id;
  • Join to HZ_CUST_ACCOUNTS on CUST_ACCOUNT_ID to resolve the account number, and to HZ_PARTY_SITES for validated addresses.
  • Join to AP_BANK_ACCOUNTS_ALL on PAYMENT_ID to report the stored payment instrument for audit or reconciliation.

Analysts commonly use such queries to verify that storefront defaults are correctly configured, to troubleshoot failed express checkouts, and to audit which customers have stored payment preferences.

Related Objects

The relationships below are documented foreign keys from IBE_ORD_ONECLICK:

  • HZ_PARTIES — joined via PARTY_ID; the registered customer.
  • HZ_CUST_ACCOUNTS — joined via CUST_ACCOUNT_ID; the ordering customer account.
  • HZ_PARTY_SITES — joined via BILL_TO_PTY_SITE_ID and SHIP_TO_PTY_SITE_ID; default addresses for both roles.
  • AP_BANK_ACCOUNTS_ALL — joined via PAYMENT_ID; the stored payment bank account.

These satellite and hub-backed objects supply the master data consumed by the iStore checkout engine. Note that the ETRM metadata records this table as "Not implemented in this database," indicating it may not exist in every 12.1.1/12.2.2 instance and its presence depends on whether iStore one-click functionality was deployed.