Description
When master data is transferred by batch input, the "Earliest MDchange" field (MD = master data) is filled in infotype 0003. In thisparticular instance, however, you need to avoid this happening becauseit would trigger a retroactive accounting run that is neither wantednor required (since you have yet to effect production startup for thetransferred set of personnel numbers). To prevent such a retroactiveaccounting run from being triggered, you must reset the "Earliest MDchange" field in infotype 0003.
This program resets the "Earliest MD change" field in infotype 0003.Proceed as follows:
"Earliest MD change" < "Date of comparison" ?
|
|--------------------|
| |
yes no
| |
reset no action
|
"Effect changes" ?
|
|---------------------|
| |
yes no
| |
new infotype no action
save 0003 on database
The date in the "Earliest MD change" field is reset (initialized) forall of the personnel numbers whose "Earliest MD change" date is furtherback in the past than the "Date of comparison" specified on theselection screen.
If the "Effect changes" checkbox is flagged, the changed infotype 0003record is saved on the database with the reset "Earliest MD change"date.
To avoid inconsistencies, the personnel numbers to be processed arelocked before processing if the "Effect changes" checkbox is flagged.If a personnel number cannot be locked, it is not processed. Lockedpersonnel numbers are listed separately in an output list at the end ofthe program.
The program does not recognize whether the "Earliest MD change" fieldis filled by the transfer of old data, or whether itis filled by an intentional change of dates after the transfer of olddata. For this reason, you should run this program immediately afterthe transfer of old data.

Example
Master data is transferred from the legacy system for personnel numbers1, 2, and 3. The production startup is planned for January 1, 1997. The"Earliest MD change" field is filled for all three personnel numbersduring the data transfer:
|--------------------------------------|
|Pers.No. |Earliest MD change |
|---------|----------------------------|
| 1 | May 27, 1989 |
| 2 | April 1, 1992 |
| 3 | January 1, 1997 |
|--------------------------------------|
You start the program with "Date of comparison" = January 1, 1997. Theresult is as follows:
|--------------------------------------|
|Pers.No. |Earliest MD change |
|---------|----------------------------|
| 1 | |
| 2 | |
| 3 | January 1, 1997 |
|--------------------------------------|
The "Earliest MD change" date is reset for personnel numbers 1 and 2because it is further back in the past than the "Date of comparison".Personnel number 3, however, is not changed because the "Earliest MDchange" date is the same as the "Date of comparison".
If the "Effect changes" checkbox has also been flagged, the changedinfotype 0003 data is stored on the database.