HOME
1.Trading Subsystem
The trading subsystem in WebSphere Commerce provides the logic, function and data relevant for negotiating the price and quantity of a product or set of products between the buyer and seller organization. The trading subsystem includes auctions, contracts, and Request for Quote (RFQ) components that are used to carry out specific transactions between organizations.2.Terminologies used in Trading subsystem
2.1.Business Relationship Management
To customize what a customer can do in a store use the business relationship management system. By using this system, you can entitle customers to various aspects of a store such as what products they can purchase, the price they pay, and what payment methods a store accepts.
Customer entitlement is controlled by business accounts, contracts, and business policies.
The default customer entitlement is defined by a store's default contract. This default contract typically specifies that customers can access the master catalog and purchase products at standard prices.
2.2.Contracts
Contracts enable a customer organization to purchase products from a store at a specified price for a specified time under specific conditions. You can use WebSphere Commerce Accelerator to manage contracts. Specifically, you can create, change, deploy, suspend, resume, and unlock contracts.
A contract consists of the following elements.
2.2.1.Profile
The contract profile contains the identifying information for the contract. This information includes a unique name for the contract, a short description, and a time period for which the contract is valid.
2.2.2.Participants
Contract participants are the organizations that take part in the contract. There is a buyer organization, a seller organization, and contacts at both organizations.
2.2.3.Terms and conditions
Contract terms and conditions are the rules that cover the actual implementation of the contract. Contract terms and conditions cover such information as product pricing, returns and refunds, payment, shipping, billing, and order approval.
2.2.4.Attachments
Contract attachments cover any information that is not covered by the previous elements such as file attachments that provide additional information about the contract and any general remarks about the contract. WebSphere Commerce uses the Universal Resource Identifiers (URIs) for contract attachments, not the actual attachments.
2.2.5.References
A contract can refer to another contract to share its terms and conditions. For example, contract A can refer to contract B. Thus, a buyer who is entitled to contract A is entitled to all the terms and conditions from contract A, and to all the terms and conditions in contract B.
2.3.Business Policies
Business policies are sets of rules followed by a store that define business processes, industry practices, and the scope and characteristics of a store's or group of stores' offerings.
2.3.1.Catalog business policies
Catalog business policies define the scope and characteristics of the catalog of products for sale in a store which includes the prices and the categorization of products in a store's catalog.
2.3.2.Payment business policies
Invoicing, payment, and refund business policies define how a store accepts payments, pays refunds, and the format of a store's invoices.
2.3.3.Returns business policies
Returns business policies define whether refunds are accepted, the time period they are accepted for, and any restocking fees that are applied to returns.
2.3.4.Shipping business policies
Shipping business policies define the shipping providers a store can use and the charges that are associated with each type.
2.3.5.Referral interface business policies
Referral interface business policies define the relationship between a proxy store and a remote store.
2.4.Request for Quote
A buyer can create a Request for Quote (RFQ), by using the WebSphere Commerce Accelerator, for unique variations of goods and services that are offered in a catalog. If buyers cannot find a product or category that match their needs within a catalog, they can select attributes from the personalized dictionary to precisely define the product specifications. A buyer can also create an RFQ by using the contents in their shopping cart, or add a shopping cart to an existing RFQ.
There are three RFQ notification messages: The RFQ was submitted successfully; The RFQ was closed successfully; and The RFQ was completed successfully.
Messaging subsytem in WCS
Catalog Subsystem
Subsystems in WCS
Organizational Structure in WCS
2.2.Contracts
Contracts enable a customer organization to purchase products from a store at a specified price for a specified time under specific conditions. You can use WebSphere Commerce Accelerator to manage contracts. Specifically, you can create, change, deploy, suspend, resume, and unlock contracts.
A contract consists of the following elements.
2.2.1.Profile
The contract profile contains the identifying information for the contract. This information includes a unique name for the contract, a short description, and a time period for which the contract is valid.
2.2.2.Participants
Contract participants are the organizations that take part in the contract. There is a buyer organization, a seller organization, and contacts at both organizations.
2.2.3.Terms and conditions
Contract terms and conditions are the rules that cover the actual implementation of the contract. Contract terms and conditions cover such information as product pricing, returns and refunds, payment, shipping, billing, and order approval.
2.2.4.Attachments
Contract attachments cover any information that is not covered by the previous elements such as file attachments that provide additional information about the contract and any general remarks about the contract. WebSphere Commerce uses the Universal Resource Identifiers (URIs) for contract attachments, not the actual attachments.
2.2.5.References
A contract can refer to another contract to share its terms and conditions. For example, contract A can refer to contract B. Thus, a buyer who is entitled to contract A is entitled to all the terms and conditions from contract A, and to all the terms and conditions in contract B.
2.3.Business Policies
Business policies are sets of rules followed by a store that define business processes, industry practices, and the scope and characteristics of a store's or group of stores' offerings.
Business policies are enforced with a combination of one or more business policy commands that implement the rules of the business policy. Each business policy command is a Java class. A business policy command can be shared by multiple business policies. The behavior of the business policy command is determined by the parameters that are passed to the command.
Parameters affecting the function of a business policy command can be introduced in three places:
- The contract term and condition, which refers to the business policy
- The business policy definition
- The business policy command that enforces the policy
A buyer can create a Request for Quote (RFQ), by using the WebSphere Commerce Accelerator, for unique variations of goods and services that are offered in a catalog. If buyers cannot find a product or category that match their needs within a catalog, they can select attributes from the personalized dictionary to precisely define the product specifications. A buyer can also create an RFQ by using the contents in their shopping cart, or add a shopping cart to an existing RFQ.
There are three RFQ notification messages: The RFQ was submitted successfully; The RFQ was closed successfully; and The RFQ was completed successfully.
Messaging subsytem in WCS
Catalog Subsystem
Subsystems in WCS
Organizational Structure in WCS
No comments:
Post a Comment