When you are extending the default tax calculation process with an externalized customization extension, you 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 your catalog products and SKUs.
Procedure
-
Enable tax integration
extensions.
-
Go to the WCDE_installdir/samples/DataLoad/Catalog/
directory.
-
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.
Note: To apply tax codes to all products or SKUs within a category, load the tax
calculation code for a category.
For more information about the columns and type of data to include within this file, see
Category calculation
code.
-
Load the files into the
database.
-
Test your 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. You can view the tax codes with the interface for your extension. View the codes
through the method
TaxIntegrationCustomOrderItem.getTaxCode.