Notice that all conflicts should have been solved before creating rosters. At least any conflict refering to the period you are about to create (including overlaping conflicts). Marked conflicts in the Database (where RPL changes the Status field to “Conflict”) are NOT processed. Unmarked conflicts in the Database (no Conflict message but still a divergence in data lines) does not prevent RPL from running, but you may loose data as the last processed data line overwrites the previous. Tip Tell RPL to ignore a data line by entering “?” in the Status field. Sometimes your Database contains lines awaiting e.g. a decision on a meeting. Put a question mark on them and remove it at any time to activate the lines again.
Edition: 2.27
ATS DATA DESIGN, USER GUIDE
Page: 94 Jan 2012