This method checks whether a confirmation record> with thespecified key exists.
The key of a confirmation record has the following components:
- Confirmation> - confirmation number
- Confirmationcounter > - confirmation counter
The Return> parameter returns notifications for the followingexception situations:
- The confirmation record does not exist
- The confirmation record is an order with an order category other than aprocess order assigned.
The Return> parameter transfers detailed information and messagetexts for errors that have occurred.
The Return> parameter is filled in the following exceptionsituations:
- The confirmation does not exist
- The order for which the confirmation was created does not exist
- The order for which the confirmation was created is not a process order
If the system cannot determine an exception situation, then the returnparameter is returned with initial values.
The Confirmation> parameter transfers the confirmation number.
The number is assigned internally for each phase of an order when thephase is created. It uniquely identifies the phase.
If a confirmation is created not for the phase but for the order, thenthe number is assigned when the first confirmation is created and it isthen stored in the order header.
Together with the confirmation counter Confirmationcounter>, theconfirmation number forms the key of every confirmation record in theAFRU> table.
The Confirmationcounter> parameter transfers the confirmationcounter.
The internally assigned counter distinguishes between severalconfirmations for the same phase or for the same order. The lastconfirmation counter assigned is retained in the phase or in the order.
Together with the confirmation number Confirmation> theconfirmation counter forms the key of every confirmation record in theAFRU> table.