Functionality With this method actual data can be copied as time eventconfirmations> to operations in production orders. The time event confirmations are only marked for further processing,which means that check of the transferred actual data and saving the dat a in the AFRU confirmation table takes place in a subsequent step. Thiscould be, for instance, using program CORUPROC1 in a periodicallyrecurring batch job. Alternatively in Customizing of Plant data capt ure> you can set the Immediate update> indicator in theDefine communication parameters for production orders> so that theprocessing of transferred data is started on immediately after the datatransfer. As well as the actual data for the confirmation, the actual data for thegoods movement that are posted together with a confirmation can betransferred. If no goods movements have been entered for a confirmation,the system determines items for backflushing> and automaticgoods receipt> automatically, when it continues processing theconfirmation.Notes Parameter>
- Return>
If the system could not post the confirmations, due to a serious error,it gives you information about the errors in the Return>parameter.
- Timetickets>
The data of the confirmation time tickets> are transferred in theTimeevents> table.
- Goodsmovements>
If goods movements are to be posted differently to the standard logic,these goods movements can be transferred in the Goodsmovements>table.
- LinkConfGoodsmov>
The assignment of goods movements to a confirmation is via theLinkConfGoodsmov> table. Each entry in the Goodsmovements>table requires an entry in this table, whereby the index in theLinkConfGoodsmov-Index_Confirm> field refers to the line of thecorresponding confirmation in the Timetickets> table and the indexin the LinkConfGoodsmov-Index_Goodsmov> table to the correspondinggoods movement in theGoodsmovements> table. If you want to prevent the use of the standard logic to post a goodsmovement for a confirmation, you should make an entry in the tableLinkConfGoodsmov> in which the index in the fieldLinkConfGoodsmov-Index_Confirm> refers to the row of the relatedconfirmation in the table Timetickets>. This is in addition to theconfirmation in table Timetickets>. In the fieldLinkConfGoodsmov-Index_Goodsmov> you should enter the initialvalue 0. In this case, it is not necessary to make an entry in the tableGoodsmovements>. If there is no entry in the LinkConfGoodsmov> table, the goodsmovements for backflushing and for the automatic goods movements aredetermined using a SAP standard method.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 Goods movements that should be posted as the result of a confirmation. 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 other parameter table LinkConfGoodsmov >. If at least one goods movement is assigned to a confirmation, noautomatic goods movements are determined for a confirmation when it issaved. That is, the goods movements that are transferred cannot beregarded as supplementary to the goods movements that are automaticallyposted. Rather, the goods movements that are transferred representreplacement items for the goods movements that are automaticallyposted.Description Each individual goods movement item is assigned to a confirmation viathe parameter table LinkConfGoodsmov>. Items that are notassigned to a confirmation cannot be taken into account when theconfirmation is saved. Assignment occurs via the IndexConfirm> and IndexGoodsmov>indices. For this process the IndexConfirm> index has to refer tothe entry in the parameter table Timetickets> 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 making an entry in theLinkConfGoodsmov> table, without an entry having to be made inthe Goodsmovements> table. In this case, the index in theIndexConfirm> field has to refer to the confirmation in question,whereas the initial value 0> has to be entered in theIndexGoodsmov> field.Description Table of confirmations to be entered, as time tickets. 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, in addition to entering the operation. Each entry in the Timetickets> table represents a separateconfirmation that is checked and processed in the sequence in which itis transferred.
|