Functionality You can use this method to create order confirmations> for theprocess order. You can also use it to transfer goods movements that should be postedwith a confirmation. If no goods movements were specified for a confirmation, then the goodsmovements are determined using the standard logic for backflushes andautomatic goods receipt. INCLUDE BAPI_PRODORDCONF_HINT_COMMIT OBJECT DOKU ID TX Authorization check> INCLUDE BAPI_PROCORDCONF_CD_BERECHT OBJECT DOKU ID TX INCLUDE BAPI_PROCORDCONF_CD_RETURN OBJECT DOKU ID TXDescription The PostWrongEntries> parameter controls which confirmations aretransferred into the error pool. You can correct and re-post the entries of the error pool by using thepost-processing of confirmations>.Value range
- 0: No confirmations
- 1: Only incorrect confirmations
- 2: Incorrect confirmations and confirmations that cannot be processed
because of a lock situation.Default 0: No confirmations Description The parameter Testrun> controls whether the confirmation data isintended for posting or is only checked in test mode.Value range
- X: The confirmation data is checked in text mode.
Access is not locked for any objects.
- Blank: Once the confirmation data has been checked it is designated for
posting. Lock entries are set for the objects in question.Default Blank: Test mode Description The table Athdrlevels > creates confirmations as confirmations forthe order. The confirmed order is identified in the field ORDERID>. Each entry in the AtHdrLevels> table represents a separateconfirmation, which is checked and processed in the sequencetransferred.Description The DetailReturn> table provides one of the following pieces ofinformation for each confirmation:
- Successful posting
- Exception situation (due to incorrect data or current lock situation)
For each confirmation transferred in the AtHdrLevels> table, anentry is made in the DetailReturn> table. For a successful posting of a confirmation, the key of the confirmationis 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 case of a lock situation, theFLG_LOCKED> indicator is set.Description The Goodsmovements> table contains goods movements that shouldbe posted independently of the confirmations. The following automatic goods movements can be posted together withconfirmations:
- Backflushes of components
- Automatic goods receipt postings for the assembly
To complete or correct the goods movements, the data can be transferredto the Goodsmovements> table. Goods movements are assigned to their respective confirmations using theLinkConfGoodsmov> table. If at least one goods movement is assigned to a confirmation, then noautomatic goods movement is determined during saving.Default Note When you are posting goods movements using the confirmation, you cannotuse the entire MM functionality. This applies to the confirmation dialogtransactions and also for the confirmation BAPIs. Example: The indicator NO_TRANSFER_REQ> = X in the Goodsmovements>table is set to prevent a transport requirement being created when thegoods movement is executed. The inventory management structureBAPI2017_GM_ITEM_CREATE> is used for transferring the goodsmovements to confirmation BAPIs. However, this contains some fields thatdo not play a part in or are not supported for confirmations forproduction orders. The indicator, therefore, has no effect.Description The LinkConfGoodsmov> table assigns a confirmation to each goodsmovement item. The assignment is made through the IndexConfirm> andIndexGoodsmov:> indexes.
- IndexConfirm > refers to the entry in the AtHdrLevels>
table.
- IndexGoodsmov> refers to the entry in the Goodsmovements>
table. Items that are not assigned to a confirmation are not taken intoconsideration when you save. If you want to prevent goods movements from automatically beingassigned, because none have accrued, then you can prevent this with anentry in the LinkConfGoodsmov> table, without making an entry inthe Goodsmovements> table. In this case, the IndexConfirm> field must link to theconfirmation concerned and the IndexGoodsmov> field must have theinitial value 0>.
|