Functionality
You can use this method to confirm time events for operations inproduction orders.
You can also transfer good movements, that are posted together with aconfirmation. If no goods movements have been entered for aconfirmation, they are determined using the standard logic forbackflushing and automatic goods receipt for confirmations.

Notes
Authorization check
The authorization object C_AFRU_AWK is checkedtogether with activity 01 (create), the order type and the work of theproduction order to be confirmed.
Parameters

• PostWrongEntries

You use the PostWrongEntries parameter to control whether in anexception (incorrect data/ locked objects) the confirmations areaccepted by the SAP system and placed in the pool of incorrectconfirmations.
Exceptions for confirmations are logged in the DetailReturnparameter table.
The following characteristic values of the PostWrongEntriesparameter are possible:
" ": Confirmations, in which no exception occurred, are posted. All theconfirmations are not processed, they are not placed in the pool forincorrect confirmations.
"1": Confirmations, in which no exception occurred, are posted. Allconfirmations with incorrect data are placed in the pool for incorrectconfirmations. On the other hand, confirmations that are not posted duea lock situation are not processed, they are not placed in the pool.
"2": Confirmations, in which no exception occurred, are posted. Allconfirmations with exceptions are placed in the pool.

• Testrun

You use the Testrun parameter to specify that the transfereddata are only checked to see if they are correct. Locking of objectssuch order and reservation as well as the updating of databases doesnot take place in this mode.
You set the value "X" to activate the Testrun mode.

• Return

If confirmations could not be processed, due to a serious error, youreceive information about the error in the Return parameter.

• Timeevents

The confirmation data is transfered to the Timeevents table.

• Goodsmovements

If goods movements should be posted that differ from the standardlogic, transfer these goods movements in the Goodsmovementstable.

• LinkConfGoodsmov

The goods movements are linked to a confirmation via theLinkConfGoodsmov table. There must be an entry in this table forevery entry in the Goodsmovements table. The index in theLinkConfGoodsmov-Index_Confirm field refers to the lines in thecorresponding confirmation in the Timeevents table and the indexin the LinkConfGoodsmov-Index_Goodsmov field refers to thecorresponding goods movement in the Goodsmovements table.
If you want to prevent a goods movement being posted during aconfirmation according to the standard logic, make an entry in theLinkConfGoodsmov table as well as in the Timeeventstable. The index in the LinkConfGoodsmov-Index_Confirm fieldrefers to the lines of the corresponding confirmation in theTimeevents table. Enter the initial value 0 in theLinkConfGoodsmov-Index_Goodsmov field. It is not necessary tomake an entry in the Goodsmovements table, in this case.
If no entry exists in the LinkConfGoodsmov table for aconfirmation, goods movements are determined using the standard logicfor backflushing and automatic goods receipt for confirmations.

• DetailReturn

The DetailReturn table informs you for each confirmation to beentered, whether a confirmation could not be entered due to a lockconflict or which error occurred.
If the confirmation could be enterd successfully, the key of theconfirmation is logged in the fields DetailReturn-Conf_No andDetailReturn-Conf_Cnt.
In the case of a lock conflict, the DetailReturn-Flg_Locked indicator is set.
If the data is found to be incorrect, a corresponding error message iswritten in the relevant fileds of the DetailReturn table.

Description
The Return parameter is only used for serious errors that prevent allconfirmations from being processed further. As a rule, this type oferror only occurs if the transferred confirmation data cannot beconverted into the internal structures, because conventions regardingdata definitions have not been adhered to.
The Return parameter's structure contains all the necessaryinformation about the error in detail. This is also prepared in themessage text MESSAGE.

Default
If no serious error is found, the return parameter is returned withinitial values.

Description
Controls which time events are transferred to the error pool.
Error pool entries can be corrected and posted usingReprocessing Confirmations.

Value range


• 0: Neither time events with errors nor time events that cannot be
processed due to a lock situation are transferred to the error pool.

• 1: Time events with errors are transferred to the error pool, whereas
time events that cannot be processed due to a lock situation are nottransferred to the error pool.

• 2: Both time events with errors and time events that cannot be
processed due to a lock situation are transferred to the error pool.

Default
The default value is "0". That is, no time events are transferred tothe error pool.

Description
Indicator that can be used to control whether confirmation data is tobe defined for posting, or whether confirmation data is merely to bechecked in test mode. In test mode, none of the objects are locked andthey can still be accessed if required.

