Functionality
You use this method to enter time confirmations for operations frommaintenance/service orders.
Goods movements for a confirmation are determined for confirmationusing the standard logic for backflushing and automatic goods receipt.
INCLUDE BAPI_COMMIT OBJECT DOKU ID TX LANGUAGE EN

Notes
INCLUDE BAPI_PRODORDCONF_HINT_COMMIT OBJECT DOKU ID TX
Authorization check
The authorization object C_AFRU_AWK with activity01 (create) and the order type and plant for the confirmed maintenance/service order are checked.
Parameter

• PostWrongEntries

The POSTWRONGENTRIES parameter is used to control if theconfirmations to be entered in the event of exceptions (incorrect data/locked objects) should be taken from the SAP system and entered in thepool of incorrect confirmations.
Exceptions for a confirmation are logged in the DETAILRETURNparameter table.
The following types of POSTWRONGENTRIES parameter are possible:
" ": Confirmations for which no exceptions occur are posted. All otherconfirmations are rejected and are not transferred to the error pool.
"1": Confirmations for which no exceptions occur are posted. Allconfirmations for which incorrect data is determined are transferred tothe error pool. Confirmations that could not be posted due to a locksituation are not processed. That is, such confirmations are nottransferred to the error pool.
"2": Confirmations for which no exceptions occur are posted. Allconfirmations for which incorrect data or lock situations aredetermined are transferred to the error pool.

• Testrun

The TESTRUN parameter is used to control if the transferredconfirmation data is only checked for correctness. In this mode,objects such as order/message and reservation are not locked, and thedatabases are not updated.
To activate the TESTRUN mode, set the value "X".

• Return

If the confirmations could not be booked due to a fatal error, theRETURN parameter provides information on the errors thatoccurred.

• Timetickets

The data for the time confirmation are transferred to theTIMETICKETS table.

• DetailReturn

For each confirmation, the DETAILRETURN table gives informationon whether the confirmation was entered successfully, and if theconfirmation could not be entered due to a lock conflict or which erroroccurred.
If the confirmation could be entered successfully, the key for theconfirmation created is logged in the DETAILRETURN-CONF_No andDETAILRETURN-CONF_CNT fields.
If there is a lock conflict, the DETAILRETURN-FLGLOCKED
indicator is set.
If incorrect confirmation data is determined, the relevant errormessage is issued in the corresponding fields of the DETAILRETURN table.

Description
The return parameter is only used for fatal errors due to which none ofthe confirmations can be processed sucessfully. Such errors usuallyonly occur if the transferred confirmation data cannot be transferredto the internal structures, since conventions regarding the datadefinitions have not been observed.
The structure of the RETURN parameter contains all the necessaryinformation on the error that occured, both in detail and formatted inthe MESSAGE message text.

Default
If no fatal error is determined, the return parameter is returned withinitial values.

Description
Controls which confirmations are transferred to the error pool.
Entries in the error pool can be corrected and posted subsequently bypostprocessing of confirmations.

Value range


• 0: Neither incorrect confirmations nor confirmations that could not be
processed due to a lock situation are transferred to the error pool.

• 1: Incorrect confirmations are transferred to the error pool.
Confirmations that cannot be processed due to a lock situation are nottransferred to the error pool.

• 2: Both incorrect confirmations and confirmations that could not be
processed due to a lock situation are transferred to the error pool.

Default
Default value is "0", that is, no confirmation is transferred to theerror pool.

Description
Indicator that controls whether the confirmation data is to be plannedfor the update or whether the confirmation data will simply be checkedin the check mode. In the check mode, none of the objects are lockedagainst possible competing accesses.

Value range


• "X": In the check mode, the transferred data is simply checked.


• " " (SPACE): The confirmation data is to be planned for the update
after successful checks. Lock entries are therefore also deducted forthe objects affected.

Default
With the preassigned value " ", the confirmation data is planned forthe update, as long as no errors are determined.

Description
The DETAILRETURN parameter table gives information on thesuccessful posting of each individual confirmation in the
TIMETICKETS table, or information on the exceptions determined due toincorrect data or current lock situations.
An entry is made in the DETAILRETURN table for each confirmationtransferred to the TIMETICKETS table. That is, for example, thethird entry in the DETAILRETURN table gives information on theposting of the third confirmation in the TIMETICKETS table.
If the confirmation is posted successfully, the specified key for theconfirmation is shown in the CONF_NO and CONF_CNT fields.Otherwise all details on the exceptions are shown in the individualfields but are also transferred to the MESSAGE message text. Ifa lock situation occurred, the FLG_LOCKED indicator is also set.

Description
Table of confirmations to be created.
The OPERATION object that has been confirmed, can be identifiedby entering the confirmation number in the CONF_NO field.Alternatively, you can identify the operation by entering the order andthe operation, possibly with suboperations, in the ORDERID,OPERATION and possibly SUB_OPER fields.
If an individual capacity is to be confirmed, you can identify theindividual capacity using the CAPA_CATEGORY and SPLITfields, as well as entering the operation.
Each entry in the TIMETICKETS table displays a separateconfirmation that is checked and processed in the specified sequence.