When the user schedules a job that prints the logs for a costing run (with CK32), error message CK267 is issued because no logs yet exist. The user, however, wants to run the job as a follow-up job for selection, structure explosion or costing so that logs will exist when the print job is run.
The system checks whether logs exist at AT SELECTION-SCREEN.
This check, however, is not actually needed until START-OF-SELECTION.
The program has been corrected for 3.0B and 2.2G. A preliminary correction is possible. In Report SAPRCK32, deactivate the lines marked with <<<<<
No comments:
Post a Comment