FI_TAX_GET_TXJCD_LEVELS error when trying to release billing document.

Question

We are in the process of converting from non-jurisdiction sales tax  to jurisdiction sales tax procedure.  I have setup our sandbox with the new jurisdiction procedure TAXUSJ and corresponding pricing procedure.  So far things are looking pretty good... however.  When the user tries to do a release on a billing document, it won't complete and the log shows the error:
System error in routine FI_TAX_GET_TXJCD_LEVELS error code 2 function builder TAX2
I have looked through SAP Notes and found references to this in regards to CRM.  We don't use CRM.
I have added jurisdiction codes to the company code and business partners (customers), also sales offices and plant.  I have setup the tax codes and the UTXJ condition type with the standard:
UTXJ 0 0 O0
UTXJ 0 1 O0
UTXJ 1 0 O0
UTXJ 1 1 O1
In the previous config, using TAXUS (non-jurisdiction) each of the sales offices was given a tax code, and that is what was used for sale tax.  So there are existing (and this is where the release issue arises) documents that use these codes (HQ, SE, NE, SP, etc) rather then O1.  Could this have something to do with the error? 
Document created in the new jurisdiction config can be released without a problem.  It is just occuring with documents created previous to the conversion.
What have I missed in config? 
Thanks for any info that may help shed light on this.  This is the last stumbling block to converting to the jurisdiction sales tax and we need to get it resolved as soon as possible.
Laurie McGinley

Answer 1

Briefly, for the document that needs to be released, and is getting the 'can't find tax code' error in the notes.
Correct values for TXJCD, TXJDP and TXJLV need to be added to the oringal document records that is to be released, tables: BSEG  BSET KNOV and VBRP.  In addition look into table KNOV for the field KNTYP.  We had to address the KNTYP field in KONV because it stored the code for the previous taxing procedure, which cant be found in the current one.  Changing it to the equivalent code for the current taxing proceudure worked.
I capture all the record pre and post change information for each of the changed records should there be a need to go back.  But so far it seems to be working.  Tho some of the notes indicate the need to add txjcd data to existing records to fix a similar problem, we needed to go a step further and modify records in 2 additional table.
Again.  We went from non-jurisdiction method where no jurisdictional information was captured to jurisdictional sales tax.  And the issue is around reversing documents that were originally created in the previous taxing procedure.