cancel
Showing results for 
Search instead for 
Did you mean: 

Tax Jurisdiction Error in SRM

Former Member
0 Kudos

Hello,

We are currently building our SRM 4.0 client in Extended Classic. We have set the tax calculation in the IMG to be 'Tax calculation occurs in R/3' and have set the tax code I1 as default. It should be noted that we are using internal tax calculation procedures in R/3 directly and not hooked up to a third party like Taxware or Vertex.

When creating a SRM shopping cart, we get an error message generated from the R/3 System, 'Tax code I1 does not exist for jurisidiction code' (message number FF718). When creating a purchase order directly in the R/3 system with the same information, the tax calculates correctly.

I have referenced OSS note 436760 regarding implementing BAdI BBP_TAX_MAP_BADI. However, I believe the tax calculation should be standard functionality in SRM.

Can someone confirm if they had to implement this BAdI to address this issue or if there is another problem that is preventing the tax code from being populated?

-regards

Shaz

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi,

The foll threads might be useful to you:

1>

2>

3>

Regards,

Disha.

Pls reward points for helpful asnwers.

Former Member
0 Kudos

Disha,

Thank you for these threads. All of these threads point to implementing the BBP_TAX_MAP_BADI.

This seems surprising as I figured that SRM would just read the tax calculations directly in SAP R/3 if the 'Tax calculation occurs in SAP R/3' setting was made.

I have rewarded points.

-regards

Shaz

Former Member
0 Kudos

Hi Shaz,

You are right..We have implemented the CLassic scenario at our place with teh only setting for Tax calculation being "'Tax calculation occurs in SAP R/3"(No BADI implemented) and things are working fine....But may be with the BADI you can overwrite the std settings....

Let me know if any success...

BR,

Disha.

Thanks for the points too!!:-)

Former Member
0 Kudos

Hi Shaz,

I have exactley the same problem... have you found a solution to it? Did you have to implement the BADI? If you did... did the BADI solve the problem?

Please let me know... Johanna

Former Member
0 Kudos

Johanna,

According to SAP, we will need to implement the BAdI BBP_TAX_MAP_BADI in order to pass the jurisdiction code in SRM to R/3 to calculate the tax rate in SRM.

If your R/3 system is connected to a third party tax calculation package like Vertex or Taxware, you should not need to implement this BAdI but if your tax calculations are based on standard tax tables in SAP R/3, you will need to follow the instructions in OSS note 436760 to implement the tax rate calculation.

-regards

Shaz

Former Member
0 Kudos

Johanna,

According to SAP, we will need to implement the BAdI BBP_TAX_MAP_BADI in order to pass the jurisdiction code in SRM to R/3 to calculate the tax rate in SRM.

If your R/3 system is connected to a third party tax calculation package like Vertex or Taxware, you should not need to implement this BAdI but if your tax calculations are based on standard tax tables in SAP R/3, you will need to follow the instructions in OSS note 436760 to implement the tax rate calculation.

-regards

Shaz