Shipping Costs Estimation in the Java Cart

This function or procedure is only available with SAP CRM as the back end connected to SAP Web Channel Experience Management. Note that a system connection between SAP CRM and SAP ERP might be required.

This function enables Web shop customers to estimate shipping costs for products in their shopping carts. The final shipping costs are shown during checkout. For more information about this, see Checkout. For information about estimated shipping costs in the Java cart with SAP ERP back end and in the back-end cart with either back end, see Java Cart or Back-End Cart. Shipping costs are defined by pricing as part of your pricing procedure. For more information about pricing, see Pricing in the Shopping Cart.

Prerequisites

• If you want to enable Web shop customers to use specific countries as a parameter for estimated shipping cost calculation, you have selected these countries in the standard delivery customizing. You do this in Customizing for SAP CRM, under  SAP NetWeaver General Settings Set Countries Specify Countries in mySAP Systems (CRM, SRM, SCM,...) .
• If you want to enable Web shop customers to use regions (for example, state or province) as a parameter for estimated shipping cost calculation, you have defined regions. You do this in Customizing for SAP CRM, under  SAP NetWeaver General Settings Set Countries Insert Regions .
• If you want to enable Web shop customers to use delivery types (also called shipping conditions) as a parameter for estimated shipping cost calculation, you have defined delivery types. You do this in Customizing for SAP CRM, under  Master Data Business Partner Define Attributes Define Shipping Conditions .
• You have entered a reference business partner (specifically for pricing in the Java cart) in the Sales Transactionsmodule of Web Channel Builder. If Web shop customers have not logged on, the system uses this reference business partner for determining the default country, default region, and other attributes for pricing. You create a reference business partner for pricing on the WebClient UI (for example, with the business role Sales Professional (SALESPRO). You do this under  Account Management Accounts .
• If you want to enable Web shop customers to use delivery types, you have enabled delivery types, selected delivery types for this Web shop, and entered a default delivery type, in the Common Settings module of Web Channel Builder.
• You have enabled the Java cart in the Sales Transactions module of Web Channel Builder.
• The cart must enforce dynamic pricing. For more information about the dynamic pricing setting for the cart, seePricing in the Shopping Cart.

Features

• Before logging on
  When Web shop customers add products to the shopping cart, the system calculates (and dynamically recalculates) estimated shipping costs using the following shipping parameters:
  • Country
  • State or region
  • Delivery type
• After logging on
  Web shop customers cannot change shipping parameters in the shopping cart. The system calculatesestimated shipping costs, using data from default checkout profiles. However, Web shop customers can use different checkout profiles or select different bill-to addresses and ship-to addresses during checkout. For more information about checkout profiles and checkout, see Checkout Profiles and Checkout, respectively.

Checkout Profiles

This function or procedure is available with SAP CRM or SAP ERP as the back end connected to SAP Web Channel Experience Management. Note that if you use SAP CRM as the back end, a system connection between SAP CRM and SAP ERP might be required.

This function enables Web shop customers to create checkout profiles. Checkout profiles enable Web shop customers to save standard combinations of checkout-relevant settings for use during checkout, which speeds up the checkout process considerably. Web shop customers create checkout profiles under  My Account Settings Checkout Profiles .

Prerequisites

The following table explains prerequisites by back end:

SAP CRM Back End

SAP ERP Back End

You have defined checkout profile groups for one or more Web shops in Customizing for SAP CRM under  Customer Relationship Management SAP Web Channel Experience Management E-Commerce Checkout Profiles Define Checkout Profile Groups . The delivered setting for checkout profile group is 01. You have enhanced write access from the Web shop to the back end and read access from the back end to the Web shop in Customizing for SAP CRM under Customer Relationship Management SAP Web Channel Experience Management E-Commerce Checkout Profiles BAdI: Checkout Profiles .

You have defined checkout profile groups for one or more Web shops in Customizing for SAP ERP under Sales and Distribution SAP Web Channel Experience Management Checkout Profiles Define Checkout Profile Groups . The delivered setting for checkout profile group is 01. You have enhanced write access from the Web shop to the back end and read access from the back end to the Web shop in Customizing for SAP ERP under Sales and Distribution SAP Web Channel Experience Management Checkout Profiles BAdI: Checkout Profiles .

The following are prerequisites for both back ends:

• You have added the Checkout Profiles menu option under the Settings menu heading in the My Account module of Web Channel Builder.
• You have entered a checkout profile group in the Checkout module of Web Channel Builder.
   Note

  The BAdI uses the checkout profile group as a filter value. That is, if you enter the standard checkout profile group 01 in Web Channel Builder, the system uses the default delivered BAdI implementation. If you define and enter another checkout profile group in Web Channel Builder, the default BAdI implementation is not run.
• You have made settings for delivery types in the Checkout module of Web Channel Builder.

Default BAdI Implementations

SAP CRM Back End	SAP ERP Back End
The default BAdI implementation (CRM_WEC_CHECKOUT_PROFILE) for BAdI: Checkout Profiles (COM_WEC_CHECKOUT_PROFILE) does the following: Provides default checkout profile during first read from Web shop (when no checkout profile is defined) Checks for the existence of the ship-to address and bill-to address Checks for the existence of the business partner	The default BAdI implementation (ERP_WEC_CHECKOUT_PROFILE) for BAdI: Checkout Profiles (COM_WEC_CHECKOUT_PROFILE) checks for the existence of the customer.

Features

• Creating checkout profiles
  Web shop customers can create and update checkout profiles. They can save different combinations of settings in multiple checkout profiles and can select one checkout profile as the default. They cannot remove the default checkout profile.
  The following table explains the information that Web shop customers can save in checkout profiles by back end:

  SAP CRM Back End	SAP ERP Back End
  Payment method Bill-to address (consumer scenario only) Ship-to address (consumer scenario only) Delivery type	Payment method Delivery type  Note Web shop customers can save one address. They can find this address under  My Account Settings Personal Data .

   Note

  In the consumer scenario, Web shop customers see the checkout profiles they created themselves.

  In the contact scenario, Web shop customers automatically see all checkout profiles created by any contact of their company, not just the ones they created themselves for their company.
  For more information about payment methods, see Payment Methods.
• Checking out
  When Web shop customers have saved at least two checkout profiles, they can do the following in the Personal Details checkout step:
  • View their checkout profiles
  • Select a different checkout profile for use during checkout
• Archiving
  To archive checkout profiles, the standard back-end archiving objects are used, namely:

  SAP CRM Back End	SAP ERP Back End
  Archiving object CA_BUPA for archiving business partner data	Archiving object FI_ACCRECV for archiving customer data