Home
Reference
WebSphere Commerce database schema
The WebSphere Commerce database model was designed for data integrity and optimal performance. WebSphere Commerce provides several hundred tables that store WebSphere Commerce instance data. To maintain data integrity, and to ease maintenance referential integrity, constraints are widely used in the database model. Indexes are used carefully on tables to avoid over-indexing and to provide a good balance between data retrieval and data manipulation activities (insert and update). The business rules are implemented at the application level rather than by using database trigger. Triggers, however, are used to facilitate data staging and optimistic locking. A limited number of SQL-based database stored procedures are used for data intensive activities.
Data models
Any given database data model displays the relationship among database tables in the schema.
Order Management
The order management data model shows the relationship between database tables related to the Order Management subsystem.
Procurement
The Procurement data model shows the relationship between database tables that contain information about procurements.

Reference
- WebSphere Commerce API reference
  WebSphere Commerce exposes two main programming APIs. The first and newest API is a REST interface, and most new classes are exposed here. The legacy Java API also contains new classes not suitable for REST, and can be browsed in Javadoc format.
- Cross-reference of data beans, EJB beans, and tables
  Data beans are grouped into several component groups.
- Cross-reference of commands, tasks, and tables
  URL commands, controller commands, task commands, view commands and tables are related to each other.
- Cross reference: Commands to beans to database tables
  Use this information when you are customizing a command and you want to know which tables are affected. You should also use this topic if you are modifying a table and want to know which commands and beans are affected.
- API changes between WebSphere Commerce Version 7.0.0.9 and WebSphere Commerce Version 8.0.0.0
  If you are migrating version 7.0 of WebSphere Commerce, review the API changes between releases.
