This Standard Operating Procedure (SOP) describes processes for changing or deleting order lines on an existing un-finalized shopping cart utilizing IP1 Web Services. This is sub-process for the different ordering scenarios outlined in:

Procedure

It is your responsibility to ensure that you understand this procedure before performing the following tasks.

Note	Deviations from this procedure should be covered by procedures written by your company. Before performing any tasks please ensure all the business rules are set-up accordingly.

Process overview This section documents the Headline Processes for the website and web user to manage changes to existing cart lines or deletion of cart lines in the shopping cart. It assumes: One or more cart lines have already been added to the shopping cart. The shopping cart has not been finalized (check out process not completed) For this main scenario, we’ve assumed website design allows user to key zero Order Quantity to signify deletion of a cart line, and we’ve assumed the design allows user to make changes to multiple cart lines at once. User selects “View Cart” from the website, then the website executes viewCart. The website presents cart contents. For each cart line, it will show an editable Order Quantity field. Of course, the website would also show other information for each cart line such as item code, description, expected supply or backorder quantities, pricing, etc. User makes changes to the Order Quantity for one or more cart lines, then clicks “Update Cart” button. The website exectutes updateCartLines with the new orderQuantity for each cart line. The website will pass following mandatory request fields for each cart line: lineNumber item orderQuantity If the orderQuantity is set to 0, updateCartLines will delete the cart line If successful, a process number and line number for the cart line is returned. Website can obtain revised shopping cart details and values from IP1 by specifying viewCartWithGeneratedLines = True when executing updateCartLines, or by executing the viewCart web service following any updates. Website displays a revised cart with message “Your cart has been updated” Refer to updateCartLine and updateCartLines.
Alternative scenario variations Check box used to signify “Delete from Cart” against each cart line Instead of using zero Order Quantity to identify which line(s) to delete, the website could be designed with a check box next to each cart line to signify if user wants to delete that line. In this scenario, user would still be able to mark multiple lines for deletion at once. Once the user presses the ‘Update Cart” button, the website would process deleteCartLine operation for each of the lines with the check box marked for deletion. Individual “Delete from Cart” button for each cart line Instead of Check Box or zero Order Quantity to identify which line(s) to delete, the website could be designed with an individual ‘Delete from Cart” button against each cart line. In this scenario, no other updates would occur and the user / website would only be able to process deleteCartLine operation for the one selected line. Individual update of each cart line The website could be designed to only allow user to modify a single cart line at a time. In this case, the website could execute updateCartLine instead of updateCartLines. Update (override) of other optional field values for each cart line Depending on implementation for each business, there could be an optional requirement to allow override of other cart line values. For example, this might be used where client has elected to develop their own promotion or special pricing handling on the web site instead of utilizing IP1’s various pricing facilities. Note: Iptor recommend using in built IP1 pricing features (eg. Price master, special pricing, promotions or order based incentives) rather than web overrides, as this provides greater control & visibility of all pricing through the ERP, and we believe this also reduces Total Cost of Ownership for the web ordering solutions. In this scenario, the website would allow user entry (or derive from its own database) override values for one or more of these optional fields and pass this through updateCartLine or updateCartLines operations: typeOfSale warehouseLocation warehouseNumber customerReference unitOfMeasure unitPriceActual discRateActual taxRateActual fixedPriceFlag fixedDiscountFlag firmSaleTransactionFlag IP1 will send response message if an invalid value is specified. Note that fields other than item and orderQuantity are not maintainable unless allowOverride is set in config.properties. An example of a path to find this file is: C:\IBSAPP\AppServer85\profiles\BKDEVR77EARJ\installedApps\AUPSY499Node13Cell\IBSECommerce_20150624.ear\config

Process overview

This section documents the Headline Processes for the website and web user to manage changes to existing cart lines or deletion of cart lines in the shopping cart. It assumes:

One or more cart lines have already been added to the shopping cart.
The shopping cart has not been finalized (check out process not completed)

For this main scenario, we’ve assumed website design allows user to key zero Order Quantity to signify deletion of a cart line, and we’ve assumed the design allows user to make changes to multiple cart lines at once.

User selects “View Cart” from the website, then the website executes viewCart.
The website presents cart contents. For each cart line, it will show an editable Order Quantity field.
- Of course, the website would also show other information for each cart line such as item code, description, expected supply or backorder quantities, pricing, etc.
User makes changes to the Order Quantity for one or more cart lines, then clicks “Update Cart” button.
The website exectutes updateCartLines with the new orderQuantity for each cart line. The website will pass following mandatory request fields for each cart line:
- lineNumber
- item
- orderQuantity
If the orderQuantity is set to 0, updateCartLines will delete the cart line
If successful, a process number and line number for the cart line is returned.
Website can obtain revised shopping cart details and values from IP1 by specifying viewCartWithGeneratedLines = True when executing updateCartLines, or by executing the viewCart web service following any updates.
Website displays a revised cart with message “Your cart has been updated”

Refer to updateCartLine and updateCartLines.

Alternative scenario variations

Check box used to signify “Delete from Cart” against each cart line

Instead of using zero Order Quantity to identify which line(s) to delete, the website could be designed with a check box next to each cart line to signify if user wants to delete that line. In this scenario, user would still be able to mark multiple lines for deletion at once. Once the user presses the ‘Update Cart” button, the website would process deleteCartLine operation for each of the lines with the check box marked for deletion.

Individual “Delete from Cart” button for each cart line

Instead of Check Box or zero Order Quantity to identify which line(s) to delete, the website could be designed with an individual ‘Delete from Cart” button against each cart line. In this scenario, no other updates would occur and the user / website would only be able to process deleteCartLine operation for the one selected line.

Individual update of each cart line

The website could be designed to only allow user to modify a single cart line at a time. In this case, the website could execute updateCartLine instead of updateCartLines.

Update (override) of other optional field values for each cart line

Depending on implementation for each business, there could be an optional requirement to allow override of other cart line values. For example, this might be used where client has elected to develop their own promotion or special pricing handling on the web site instead of utilizing IP1’s various pricing facilities.

Note: Iptor recommend using in built IP1 pricing features (eg. Price master, special pricing, promotions or order based incentives) rather than web overrides, as this provides greater control & visibility of all pricing through the ERP, and we believe this also reduces Total Cost of Ownership for the web ordering solutions.

In this scenario, the website would allow user entry (or derive from its own database) override values for one or more of these optional fields and pass this through updateCartLine or updateCartLines operations:

typeOfSale
warehouseLocation
warehouseNumber
customerReference
unitOfMeasure
unitPriceActual
discRateActual
taxRateActual
fixedPriceFlag
fixedDiscountFlag
firmSaleTransactionFlag

IP1 will send response message if an invalid value is specified.

Note that fields other than item and orderQuantity are not maintainable unless allowOverride is set in config.properties. An example of a path to find this file is:

C:\IBSAPP\AppServer85\profiles\BKDEVR77EARJ\installedApps\AUPSY499Node13Cell\IBSECommerce_20150624.ear\config