Technote

(troubleshooting)
Taxes not applied during runtime in the Extended Sites model
Problem(Abstract)
You configure tax at the Storefront Asset Store level in an Extended Sites model, but notice the tax calculations are not applied during runtime. You expect that the tax configurations will be inherited by the Hosted store from the Asset store.
Cause By default, WebSphere Commerce Accelerator does not support configuring tax at the storefront asset store level. The 'Change Tax' menu option in Accelerator is only available in the Hosted store (or Extended site) itself. Resolving the problem You can load tax data directly to the database, but only some of the tax tables can be used at the storefront asset store level.

Only some tables in the calculation and tax data model take into consideration Extended Sites store paths (the relationships between the Storefront Asset Store and the Hosted stores in STOREREL table).

The table below lists the relevant tables to configure tax. The 'Supported store path' column lists which entry in STOREREL would be required to build the relationship to the asset store, if applicable. 'Supports store group' is whether or not a store group could be used for the configurations in this table. Only tables with a reference to STOREENT support store groups.


Table
Supported store path
Supports store group

CALCODE
com.ibm.commerce.calculation
no

CATENCALCD
com.ibm.commerce.calculation
no

CATGPCALCD
com.ibm.commerce.calculation
no

CALSCALE
com.ibm.commerce.calculation
yes

JURST
none
Shipping JURST, yes.
Tax JURST, no.

JURSTGROUP
none
Shipping JURSTGROUP, yes.
Tax JURSTGROUP, no.

TAXCGRY
none
yes

When configuring tax in the Extended Sites model, you have two choices:

  1. Configure all the tables above for the specific hosted stores individually

  2. Configure calculation tables (CALCODE, CATENCALCD, CATGPCALCD, CALSCALE) at the asset store level, and the juristdcition (JURST, JURSTGROUP) and tax category (TAXCGRY) tables for the the specific hosted stores individually. If you choose this option, you could also simplify the jurisdiction definitions by grouping stores into a store group,



The com.ibm.commerce.tax (-2) store relationship type in the STOREREL table is not honored. The calculation relationships mentioned above use the com.ibm.commerce.calculation (-27) relationship.
Cross Reference information
Segment Product Component Platform Version Edition
Commerce WebSphere Commerce - Express Configuration i5/OS, Linux, Windows 6.0, 6.0.0.1, 6.0.0.2, 6.0.0.3, 6.0.0.4
Commerce WebSphere Commerce Professional Edition Configuration AIX, i5/OS, Linux, Solaris, Windows 6.0, 6.0.0.1, 6.0.0.2, 6.0.0.3, 6.0.0.4
   

Document Information

Current web document: http://www.ibm.com/support/docview.wss?uid=swg21302881