|
|
The Order Processing Database Schema
This topic describes the database schema for Managing Purchases and Processing Orders services. Understanding this schema will be helpful to those who may be customizing or extending the technologies provided in the product.
This topic includes the following sections:
The Entity-Relation Diagram
Figure 1-1 shows the logical Entity-Relation diagram for the WebLogic Portal order and discount tables in the WebLogic Portal database. See the subsequent sections in this chapter for information about the data type syntax.
Figure 1-1 Entity-Relation Diagram for the Order and Discount Tables
Explanations for the columns in each table are provided in the remainder of this topic.
List of Tables Comprising the Order Processing Schema
The Commerce services order management system is comprised of the following tables:
The Order Processing Data Dictionary
In this section, the schema tables are arranged alphabetically as a data dictionary.
Note: Even though the following documentation references "foreign keys" to various tables, these constraints do not currently exist in this release of Commerce services. However, they will be in place in future versions of Commerce services and we want you to be aware of these relationships now.
The DISCOUNT Database Table
Table 1-1 describes the metadata for the Commerce services DISCOUNT table. This table stores stores one or more discount records for every DISCOUNT_SET record.
See the section for information about the constraint defined for this table.
The Primary Key is DISCOUNT_ID.
The DISCOUNT_ASSOCIATION Database Table
Table 1-2 describes the metadata for the Commerce services DISCOUNT_ASSOCIATION table. This table associates each customer with a discount and maintains information regarding the times the customer has used each discount.
See the section for information about the constraint defined for this table.
The Primary Key is DISCOUNT_ASSOCIATION_ID.
The ORDER_ADJUSTMENT Database Table
Table 1-3 describes the metadata for the Commerce services ORDER_ADJUSTMENT table. This table is used to maintain information about a discount taken at the order level (for example, $20.00 off any order between 1/1/02 and 1/31/02.)
See the section for information about the constraint defined for this table.
The Primary Key is ORDER_ADJUSTMENT_ID.
The ORDER_LINE_ADJUSTMENT Database Table
Table 1-4 describes the metadata for the Commerce services ORDER_LINE_ADJUSTMENT table. This table is used to maintain information about a discount taken at the order line item level (for example, 10% off SKU "Power Drill").
See the section for information about the constraint defined for this table.
The Primary Key is ORDER_LINE_ADJUSTMENT_ID.
The WLCS_CREDIT_CARD Database Table
Table 1-5 describes the metadata for the Commerce services WLCS_CREDIT_CARD table. This table is used to store information related to a customer's credit card(s) in the order processing database.
See the section for information about the constraint defined for this table.
The Primary Key is CREDIT_CARD_ID.
The WLCS_CUSTOMER Database Table
Table 1-6 describes the metadata for the Commerce services WLCS_CUSTOMER table. This table is used to store information about the customer in the order processing database.
The Primary Key is CUSTOMER_ID.
The WLCS_ORDER Database Table
Table 1-7 describes the metadata for the Commerce services WLCS_ORDER table. This table is used to store information about a customer's specific order in the order processing database.
Note: The Commerce services product does not populate the SHIPPING_AMOUNT, SHIPPING_CURRENCY, PRICE_AMOUNT, or PRICE_CURRENCY columns.
The Primary Key is ORDER_ID.
The WLCS_ORDER_LINE Database Table
Table 1-8 describes the metadata for the Commerce services WLCS_ORDER_LINE table. This table is used to store information about each line of a customer's shopping cart in the order processing database.
See the section for information about the constraint defined for this table.
The Primary Key is ORDER_LINE_ID.
The WLCS_SAVED_ITEM_LIST Database Table
Table 1-9 describes the metadata for the Commerce services WLCS_SAVED_ITEM_LIST table. This table is used to store information about the customer's saved shopping cart items in the order processing database.
There is no Primary Key.
The WLCS_SECURITY Database Table
Table 1-10 describes the metadata for the Commerce services WLCS_SECURITY table. This table is used to persist public and private keys for encryption and decryption purposes in the order processing database. This table is meant for internal use by the Commerce services product.
There is no Primary Key.
The WLCS_SHIPPING_ADDRESS Database Table
Table 1-11 describes the metadata for the Commerce services WLCS_SHIPPING_ADDRESS table. This table is used to store information related to a customer's shipping address(es) in the order processing database.
See the section for information about the constraint defined for this table.
The Primary Key is SHIPPING_ADDRESS_ID.
The WLCS_SHIPPING_METHOD Database Table
Table 1-12 describes the metadata for the Commerce services WLCS_SHIPPING_METHOD table. This table is used to store information about the shipping method in the order processing database.
The Primary Key is PK_IDENTIFIER.
The WLCS_TRANSACTION Database Table
Table 1-13 describes the metadata for the Commerce services WLCS_TRANSACTION table. This table is used to store data for every payment transaction in the order processing database.
See the section for information about the constraint defined for this table.
The Primary Key is TRANSACTION_ID.
The WLCS_TRANSACTION_ENTRY Database Table
Table 1-14 describes the metadata for the Commerce services WLCS_TRANSACTION_ENTRY table. This table is used to store (log) the different states a payment transaction has passed through in the order processing database.
See for information about the constraint defined for this table.
The Primary Key is TRANSACTION_ENTRY_ID.
The SQL Scripts Used to Create the Database
The database schemas for WebLogic Portal and WebLogic Personalization Server are all created by executing the create_all script for the target database environment.
Scripts
Regardless of your database, execute one of the following to generate the necessary database objects for the modules desired ( WebLogic Portal, WebLogic Personalization Server, Commerce services, Campaign services and Sample Portal):
The following are the various directories underneath WL_COMMERCE_HOME/db
(as seen in a UNIX environment):
PORTAL_HOME/db/cloudscape/351
PORTAL_HOME/db/oracle/817
Note: In this documentation,PORTAL_HOME is used to designate the directory where the product is installed.
Each of the databases supported have the same number of scripts in each of their subdirectories. The scripts are listed and described in Table 1-15 below.
Defined Constraints
Various constraints are defined and used in the Order database schema. These constraints can be found in the following scripts:
wlcs_create_fkeys.sql—contains the Foreign Keys
wlcs_create_tables.sql—contains the Check Constraints
|
Copyright © 2001 BEA Systems, Inc. All rights reserved.
|