Skip to Content
0
Feb 23, 2011 at 12:15 PM

COHV: Is this standard behaviour in ECC6.0

313 Views

Hi All,

We have upgraded from 4.7 to ECC6.0. We have the following doubt.

In Tcode COHV, we are mass confirming orders. But all go into incorrect status. In 4.7 it worked fine even if one confirmation was in error, the others were processed. But in ECC6.0 if one is in error the others are also errored out. Is this standard?

The long text is below.

Confirmation cannot be successfully saved

Message no. RU532

Diagnosis

The confirmation was declared as being incorrect because multiple confirmations were processed at the same time during saving and a serious problem occurred with one of these confirmations.

A case like this occurs, for example, if a trigger point is to be triggered when you save a confirmation that was transferred via BAPI or BDE interface and is processed in the background.

Since a function like this can require an additional dialog step but this is not possible for background processing, all confirmations processed at the same time have to be declared as being incorrect. Otherwise, data inconsistencies could arise in the operation for which the trigger point is to be triggered.

Procedure

The confirmations are saved as incorrect in the R/3 System. You can reprocess them in a later dialog step using 'Reprocessing incorrect confirmations':

Thanks in Advance.

Sandeep