Associating tax codes with products

When we are extending the default tax calculation process with an externalized customization extension, we can pass catalog entry attribute information to your extension. For instance, if your tax service provider requires more details, such as the mapping between products and tax calculation codes. By default, the implementation for the sample tax integration externalized customization extension that is provided by IBM can associate products and SKUs with tax codes. If tax codes are associated with products or SKUs when the extension is called to send the products or SKUs to your tax service provider for tax calculation, the extension sends the tax code association with the product or SKU details. If no tax code is associated, the extension sends only the product or SKU details. If your tax service provider cannot map products and SKUs with the appropriate tax codes, associate the tax codes with the catalog products and SKUs.

Procedure

1. Enable tax integration extensions.

2. Go to the WCDE_installdir/samples/DataLoad/Catalog directory.

3. Within the Catalog directory, create the following CSV input files to register the sample tax integration extension: If any of the CSV files exist, replace the files or update the files to include the rows in the following files.

   • SalesTaxCode.csv

     This file is used for loading sales tax calculation codes for a store. For more information about the type of data that can be included within this file, see SalesTaxCode.

   • CatalogEntryCalculationCode.csv

     This file is used for associating tax calculation codes with products or SKUs. For more information about the type of data that can be included within this file, see Catalog entry calculation code.

   Note: To apply tax codes to all products or SKUs within a category, load the tax calculation code for a category.

   • CatalogGroupCalculationCode.csv

   For more information about the columns and type of data to include within this file, see Category calculation code .

4. Load the files to the database.

5. Test our changes to verify that part numbers and tax codes are passed to your externalized customization extension implementation class and that order items are no longer grouped by tax code, with each group having tax calculated by separate calls for tax calculation to your tax service provider. We can view the tax codes with the interface for our extension. View the codes through the method TaxIntegrationCustomOrderItem.getTaxCode.