topic Re: Tax code & does not exist for jurisdiction code & during batch processing in Application Development and Automation Discussions

Tax code & does not exist for jurisdiction code & during batch processing

Former Member — Wed, 06 Nov 2013 21:43:26 GMT

Hello,

We are getting "Tax code & does not exist for jurisdiction code &" error while processing EDI Invoices using a batch job. But when we reprocess the failed IDoc, it posts successfully.

Say, we are processing 4000+ IDocs using RBDAPP01 posting program, most of them would fail with the message 'Tax code & does not exist for jurisdiction code &' . But when we change the status and reprocess it (batch or individual processing), the IDocs would post without any issues,

FI consultant has already checked the configuration involved Tax code maintenance. All have been maintained correctly. We are passing tax codes in the idoc segment. But the error shows a different tax code.

Eg: If we pass U1 in the tax code segment, the error message would be "Tax code C2 does not exist for jurisdiction code".

Individual debugging doesn't help since the idocs are getting posted, if processed individually.

Can you help us on below,

1) why the Idocs failed to get posted in first place?

2) why the idoc posting picks tax code C2 from no where?

Thanks,

Surya.

Re: Tax code & does not exist for jurisdiction code & during batch processing

former_member192854 — Wed, 06 Nov 2013 22:55:30 GMT

It sounds like there is something in your logic which is messing up the population of you 'tax' field in some structure. I think you should check on moving data between the structures in the custom development pieces in the IDoc process.

Best, Sander

Re: Tax code & does not exist for jurisdiction code & during batch processing

Former Member — Thu, 07 Nov 2013 22:38:14 GMT

Thanks for your reply. The issue was with one of the customer exits.

Re: Tax code & does not exist for jurisdiction code & during batch processing

former_member192854 — Fri, 08 Nov 2013 00:02:30 GMT

And, what was the issue there?

Re: Tax code & does not exist for jurisdiction code & during batch processing

Former Member — Fri, 08 Nov 2013 19:09:51 GMT

Memory exported from a previous exit, was not cleared after import. So, during batch processing, old memory was used. It was hard to replicate the issue in non-prod, because of too many validations involved in the customer exits.This was the reason why we faced this issue occasionally during batch and the IDocs got posted when processed individually.