Hierarchy
FI-CA (Software Component) FI-CA⤷
FI-CA (Application Component) Contract Accounts Receivable and Payable⤷
FKKB (Package) Contract A/R & A/P: Central Objects 
Attribute
| Message class |  |
>3 | |
| Short Description |  |
Contract A/R and A/P: Central functions | |
| Message Number |  |
568 | |
| Documentation status | Space: object requires documentation |
||
| Authorization check Error Message | |||
| Changed On |  |
20050224 |
Message Text
Help Document
Note
This message is only relevant if you use Tax Jurisdiction Codes (to determine tax rates in the USA) in client . If just a test company code has been created in your client that does contain the settings for Jurisdiction Codes, but you do not want to use them, you can ignore this warning.
Diagnosis
During the upgrade run it was determined that a company code exists in client that refers to country key . It is defined that the Tax Jurisdiction Code use is active for this country key.
From Release 4.61 the Jurisdiction Code is no longer stored in the contract account master data but in the partner address (the address that is entered in the contract account as the address relevant for Jurisdiction Codes). So that you do not have to re-enter already entered Jurisdiction Codes, there is the FKK_TRANSFER_JDC_TO_BPADDR report for transferring the Jurisdiction Codes from the contract account to the appropriate partner address on the account. Before the upgrade, this report was not executed in client . The report can be executed after the upgrade. This can also take place in live operation. However, it is recommended that you start the report before the productive phase. When executing in the productive phase, you must realize that the report locks individual partners and accounts. This prevents accounting clerks from changing the master data. Partners and accounts that are locked by accounting clerks cannot be processed with the report. These cases are output to the report logs and must be postprocessed after restarting the report by specifying the contract accounts.
System Response
If the report is started in live operation the Jurisdiction Codes are not available before execution in the associated partner addresses for the contract acconts. This can mean that when accounting clerks are changing business partner master data, they are required to define the Jurisdiction Code in the addresses. This additional work can be avoided by executing the report.
As the Jurisdiction Code is still contained in the contract account master data, no negative effects (other than those described above) are caused if you execute the report in live operation.
Procedure
If you do not use any Jusrisdiction Codes and if this warning was only created by a test company code that is not used in your system, then there is nothing to do.
If you work with Jurisdiction Codes, start the FKK_TRANSFER_JDC_TO_BPADDR report before live operation if possible. If this is not possible it is recommended that you execute the report outside working hours (at the weekend, for example) as it has a long runtime with large amounts of contract account in-force business.
Parallel report execution is possible for large datasets. For this, proceed as follows:
- First you can split the quantity of contract account numbers into a user-defined number "n" of intervals that are about the same size.
- Then you should start the conversion report "n" times by specifying the intervals. The report is only influenced to the extent that two contract account that are assigned to the same partner cannot be processed simultaneously. As the accounts are processed relatively swiftly, there is little overlapping with parallel execution.
Interval processing does not have to be simultaneous but can also take place sequentially (over several weekends, for example).
Note:
For parallel execution you must ensure that all contract accounts are processed for this report: When splitting the contract account numbers into intervals you must ensure that all intervals are processed and that the quantity of intervals covers the complete contract account in-force business.
To ensure that all contract accounts have been correctly processed, you should check the logs for all runs. If a business partner has been locked by an accounting clerk (or a parallel run), an entry is written in the log. These records must be postprocessed manually. The report must be restarted for these partners.
Procedure for System Administration
History
| Last changed on/by | |
20080716 | SAP |
| SAP Release Created in |
