Invalid/unnecessary CORR documents created when copying to target version

Question

Hi,
we recently discovered a large amount of inexplicable and unnecessary CORR documents in our target system V110. This is the summary of my investigation:
Invalid CORR journals:
In our foreign currency companies, the system creates reversing and non-reversing CORR journals in the target system V110 after the copy task
ran. The journals contain unexplicable amounts and posts to items and
ttypes that were not used in the source system V100. This creates
incorrect values in the target system. Does anybody know what is causing the creation of
those CORR journals and how can they be stopped?
Unnecessary CORR journals:
The system posts a reversing CORR journal in the target system due to a
difference between the source and target system. But even when the
difference is corrected in the source system it still continues to post
the CORR journal each month as reversing indefinately. Does anybody know why the
system is posting this CORR journal as reversing instead of non-reversing
and how can we stop those CORR journals from being posted after the
correction the the source system is done?
Your help would be very much appreciated : )

Answer 1

Hi Tanja,
I saw these CORR records many times during copy process.
One of the explanations:
Copying into Another Group Currency
To copy into another group currency, enter a currency translation method in Customizing for the copy method that is to use a rounding method. When performing a copy task, the system carries out the currency translation specified in the copy method.
The copy task consists of the following steps:
       1.      Read source data
       2.      Execute mapping (if defined)
       3.      Execute the BAdI (if defined)
       4.      Currency translation and rounding according to the currency translation method
       5.      Write target data in the target version
When totals data is copied, rounding differences can cause additional data rows. When documents are copied, additional document line items can be created.
If you periodically copy data (that is not accumulated), you can create the opening balances by copying the associated totals records one time only using the nonperiodic copy function .
If you copy the totals records cumulatively and copy documents at the same time, the system behaves as follows:
●      Totals records and documents are translated separately. However, documents are always translated periodically.
●      Then the system compares the translated totals records with the sum of the translated documents. Here, the translation of totals records takes precedence.
If a difference is found, the system creates a correction document. The document text denotes that this is a correction document. The correction document is also listed in the copy task log.
When data is translated into another group currency, the copy task log shows the following in addition to the ordinary information:
●      In the source data section: the group currency key of the source version
●      Error messages generated during currency translation
●      In the target data section: rounding differences
●      Correction documents (if created)
http://help.sap.com/erp2005_ehp_02/helpdata/en/43/7c91ea3c087101e10000000a1553f7/frameset.htm
Correction document is a CORR one.