Site assets information model diagram description
This diagram illustrates the types of data the site contains and their relationships to the site.
- Language
- A site can define many languages in the LANGUAGE table, and describe them in the LANGUAGEDS table. Each store generally supports a subset of these languages by adding rows to the STORELANG table. The ten pre-defined languages are: German, Traditional and Simplified Chinese, Japanese, Korean, Italian, French, Spanish, Brazilian Portuguese, and English. A language is associated with one site, and one site can have many languages associated with it.
- Member attributes
- Member attributes are stored in the MBRATTR table and represent the set of defined attribute names for which values can be stored for organizations or users. Examples of such attribute names include JobFunction, ProcurementCard, SpendingLimit, ReferredBy, and CountryOfOperation. Attribute values for particular organizations or users are stored in the MBRATTRVAL table, and these values can be different for different stores or store groups. Member attributes are associated with one site and have a dependant relationship with attribute types.
- Attribute types
- Attribute types are stored in the ATTRTYPE table and represent the defined data types that can be used to represent attribute values. Examples of data types include INTEGER, STRING, and FLOAT. A member can only have one attribute type.
- Member group type
- Member group types are stored in the MBRGRPTYPE table and represent the set of defined member group usages. Member groups are assigned usages by adding rows to the MBRGRPUSG table. Examples of member group usages include AccessGroup (for use with access control policies) and UserGroup (for general purposes, such as customer groups). A member group type is associated with one site. A site can have one or more member group types.
- User
- User represents authenticated user identities. Users generally represent customers placing or approving orders on behalf of buying organizations, selling agents processing orders for selling organizations or maintaining store level assets, or Site Administrators maintaining the WebSphere Commerce Server instance. Each user is associated with one site and is defined in the USERS table. A user is associated with one site, and a site can have one or more users.
- Organization
- Organization represents organizations and organizational units within organizations. Organizations generally represent business entities responsible for buying or selling. Orders placed by customers in a B2B direct buying organization are recorded as being placed on behalf of the buying organization. Stores, catalogs, and fulfillment centers are owned by organizations that are responsible for certain aspects of selling. Organizations are defined in the ORGENTITY table. An organization is associated to one site. A site can have one or more organizations belonging to it.
- Role
- Role represents the set of defined roles that users can be assigned within organizations. For example, a user may be assigned the role of Customer Service Representative within a selling organization, or may be assigned the role of Buyer Approver within a buying organization. The names and descriptions of the default roles are populated in the ROLE table. Role is associated with one site. A site can have one or more roles associated with it.
- Quantity unit conversion
- Each site has quantity conversions. These represent multiplication or division operations that are used to convert between different units of measure. These are populated in the QTYCONVERT table. A quantity unit conversion is associated with one site, and a site can have one or more quantity unit conversions associated with it. A quantity unit conversion has one owner which is a quantity unit. A quantity unit may have one or more quantity unit conversions.
- Quantity units
- Quantity units represent the set of units of measure for the site. They are defined in the QTYUNIT table and described in the QTYUNITDSC table. Each store can specify how amounts in each unit of measure are rounded and formatted for display, depending on their intended usage, by adding rows to the QTYFORMAT table. A quantity unit is associated with one site, and one site can have one or more quantity units.
- Tax types
- Tax types represent the calculation usages that calculate taxes. Sales tax and shipping tax are two different calculation usages that calculate taxes. Tax types are defined in the TAXTYPE table.
- Calculation usage
- Calculation usage represents the different kinds of calculations that can be performed by the OrderPrepare command. Calculation usages are defined for discounts, shipping, sales tax, shipping tax, and e-coupons. Calculation usages are defined in the CALUSAGE table.
- Currency
-
Each site defines a number of currencies in the SETCURR table and describes them in the SETCURRDSC table. Each store supports a subset of these currencies by adding rows to the CURLIST table, one row for each currency supported. A currency is associated with one site, and a site can have one or more currencies.
- Number usage
- Number usage represents the intended usage for numbers. Stores can specify different rounding and formatting rules for the numbers they display according to how they are used. For example, a store may round unit prices to four decimal places by specifying the "unit price" usage, but other monetary amounts to two decimal places by specifying the "default" usage. Number usage is defined in the NUMBRUSG table, and described in the NUMBRUSGDS table. Number usage is part of one site. A site can have zero or more number usages.
- Item types
- Item types represent the different kinds of base items. The two types of base items in WebSphere Commerce are dynamic kit and normal item. Item types are pre-defined in the ITEMTYPE table. Item types are part of one site. A site can have zero or more item types.
- Device formats
- Device formats are stored in DEVICEFMT table and represent the many device formats a site uses such as browsers, I_MODE, e-mail, XMLMQ, and XMLHTTP. All these device types allow users to interact with the site through various media. A device format is part of one site. A site can have zero or many device formats.
- Store relationship types
A store relationship type (StoreRelType) defines the type of relationship between two stores. Each type of store relationship defines its own relationship, that is, what roles each partner in the relationship will play and what the relationship between the two is. A store relationship type is defined in the STRELTYP table, and described in the STRELTYPDS table. A store relationship type is part of one site, and a site can have zero or more store relationship types.