Websphere Commerce Trading SubSystem Part1

A trading agreement is used to manage business relationship between a buyer and  seller organization. Different types of trading agreement in websphere commerce are

1. Business Accounts
2. Request for Quotes(RFQ)
3. Contract
Account and contract are an essential function in Web Sphere Commerce. They are widely used to define terms and conditions between a shopper and seller in typical business-to-business (B2B) scenarios. In WebSphere Commerce, contract terms and conditions are also referred to as contract terms or terms. These terms cover different aspects, such as price, product, shipping, return, order, payment, and content. These terms and conditions represent the business agreements or restrictions between buyers and shoppers that can impact the entire purchase operation.

Although WebSphere Commerce provides a comprehensive out-of-the-box terms, customers usually have specific requirements on the agreements between the buyer and seller. These terms need to be implemented via extra development in the WebSphere Commerce contract model.

Business Accounts represents represents a business account between a Buyer organization and a Seller organization. A business account can be used to organize various trading agreements, and to specify special trading terms and conditions.

A business account can be used to organize various trading agreements and to specify terms and conditions that are related to the relationship between buyer and seller. 
Creating a business account

To create a business account, use the Business Relationship Management tools in WebSphere Commerce Accelerator. The seller administrator creates a buyer organization using the Organization Administration Console before a new business account can be created. Ensure that at least one person associated with the buyer organization is a registered customer (a contact at the buyer organization is required).

Prerequisites for creating Account

Ensure that the Organization Participant role is assigned to the organization for which you are creating the account.Ensure that the buyer organization that was created is a member of the Registered Customers. Add the buyer organization if required.

Before creating an account register an organization and user.






Steps to Create an Account in Commerce Accelerator
  1. Open the Web Sphere Commerce Accelerator.
  2. Go to Sales > Accounts. The Account List page displays, containing business accounts currently defined for the selected store. If you do not see this menu, then your logon ID does not have the appropriate authority to perform this task. Contact your Site Administrator.
  3. Click on New. The Account notebook displays.
  4. Complete the fields for each page as required, and use the links on the left side to switch between pages.
  5. Click OK to save the business account and close the notebook. The business account is displayed in the Account List page.


Tables involved

Each row of this table represents a business account between a Buyer organization and a Seller organization. A business account can be used to organize various trading agreements, and to specify special trading terms and conditions.
DEFAULTCONTRACT column indicates if purchases using Store default contract is allowed. Valid values are as follows:
0=Not allowed 1=Allowed
Each row in this table represents a Trading Agreement.
This table stores information about the type of trading for a Trading Agreement.
Types of trading types / Trading type ID. Valid values are as follows
0 = Account
1 = Contract
2 = RFQReq
3 = RFQResp
4 = RFQResult
5 = Exchange
6 = Auction
7 = ReverseAuction

Business Accounts includes below five components as mentioned below

1.Purchase Order
2.Credit Line
4.Display Customization

1. Purchase Order

The purchase order number is what a customer must provide when ordering at the store. The purchase order number authenticates the customer as one that is authorized to order from the store, as stipulated in the terms and conditions within the contract between the store and the customer. 
User can define PO number based on the following steps. 
Open the WebSphere Commerce Accelerator.
  1. Click Sales > Accounts. The Account List page displays, containing business accounts currently defined for the selected store. If you do not see this menu, then your logon ID does not have the appropriate authority to perform this task. Contact your Site Administrator.
  2. Select the check box to the left of the business account that you want to work with. Click Change. The Account notebook opens.
  3. When you open the notebook, the Customer page displays. From the left navigation frame, click Purchase Order. The Account Purchase Order page displays.
  4. Click Add. The Add Purchase Order dialog displays.
  5. In the Purchase order number field, type the number to uniquely identify this purchase order.
  6. To specify a maximum spending amount for this purchase order, select Spending limit, type the amount, and select the type of currency to use.
  7. Click OK to save the purchase order. 
If a purchase order number is defined with the business account, then all the orders processed for that customer will require that a purchase order number be entered.

Types of Buyer Purchase Order (PO):

1.Blanket PO
2.Limited PO
3.Single-use Individual PO
4.Multiple-use Individual PO

1.Blanket PO- This is used for unlimited number of orders
2.Limited PO-  This is used for orders where the total amount of all orders made specifying the 
   limited purchase order number doesn’t exceed a spending limit.
3.Single-use Individual PO-This is used for one order and is acceptable purchase order number 
   is  not predefined.
4.Multiple-use Individual PO (PO Number can be used by more than one order).

Tables Involved

Each row of this table represents a Purchase Order Number. It is that the Buyer organization of the Account has defined or used for Trading with the Seller organization. The number is only unique within the Account.

This table defines the different types of Buyer Purchase Order for the Site.

