This method can be used to enteractivity confirmations> for phases of process orders.
If the first confirmation that is entered is an activity confirmation,the status of the phase is set to Partially Confirmed>.Activity confirmations do not effect the confirmation status in anyother way.
INCLUDE BAPI_PRODORDCONF_HINT_COMMIT OBJECT DOKU ID TX
INCLUDE BAPI_PROCORDCONF_CD_BERECHT OBJECT DOKU ID TX
INCLUDE BAPI_PROCORDCONF_CD_RETURN OBJECT DOKU ID TX
The parameter PostWrongEntries> controls which confirmationsare transferred to the error pool.
Entries in the error pooll can be corrected and re-posted usingPost-processing of confirmations>.
- 0: No confirmation
- 1: Only incorrect confirmations
- 2: Incorrect confirmations and confirmation that cannot be processeddue to a lock situation
0: No confirmations
The Activities> table transfers the confirmations to be createdas time events.
The confirmed object phase can be identified as one of the followingtypes:
- By the confirmation number in the CONF_NO> field
- By a combination of the following specifications:
Order in the ORDERID> field
Phase in the PHASE> field
Possible secondary resource in the SEC_RESOURCE> field
Each entry in the Activities> table represents a separate timeevent, which is checked and processed in the transferred sequence.verarbeitet wird.
The DetailReturn> table provides one of the following pieces ofinformation for each confirmation:
- Successful posting
- Exception situation (on account of incorrect data or current locksituation)
For each confirmation transferred to the Activities> table, anentry is made in the DetailReturn> table.
For the successful posting of a confirmation, the key of theconfirmation is made available in the CONF_NO> and CONF_CNT>fields.
Otherwise, all the details for the exception situation are madeavailable in the respective fields and the report text is transferred tothe MESSAGE> field. In the event of a lock situation, theFLG_LOCKED> indicator is also set.