Setting up taxes with extended sites
Aleksander Kovač 270004M7HS Visits (3711)
This text gives a short demonstration on how to configure extended site (esite) specific tax values for products located in catalog asset store (CAS). Tested with v7 FP8 FEP7 Enterprise edition.
WebSphere Commerce provides a flexible tax framework out of the box. An overview of capabilities is available on the following link: Taxes
In short, the main out of the box features are:
In what follows I will demonstrate how to configure taxes for an extended site, both default and category specific rates. Reference used was: Setting up taxes
The store I will configure is AuroraESite, with the products stored in CAS. First, we log in to Commerce Accelerator, select AuroraEsite and AuroraESite fulfillment center. Then we proceed by defining a jurisdiction for the store. Since my test user is defined with address in the United States, I will define a United States default jurisdiction (no region). Then we configure tax codes, categories and rates, as follows:
Picture 1: Configuring (default) jurisdiction.
Picture 2: Configuring tax codes (US sales tax. WD is women's dresses). The default code is applied to all products in an esite.
Picture 3: Configuring tax categories.
Picture 4: Configuring tax rates.
Picture 5: Assigning tax categories to tax codes.
To assign the US-Sales tax-WD tax category to women's dresses category, the following data must be inserted into the database:
-- For actual values examine your database
INSERT INTO CATGPCALCD (STORE_ID, CATGPCALCD_ID, CATGROUP_ID, CALCODE_ID) VALUES (10152, 10155, 10006, 10201)
The following tables are relevant when applying taxes: CATGPCALCD and CATENCALCD (category and product levels)
Once the configuration is completed, upda
My test consisted of the following steps: add two items to the basket; 30$ shoes and 100$ dress, with 10% discount. The tax value at checkout should be 30*0.9*0.1$ + 100*0.9*0.15$ = 16.2$. Test was successful, as can be seen from the picture below.
Picture 6: Test passed.