Debugging tips: Error message FF793 – “SYST: Tax jurisdiction code at lowest level not transferred”
This error message FF793 is related to tax conditions with tax jurisdiction active. The error message is raised when in VF02 the invoice should be released to accounting:
1. Check where the error message is raised
Here the error is raised in the FI area, in Include LTAX2F01, FORM CHECK_BSEG_BSET which is called in function module FI_TAX_CALCULATION. Therefore with breakpoints we start here:
The cause of this error can be seen in this coding. Tax jurisdiction is active for the company code (lv_isactive = X) and for the tax condition ZGST the field TXJDP (“Tax Jurisdiction Code – Jurisdiction for Lowest Level Tax” , here: <ls_bset>-txjdp) is not filled. Then the error is raised.
The call stack looks like this:
2. Find the root cause
To find out what causes the error, we have to go back to function modules RV_ACCOUNTING_DOCUMENT_CREATE and AC_DOCUMENT_CREATE, to check the tax conditions.
The two shown tables XACCIT and XACCCR contain the data that is transferred to FI, the link between the two tables is POSNR:
Here it can be seen that ZGST is a tax condition and TXJDP is not filled.
In the other table the values can be found:
Responsible for the error is the empty field TXJDP for tax condition ZGST.
To find out why the field had not been filled, we have to check the Include LV60BF00, FORM ACCOUNTING_TAX_LINE, because in the standard coding here the filling should be done:
Taxjurisdiction is active, the first step is to fill xaccit-txjcd according to the condition category (XKOMV-KNTYP). For taxjurisdiction tax conditions the categories 1 – 4 are used (V/06 field T685A-KNTYP):
1 = Tax JurDic level 1 (with license check KNVL)
2 = Tax JurDic level 2
3 = Tax JurDic level 3
4 = Tax JurDic level 4
In the example with customer own tax condition ZGST, the field was empty.
After that the decision which tax jurisdiction level is used, the next step is to fill the field XACCIT-TXJLV, according to the XKOMV-KNTYP:
And finally filling of TXJDP is done.
As the tax condition ZGST was not customized as a taxjurisdiction condition the field could not be filled, and remained empty, leading to the error FF793 afterwards.
The tax conditions have to be configured as taxjurisdiction conditions. To avoid the error the customizing of the condition type (V/06) and pricing procedure (V/08) would have to be adjusted.
The standard procedure with taxjurisdiction conditions UTXD and UTXE is for US RVAXUD with tax conditions XR1…XR6.
More information on tax jurisdiction can be found on the SAP Help Portal:
This could be the way to findout the error reason! 🙁
Thanks for showing another way of error finding in SAP. 🙂
Hi Tobias Reiner Dolgener
Its a nice doc. Thanks for sharing
You mentioned that "To avoid the error the customizing of the condition type (V/06) and pricing procedure (V/08) would have to be adjusted."
What change is needed in V/08?
Br, Ajay M
Hi Ajay M,
thanks for your feedback.
In transaction V/06 the condition type is to be configured. There you would have to take care that the relevant condition type is defined not only as tax (in condition class) but also in condition category as tax jurisdiction:
Whereas in the pricing procedure customizing transaction V/08 the correct sequence of the tax jurisdiction conditions will have to be set up, compare it with the standard one, RVAXUD:
Hi Tobias Reiner Dolgener
Many thanks for such a quick response.
Our Pricing procedure (Brazil) is set up like this. The only difference I see as compared to what you gave for US is the Calc Type and Bas. Type. Is that the reason?
IBRX is the Base condition (Similar to UTXD) and IPI3, others are like XR1 - XR6
I have raised it to SAP OSS though. Just wanted to see if I can myself find a solution with SCN assistance
Can you throw some light please?
Br, Ajay M
Hi Ajay M,
the Brazil pricing procedure is very specific, and your question not related directly to my blog. If you would like to get suggestions here on SCN, please post your question in the SAP ERP SD Billing forum.
I strongly recommend that the "new" (since 2004) debugger be used, as it is more powerful and is continually being developed.
I've been posting goods issue using VL02N and tax jurisdiction code gets populated when looking at the accounting document(FB03) but when we upgraded into SP12, the tax jurisdiction code won't populate anymore. Do you know the reason why? Is there a way to populate the tax jurisdiction code using VL02N transaction code?