RE:[sap-log-mm] Harmonized Tariff Code

Posted by Sap Land Wednesday, 13 July 2011 12:44

Posted by JDH
on Jul 13 at 3:48 PM

Hi Bob,

In addition to maintaining the HTC Code in the Material Master for Customs purposes (as David mentioned), numerous companies also use the Code to create more specific Conditions (MEK1), so the final Price in a PO is more accurate and used for Costing by FI.

For example; either a standard or custom Condition Type is added as part of your pricing schema. Next, an Access Sequence should exist for the Condition Type (e.g., Vendor/Purch Org/HTC) in MEK1. If, for example, a Condition record exists that HTC 8421.39.8015 = 10%, then each time a PO is created for this Vendor/Purchase Org and HTC 8421.39.8015 combination (which it reads the HTC from the Material Master when the material is entered in the PO) the system will automatically calculate 10% against the PO price and giving FI a more accurate final cost.

This is just one example of numerous ways you can use HTC's to develop more accurate price/cost processes.

I hope this suggestion may provide you with more information or options to consider for your organization.

---------------Original Message---------------
From: Bob Schmidt
Sent: Wednesday, July 13, 2011 11:07 AM
Subject: Harmonized Tariff Code

Hello fellow users!

One of our product groups has expressed the need to capture the Harmonized Tariff Code. I had never heard of this before and have found some information on the internet but I have an SAP specific question. Is this something similar to a UPC or EAN code? Should it be added into one of the fields on the "Foreign trade export" tab in material maintenance or should it be under "Additional EANs" tab in "Additional data" or someplace else?

Any help is appreciated.

Thank you

Bob Schmidt - Operations
AAF International - Corporate
10300 Ormsby Park Place, Suite 600
P.O. Box 35690
Louisville, KY 40232 USA
+1 502 637 0446 - office, fax
+1 502 472 8463 - cell
email@removed
www.aafintl.com

To Read AAF Information & Confidentiality Notice (click here)

??

__.____._