Note
This message is only relevant if you use Tax Jurisdiction Codes(to determine tax rates in the USA) in client &V1&. If just a testcompany code has been created in your client that does contain thesettings for Jurisdiction Codes, but you do not want to use them, youcan ignore this warning.

Diagnosis
During the upgrade run it was determined that a company code exists inclient &V1& that refers to country key &V2&. It is defined that the TaxJurisdiction Code use is active for this country key.
From Release 4.61 the Jurisdiction Code is no longer stored in thecontract account master data but in the partner address (the addressthat is entered in the contract account as the address relevant forJurisdiction Codes). So that you do not have to re-enter alreadyentered Jurisdiction Codes, there is the FKK_TRANSFER_JDC_TO_BPADDR
report for transferring the Jurisdiction Codes from the contractaccount to the appropriate partner address on the account. Before theupgrade, this report was not executed in client &V1&. The report can beexecuted after the upgrade. This can also take place in live operation.However, it is recommended that you start the report before theproductive phase. When executing in the productive phase, you mustrealize that the report locks individual partners and accounts. Thisprevents accounting clerks from changing the master data. Partners andaccounts that are locked by accounting clerks cannot be processed withthe report. These cases are output to the report logs and must bepostprocessed after restarting the report by specifying the contractaccounts.

System Response
If the report is started in live operation the Jurisdiction Codes arenot available before execution in the associated partner addresses forthe contract acconts. This can mean that when accounting clerks arechanging business partner master data, they are required to define theJurisdiction Code in the addresses. This additional work can be avoidedby executing the report.
As the Jurisdiction Code is still contained in the contract accountmaster data, no negative effects (other than those described above) arecaused if you execute the report in live operation.

Procedure
If you do not use any Jusrisdiction Codes and if this warning was onlycreated by a test company code that is not used in your system, thenthere is nothing to do.
If you work with Jurisdiction Codes, start theFKK_TRANSFER_JDC_TO_BPADDR report before live operation ifpossible. If this is not possible it is recommended that you executethe report outside working hours (at the weekend, for example) as ithas a long runtime with large amounts of contract account in-forcebusiness.
Parallel report execution is possible for large datasets. For this,proceed as follows:
First you can split the quantity of contract account numbers into auser-defined number "n" of intervals that are about the same size.
Then you should start the conversion report "n" times by specifying theintervals. The report is only influenced to the extent that twocontract account that are assigned to the same partner cannot beprocessed simultaneously. As the accounts are processed relativelyswiftly, there is little overlapping with parallel execution.
Interval processing does not have to be simultaneous but can also takeplace sequentially (over several weekends, for example).
Note:
For parallel execution you must ensure that all contract accounts areprocessed for this report: When splitting the contract account numbersinto intervals you must ensure that all intervals are processed andthat the quantity of intervals covers the complete contract accountin-force business.
To ensure that all contract accounts have been correctly processed, youshould check the logs for all runs. If a business partner has beenlocked by an accounting clerk (or a parallel run), an entry is writtenin the log. These records must be postprocessed manually. The reportmust be restarted for these partners.