Diagnosis
The confirmation was declared as being incorrect because multipleconfirmations were processed at the same time during saving and aserious problem occurred with one of these confirmations.
A case like this occurs, for example, if a trigger point is to betriggered when you save a confirmation that was transferred via BAPI orBDE interface and is processed in the background.
Since a function like this can require an additional dialog step butthis is not possible for background processing, all confirmationsprocessed at the same time have to be declared as being incorrect.Otherwise, data inconsistencies could arise in the operation for whichthe trigger point is to be triggered.

Procedure
The confirmations are saved as incorrect in the R/3 System. You canreprocess them in a later dialog step using 'Reprocessing incorrectconfirmations':
Call function