Scribd
Upload
671 views

Automatic Determination of Tax Code in PO

The document describes steps to automatically determine tax codes in purchase orders (POs) in SAP. It involves copying an existing access sequence and condition type, creating new records to derive tax codes based on fields like purchaser organization, vendor, and plant, and adding the new condition type to pricing procedures so tax codes are automatically assigned during PO creation based on the item and partner fields. The changes were tested and reflected correctly for two example plants.

Uploaded by

upkumar871
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
671 views

Automatic Determination of Tax Code in PO

The document describes steps to automatically determine tax codes in purchase orders (POs) in SAP. It involves copying an existing access sequence and condition type, creating new records to derive tax codes based on fields like purchaser organization, vendor, and plant, and adding the new condition type to pricing procedures so tax codes are automatically assigned during PO creation based on the item and partner fields. The changes were tested and reflected correctly for two example plants.

Uploaded by

upkumar871
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 6

Automatic Determination of Tax Code in PO

Used: Standard Access Sequence 0003 & Standard Condition type NAVS

Step 1: Used the Copy of access sequence 0003 & created another access sequence Z003

Copied to Z003-Tax Classification New

Step 2: Created access sequence for Purch.Org./Vendor/Plant to derive various tax codes through M/03.
Step 3: Assigned table 954 in the newly created table in Z003 along with already present table through M/07.

Step 4: Copied standard condition type NAVS & created new condition type ZNAV.
Also assign the earlier access sequence Z003 to the condition type.

Step 5: Now create the condition records for tax code determination through MEK1.
Maintained two Condition record as:
Step 6: Finally add the condition type ZNAV to your pricing procedure.
Simulation during PO Creation:

1. For Plant 1000-Nocil Ltd

2. For Plant 1060-Ports

The changes were reflecting in a perfect manner.

In case of tax code preferably use at least one item level field in access sequence table used. As tax code is
determined at item level. Otherwise it can lead to non refresh of tax code for different data.

Taxes:

You might also like