Diagnosis
When tables PTRV_PERIO and PTRV_ROT_AWKEY were read, no entry withposting run number &v1& was found.
The cause can be incorrect Customizing (see possible error message whencreating the posting run) or a previous data transfer from a sourcesystem with a release < 4.5A to the target system with accounting.Since, in this case, the dataset in the source system is kept, the tripdata can not be read when the transaction PRRW is called in the targetsystem.

System Response
When the posting run is rejected, trip statuses are not reset.

Procedure
In this case, reset the status of the relevant trips manually in thesource system.