This table is used to keep track of Purchase Amounts by Purchase Order number and by Orders. Entries are created only for Orders against Limited Purchase Order (PO) numbers.

 2. Credit Line


A credit line is a payment method that provides the ability for a buyer to delay the payment settlement for all orders.The account holder is responsible for payment settlement on an outstanding credit line balance. If a credit line is used for payment, the seller debits the account for order at the time of payment capture, and the account is credited during payment settlement. Payment settlement of credit line happened outside websphere commerce.

Each row of this table represents a credit line the account holder (buyer organization) has with the seller organization. This credit line is associated with a specific business account.

Each row of this table stores a payment summary XML that could be sent to an external accounting system. The summary is by Store, Account, and payment policy.
Payment using credit line uses the following command DoPaymentActionsPolicyCmdImpl

The DoPaymentActionsPolicyCmd implementation class for payment processing component being used. When PaymentEventListenerCmdImpl listens a payment event raised by payment rules component. It will call this class to execute the corresponding payment action through calling the API of payment processing component according to the payment/refund action data.


Invoice is a document that notifies the account holder that an order has been released for fulfillment center under their account and lists the following details.
1.      Items
2.      Prices
3.      Purchase Order Numbers
4.      Shipping Charges
5.      Total amount Billed

Only one invoice can be generated for a release.


This table stores the invoice XML generated for the order release. An order release is represented by a row in the ORDRELEASE table.

4.Display customization


WebSphere Commerce allows you to change the look of display pages in your store for every business customer by specifying the DisplayCustomizationTC term and condition in the business account definition. This display customization can be as simple as adding a different logo, or as complex as having a custom store name and message, for each customer.

Display customization involves more than specifying the customized portion of a display page in the business account. It must be planned as a part of your store from the beginning. Any pages in your store must be designed and coded to include the customizable portion of the page.
The DisplayCustomizationTC is then used by WebSphere Commerce to locate the customized portion of the page.

You can create a business account that takes advantage of display customization using two methods:

1.    Define a business account in an XML file, specify the information defined in the DisplayCustomizationTC term and condition in the XML file, and import the business account XML file into WebSphere Commerce using the command.

2.   Use the Account notebook within the WebSphere Commerce Accelerator to specify what to display to each customer.

JSP code snippet: Display customization terms and conditions
The CustomizationTCDisplay.jsp file displays the customization information according to the display customization terms and conditions for the a user's current session logon ID, store ID, and the selected language ID.
It  will show the below information:
Company logo image
Customized text field one
Customized text field two
For this snippet implementation purpose, a relative path is expected for the company logo to display correctly.
The CustomizationTCDisplay.jsp file is available under the following directory:


<wcbase:useBean id="contract_StoreBean" classname="com.ibm.commerce.common.beans.StoreDataBean" />
<wcbase:useBean id="contract_DisplayTCBean" classname="com.ibm.commerce.tools.contract.beans.DisplayCustomizationTCDataBean" >
<c:set property="languageId" value="${CommandContext.languageId}" target="${contract_DisplayTCBean}" />
<c:set property="userId"     value="${CommandContext.userId}"     target="${contract_DisplayTCBean}" />
<c:set property="storeId"    value="${CommandContext.storeId}"    target="${contract_DisplayTCBean}" />
[Data Bean Activation] --%>
<table id="Contract_DisplayCustomizationTC_Table_1">
<%-- Display the specified company logo image picture --%>
<td id="Contract_DisplayCustomizationTC_TableCell_1">
<img src='<c:out value="${contract_StoreBean.filePath}${contract_DisplayTCBean.attachmentURL[1]}"/>' alt= "company logo image">
<%-- Display the customized text field one --%>
<td id="Contract_DisplayCustomizationTC_TableCell_2">
<c:out value="${contract_DisplayTCBean.displayText[1]}"/>
<%-- Display the customized text field two --%>
<td id="Contract_DisplayCustomizationTC_TableCell_3">
<c:out value="${contract_DisplayTCBean.displayText[2]}"/>


Read more on Websphere Commerce Trading SubSystem Part2.

1 comment:

  1. I really appreciate information shared above. It’s of great help. If someone want to learn Online (Virtual) instructor lead live training in TECHNOLOGY , kindly contact us http://www.maxmunus.com/contact
    MaxMunus Offer World Class Virtual Instructor led training on TECHNOLOGY. We have industry expert trainer. We provide Training Material and Software Support. MaxMunus has successfully conducted 100000+ trainings in India, USA, UK, Australlia, Switzerland, Qatar, Saudi Arabia, Bangladesh, Bahrain and UAE etc.
    For Demo Contact us.
    Saurabh Srivastava
    E-mail: saurabh@maxmunus.com
    Skype id: saurabhmaxmunus
    Ph:+91 8553576305 / 080 - 41103383