Functionality
This method enables you to confirm time events for productionorder operations.
You can enter any goods movements to be posted with a confirmation, aswell as any single-unit batch information for the goods movements.
If no goods movements are entered for a confirmation, they are set forconfirmation in accordance with the standard logic for backflushes andautomatic goods receipts.

Notes
INCLUDE BAPI_PRODORDCONF_HINT_COMMIT OBJECT DOKU ID TX
This method uses the methodBAPI_PRODORDCONF_CREATE_TE und andits parameters.
INCLUDE /SAPMP/BAPI_GOODSMOVEMENT OBJECT DOKU ID TX

Description
The return parameter is only used for grave errors that prevent any ofthe confirmations from being processed successfully. These errorsnormally only occur when the transferred confirmation data cannot betransferred to the internal structures because data definitionconventions were not adhered to.
The Return parameter contains detailed information about theerror in its structure. This information is also available, formatted,in the MESSAGE message text.

Default
If the system does not determine any grave errors, the parameter isreturned with the initial values.

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

Value range

• 0: Neither incorrect time events nor time events that cannot be
processed because they are locked are transferred to the error pool.

• 1: Incorrect time events are transferred to the error pool.
Time events that cannot be processed because they are locked are nottransferred to the error pool.

• 2: Both incorrect time events and time events that cannot be
processed because they are locked are transferred to the error pool.

Default
Default value is "0", in other words, no time event is transferred tothe error pool.

Description
Indicator used to control whether the confirmation data is provided forposting or only checked in the test mode. In the test mode no objectsare locked against concurrent access.

Value range


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


• " " (SPACE): The confirmation data is provided for posting after being
checked successfully. Even lock entries are deducted for the relevantobjects.

Default
The confirmation data is provided for posting with the defaulted value "", if no errors are found.

Description
The DetailReturn parameter table provides details about thesuccessful posting of each time event in the Timeevents table, orabout any exceptions caused by incorrect data or current locks.
An entry is made in the DetailReturn table for each confirmationimported into the Timeevents table. For example, the third entryin the DetailReturn table provides information about the postingof the third confirmation in the Timeevents table. When a confirmationis posted successfully, the confirmation number issued is displayed inthe CONF_NO and CONF_CNT fields.
In the case of an exception, comprehensive details are provided in thevarious fields, formatted, and returned in the MESSAGE messagetext.
In the case of a lock, the FLG_LOCKED indicator is set.

Description
Goods movements to be posted independently of confirmations. Automaticgoods movements, that is to say, Backflushes of Components andAutomatic Goods Receipt Postings for Assembly, can be posted witha confirmation. If you want to make any additions or corrections to thisgoods movement data, it can be entered in the Goodsmovementstable. The goods movements for each confirmation are assigned using theLinkConfGoodsmov parameter table.
If a confirmation is assigned to at least one goods movement, the systemdoes not determine any automatic goods movements when the confirmationis saved. In other words, the transferred goods movements cannot beregarded as additional goods movements to the automatically posted goodsmovements, but rather as substitute items.

Default

Note
You cannot use all the indicators in the Goods Movements table. Forexample, the NO_TRANSFER_REQ = X indicator is set to prevent a transferrequirement being created when a goods movement is made. However, thisindicator has no effect and a transport requirement is creatednonetheless.
Cause: The BAPI2017_GM_ITEM_CREATE inventory management structure isused to transfer goods movements to confirmation BAPIs. However, thiscontains some fields that are redundant or not supported in productionorder confirmations. Not all MM functions can be supported when you postgoods movements using the confirmation. This applies not only to theconfirmation dialog transactions but also to the confirmation BAPIs.
INCLUDE /SAPMP/BAPI_GOODSMOVEMENT_IT

Description
Each individual goods movement item is assigned to a confirmation usingthe LinkConfGoodsmov parameter table. The system cannot takeitems that are not assigned to a confirmation into account when saved.
The items are assigned using the IndexConfirm andIndexGoodsmov indices. The IndexConfirm index referencesthe entry in the AtHdrLevels parameter table, and theIndexGoodsmov index references the entry in theGoodsmovements parameter table.
There should therefore be an equal number of entries in theLinkConfGoodsmov and Goodsmovements tables.
Exception: If you wish to prevent the system from automaticallyassigning goods movements to confirmations (because none have arisen),you can do so by making an entry in the LinkConfGoodsmov tablewithout the need for an entry in the Goodsmovements table. Inthis case, the index in the IndexConfirm field must reference therelevant confirmation. You should enter the initial value 0 inthe IndexGoodsmov field.

Description
Table containing the confirmations to be entered, in the form of timeevents.
The confirmed object Operation can be identified by entering theconfirmation number in the CONF_NO field. Alternatively, theoperation can be identified by entering the order, sequence, operation,and if necessary, suboperation in the ORDERID, SEQUENCE,OPERATION and SUB_OPER fields.
If the confirmation is for an individual capacity, as well asspecifiying the operation, you can also identify the individual capacityusing the CAPA_CATEGORY and SPLIT fields.
As well as identifying the confirmed object, each time event has to bedescribed by specifying a valid record type in the RECORDTYPEfield. The following record types are permitted:


• A10: Begin Tear Down


• A20: Partial Finish Tear Down


• A30: Suspend Tear Down


• A40: End Tear Down


• B10: Begin Processing


• B20: Partial Finish Processing


• B30: Suspend Processing


• B40: End Processing


• R10: Begin Set Up


• R20: Partial Finish Set Up


• R30: Suspend Set Up


• R40: End Set Up


• V20: Partial Finish Variable Activity


• V40: End Variable Activity

Also enter the date and time for each time event in the LOGDATEand LOGTIME fields.
Each entry in the Timeevents table constitutes a separate timeevent, which will be checked and processed in the specified sequence.