Example CommodityMappings-US file format
SDITYPE=COMMODITYMAPPINGS-US
Column name | Format | Required | Description |
|---|---|---|---|
ProductCode | varchar2(100) (See Description) | Yes | The source code passed in from your ERP system. |
ProductCodeType | N/A | N/A | Leave blank. Reserved for future use |
CommodityCode | varchar2(100) (See Description) | Yes | The commodity code in Determination. It's related to a product in the Determination product tree. |
StartDate | mm/dd/yyyy | Yes | The date (mm/dd/yyyy) on which the product mapping becomes active. |
EndDate | mm/dd/yyyy | No | The date (mm/dd/yyyy) on which the product mapping terminates. If left blank, the mapping doesn't automatically end. |
CustomProduct | varchar2(100) (See Description) | Yes | Indicates whether the Product Mapping data applies to a Custom Product (Y) or a Tax Data Provider Product (N). |
ProductCodeDesc | Varchar2(100) | No | Provide product code description in this field |
Example commodity mappings file
Commodity mappings can be created for U.S. commodities. For example, this file maps 3 U.S. commodity codes to 3 product codes with specific start dates, and indicates if it's a custom code:
sdiType=CommodityMappings-US,,,,,,
ProductCode, ProductCodeType, CommodityCode, StartDate,
Enddate, CustomProduct, ProductCodeDesc
Q45J,,4011724.11,08/10/2023,,N,
T567,,7000000,09/01/2023,,N,
FRM-23,,AGProd,11/03/2023,,Y,
note
You can't use CSV files to update existing commodity code mappings.