This topic describes all tasks contained in the WebSphere Commerce business process model. Tasks are grouped by role. The
task name
links to the WebSphere Commerce help topic that describes how to perform the task.
- Approve registration
-
If the Seller decides to accept the registration request, then the customer is put in approved state. A notification is sent
out to let them know that their request has been accepted and that they can now shop in the store.
|
- Check product compliance (External task)
-
The Channel Manager decides verify that online stores comply with their service agreements, or has received information that
a Seller is violating its service agreement.
|
- Create account for base contracts
-
Create an account to hold base contracts |
- Create organization
-
Create an organization in the administrative domain to place the Extended Site under. |
- Create Seller
-
Create the Ex-Site administrator that will administer an Extended Site. |
- Create service agreement
-
Create an XML document that represents the service agreement between the hub (channel, hosting or supplier hub) and the business
partner. This includes all the terms and conditions that have been negotiated with the business partner, and the initial configuration
of their online or proxy store.
|
- Delete store
-
Delete a store so that it is removed from the WebSphere Commerce system. The store is not available for reports.
|
- Determine Ex-Site admin domains
-
Determine the administrative domain required for the Extended Sites. |
- Determine Ex-Site administrator
-
Determine who will be the administrator of the Extended Site. |
- Find store
-
Search for a store by the store name, service agreement name, or the store state. |
- Import service agreement
-
Import the XML document representing the service agreement between the hub (channel, hosting or supplier hub) and its business
partner. The service agreement will be set-up in the system, and the store will be created for the business partner.
|
- Inform resellers (External task)
-
Inform all the resellers at the site that a new distributor is available to deliver quotes and transfer shopping carts and
orders. The reseller should update its profile to indicate the appropriate user ID and password for that distributor, and
specify whether or not that distributor should appear on their preferred list of distributors.
|
- Lock Seller organization
-
Lock the organization to prevent the users who belong to that organization from logging into the WebSphere Commerce system. |
- Negotiate with distributor (External task)
-
Negotiate with the distributor to determine the terms and conditions for enabling the distributor at the channel hub. These
terms can include: the period of time the distributor will be available, the functions and communications protocols supported
by the distributor, and whether or not the distributor is restricted from offering quotes for particular categories or products.
|
- Notify Seller (External task)
-
Inform the Seller by e-mail or other methods of communication that the Seller's store has been created or that store operation
has been resumed. The Seller may now complete the configuration of their store, and then open the store.
|
- Notify Seller about inactivity (External task)
-
Inform the Seller by e-mail or other methods of communication that the Seller's store has been inactive for a certain period
of time and that it may be removed from the hub (channel, hosting or supplier hub).
|
- Notify Seller about locking (External task)
-
The Channel Manager informs the Seller by e-mail or other methods of communication that the Seller's organization has been
locked. The Channel Manager provides the Seller the reason for locking their organization, and the terms by which they will
unlock the organization.
|
- Notify Seller about suspension (External task)
-
The Channel Manager informs the Seller by e-mail or other methods of communication that the Seller's store has been suspended.
The Channel Manager provides the Seller the reason for the suspension, and the terms by which the problem can be fixed.
|
- Notify supplier
-
Inform the supplier by e-mail or other methods of communication that the supplier's store has been created or that store operation
has been resumed. The supplier may now complete the configuration of their store, and then open the store.
|
- Produce inactive store reports (External task)
-
Create a report of stores that have been inactive for a certain period of time. An inactive store is one that has not taken
any orders for a certain period of time.
|
- Produce product sales report
-
Create a report about the products sold by a store. Look for products that are not allowed to be sold, or whose descriptions
contain offensive text.
|
- Receive request from Seller (External task)
-
The Channel Manager receives a request from a Seller that they would like to have a hosted store on the hub (channel, hosting
or supplier hub) site.
|
- Receive request from supplier
-
The Channel Manager receives a request from a supplier that they would like to have a hosted store on the supplier hub. |
- Register distributor
-
Set up the distributor on the site by creating an organization and enabling the WebSphere InterChange Server adapter communication
mechanism for the distributor.
|
- Reject registration
-
If the Seller decides to reject the registration request, then the customer is not approved -- and cannot shop. A notification
is sent to the customer that their request has been rejected.
|
- Resume store
-
The Channel Manager can resume operation of the store to allow the Seller to make their store available to customers. |
- Review approval request
-
The Seller navigates to the administrative UI, finds the pending request, and chooses either to approve or reject it. |
- Search for products
-
Use the Product Management tools within the WebSphere Commerce Accelerator to search the products that are sold by a store.
Look for products that are not allowed to be sold, or whose descriptions contain offensive text.
|
- Search keywords in store directory
-
Search the store directory to find products that should not be sold, or have descriptions that include offensive text. |
- Suspend store
-
The Channel Manager can suspend a store to prevent the store owner from making the store available online. The store owner
can access the store to make any modifications, but they cannot open the store. Only once the Channel Manager has resumed
the store can the store owner open the store to make it available to customers.
|
- View e-Marketing Spots
-
Enter the online store to view the e-Marketing Spots that are displayed to customers. Look for products that are not allowed
to be sold, or whose descriptions contain offensive text.
|
- Add ad-hoc item to return request
-
Add an ad-hoc item to the return request. An ad-hoc item is one that is not in the original order. |
- Add catalog item
-
Add a catalog item to the return request, without referencing an existing order item. |
- Add order item to return request
-
Add an order item to the return request. This indicates that the item is an item being returned. |
- Adjust refund amount
-
Adjust the refund amount up or down based on negotiation with the customer. |
- Assign roles to user
-
The Customer Service Representative may choose to assign additional roles to the user, beyond what is automatically assigned.
See the WebSphere Commerce production online help for more information on role assignment.
|
- Chat with other CSR
-
A customer service representative can use the customer care applet to chat with other customer service representatives to
get additional help for a customer care request, or use it to inform another customer service representative about transferring
a customer care request to a different queue.
|
- Create customer record
-
Create a new customer based on information obtained: -- Logon -- Password -- Name -- Challenge question/answer -- Preferred currency/language -- Address -- Contact information -- Demographic information The customer should be enabled.
|
- Determine Customer to update
-
The first step is that the Customer Service Representative needs to determine which user to update. |
- Determine parent organization
-
In the B2B scenario, the customer must choose a parent organization. This represents the buyer organization under which the
customer wants to be registered.
|
- Enter comment
-
Enter a comment to be kept with the order. The comment can optionally be chosen to be e-mailed to the customer. |
- Enter order price adjustments
-
The Customer Service Representative can enter order price adjustments. This price adjustments that can be entered are -- An amount to be subtracted from the order -- An amount that will be the shipping charge -- A coupon identifier that will be used to calculate a discounted price
|
- Find catalog item
-
Find an item by name or part number in the catalog. |
- Find customer
-
Find the customer using information obtained from them -- Logon ID -- First name -- Last name -- Phone number -- e-mail address -- Zip/postal code -- Account (BE)
|
- Find customer's order
-
Find an order for a customer. A search can be performed using one of the following: -- Order number -- Customer logon ID -- Advanced Search options: --- Order creation date range --- Order modification date range --- Customer information: ---- First name ---- Last name ---- Address ---- Phone number ---- E-mail address ---- ZIP/postal code
|
- Find order item
-
Find an order item in an existing order. |
- Find order(s)
-
Find by: order number and customer logon Id Advanced query: by all order fields: address, order status, date (start end), e-mail, phone
|
- Find products for customer
-
Find products for the customer that will be added to the shopping cart. Products can be found using a fuzzy search by either
product name or SKU.
|
- Find return
-
Find the return in the system. |
- Gather customer information
-
Customer service representatives can get information about customers while they are monitoring a customer care queue. By default
the following information is available: --Customer profile: The customer's account information and purchase history --Shopping cart: Information about the products that have been put into the customer's shopping cart
In addition, during a chat session with a customer, customer service representatives can also view the page that the customer
is browsing.
|
- Give customer return instructions (External task)
-
Give instructions to the customer as to how and where to return the goods. |
- Handle item availability
-
A customer chooses one of the three Availablility to Promise methods to manage backordered items. There are three available
methods: ship the order when all the items are available, ship the available items first then ship the rest of the items when
they are available, and ship the available items only. The CSR moves the items that the customer does not want now to another
order or removes the unwanted items.
|
- Modify return request
-
Modify the return request to allow it to be successfully approved. |
- Monitor customer care request
-
Customer service representatives must start the customer care applet using the WebSphere Commerce Accelerator to be able to
monitor a customer care queue and accept requests from customers.
|
- Negotiate return (External task)
-
Negotiate with customer over the denial in an attempt to resolve the dispute. |
- Notify customer about RMA number (External task)
-
Notify the customer that a Return Merchandise Authorization(RMA) has been generated and provide the RMA number for reference. |
- Notify customer order doesn't exist (External task)
-
Inform the customer that the order does not exist in whatever means the business supports. |
- Notify customer order is denied (External task)
-
Redirect to quote expiry, URL if specified, to inform buyer that the quote is not valid and the store does not accept expired
quotes or it accepts them but the total that was recalculated was larger than the original order total and the store does
not allow this.
|
- Notify customer refund won't happen (External task)
-
Notify the customer that the refund for the return request will not be issued to the customer. An example of when this might
occur is for a store that does not support refunds to a person that is not a registered user.
|
- Notify customer ret doesn't exist (External task)
-
Inform the customer that the return does not exist in the system. |
- Notify customer return is denied (External task)
-
Notify the customer that the return has been rejected. |
- Obtain customer information
-
Obtain information from the customer that will allow the customer to be found in the system. One of the following can be used
to find a customer's record: -- Logon ID -- First name -- Last name -- Phone number -- E-mail address -- ZIP/Postal code -- Account (BE)
|
- Provide a solution
-
A customer service representative can provide a solution to the customer either by answer the question in plain text format,
or by re-direct the customer's browser to the Web page that the customer is looking for.
|
- Receive return request
-
Receive the return request from the customer, which typically would be via mail or e-mail. The request should identify the
original order and/or the customer that placed the original order. It is possible that customer did not place the original
order and that the original order is not identified.
|
- Reject return updates
-
The updates will be rejected if the goods for the return have been received already or a credit was issued already. |
- Remove ad-hoc item from return req
-
Remove an ad-hoc item from the return request. |
- Remove order item from return req
-
Remove an order item from the return request. |
- Requeue request
-
If a customer service representative concludes that a customer care request can be better served by another customer service
representative, he can requeue the request to the queue that is assigned to the target customer service representative.
|
- Reset password
-
The Customer Service Representative can reset a customer's password on their behalf. This will generate a new password for
the customer, and send them an email notification with the new password. See 'password reset' in the online help for more
details.
|
- Select line of credit
-
Select line of credit as the payment method to be used for issuing the credit to the returner. |
- Select shipping address
-
The customer provides the shipping address and the CSR enters it. The address is remembered for the registered customer. Multiple
shipping addresses per order can be entered.
|
- Understand customer request
-
Usually, a chat session with a customer starts with a series of questions and answers sent back and forth between the customer
and the customer service representative, until the customer service representative fully understands the background of the
request.
|
- Update customer profile information
-
The WebSphere Commerce member subsystem supports storing user profile information about customers. This information is extensible
if there are requirements to capture additional information. The user profile covers information from the user profile, demographics,
and business profile tables. See the UserRegistrationUpdateCmd in the online help for the complete list of attributes supported
by default in WebSphere Commerce member subsystem.
|
- Update partner site uid and pwd
-
This task is only available in the demand chain model. The partner site userid and password can be used to define user credentials
for multiple distributors. See the topic Partner groups and partner sites in the WebSphere Commerce production online help
for more details.
|
- Update refund method
-
Update the refund payment method. |
- Add ad-hoc item to return request
-
Add an ad-hoc item to the return request. An ad-hoc item is one that is not in the original order. |
- Add catalog item
-
Add a catalog item to the return request, without referencing an existing order item. |
- Add coupon into coupon wallet
-
A customer selects a suitable coupon from the coupon wallet. |
- Add order item to return request
-
Add an order item to the return request. This indicates that the item is an item being returned. |
- Add product into requisition list
-
A customer can select a previously created requisition list. The items are added to the selected requisition list. |
- Add product to requisition list
-
A registered customer adds a product into a requisition list. |
- Add product to shopping cart
-
A customer adds a selected product into a shopping cart. If a shopping cart already exists, the product will be added into
it. Otherwise, a new shopping cart will be created.
|
- Add product to wish list
-
A registered customer adds a product into a wish list. If no wish list exists, a new one is created. |
- Add SKU to shopping cart
-
The customer orders a product by directly inputting a SKU number. |
- Adjust addresses in shopping cart
-
Change the desired products in the order to the new address. |
- Adjust refund amount
-
Adjust the refund amount up or down based on negotiation with the customer. |
- Answer questions
-
The customer selects an answer to one question at a time. Each time, the answer will narrow down the set of the products the
customer is interested in.
|
- Approve return manually
-
Manually approve the return. Return items will have an "Approved Manually" state. |
- Assign CSR to queues
-
Customer service supervisor can assign customer service representatives to a store's customer care queue using the WebSphere
Commerce Accelerator.
|
- Assign roles to user
-
The Customer Service Representative may choose to assign additional roles to the user, beyond what is automatically assigned.
See the WebSphere Commerce production online help for more information on role assignment.
|
- Cancel scheduled order
-
The customer can cancel an order that they have previously scheduled. |
- Change password
-
The customer is prompted to change the password. The changed password is saved as the permanent password. |
- Chat with other CSR
-
A customer service representative can use the customer care applet to chat with other customer service representatives to
get additional help for a customer care request, or use it to inform another customer service representative about transferring
a customer care request to a different queue.
|
- Check e-mail
-
The customer checks the e-mail in the inbox. |
- Choose checkout type
-
A registered customer can choose checkout type: regular checkout, or quick checkout. |
- Choose contracts for products
-
The customer selects which one of the available contracts they would like to use for pricing each product. |
- Choose how to handle back orders
-
A customer chooses one of the two Available to Promise methods to manage backordered products. There are two available methods:
ship the order when all the products are available, or ship the available products first then ship the rest of the products
when they are available.
|
- Copy list products to shopping cart
-
Customer places an order from the requisition list page, causing the products from the list to be added to the shopping cart. |
- Create address
-
The customer creates an address in the address book. |
- Create address book
-
The customer creates one ore more addresses in the address book. |
- Create autobid
-
Create the autobid with the specified information such as the initial bid price, the maximum bid limit, the desired quantity,
their willingness to accept a partial quantity and billing, shipping information for the order. The bid activity is monitored
for autobids and bids are periodically updated to maintain a winning status until the maximum bid limit is reached.
|
- Create bid
-
Create the bid with the specified information such as the bid price, the desired quantity, their willingness to accept a
partial quantity and billing, shipping information for the order.
|
- Create customer care queues
-
The customer service supervisor can create a customer care queue for the store using the WebSphere Commerce Accelerator. |
- Create customer record
-
Create a new customer based on information obtained: -- Logon -- Password -- Name -- Challenge question/answer -- Preferred currency/language -- Address -- Contact information -- Demographic information The customer should be enabled.
|
- Create new requisition list
-
From the Requisition List screen, a customer creates a new requisition list by clicking on the Create Requisition List button. |
- Create shopping cart
-
Create a shopping cart for a customer. |
- Create shopping cart from order
-
The customer clicks the "Re-order" link for the order that they would like to reorder. The products from that order are placed
into the current shopping cart.
|
- Delete address
-
The customer deletes an address in the address book. |
- Determine Customer to update
-
The first step is that the Customer Service Representative needs to determine which user to update. |
- Determine parent organization
-
In the B2B scenario, the customer must choose a parent organization. This represents the buyer organization under which the
customer wants to be registered.
|
- Enter billing address
-
The customer provides a billing address and submits it. The address is remembered for the registered customer. For guest customers,
the address is remembered as long as the customer does not close the browser.
|
- Enter comment
-
Enter a comment to be kept with the order. The comment can optionally be chosen to be e-mailed to the customer. |
- Enter order price adjustments
-
The Customer Service Representative can enter order price adjustments. This price adjustments that can be entered are -- An amount to be subtracted from the order -- An amount that will be the shipping charge -- A coupon identifier that will be used to calculate a discounted price
|
- Enter payment information
-
The customer specifies the payment information, such as payment method, and credit card information. |
- Enter personal identification
-
The customer specifies a registered e-mail address, to which the e-mail that has a temporary password is sent. |
- Enter promotion code
-
Customers have the option to provide a promotion code to receive discounts or special offers on their order. |
- Enter recipient information
-
The customer provides one or more e-mail addresses of the recipients, and optionally provides descriptions. |
- Enter registration information
-
The customer provides required registration information, including e-mail address and password. |
- Enter search criteria
-
In simple search mode, the customer can type one line of text for the search criteria. In advanced search mode, a variety
of search criteria can be specified.
|
- Enter shipping address
-
The customer provides the shipping address and submits it. The address is remembered for the registered customer. For the
guest customer, the address is remembered as long as the customer does not close the browser. The customer can specify multiple
shipping addresses per shipping method.
|
- Examine addresses in shopping cart
-
Check the addresses for products in the shopping cart to determine if any of them are currently going to the address that
needs updating.
|
- Find catalog item
-
Find an item by name or part number in the catalog. |
- Find customer
-
Find the customer using information obtained from them -- Logon ID -- First name -- Last name -- Phone number -- e-mail address -- Zip/postal code -- Account (BE)
|
- Find customer's order
-
Find an order for a customer. A search can be performed using one of the following: -- Order number -- Customer logon ID -- Advanced Search options: --- Order creation date range --- Order modification date range --- Customer information: ---- First name ---- Last name ---- Address ---- Phone number ---- E-mail address ---- ZIP/postal code
|
- Find order item
-
Find an order item in an existing order. |
- Find order(s)
-
Find by: order number and customer logon Id Advanced query: by all order fields: address, order status, date (start end), e-mail, phone
|
- Find orders requiring payment attn
-
This task involves looking for orders that have a bad payment status. In some cases, the status in itself is not necessarily
bad, but it has been in that state for too long to be considered good. Some examples are: -- An order with status A indicates that the order requires review. The payment system has returned AVS code(s) that the
store does not accept. -- An order has been in state M (pending authorization) for an unacceptable amount of time.
|
- Find products for customer
-
Find products for the customer that will be added to the shopping cart. Products can be found using a fuzzy search by either
product name or SKU.
|
- Find return
-
Find the return in the system. |
- Find scheduled order
-
The customer clicks on Order Status, and browses through the list of scheduled orders to find the one they would like to view. |
- Gather customer information
-
Customer service representatives can get information about customers while they are monitoring a customer care queue. By default
the following information is available: --Customer profile: The customer's account information and purchase history --Shopping cart: Information about the products that have been put into the customer's shopping cart
In addition, during a chat session with a customer, customer service representatives can also view the page that the customer
is browsing.
|
- Give customer return instructions
-
Give instructions to the customer as to how and where to return the goods. |
- Handle item availability
-
A customer chooses one of the three Availablility to Promise methods to manage backordered items. There are three available
methods: ship the order when all the items are available, ship the available items first then ship the rest of the items when
they are available, and ship the available items only. The CSR moves the items that the customer does not want now to another
order or removes the unwanted items.
|
- Log on
-
A registered user logs on to the store by providing the ID and the corresponding password.
|
- Modify address book
-
The customer modifies or deletes the addresses in the address book, or adds new addresses. |
- Modify return request
-
Modify the return request to allow it to be successfully approved. |
- Modify shopping cart
-
Modify the shopping cart by adding items to it or removing items from it. |
- Monitor customer care request
-
Customer service representatives must start the customer care applet using the WebSphere Commerce Accelerator to be able to
monitor a customer care queue and accept requests from customers.
|
- Negotiate return
-
Negotiate with customer over the denial in an attempt to resolve the dispute. |
- Notify customer about RMA number
-
Notify the customer that a Return Merchandise Authorization(RMA) has been generated and provide the RMA number for reference. |
- Notify customer order doesn't exist
-
Inform the customer that the order does not exist in whatever means the business supports. |
- Notify customer order is denied
-
Redirect to quote expiry, URL if specified, to inform buyer that the quote is not valid and the store does not accept expired
quotes or it accepts them but the total that was recalculated was larger than the original order total and the store does
not allow this.
|
- Notify customer refund won't happen
-
Notify the customer that the refund for the return request will not be issued to the customer. An example of when this might
occur is for a store that does not support refunds to a person that is not a registered user.
|
- Notify customer ret doesn't exist
-
Inform the customer that the return does not exist in the system. |
- Notify customer return is denied
-
Notify the customer that the return has been rejected. |
- Obtain customer information
-
Obtain information from the customer that will allow the customer to be found in the system. One of the following can be used
to find a customer's record: -- Logon ID -- First name -- Last name -- Phone number -- E-mail address -- ZIP/Postal code -- Account (BE)
|
- Provide a solution
-
A customer service representative can provide a solution to the customer either by answer the question in plain text format,
or by re-direct the customer's browser to the Web page that the customer is looking for.
|
- Receive return request
-
Receive the return request from the customer, which typically would be via mail or e-mail. The request should identify the
original order and/or the customer that placed the original order. It is possible that customer did not place the original
order and that the original order is not identified.
|
- Reject return updates
-
The updates will be rejected if the goods for the return have been received already or a credit was issued already. |
- Remove ad-hoc item from return req
-
Remove an ad-hoc item from the return request. |
- Remove order item from return req
-
Remove an order item from the return request. |
- Remove requisition list
-
The customer can remove a requisition list from their account by clicking the 'Remove' link beside the requisition list. |
- Remove requisition list item
-
The customer can remove an item from the requisition list by clicking the appropriate link beside the item that is to be removed. |
- Request return update
-
The customer requests an update to their return request. |
- Requeue request
-
If a customer service representative concludes that a customer care request can be better served by another customer service
representative, he can requeue the request to the queue that is assigned to the target customer service representative.
|
- Reset password
-
The Customer Service Representative can reset a customer's password on their behalf. This will generate a new password for
the customer, and send them an email notification with the new password. See 'password reset' in the online help for more
details.
|
- Respond to a message in the forum
-
Respond to messages in the forum. |
- Review order summary
-
The customer views the summary of an order before submitting it. The ordered products and order prices (discount information
is displayed where applicable), are reviewed.
|
- Review pricing
-
The customer checks that the pricing on the order is acceptable. |
- See all bids
-
View the bids submitted by all participants in an auction. |
- Select a requisition list
-
The customer select a requisition list from a list of existing requisition lists. |
- Select advertised product
-
The customer clicks on the advertised product; the product page displays. |
- Select an existing requisition list
-
A customer can select a previously created requisition list. The items are added to the selected requisition list. |
- Select an order
-
The customer can choose any order in the summary table and view details. |
- Select attributes
-
If the product has one or more attribute, the customer can choose values for the attributes. Once the attributes are specified,
the page that contains the matching product item displays.
|
- Select backorder handling
-
A customer chooses one of the three Available to Promise methods to manage backordered items. There are three available methods:
ship the order when all the items are available, ship the available items first then ship the rest of the items when they
are available, and ship the available items only.
|
- Select comparison criteria
-
The comparison criteria consist of a range of product attributes. By selecting the criteria, only the products that are within
that range are displayed.
|
- Select coupon to redeem
-
The customer selects one or more available coupons to redeem. The price of the order is adjusted accordingly. |
- Select current order
-
A customer views the current order. |
- Select default list name
-
The name "Unknown name" is provided as the default requisition list name. If a customer does not specify the requisition list
name, this name will be used. Multiple requisition lists can share the same name.
|
- Select hosted store
-
A customer selects a hosted store link from the search results. |
- Select item
-
An item is a product that has a SKU. The customer selects an item by clicking on the link to the item information page. |
- Select line of credit
-
Select line of credit as the payment method to be used for issuing the credit to the returner. |
- Select new addresses
-
Select new addresses for products that are currently going to the address that needs to be deleted. |
- Select payment method
-
Select a method of payment from those that are eligible to be selected. |
- Select previously placed order
-
The customer chooses which of their placed order of interest. |
- Select product
-
The customer clicks on a product link, and the product information displays. The customer may be able to specify product attributes
on this page.
|
- Select product attributes
-
If the product has one or more attribute, the customer can choose values for the attributes. Once the attributes are specified,
the page that contains the matching product item displays.
|
- Select product from req list
-
The customer selects a product from a requisition list to order |
- Select product from search result
-
The returned search results contain links to the matching products. A customer clicks on one of the links, and the information
of the linked product displays.
|
- Select product from wish list
-
A customer selects a product from the wish list |
- Select product in the e-mail
-
The customer clicks on a link or image of the product; the product page displays. |
- Select requisition list
-
A customer selects an existing requisition list that they would like to modify. |
- Select shipping address
-
The customer provides the shipping address and the CSR enters it. The address is remembered for the registered customer. Multiple
shipping addresses per order can be entered.
|
- Select shipping method
-
The customer selects one or more shipping methods for the ordered items. |
- Select SKU
-
A product can have mutiple SKUs. The customer selects a SKU by clicking on the link to the SKU information page. |
- Select store category
-
A customer selects one of the many store categories available on the site. |
- Select subcategory
-
The customer clicks on a category link, and the page that contains all of the subcategories or products displays. |
- Select suggested product
-
The customer clicks on the advertised product; the product page displays. |
- Select supplier and contract
-
Select the supplier and contract to buy from. |
- Select supplier and list
-
Customer selects a supplier and a requisition list to order from. |
- Select supplier shopping cart
-
Products from different suppliers are added to separate shopping carts. The registered customer selects the shopping cart
of a particular supplier to check out.
|
- Send the wish list
-
The customer sends the wish list to all the recipients by clicking <b>Send wish list</b>. |
- Specify scheduling conditions
-
The customer can select when they want the first of the scheduled orders to occur, and how often they would like it to repeat
after that.
|
- Specify sku(s)
-
A customer can add one or more items to a requisition list. To add items the customer specifies the SKU. |
- Specify supplier and SKU(s)
-
A customer can add one or more items to a requisition list. To add items, the customer specifies the supplier and SKU(s). |
- Specify user identification
-
The customer types in their user ID so that their password can be reset. |
- Submit order
-
The customer submits an order for processing. The credit card number is validated before the submission is successful. |
- Submit registration form
-
The customer submits the registration form. If the data in the form is complete and valid, the customer is registered. |
- Understand customer request
-
Usually, a chat session with a customer starts with a series of questions and answers sent back and forth between the customer
and the customer service representative, until the customer service representative fully understands the background of the
request.
|
- Update address book
-
The customer modifies or deletes the addresses in the address book, or adds new addresses. |
- Update customer profile information
-
The WebSphere Commerce member subsystem supports storing user profile information about customers. This information is extensible
if there are requirements to capture additional information. The user profile covers information from the user profile, demographics,
and business profile tables. See the UserRegistrationUpdateCmd in the online help for the complete list of attributes supported
by default in WebSphere Commerce member subsystem.
|
- Update list item quantity
-
The customer chooses a product and enters in a new quantity in the space provided. Clicking on the appropriate button will
update the quantity of the chosen product.
|
- Update partner site uid and pwd
-
This task is only available in the demand chain model. The partner site userid and password can be used to define user credentials
for multiple distributors. See the topic Partner groups and partner sites in the WebSphere Commerce production online help
for more details.
|
- Update personal information
-
The customer provides and then saves their personal information. |
- Update quick checkout profile
-
The customer updates the information recorded in a quick checkout profile. |
- Update refund method
-
Update the refund payment method. |
- Update registration information
-
The customer provides and then saves their personal information. |
- Update requisition list name
-
The customer can change the name of the current requisition list by entering in a new name into the Requisition List Name
field and then clicking the 'Change Name' button.
|
- Update shopping cart
-
The customer makes any updates necessary to the shopping cart. Updates can include changing quantities or contracts for existing
products, or adding new products.
|
- View list of order status summary
-
The customer can view the table that contains a brief summary of the status of each order. |
- View order detail
-
Customers can choose any order in the summary table and view the details. For the selected order, a page displays with detailed
order status information. The complete list of purchased products are shown on this page.
|
- View order history
-
The customer can view the table that contains a brief summary of the status of each order. |
- View order status detail
-
For the selected order, a page displays with detailed order status information. |
- View order summary
-
The customer views the summary of an order before submitting it. The ordered items, order prices (discount and coupon information
is displayed where applicable), and payment information display.
|
- Add attributes
-
Add or modify attributes that describe a product, service, part, SKU, kit or bundle. This could include images, additional
translated descriptions, manufacturer or supplier data, MSRP, descriptive attribute information, and defining attribute information
for products. A combination of the set of defining attribute's values determine the SKUs for a product.
|
- Add category attributes
-
Add or modify attributes which describe the Category. This includes images, descriptions and other information in different
languages associated with the Category.
|
- Add category hierarchy
-
Add or modify the relationship of a Category within the hierarchy of the Catalog / Taxonomy. A Category can be added as a
child Category to the root of the Catalog or as a child of another Category.
|
- Adjust inventory reservation
-
Adjust the inventory for a given inventory reservation by the amount of the given quantity. This is a task command. Required
arguments are inventory reservation number and adjustment quantity (which may be negative). If the quantity argument is negative, it means release inventory. If this is the case, see whether or not there is enough
inventory reserved to satisfy the release amount. If quantity argument is positive, it means add inventory to the reservation. If this is the case, see whether or not there
is enough inventory to satisfy the additional reservation amount. If the above edit checks are successful, adjust the quantity reserved by the amount of the quantity argument.
|
- Assign display pages
-
Each catalog, category, product or SKU requires an associated JSP file for display. The category, product or SKU may be assigned
a specific JSP file, a default JSP file per store or per site.
|
- Categorize product
-
Add or modify the relationship of a product, part, service, kit or bundle under a category of the hierarchy of the catalog
or taxonomy.
|
- Close expected inventory record
-
This task creates an expected inventory record for the specified vendor for the specified item.
Input: -- Fulfillment center -- Expected data -- Quantity -- part number (item specification) -- Comments
|
- Create associations
-
The Product Manager creates an association between a source product or SKU and target product or SKU, or between a source
category and target category. A search for the source and target is performed and then the following associations can be
specified: -- Cross sell -- Up sell -- Accessory -- Replacement -- Alternative -- Substitute The associations can be used within marketing campaign initiatives that schedule and provide content to e-Marketing Spots
within JSP files.
|
- Create catalog
-
The Product Manager or Category Manager creates a master catalog or sales catalog. The catalog has attributes such as images
and descriptions in multiple languages.
|
- Create category
-
Create a category within the catalog. |
- Create composite product
-
Create a product as a composite product. The composite product will define a set of attributes and its associated possible
values
|
- Create configurable product
-
Create a configurable product or dynamic kit as a product. A configurable product will define a set of attributes and its
associated possible values.
|
- Create data export transform
-
The format of the data from WebSphere Commerce will be a fixed XML format from which customers must map to their XML or text
format.
|
- Create data import transform
-
Since the format of externally supplied product or category data may not match WebSphere Commerce's XML-based format, WebSphere
Commerce provides editors to assist the mapping of fields prior to the database load.
|
- Create drop ship inventory receipts
-
This task is takes a list of items to be drop-shipped and creates inventory receipts for the items for the target fulfillment
center.
|
- Create expected inventory record
-
This task creates an expected inventory record for the specified vendor for the specified item.
Input -- Fulfillment center -- Expected data -- Quantity -- Part number (item specification) -- Comments
|
- Create guided sell rules
-
The Guided Sell shopping metaphor provides product recommendations in which a list of SKUs are returned based on the customers
answers to a set of presented questions. The Guided Sell Tool within WebSphere Commerce Accelerator is used to create a search
space over a set of products. A search space can be created on a specific category within either the master or sales catalog,
or by selecting specific products. The Guided Sell Tool is then used to create a set of hierarchical questions on the search
space. Each question in the hierarchy reduces the number of products and SKUs within the search space. Creating the tree
requires the following: -- Create the question with text. -- Specify the attribute constraint which applies to the question. -- Add the question into the hierarchy.
|
- Create package
-
Create a product for a package. The package will define a set of attributes and its associated possible values. |
- Create part
-
A part is a product within the master catalog that may not be sold individually but rather is used to build kits and bundles
in the catalog.
|
- Create product
-
A product is a high level container which defines a set of attributes and its associated possible values. These values describe
the SKUs of that particular product.
|
- Create product comparison rules
-
The Product Comparison shopping metaphor provides a view of multiple SKUs usually in tabular form such that the values of
each attribute of the SKUs are displayed for comparison. WebSphere Commerce provides the Product Advisor Tool to create a search space over a set of products which have like attributes
for the comparison. A search space can be created on a specific category within either the master or sales catalog, or by
selecting specific products. Within the search space, attributes are selected to create rules that customers will base their selection of products on.
In addition, display mechanisms for the attributes are specified for the comparison view within a JSP file.
|
- Create product exploration rules
-
The Product Exploration shopping metaphor provides search capabilities possible ranges of values for attributes of SKUs are
selected by the customer in order to reduce the list of products to display. WebSphere Commerce provides the Product Advisor
Tool to create a search space over a set of products which have like attributes for the exploration. A search space can be
created on a specific category within either the Master or Sales Catalog, or by selecting specific products. Within the search space, attributes are selected to create rules that businesses will base their search of products on. In
addition, display mechanisms for the attributes are specified for the exploration view within a JSP file.
|
- Create service
-
A service is a product within the master catalog that the business provides accompanying another product. Examples of services
are warranties, gift wrapping, or personalized messages.
|
- Create SKU
-
A SKU represents a buyable instance of a product and is defined by a particular combination of the product's attribute values.
For example, a product may be a knit sweater with the following defining attributes: color ( values are red or blue) and
size (values are S, M, or L). There could potentially be 6 SKUs associated with the product, one for each combination of
the defining attributes (red-S, red-M, red-L, blue-S, blue-M, blue-L). Each SKU may specify its own attributes such as images, MSRP and descriptions. SKUs may be generated based on possible combinations
of the product and its defining attributes.
|
- Create vendor
-
This task creates a vendor in WebSphere Commerce. A vendor must exist and serve is input when creating expected inventory
records.
|
- Define replacement product
-
The Product Manager creates an association between the discontinued product and the new announced product. This association
can be used in marketing campaign initiatives that schedule and provide content to e-Marketing Spots within JSP files.
|
- Delete expected inventory record
-
This task deletes an existing expected inventory record for the specified vendor for the specified item.
Input: A ra_id indentifying an expected inventory record
|
- Determine reason inventory found (External task)
-
This is an external task that will determine the reason for the inventory adjustment. The output of the task is an adjustment
reason code. The code is maintained with the adjustment for tracking and reporting purposes.
|
- Determine reason inventory is lost (External task)
-
This is an external task for determining the reason for the adjustment. This reason will be specified when making the adjustment.
The output of this task is an adjustment code.
|
- Export product/category data
-
The unloading of the product and category data from the WebSphere Commerce database using a mass export utility. |
- Find expected inventory records
-
The task is used to find expected inventory records. It finds a expected inventory records for a vendor for a particular store.
|
- Find vendor
-
The task is used to find a vendor, since one is required for creating expected inventory records. It finds a vendor for a
particular store.
|
- Get list of drop-shippable items
-
This task is used to determine the list of items that will be drop-shipped from the target drop-ship fulfillment center.
The output is a list of items and a fulfillment center.
|
- Import product/category data
-
The loading of the product or category data into the WebSphere Commerce database using the Loader utility. |
- Override price
-
Sets a price for a product against the master catalog. Each product may have a different price assigned for each supported
currency. Each supported currency may have ranged pricing based on quantity purchased. This is the price that is used within
the default contract for a store. Shoppers may be entitled to other contracts that could result in a different price being
offered.
|
- Remove product
-
A product is removed from the Master Catalog either physically or logically such that it cannot be bought or viewed. |
- Review strategy
-
At this stage, the product manager will analyze the current product strategy against the product strategy document. Based
on this analysis, decisions to make changes to the current product/catalog are made.
|
- Select category
-
Select an existing category within a Master Catalog or Sales Catalog to add to the current Sales Catalog. |
- Select customer segment
-
Select the customer segment targeted for this activity. |
- Select expected inventory record
-
Select an expected inventory record from those in the list. |
- Select product subset
-
Select a subset of products and categories that will be available in the online catalog. Any products or categories that
are not selected in the subset, will not be available for purchase in the online store.
|
- Select products
-
Select products for which the standard price is being defined |
- Select products and categories
-
The Product Manager must first select the set of products or categories to promote with merchandising concepts. |
- Set coupon properties
-
Optionally set the relative number of days in which the coupon will expire after being issued. |
- Set price
-
Sets a price for a product against the master catalog. Each product may have a different price assigned for each supported
currency. Each supported currency may have ranged pricing based on quantity purchased. This is the price that is used within
the default contract for a store. Shoppers may be entitled to other contracts that could result in a different price being
offered.
|
- Set price adjustments
-
Allows the reseller to set a pricing adjustment on a manufacturer's product. For example, a manufacturer's products may have
a MSRP price list set against them. In this case, the reseller may wish to set an adjustment that offers all products in
a particular category at a 10% below the MSRP price. Alternatively, the manufacturer may have prices set according to cost.
In this case, the reseller would mark-up the prices based on a percentage they wish to make on each sale (say, 15%).
|
- Set product state
-
A product can have associated states to indicate its stage in the life cycle: Announced Product, Available Product, Discontinued
Product, or Withdrawn Product. The product state can include dates to indicate the next state change
|
- Set promotion properties
-
Each promotion has a name, description, and priority. These may be set at creation time. Promotion limits may also be set
to describe how a promotion should be applied when procesing an order. The limits are as follows: -- Limit on how many times a promotion can be applied to an order, any order; -- Limit on how many time a promotion can be applied for an individual shopper; -- Limit on the number of times a promotion can be applied overall. In addition, an optional promotion code may be specified. When a promotion code is specified for a promotion, the business
user may indicate whether or not the customer needs to enter the code in order to redeem the promotion.
|
- Set promotion rewards
-
For product promotion, the following types may be selected: --Percentage off per item or product --Fixed amount off for all items or products --Fixed amount off per item or product --Buy any item or product, get one more at a discount --Free gift with purchase For order promotion, the following types may be selected: --Percentage off --Fixed amount off --Free gift with purchase For shipping promotion, the following types may be selected: --Discounted shipping
|
- Set promotion schedule
-
Set effective dates, days, and times in which the promotion is valid. |
- Update affected kits
-
Any kits or bundles that contain the discontinued product need to be updated. Updates can take the form of one or more of
the following: -- The kit is also marked as discontinued. -- The kit's price and description are modified to reflect the change. -- The replacement product is substituted in the kit.
|
- Update attributes
-
Add or modify attributes that describe a product, service, part, SKU, kit or bundle. This could include images, additional
translated descriptions, manufacturer or supplier data, MSRP, descriptive attribute information, and defining attribute information
for products. Each combination of the set of defining attribute's values determine the SKUs for a product.
|
- Update expected inventory record
-
This tasks creates an expected inventory record for the specified vendor for the specified item.
Input: -- Fulfillment center -- Expected data -- Quantity -- Part number (item specification) -- Comments
|
- Update kits and bundles
-
If the contents of the catalog have been changed, some kits and bundles may no longer be correct or applicable. The validity
of any kit or bundle that is affected by a catalog update such as a product announcment or withdrawal must be verified and
updated appropriately.
|
- Update merchandising
-
Merchadising associations may no longer be relevant or can be enhanced. Affected merchandising associations need to be updated
to reflect the current catalog.
|
- Update price
-
The product manager updates the product price as a ruesult of the base list price change. This price change may be a fixed
price override or a percentage adjustment.
|
- Add coupon into coupon wallet
-
A customer selects a suitable coupon from the coupon wallet. |
- Add product into requisition list
-
A customer can select a previously created requisition list. The items are added to the selected requisition list. |
- Add product to requisition list
-
A registered customer adds a product into a requisition list. |
- Add product to shopping cart
-
A customer adds a selected product into a shopping cart. If a shopping cart already exists, the product will be added into
it. Otherwise, a new shopping cart will be created.
|
- Adjust addresses in shopping cart
-
Change the desired products in the order to the new address. |
- Cancel scheduled order
-
The customer can cancel an order that they have previously scheduled. |
- Change password
-
The customer is prompted to change the password. The changed password is saved as the permanent password. |
- Check e-mail
-
The customer checks the e-mail in the inbox. |
- Choose contracts for products
-
The customer selects which one of the available contracts they would like to use for pricing each product. |
- Choose how to handle back orders
-
A customer chooses one of the two Available to Promise methods to manage backordered products. There are two available methods:
ship the order when all the products are available, or ship the available products first then ship the rest of the products
when they are available.
|
- Copy list products to shopping cart
-
Customer places an order from the requisition list page, causing the products from the list to be added to the shopping cart. |
- Create address
-
The customer creates an address in the address book. |
- Create address book
-
The customer creates one ore more addresses in the address book. |
- Create autobid
-
Create the autobid with the specified information such as the initial bid price, the maximum bid limit, the desired quantity,
their willingness to accept a partial quantity and billing, shipping information for the order. The bid activity is monitored
for autobids and bids are periodically updated to maintain a winning status until the maximum bid limit is reached.
|
- Create bid
-
Create the bid with the specified information such as the bid price, the desired quantity, their willingness to accept a
partial quantity and billing, shipping information for the order.
|
- Create new requisition list
-
From the Requisition List screen, a customer creates a new requisition list by clicking on the Create Requisition List button. |
- Create shopping cart from order
-
The customer clicks the "Re-order" link for the order that they would like to reorder. The products from that order are placed
into the current shopping cart.
|
- Delete address
-
The customer deletes an address in the address book. |
- Enter billing address
-
The customer provides a billing address and submits it. The address is remembered for the registered customer. For guest customers,
the address is remembered as long as the customer does not close the browser.
|
- Enter payment information
-
The customer specifies the payment information, such as payment method, and credit card information. |
- Enter personal identification
-
The customer specifies a registered e-mail address, to which the e-mail that has a temporary password is sent. |
- Enter promotion code
-
Customers have the option to provide a promotion code to receive discounts or special offers on their order. |
- Enter shipping address
-
The customer provides the shipping address and submits it. The address is remembered for the registered customer. For the
guest customer, the address is remembered as long as the customer does not close the browser. The customer can specify multiple
shipping addresses per shipping method.
|
- Examine addresses in shopping cart
-
Check the addresses for products in the shopping cart to determine if any of them are currently going to the address that
needs updating.
|
- Find scheduled order
-
The customer clicks on Order Status, and browses through the list of scheduled orders to find the one they would like to view. |
- Log on
-
A registered user logs on to the store by providing the ID and the corresponding password.
|
- Modify address book
-
The customer modifies or deletes the addresses in the address book, or adds new addresses. |
- Remove requisition list
-
The customer can remove a requisition list from their account by clicking the 'Remove' link beside the requisition list. |
- Remove requisition list item
-
The customer can remove an item from the requisition list by clicking the appropriate link beside the item that is to be removed. |
- Respond to a message in the forum
-
Respond to messages in the forum. |
- Review order summary
-
The customer views the summary of an order before submitting it. The ordered products and order prices (discount information
is displayed where applicable), are reviewed.
|
- Review pricing
-
The customer checks that the pricing on the order is acceptable. |
- See all bids
-
View the bids submitted by all participants in an auction. |
- Select a requisition list
-
The customer select a requisition list from a list of existing requisition lists. |
- Select an existing requisition list
-
A customer can select a previously created requisition list. The items are added to the selected requisition list. |
- Select an order
-
The customer can choose any order in the summary table and view details. |
- Select coupon to redeem
-
The customer selects one or more available coupons to redeem. The price of the order is adjusted accordingly. |
- Select current order
-
A customer views the current order. |
- Select default list name
-
The name "Unknown name" is provided as the default requisition list name. If a customer does not specify the requisition list
name, this name will be used. Multiple requisition lists can share the same name.
|
- Select item
-
An item is a product that has a SKU. The customer selects an item by clicking on the link to the item information page. |
- Select new addresses
-
Select new addresses for products that are currently going to the address that needs to be deleted. |
- Select previously placed order
-
The customer chooses which of their placed order of interest. |
- Select product attributes
-
If the product has one or more attribute, the customer can choose values for the attributes. Once the attributes are specified,
the page that contains the matching product item displays.
|
- Select product from req list
-
The customer selects a product from a requisition list to order |
- Select product from wish list
-
A customer selects a product from the wish list |
- Select requisition list
-
A customer selects an existing requisition list that they would like to modify. |
- Select shipping method
-
The customer selects one or more shipping methods for the ordered items. |
- Select SKU
-
A product can have mutiple SKUs. The customer selects a SKU by clicking on the link to the SKU information page. |
- Select supplier and contract
-
Select the supplier and contract to buy from. |
- Select supplier and list
-
Customer selects a supplier and a requisition list to order from. |
- Select supplier shopping cart
-
Products from different suppliers are added to separate shopping carts. The registered customer selects the shopping cart
of a particular supplier to check out.
|
- Specify scheduling conditions
-
The customer can select when they want the first of the scheduled orders to occur, and how often they would like it to repeat
after that.
|
- Specify sku(s)
-
A customer can add one or more items to a requisition list. To add items the customer specifies the SKU. |
- Specify supplier and SKU(s)
-
A customer can add one or more items to a requisition list. To add items, the customer specifies the supplier and SKU(s). |
- Specify user identification
-
The customer types in their user ID so that their password can be reset. |
- Update address book
-
The customer modifies or deletes the addresses in the address book, or adds new addresses. |
- Update list item quantity
-
The customer chooses a product and enters in a new quantity in the space provided. Clicking on the appropriate button will
update the quantity of the chosen product.
|
- Update personal information
-
The customer provides and then saves their personal information. |
- Update quick checkout profile
-
The customer updates the information recorded in a quick checkout profile. |
- Update registration information
-
The customer provides and then saves their personal information. |
- Update requisition list name
-
The customer can change the name of the current requisition list by entering in a new name into the Requisition List Name
field and then clicking the 'Change Name' button.
|
- Update shopping cart
-
The customer makes any updates necessary to the shopping cart. Updates can include changing quantities or contracts for existing
products, or adding new products.
|
- View list of order status summary
-
The customer can view the table that contains a brief summary of the status of each order. |
- View order detail
-
Customers can choose any order in the summary table and view the details. For the selected order, a page displays with detailed
order status information. The complete list of purchased products are shown on this page.
|
- View order history
-
The customer can view the table that contains a brief summary of the status of each order. |
- View order status detail
-
For the selected order, a page displays with detailed order status information. |
- Add message
-
Create new message in the forum. |
- Add user to member group
-
Adds a customer to a given membergroup. See 'explicit membergroups' in the online help for more details. |
- Assign roles to buyer admin
-
The new user is assigned the role of buyer administrator in the new buyer organization. |
- Cancel RFQ response
-
Cancel the RFQ response. |
- Check for anomalies (External task)
-
Check for anomalous bidding activities. |
- Close store
-
Close the store to make the online store unavailable to customers. The store owner can access the store to test that any store
modifications are implemented successfully. When the changes are completed, the store owner can open the store.
|
- Create departments
-
The buyer organization can be partitioned into multiple departments. |
- Create store
-
Use the Store Creation wizard within the WebSphere Commerce Accelerator to create an online store. The store can resell products
from the hub's catalog (channel, hosting or supplier hub). The store has the option to use their own catalog, or to use both
the hub's catalog and their own.
|
- Delete message
-
Delete messages in the forum. |
- Determine organization parent
-
Organizations must always have a parent. The Seller would have communicated the parent organization as part of the creation
request.
|
- Enter buyer admin registration info
-
Information about the buyer administrator is entered, including e-mail address and password. |
- Enter required organization info
-
On a Seller's behalf, the Customer Service Representative would enter information about the new buyer organization into the
system. See the OrgEntityAddCmd in the online help for more details on the parameters available, including the mandatory parameters.
|
- Fix store data
-
The store owner uses the WebSphere Commerce Accelerator to fix the problems in their store that violate their use of the hub
(channel, hosting or supplier hub) that were identified by the Channel Manager.
|
- Force-close auction
-
Close the bidding for an auction manually. |
- Manage order failed bid(s) (External task)
-
If a problem occurs while creating the order from the winning bid(s) (for example, if Payment Manager is not active), the
order is not created. Fix the problem and recreate the order again.
|
- Mark customer message to public
-
Mark messages created by customer to public. |
- Notify Channel Manager (External task)
-
The Seller notifies the Channel Manager that the modifications to the Seller's store have been completed. The Channel Manager
can then verify that the changes have been made to their satisfaction.
|
- Open store
-
Open the store to make the online store available to customers, so they can browse the products and place orders. |
- Read messages in the forum
-
View messages in the forum |
- Remove user from member group
-
Removes a customer from a membergroup. See 'explicit membergroups' in the online help for more details. |
- Reply to customized prod attribute
-
Respond to the customized product attributes specified by a buyer. |
- Request store creation (External task)
-
Seller requests channel manager to create a store. |
- Respond to fixed price
-
Respond to the requested product fixed prices and quantities specified by a buyer. |
- Respond to percentage adjustment
-
Respond to the requested product percentage prices and quantities specified by a buyer. |
- Respond to RFQ attachments
-
Respond to the RFQ level attachments specified by a buyer. |
- Respond to terms and conditions
-
Propose an alternative to any of the terms and conditions specified by a buyer. |
- Revert response back to draft state
-
Change the response back to "draft" state so that more modifications can be made to the response. |
- Set exclusion terms
-
You can use the WebSphere Commerce catalog filtering feature to exclude any of the products or categories in the master catalog
that you do not want to be sold at the store.
|
- Set price in the response
-
Set price in the response. |
- Set up store
-
Use the WebSphere Commerce Accelerator to set up and configure the store.
Manage administrative tasks for the store by using the tasks offered under the Store menu: --Open and close the store --Redesign the store profile and how customers will navigate through the store pages --Change tax, shipping, fulfillment center, payment, and report delivery settings --Configure the store to send and receive messages (such as to notify customers or special promotions)
Exploit a variety of marketing strategies for the store by using the tasks within the Marketing menu: --Work with customer profiles, including viewing a summary of each profile --Manage campaigns and campaign initiatives, including viewing campaign initiative statistics --Create, change, and remove campaign initiative conditions --Work with e-Marketing Spots and schedule campaign initiatives on e-Marketing Spots --Manage awareness ads
Manage merchandise offered at the store by using the tasks under the Merchandising menu: --Work with products, categories, bundles and kits for the catalog --Manage your online catalog by importing a catalog, optionally filtering the products you want to sell, and adjusting prices --Find and list expected inventory records and product vendors --Manage merchandising associations (such as up-sells or cross-sells) and other special offers such as discounts and coupons
for promotional purposes --Manage auctions, including auction styles and bid control rules
Ensure the customers always come first when dealing with the store by using the tasks under the Operations menu: --Create and change customer registration information --Reset customer logon passwords --Manage orders, including creating, changing, adding comments to, or viewing a summary of an order --Splitting and canceling orders --Transfer orders for fulfillment in the channel hub and find shopping carts fulfilled in the channel hub --Administer auctions for customers --Approve, deposit, settle, and find payment using WebSphere Commerce Payments --Manage inventory, including expected inventory records and pick batches
Track and manage your business with reports (such as inventory or order management) that you can request and view within the
Reports menu.
|
- Specify auction bid control rule
-
Specify a previously defined bid rule for Sealed Bid and Open Cry auctions. |
- Specify auction display information
-
Specify what templates to use in displaying auction rules and the product display for an auction. |
- Specify auction pricing information
-
Specify pricing information for an auction. |
- Specify auction type
-
Specify the types of auction such as Open Cry auctions, Sealed Bid auctions, and Dutch auctions (Dutch auction type cannot
be specified in bid control rule).
|
- Specify bid control rule detail
-
Specify detail of the bid control rule such as name, description, associated auction type, minimum bid value and minimum bid
quantity, minimum bid increment within specified price ranges (for Open Cry auctions).
|
- Specify duration, closing rule
-
Specify when an auction starts and the conditions under which it ends. |
- Specify product and quantity
-
Specify information about the product to be auctioned such as SKU, product name, product description and auction quantity. |
- Specify product in response
-
Substitute a product in the RFQ response. This is especially useful for a made-to-order item. The buyer may include a made-to-order
item in the RFQ; the seller then reviews the RFQ, and substitutes the item the buyer had for one the seller has in the catalog.
This can only happen if the buyer has stated that the product can be substituted. If the item does not exist in the current
catalog, the seller has to create the item first.
|
- Submit auction creation
-
Submit the request to create an auction after providing all the detail. When the auction is created, the specified quantity
of the product for auction is reserved and is no longer available for "normal" sale.
|
- Submit bid control rule creation
-
Submit bid rules determine how bidding is allowed to proceed for Open Cry and Sealed Bid auctions. |
- Submit RFQ response
-
Submit the RFQ response. The buyer then reviews the response. |
- Submit style template creation
-
Submit the creation of new auction style template. |
- Update auction display information
-
Update what templates to use in displaying auction rules and the product display for an auction. |
- Update auction pricing information
-
Update pricing information for an auction. |
- Update duration, closing rule
-
Update information on when an auction starts and the conditions under which it ends. |
- Update product and quantity
-
Update information about the product to be auctioned such as SKU, product name, product description and auction quantity. |
- Withdraw participant's bid(s)
-
Withdraw bid submitted before an auction is closed. |
- Accept batch availability response
-
Accept the inventory availability response, parse the input XML document, and determine the following data: -- Fulfillment center identifier (fulfillment location) -- A list of specified items. For each specified item, find out the following. --- The member identifier and part number of the specified item --- The external UOM code for quantity (optional) --- Quantity available --- Restock date (optional)
|
- Activate RFQ
-
Change the RFQ to the "active" state when the closing rule is met (in multi-seller RFQ) or when the closing time is reached
(in a single-seller RFQ or a special bid RFQ).
|
- Add items to Manufacturer order
-
Add the designated items to the shopping cart. |
- Add to order ship history
-
Update the ship history for the item with quantity shipped and date shipped. |
- Adjust inventory
-
Adjusts existing inventory by marking down quantities in one or more rows in the RECEIPT table when the adjustment is negative.
This is required because a receipt is not allowed to have a negative quantity. If the adjustment is positive, a quantity in
a row in the RECEIPT table will be increased.
|
- Allocate from existing inventory
-
Allocate existing inventory for a particular order item at a particular fulfillment center. The behavior of the command is as follows: -- If the order item is suitable for allocation (that is, its inventory status attribute specifies unallocated or backordered)
and there is sufficient existing inventory at one of the specified fulfillment centers (searching in order from first to last
in the input fulfillment centers) to completely allocate the quantity needed by the order item, allocate it and update the
order item to reflect the allocation. -- If the order item is still unallocated or backordered and there is sufficient existing inventory at one of the specified
fulfillment centers (searching in order from first to last in the list of input fulfillment centers) to partially or fully
allocate the quantity needed by the order item, allocate that amount rounded down as explained in the next sentence and update
the order item to reflect the allocation. When the amount to allocate cannot be allocated fully, the amount actually allocated
is rounded down to the nearest multiple of a floating-point number obtained by converting the CatEntShip.QuantityMultiple
for the CatEntry of the order item to the unit of measure specified by BaseItem, dividing by BaseItem.QuantityMultiple, and
then rounding down that multiple to the nearest integer. When there is no CatEntShip for the order item's CatEntry, CatEntShip.QuantityMultiple
is assumed to be 1 and CatEntShip.QuantityMeasure is assumed to be C62. However, when the order item has no CatEntry, the
amount to allocate is not rounded down at all (that is, it is rounded down to the nearest multiple of 1). -- If none of the needed quantity can be allocated, the order item is not changed.
|
- Approve automatically
-
This is an automatic approve based on business rules. Some examples of standard checks: -- If return is with X days -- If item is creditable -- If the quantity is less than or equal to the quantity shipped -- If the item return amount is within the amount paid.
|
- Assign fulfillment center to items
-
Assign the selected fulfillment center to items to be released to fulfillment. |
- Assign winning bid(s)
-
Winners are determined based upon the auction rules. |
- Associate item status with order
-
Associate the item status in the ORDISTAT table with a WebSphere Commerce order. |
- Auto-assign roles
-
Based on the store to which the customer is registering, the organization under which the customer is being created, and the
type of registration (in this case user registration) the customer will be granted roles in the system based on the configuration
specified in the MemberRegistrationAttributes.xml (see section on MemberRegistrationAttributes.xml in the online help for
more details). In general, a B2C site will be configured either to grant the customer a RegisteredCustomer role at the site
level, or for the store to which they are registering.
|
- Backorder from expected inventory
-
Allocate expected inventory for a particular order item at a particular fulfillment center. The behavior of the command is as follows: -- If the order item is suitable for backordering (that is, its inventory-status attribute specifies unallocated) and there
is sufficient expected inventory at one of the specified fulfillment centers (searching in order from first to last in the
list of input fulfillment centers) to completely backorder the quantity needed by the order item, backorder it and update
the order item to reflect the backorder. -- Otherwise, the order item is not changed.
Note: In the default implementation, expected ship date is computed by looking at both expected inventory receipts and expected
inventory records as well as at store policy for how long it takes to fulfill an item once an order is placed.
Alternatively, allocation may be allowed from certain fulfillment centers even when there are no inventory records or expected
inventory records available at that fulfillment center (as if there was an expectation of infinite inventory for certain stores
at certain fulfillment centers) as long as the item is not discontinued. For such unlimited-supply fulfillment centers, the
estimated availability time is derived from the policy represented by the Store.defaultBackorderOffset attribute.
|
- Calculate refund amount
-
Calculate the refund amount for the product based on business rules. In addition, calculate adjustments and taxes for the
refund.
|
- Cancel all draft RFQ responses
-
When the RFQ is closed, all responses in draft state will be cancelled and will not be included for evaluation. |
- Cancel order
-
Update the order state to canceled (X).
|
- Check external account
-
This task is used to check the payment against the customer account through an external accounting system. It is intended
for third parties to extend and write implementation code for integration with an external accounting system.
|
- Check for bid override
-
Check if the bid is overridden. When a customer's bid is overridden, an auction notification message is produced to inform
the customer that a higher bid has been placed.
|
- Check for shipped orders
-
Check for shipped orders (status S) for the store having a payment method. |
- Check order
-
Check a submitted order to make sure that it has not already been processed. The default behavior is to check whether or not
the order has payment information saved for it. If it does, the command fails.
|
- Check order acceptance
-
Check that an order can be accepted for processing. The default behavior is to check that the trading agreements for all the
order items in the order have an active status.
|
- Check payment
-
Execute the check if payment is authorized. |
- Check payment accept policy
-
Execute the business policy command to check if payment is authorized. |
- Check PO spending limit
-
Check to see whether or not the spending limit of the purchase order would be exceeded. Records of the purchase amount of purchases registered against a limited purchase order are kept in the same currency specified
for the limited purchase order. These records are kept in the LPOPURAMT table. (Note that the currency specified by the limited
purchase order must not change once the purchase order is used for any purchases.) Purchases can be made using different currencies. Checking involves doing a currency conversion if necessary before checking.
|
- Check TA spending limit
-
Check the trading-agreement (TA) spending limit to see whether or not it has been exceeded. An order may include order items that are purchased under different trading agreements, and different trading agreements may
have different spending limits. -- Checks to see whether or not the spending limit of the trading agreement would be exceeded with this purchase if the trading
agreement includes a RightToBuy-by-amount terms and conditions (TC).
Records for the purchase amount and refund amount for purchases and refunds against a trading agreement with a RightToBuy-by-amount
TC are kept in the same currency specified for the RightToBuy-by-amount TC. These records are kept in separate tables, TRDPURAMT
and TRDREFAMT respectively. Note that the currency of this RightToBuy TC must not change once the trading agreement has been
activated and purchases have been made against the trading agreement. Purchases can be made using a currency that is different from the currency specified for the RightToBuy-by-amount TC.
-- For each unique trading agreement specified in the order items that includes a RightToBuy-by-amount TC, this default implementation
converts the sum of the purchase amounts of the order items to the currency specified for the RightToBuy TC. If the resulting
amount and the sum of all purchase amounts for the trading agreement in the TRDPURAMT table exceed the RightToBuy amount in
the TC plus the sum of all refund amounts in the TRDREFAMT table for the same trading ID, the check fails.
The purchase amount of an order item is the sum of the ORDERITEMS.TOTALPRODUCT plus ORDERITEMS.TAXAMOUNT plus ORDERITEMS.SHIPCHARGE
plus ORDERITEMS.SHIPTAXAMOUNT minus ORDERITEMS.TOTALADJUSTMENT. (Similarly, the purchase amount for the whole order consists
of the sum of ORDERS.TOTALPRODUCT plus ORDERS.TOTALTAX plus ORDERS.TOTALSHIPPING plus ORDERS.TOTALTAXSHIPPING minus ORDERS.TOTALADJUSTMENT.
This is the same as the total amount passed by the caller.)
|
- Close RFQ automatically
-
Close the RFQ when the closing rule is met or when the closing time is reached. Once the RFQ is closed, no more responses
will be accepted. Before the buyer can accept or reject any response, the RFQ must be closed.
|
- Consume coupons
-
Update any coupons used for this order as a discount such that they are used.
|
- Create a receipt
-
Create an ad hoc reciept by calling CreateReceipt task command. |
- Create bid for autobid
-
Create the bid from autobid. The bid activity is monitored for autobids and bids are periodically updated to maintain a winning
status until the maximum bid limit is reached.
|
- Create contract from RFQ response
-
Create a contract from the RFQ winning response. |
- Create invoice(s)
-
Prepare an invoice for order release in the form of an XML string, store the string in the WebSphere Commerce database, and
send the invoice to the buyer contact of the account in the form of an e-mail, if the account has an invoice terms and conditions
that specify a delivery method using e-mail.
|
- Create next round RFQ request
-
Create a next round RFQ for further negotiation. |
- Create order from RFQ response
-
Create an order from the RFQ winning response. |
- Create order from winning bid
-
Process winning bids and create orders. |
- Create order status
-
Create the order status in the ORDSTAT table using the input information. -- The first order status for an order must have orderId and merchantOrderNumber specified. -- Check if the order specified in orderId exists in the ORDERS table. -- If serialization information is available, such as the sequenceNumber and the lastUpdateTimestamp parameters, check if
the values are more recent than the ones already in the ORDSTAT table; if not then no update will be performed.
|
- Create pack slip
-
Create a packing slip XML document, and save it as part of the release. <Packslip> <Order_Information Store_Name=store_name Fulfillment_Center=ffmcenter_name Order_Number=order_number Release_Number=release_number Pickbatch_Number=pickBatchId Order_Date=order_date Shipping_Provider=shipping_provider Customer_Number=customer_number Invoice_Method=invoice_Method />
<Shipto AddressID=addressId First_Name=shipto_firstname Last_Name=shipto_lastname Middle_Name=shipto_middlename Address_1=shipto_address1 Address_2=shipto_address2 Address_3=shipto_address3 City=shipto_city State=shipto_state Zip=shipto_zipcode Country=shipto_country /> <Order_Items SKU=sku Product_Name=product_name Product_Description=product_desc Catalog_Name=catalog_name Quantity=ordered_quantity Unit_Price=unit_price Total_Price=total_price Currency=currency Customer_Comments=customer_comments > <Component SKU=component_SKU Product_Name=component_product_name Product_Description=component_product_desc Quantity=component_quantity /> </Order_Items> </Packslip>
|
- Create pick slip
-
Create a pick ticket for the pick batch. An XML document is created that may be transformed into an end-user document or can
be used to integrate with back-end systems.
<Pickticket> <Pickbatch_Information Store_Name=store_name Fulfillment_Center=ffmcenter_name Pickbatch_Number=pickBatchId /> <Pickbatch_Items SKU=partNum Product_Name=shortDescription Product_Description=longDescription Quantity=quantity /> </Pickticket>
|
- Create releases
-
A release is created for each item that is being released separately. For all other items, a release is created that has
the same carrier, the same ship-to address, fulfillment center, and output queue. The release enters the ship state.
|
- Create return request
-
Create a return request using the original order as input. |
- Credit external account
-
This is an extension point for interfacing to an external accounting system.
|
- Deallocate existing inventory
-
Deallocate the line item that was allocated from existing (instock) inventory. This makes is available for allocation to other
orders.
|
- Deallocate expected inventory
-
Deallocate the backordered line item. This removes soft allocations made for this line item. This makes the expected inventory
available to be allocated to other backorders.
|
- Debit external account
-
This is an extension point for interfacing to an external accounting system.
|
- Deposit payment
-
This task executes the business-policy command to perform the deposit.
|
- Determine approval amount
-
Determine the amount in the specified currency that an approval is to be obtained for. |
- Extend order process
-
This is an extension point to extend the order process
|
- Finalize auction
-
Retrieve all Bidding Closed auctions and determine the winners of auctions. |
- Find approver group
-
Starting with the organization to which the user registers, the system walks up the hierarchy looking for an organization
with an associated approver group. When the first approval group is found, the members of that group are resolved and a notification
is sent to them that there is a request pending their approval. If a disable approval group is the first group found, then
we know that approvals have been disabled on this subtree, and we auto-approve the user.
|
- Find orders to be released
-
Find orders that are ready to be released. |
- Find orders with pending auths
-
Find submitted orders with status I (submitted) or status M (pending payment authorization). |
- Find payments for order
-
Query the payment system to determine the authorizations for the order. |
- Find stale order line items
-
Find order line items that are stale. An order line item that is stale has the following characteristics: -- It is in a shopping cart -- It is allocated or backordered -- The store supports expired allocations (ALLOCATIONGOODFOR) and the amount of time since order line item was allocated exceeds
the amount of time the allocation should be considered valid.
|
- Get eligible fulfillment centers
-
For each input item, return a list of fulfillment centers (ordered in sequence of descending preference from first to last)
that could ship that item if there was sufficient inventory. The default implementation behaves as follows: For each distinct store, shipping address, and shipping mode combination in those input order items in fulfillment centers: -- Determine a list of applicable shipping arrangements, sorted in descending sequence by their precedence attribute. (A shipping
arrangement is applicable if it is not restricted or, when it is restricted, if the shipping address matches one of the shipping
arrangement's associated shipping-jurisdiction groups.) In that sequence, build a list of fulfillment centers by adding the
fulfillment center indicated by each applicable shipping arrangement if it is not already in the list. A shipping arrangement is used to indicate that a fulfillment center can ship products on behalf of a store using a shipping
mode. A shipping mode represents a shipping carrier (for example, UPS). The result is a list of eligible fulfillment centers for each distinct shipping address and shipping mode combination.
|
- Get invalidly allocated line items
-
Determine items that are unallocated or needing reallocation. Reallocation is required if the fulfillment center changed,
the quantity changed or the ship-to address changed.
|
- Get payment methods for return
-
Get the payment methods that are allowed for the return. The default behavior is to return the payment method(s) used in the
original order.
|
- Handle payment authorization denied
-
Display an error view to the buyer if the PO number is not valid or the PO spending limit has been exceeded.
|
- Look up accepted orders
-
Find orders that are eligible to be released. The criteria is an order with payment information capture complete (C) and either at least one allocated item and the order
is not ship as complete or the order is ship as complete and at least one item is not allocated or does not have a ship-to
address.
|
- Look up existing inventory for item
-
Convert the quantity available to baseitem quantity used in the receipt quantity received attribute. To convert from available
quantity to baseitem quantity use the external UOM standard and the QTYUNITMAP table to determine the quoted quantity unit,
then convert from that quantity unit to the baseitem quantity measure, and then divide by the baseitem quantity multiple.
If UOM code is not specified, assume quantity unit. Store the restock date in the ItemFulfillmentCenter restock time attribute.
|
- Look up pmt methods in return TC
-
Get the payment methods from the contract terms and conditions. |
- Modify bid information
-
Modify the information on the bid to maintain a winning status until the maximum bid limit is reached. |
- Notify Buyer Approver
-
Notify the buyer approver for whom there is an order requiring their approval. |
- Notify customer
-
Notify the customer regarding the customer status of the process. This is a general task used to communicate information that
the customer should know. In returns processing, the customer is notified if a requested update to a return request is rejected,
because the goods were received already or a credit was issued already.
|
- Notify user of approval
-
The buyer approver sends out an email to tell the user they have been approved, including comments if desired. |
- Notify user of rejection
-
The buyer approver sends out an email to tell the user they have been rejected, including comments if desired. |
- Prepare order
-
Order preparation includes calculating product prices, adjustments, shipping charges, and tax charges. |
- Profile order for user
-
Profile the order for the user.
|
- Query releases in 'shipped' state
-
Find releases that are ready to be shipped for a fulfillment center and store. |
- Recalculate prices
-
Recalculates prices by ensuring that all the items are buyable, updates ship-to address for items not having one, validates
the configuration of items that are dynamic kits, checks inventory availability and then updates items prices, as well as
totals and calculates shipping and tax charges.
|
- Recalculate shipping and taxes
-
Recalculates shipping charges and taxes, and locks the order.
|
- Receive and create a quotation
-
Receive and validate the response to a quotation request. Create a quotation order for the shopping cart and correlate the
items in the response to the shopping cart. Record the supplier part number and the estimated supplier availability.
|
- Record authorization result
-
Record the result of an external authorization request. This task provides the system with the fact that the authorization
has been obtained.
|
- Refund payment
-
Execute the refund to the returner
|
- Refund using payment policy
-
Execute the refund as defined by the contract.
|
- Release manifest
-
Release the manifest. This can be invoked either with the ReleaseManifest Controller command or as part of the ReleaseShipConfirm
Controller Command. In other words, it can be performed as a single step as part of shipment confirmation or as a separate
step.
Tools Controller Command -- ReleaseManifestCmd
Task Command -- UpdateManifestStatusCmd
|
- Release ship notify
-
Sends an e-mail notification message to the buyer for order release shipment.
|
- Remove status for items not updated
-
Since a request for update was requested, remove the status for all items that are in the ORDISTAT table for the order and
not in the input information provided.
|
- Reprepare order
-
Recalculate shipping charges and taxes, and lock the order. A locked order means that it has been prepared and is used to
indicate whether or not an order has changed.
|
- Request inventory updates
-
Create a request for inventory for each catalog entry passed as a parameter to the command. The default implementation determines
the user credentials based on the store and the customer number and business partner grouping from the organization. A XML
document representing the request is created and sent to the distributor.
If the store has the Referral Interface Terms and Conditions (TC) defined by the default contract, transmit the inventory
level request by calling the Referral Interface batch availability request method. The following information is specified
for each product in the request: -- The member identifier and part number of the specified item. -- The external UOM code mapped from the quantity unit of the base item of the specified item
|
- Request payment deposit
-
Request that a payment be deposited. In the check (ACH) domain, this is the method of validating that the check (payment)
is good.
|
- Send E-mail to customer
-
Notify the customer regarding the customer status of the process. This is a general task used to communicate information that
the customer should know. In returns processing, the customer is notified if a requested update to a return request is rejected,
because the goods were received already or a credit was issued already.
|
- Send E-mail to merchant
-
Notify the customer regarding the customer status of the process. This is a general task used to communicate information that
the customer should know. In returns processing, the customer is notified if a requested update to a return request is rejected,
because the goods were received already or a credit was issued already.
|
- Send invoice as e-mail
-
Send the invoice as e-mail to the recipient specified in the business account |
- Send message to backend system
-
This is an extension point for integrating messaging to a back-end system. Typically, this is used to indicate that an order
has been created.
|
- Send problem to CSR
-
Send the failed payment approval to a CSR for resolution. |
- Send to payment administrator
-
Send the failed payment to a payment administrator for resolution |
- Set release capture date
-
Update the release by indicating the payment-capture date. |
- Time to activate future auction
-
It is time to activate the future auction. |
- Time to check for shipped orders
-
This task models an event that starts a scheduled command or process.
|
- Time to close auction automatically
-
Close the bidding for an auction when it is time to close. |
- Time to execute
-
This process is initiated as a scheduled task. A scheduled task starts asynchronously when the scheduler has determined that
it is time to execute.
|
- Time to release orders for store
-
This task models the event that starts a scheduled command or process.
|
- Transfer order
-
Transfer the order to the distributor's store. |
- Update billing address
-
Update the billing address. The default behavior is to update the billing address from the terms and conditions if a billing
address exists for it. If it does not exist, the billing address is updated based on the customer information associated with
the order.
|
- Update current quantity
-
Update the current available quantity on the Dutch auction. |
- Update existing order status
-
Update the existing order status in the ODSTAT table with the information provided as input. |
- Update inventory receipt
-
Performs supply netting: Quantity on hand = Quantity on hand - Quantity picked Quantity in process = Quantity in process - Quantity picked
|
- Update order item status
-
Update the order item status in the ORDISTAT table for each item in the input provided. |
- Update order release
-
Update the order release in the ORDRELEASE table with the external order number from the input information provided. |
- Update order to backorder
-
Change the order status to backordered. Backorders are not allowed to ship and thus will not be eligible for release to fulfillment
with a status of backordered.
|
- Update order to payment authorized
-
The order is not a backorder, the payment has been authorized, and there are no AVS codes that the store does not accept. |
- Update order to requires review
-
AVS codes were present that are not accepted by the store. The order is assigned a status of requires review (A). |
- Update PO spending limit
-
Perform the following: -- The default implementation inserts a row into the LPOPURAMT table if the purchase was done specifying a limited purchase
order. (No row is created if the purchase order specified is not a limited purchase order.) -- Throws an ECApplicationException if the purchase amount exceeds the purchase-order spending limits specified via a purchase-order
TC for a limited purchase order. -- If the purchase was made using a currency that is different from the currency specified for the limited purchase order,
the total amount will be converted to the purchase-order currency before storing it in the LPOPURAMT table. -- Because this task command may be called more than once, skip the insert if the row already exists. -- The total purchase amount of the limited purchase order is not decremented if a refund is issued later against the order.
|
- Update status version
-
Update versioned status by making a copy of the last order status. Its version (OSVERNBR) will be set to the maximum number
of existing version +1.
|
- Update TA spending level
-
This task performs the following: -- If a trading agreement has both RightToBuy-by-amount TC (terms and conditions) and ObligationToBuy-by-amount TC, the currency
specified for the two TCs must be the same. An order may include order items that are purchased under the same trading agreement or different trading agreements. -- If all the order items specify the same trading agreement with a RightToBuy-by-amount TC or an ObligationToBuy-by-amount
TC or both, the default implementation inserts a single row (with the total amount converted to the currency of the TC) into
the TRDPURAMT table with the TRDPURAMT.ORDERITEMS_ID column set to null. If not all order items have the same trading agreement,
the command inserts multiple rows into the TRDPURAMT table for each order item that has a trading agreement that includes
a RightToBuy-by-amount TC or an ObligationToBuy-by-amount TC or both, with purchase amount of the order item converted to
the currency of the TC. -- For each unique trading agreement in the order with a RightToBuy-by-amount TC, the command also checks to see whether or
not the total purchase amounts of the order items converted to the currency specified for the RightToBuy TC plus the sum of
all purchase amounts for the trading agreement in the TRDPURAMT table exceeds the RightToBuy amount in the TC plus the sum
of all refund amounts in the TRDREFAMT table for the same trading ID. If it does, the task command throws an ECApplicationException
and the insert does not happen.
The purchase amount of an order item is the sum of the ORDERITEMS.TOTALPRODUCT plus ORDERITEMS.TAXAMOUNT plus ORDERITEMS.SHIPCHARGE
plus ORDERITEMS.SHIPTAXAMOUNT minus ORDERITEMS.TOTALADJUSTMENT.
Because this task command may be called more than once, skip the insert if the row or rows already exist.
|
- Update TA spending limit
-
Perform the following: -- If a trading agreement has both a RightToBuy-by-amount TC(terms and conditions) and an ObligationToBuy-by-amount TC, the
currency specified for the two TCs must be the same. An order may include order items that are purchased under the same trading agreement or different trading agreements. -- If all the order items specify the same trading agreement with the RightToBuy-by-amount TC or an ObligationToBuy-by-amount
TC or both, the default implementation inserts a single row (with the total amount converted to the currency of the TC) into
the TRDPURAMT table with the TRDPURAMT.ORDERITEMS_ID column set to null. If not all order items have the same trading agreement,
the command inserts multiple rows into the TRDPURAMT table for each order item that has a trading agreement that includes
a RightToBuy-by-amount TC or an ObligationToBuy-by-amount TC or both, with the purchase amount of the order item converted
to the currency of the TC. -- For each unique trading agreement in the order with a RightToBuy-by-amount TC, the command also checks to see whether or
not the total purchase amounts of the order items converted to the currency specified for the RightToBuy TC plus the sum of
all purchase amounts for the trading agreement in the TRDPURAMT table exceeds the RightToBuy amount in the TC plus the sum
of all refund amounts in the TRDREFAMT table for the same trading ID. If it does, the task command throws an ECApplicationException
and the insert does not happen.
The purchase amount of an order item is the sum of the ORDERITEMS.TOTALPRODUCT plus ORDERITEMS.TAXAMOUNT plus ORDERITEMS.SHIPCHARGE
plus ORDERITEMS.SHIPTAXAMOUNT minus ORDERITEMS.TOTALADJUSTMENT.
Since this task command may be called more than once, skip the insert if the row or rows already exist
|
- Update trading agreement amount
-
This command does the following: -- The default implementation inserts a row into the TRDDEPAMT table for the order with the depositAmount in the default currency
of the store if all order items specify the same Trading Agreement. However, if NOT all the order items have the same Trading
Agreement, this command inserts multiple rows, one for each order item, with the deposit amount of each order item converted
to the default currency of the Store. -- The deposit amount of an order item is the sum of the ORDERITEMS.TOTALPRODUCT + ORDERITEMS.TAXAMOUNT + ORDERITEMS.SHIPCHARGE + ORDERITEMS.SHIPTAXAMOUNT minus ORDERITEMS.TOTALADJUSTMENT.
|
- Validate business account
-
Assure that the business account being used is valid. |
- Validate payment policy
-
Check if a payment policy is associated to all contracts to all the order items
Checks if the Payment Policy ID specified is valid for the Order. A Policy is valid if all Trading Agreements associated with
the OrderItems include a Payment TC that specifies this Policy and if the specified TC includes a billToAddress and pre-defined
attributes, all the other Trading Agreements must have a compatible TC that specify the same billToAddress and attributes.
Trading Agreement with no Payment TC could use any Payment Policy unless the Policy has an exclude-from-defaultTC or require-explicit-TC
clause.
|
- Validate purchase order
-
Validate the purchase-order number and checks the purchase-order spending limit.
ValidatePONumber: -- Checks the buyerPONumber against predefined purchase orders (limited or blanket purchase order) in the trading agreement
(of the account). If the buyerPONumber is one of the predefined purchase orders but the purchase order is no longer active,
it then throws an ECApplicationException. -- If the buyerPONumber is not a predefined purchase order and individualPO is not specified for the trading agreement, then
the buyerPONumber is invalid. It throws an ECApplicationException. -- If the buyerPONumber is not a predefined purchase order and individualPO is specified for the trading agreement (of the
account), it makes sure that this "individual" purchase-order number has not been used for this account if uniqueness is in
the purchase-order TC (POTCIndividual). Otherwise, it throws an ECApplicationException.
CheckPOSpendingLimit: -- Checks to see whether or not the spending limit of the purchase order would be exceeded. -- Records of the purchase amount of purchases registered against a limited purchase order are kept in the same currency specified
for the limited purchase order. These records are kept in the LPOPURAMT table. (Note that the currency specified by the limited
purchase order must not change once the purchase order is used for any purchase.) -- Purchases can be made using different currencies. Checking involves doing a currency conversion if necessary and then checking.
-- If the check fails, the command throws an ECApplicationException.
|
- Validate with external account syst
-
A task to authorize the payment against the customer account through an external accounting system. This is an extension point.
|
- Verify order item is still stale
-
Verify the order line item is still stale. An order line item that is stale has the following characteristics: -- It is in a shopping cart -- It is allocated or backordered -- The store supports expired allocations (ALLOCATIONGOODFOR) and the amount of time since order line item was allocated exceeds
the amount of time the allocation should be considered valid.
|