- WebSphere Commerce database schema
  The WebSphere Commerce database model was designed for data integrity and optimal performance. WebSphere Commerce provides several hundred tables that store WebSphere Commerce instance data. To maintain data integrity, and to ease maintenance referential integrity, constraints are widely used in the database model. Indexes are used carefully on tables to avoid over-indexing and to provide a good balance between data retrieval and data manipulation activities (insert and update). The business rules are implemented at the application level rather than by using database trigger. Triggers, however, are used to facilitate data staging and optimistic locking. A limited number of SQL-based database stored procedures are used for data intensive activities.
  - Column data type considerations
    Several column data types are available for you to use when you are creating new database table or columns.
  - Schema changes from Version 8 to Version 8 Mod Pack 4
    Database tables and columns within the WebSphere Commerce Version 8 Mod Pack 4 database schema can differ from the tables and columns in the database schema for WebSphere Commerce Version 8.
  - Schema changes from Version 8 to Version 8 Mod Pack 3
    Database tables and columns within the WebSphere Commerce Version 8 Mod Pack 3 database schema can differ from the tables and columns in the database schema for WebSphere Commerce Version 8.
  - Schema changes from Version 8.0.1.0 to 8.0.2.0
    Database tables and columns within the WebSphere Commerce Version 8.0.1.0 database schema can differ from the tables and columns in the database schema for WebSphere Commerce Version 8.0.2.0.
  - Schema changes from Version 8 to Version 8 Mod Pack 1
    Database tables and columns within the WebSphere Commerce Version 8 Mod Pack 1 database schema can differ from the tables and columns in the database schema for WebSphere Commerce Version 8.
  - Schema changes from Version 7 to Version 8
    Database tables and columns within the WebSphere Commerce Version 8.0 database schema can differ from the tables and columns in the database schema for WebSphere Commerce Version 7.
  - Deprecated tables and columns
    If a database table or column is marked as deprecated, then the table or column is outdated by newer constructs. Deprecated sections are supported for reasons of compatibility with an earlier version only. These tables or columns are obsolete or can become obsolete in future versions of WebSphere Commerce.
  - Data models
    Any given database data model displays the relationship among database tables in the schema.
    - Legend for data models
      Database tables within the WebSphere Commerce database schema are organized into functional groups, called data models.
    - Catalog
      The catalog data model shows the relationship between database tables related to the Catalog subsystem.
    - Marketing
      The marketing data model shows the relationship between database tables related to the Marketing subsystem.
    - Promotions
      The promotions data models show the relationship between database tables that are related to the promotions.
    - Member
      The member data model shows the relationship between database tables related to the Member subsystem.
    - Order Management
      The order management data model shows the relationship between database tables related to the Order Management subsystem.
      - ATP inventory
        The ATP inventory data model shows the relationship between database tables that contain information about ATP inventory.
      - ATP inventory adjustment
        This diagram shows the relationship between database tables that contain information about ATP inventory adjustments.
      - ATP expected inventory
        The ATP expected inventory data model shows the relationship between database tables that contain information ATP expected inventory.
      - ATP inventory fulfillment
        The ATP inventory fulfillment data model shows the relationship between database tables that contain information about ATP inventory fulfillment.
      - ATP inventory orders
        The ATP inventory orders data model shows the relationship between database tables that contain information about ATP inventory orders.
      - ATP inventory reservations
        The ATP inventory reservations data model diagram shows the relationship between database tables that contain information about ATP inventory reservations.
      - Billing
        The database tables that contain information about billing do not have any direct relationship with each other.
      - Calculation code
        The Calculation code data model shows the relationship between database tables that contain information about calculation codes.
      - Calculation code - direct attachment
        The Calculation code - direct attachment data model shows the relationship between database tables that contain information about direct attachments in calculation codes.
      - Calculation code - indirect attachment
        The Calculation code - indirect attachment data model shows the relationship between database tables that contain information about indirect attachments in calculation codes.
      - Calculation method
        Each row in the CALMETHOD database table indicates a task command that can be used by a store, or by stores in a store group, to perform calculations of discounts, shipping charges, sale or use tax, and shipping taxes (depending on its calculation usage).
      - Calculation rule - discount
        The Calculation rule - discount data model shows the relationship between database tables that contain information about discount data in calculation rules.
      - Calculation rule - shipping
        The Calculation rule - shipping data model shows the relationship between database tables that contain information about shipping data in calculation rules.
      - Calculation rule - tax
        The Calculation rule - tax data model shows the relationship between database tables that contain information about tax data in calculation rules.
      - Calculation scale
        The Calculation scale data model shows the relationship between database tables that contain information about calculation scales. You can use calculation scales to define ways to calculate discounts, shipping charges, and taxes within a store. The scale is part of a StoreEntity and can be associated with a particular QuantityUnit or Currency.
      - Calculation usage
        The calculation usage data model shows the relationship between database tables that contain information about calculation usage. Calculation usage includes discounts, shipping charges, and sales and shipping taxes. Calculation usage can be specified for individual stores, and affects the way that calculation codes and methods are used.
      - Country and state code
        The Country and state code data model shows the relationship between database tables that contain information about the state and country codes for taxes.
      - Currency
        The currency data model shows the relationship between database tables that contain information about currency within payments.
      - DOM inventory cache data model
        The DOM inventory cache data model shows the relationship between database tables that contain information about inventory configuration and inventory cache in DOM inventory.
      - Fulfillment
        The Fulfillment data model shows the relationship between database tables that contain information about fulfillment. Fulfillment centers are not part of a store, and hold inventory on behalf of stores.
      - Interest item
        The Interest item data model shows the relationship between database tables that contain information about interest items.
      - ***
      - Offers
        The Offers data model shows the relationship between database tables containing information about offers for trading positions.
      - Order
        The Order data model shows the relationship between database tables that contain information about orders. Members can own StoreEntities. Other Members can create Orders and Addresses. An Order may have a billing address.
      - Order adjustment
        The Order adjustment data model shows the relationship between database tables that contain information about order adjustments. Each OrderAdjustment is the total of the OrderItemAdjustments that are created when the results from a particular CalculationCode calculation are applied.
      - Order management adjustment and tax
        The Order management adjustment and tax data model shows the relationship between database tables that contain information about order management adjustment and tax data for an Order.
      - Order management - receipt and disposition
        The Order management - receipt and disposition data model shows the relationship between database tables that contain information about receipt and disposition data for an Order.
      - Order management - RMA
        The Order management - RMA data model shows the relationship between database tables that contain information about RMA (return merchandise authorization) data for an Order.
      - Order management - RMAitem
        The Order management - RMA item data model shows the relationship between database tables that contain information about RMA (return merchandise authorization) item data for an Order.
      - Order release
        The Order release data model shows the relationship between database tables that contain information about release data for an Order.
      - Order tax
        The Order tax data model shows the relationship between database tables that contain information about tax data for an Order.
      - Order trading agreement
        The Order trading agreement data model shows the relationship between database tables that contain information about order trading agreements.
      - Order item
        The Order Item data model shows the relationship between database tables that contain information about order item data.
      - Order item - allocated
        The Order Item - allocated data model shows the relationship between database tables that contain information about allocated data for an OrderItem.
      - Order item - backordered
        The Order item - backordered data model shows the relationship between database tables that contain information about backordered data for an OrderItem.
      - Pricing
        The Pricing data model shows the relationship between database tables that contain information about pricing.
      - Price rules
        The Price Rules data model shows the relationship between tables used in the Catalog Filter and Pricing tool.
      - Procurement
        The Procurement data model shows the relationship between database tables that contain information about procurements.
      - Quantity unit
        The Quantity unit data model shows the relationship between database tables that contain information about quantity units.
      - Quantity unit - references
        The Quantity unit - references data model shows the relationship between database tables that contain information about quantity units.
      - Receipt
        The Receipt data model shows the relationship between database tables that contain information about receipts.
      - Shipping
        The shipping data model shows the relationship between database tables that contain information about shipping.
      - Buy online, pickup in-store
        The Buy online, pickup in-store data model shows the relationship between database tables that contain information about online orders that are to be picked up in-store.
      - Suborders
        The suborders data model shows the relationship between database tables that contain information about suborders.
      - Subscriptions and recurring orders
        The subscriptions and recurring orders data model shows the relationship between database tables related to the service provider solution.
      - Tax type and category
        The Tax type and category data model shows the relationship between database tables that contain information about categories and types of taxes.
      - Ticklers
        The Ticklers shows the relationship between database tables that contain information about ticklers.
      - Vendor
        The Vendor data model shows the relationship between database tables that contain information about vendor.
    - Payment
      The payment data models show the database tables that are related to the payments subsystem.
    - Store
      The store data models show the relationship between database tables that are related to stores.
    - System
      The system data models show the relationship of database tables used for WebSphere Commerce system functions.
    - Trading
      The trading data models show the relationship of database tables in the Trading subsystem.
    - Content Management
      The Content Management shows the relationship between database tables that contain information about content management.
    - Content management system integration
      The content management system integration data model shows the relationship between database tables used by the solution.
    - Content versioning
      The content versioning data model shows the relationship between database tables that contain information about the content versioning.
    - Folder data model
      The folder data model shows the relationship between the database tables that include information about folder and folder items.
    - IBM Gift Center
      The IBM Gift Center data model shows the relationship between database tables that contain information about IBM Gift Center.
    - WebSphere Commerce search engine optimization
      The WebSphere Commerce search engine optimization (SEO) shows the relationship between database tables that contain information about WebSphere Commerce search engine optimization (SEO).
    - WebSphere Commerce search data model
      The WebSphere Commerce search data model shows the relationship between database tables that are related to WebSphere Commerce search.