Value range


• "X": The transferred data is merely checked in test mode.


• " " (SPACE): If the check was successful, the confirmation data is
defined for posting. Lock entries are therefore set for the affectedobjects.

Default
With the preassigned value " ", the confirmation data is defined forposting, provided no error can be found.

Description
The parameter table DetailReturn provides information about thesuccessful entry of each individual time event in the Timeeventstable, or about any exception that occurs due to incorrect data or acurrent lock situation.
An entry is made in the DetailReturn table for each time eventthat is transferred to the Timeevents table. For example, thethird entry in the DetailReturn table provides information aboutthe posting of the third time event in the Timeevents table.
If a confirmation is successfully entered, the key assigned to theconfirmation is found in the CONF_NO und CONF_CNT fields.Otherwise, all details about the exception are found in the individualfields, but also transferred in the prepared message textMESSAGE. If a lock situation occurs, the FLG_LOCKEDindicator is also set.

Description
Goods movements that should only be posted as the result of aconfirmation.
Automatic goods movements can be posted with a confirmation. One formof this is backflushing of components and the other isautomatic goods receipt posting for an assembly. If this data isadded to or corrected, the goods movement data can be transferred viathe Goodsmovements table. The assignment of goods movements toconfirmations occurs via the additional parameter tableLinkConfGoodsmov.
If at least one goods movement is assigned to a confirmation, noautomatic goods movements are determined for a confirmation when it issaved. In other words, the goods movements that are transferred cannotbe regarded as supplementary to the goods movements that areautomatically posted. Rather, the goods movements that are transferredrepresent, as it were, the replacement items for the goods movementsthat are automatically posted.

Default

Note
Note that not all of the indicators in the Goodsmovements tablecan be used. For example, indicator NO_TRANSFER_REQ = X is set in orderto avoid creation of a transfer request during a goods movement.However, this indicator has no effect - a transfer request is creatednonetheless.
Cause: Inventory management structure BAPI2017_GM_ITEM_CREATE is usedto transfer goods movements to confirmation BAPIs. However, thiscontains some fields that have no effect or are not supported duringthe confirmation of production orders. Generally, the complete range ofMM functions cannot be supported during posting of goods movements.This is valid for both confirmation dialog functions and confirmationBAPIs.

Description
Each individual goods movement item is assigned to a confirmation viathe parameter table LinkConfGoodsmov. Items that are notassigned to a confirmation cannot be included in the process when theconfirmation is saved.
Assignment occurs via the IndexConfirm and IndexGoodsmovindices. For this process the IndexConfirm index has to refer tothe entry in the parameter table Timeevents and theIndexGoodsmov index has to refer to the entry in the parametertable Goodsmovements.
As a rule, therefore, the total number of entries in theLinkConfGoodsmov table corresponds to the total number ofentries in the Goodsmovements table.
Exception: You want to prevent goods movements from being automaticallydetermined for a confirmation, because, as an exception, none havearisen. This can be achieved by an entry in the LinkConfGoodsmovtable, without an entry having to be made in the Goodsmovementstable. In this case, the index in the IndexConfirm field has torefer to the confirmation in question, whereas the initial value 0
has to be entered in the IndexGoodsmov field.

Description
Table of confirmations to be entered, as time events.
You can identify the confirmed operation by entering theconfirmation number in the CONF_NO field. Alternatively, you canidentify the operation by entering the order, sequence and operation,and if necessary the sub-operation, in the ORDERID, SEQUENCE
, OPERATION and SUB_OPER fields.
If an individual capacity is being confirmed, you can identify theindividual capacity with the help of the CAPA_CATEGORY andSPLIT fields, as well as entering the operation.
In addition to identifying the confirmed object, you also have todescribe each time event by entering a valid record type in the
RECORDTYPE field. The following record types are permitted:


• A10: Start teardown


• A20: Partial teardown


• A30: Interrupt teardown


• A40: Finish teardown


• B10: Start processing


• B20: Partial processing


• B30: Interrupt processing


• B40: Finish processing


• R10: Begin setup


• R20: Partial setup


• R30: Interrupt setup


• R40: Finish setup


• V20: Partial variable activity


• V40: Finish variable activity

Also, the date and time must be entered in the LOGDATE andLOGTIME fields for each time event.
Each entry in the Timeevents table represents a separate timeevent that is checked and processed in the sequence in which it istransferred.