- Payments subsystem
  In WebSphere Commerce, payment processing uses the Payments subsystem.
- Dynamic caching
  In general, caching improves response time and reduces system load. Caching techniques are used to improve the performance of World Wide Web Internet applications. Most techniques cache static content (content that rarely changes) such as graphic and text files. However, many websites serve dynamic content, containing personalized information or data that changes more frequently. Caching dynamic content requires more sophisticated caching techniques, such as those provided by the WebSphere Application Server dynamic cache, a built-in service for caching and serving dynamic content.
- Data Load utility configuration file schema
  The Data Load utility contains several configuration files. You can use the configuration file schema to understand and customize the data load configuration files.
- WebSphere Commerce web services
  WebSphere Commerce provides many web services.
- Utilities
  Utilities help you to accomplish administrative or configuration tasks, for example, loading data, publishing a store.
- Shopping flow URLs
  WebSphere Commerce shopping flow URLs are organized by subsystem.
- Ant targets
  A WebSphere Commerce instance can be created from the command line. The command-line utility uses Apache Ant to create the objects required. The targets are divided into several high-level groups that correspond to the environment that is to be configured.
- Glossary

Procurement data model

The Procurement data model shows the relationship between database tables that contain information about procurements.

Click any of the database table boxes to see more information about that table.