Functionality You are carrying out a backflush for the production by lot scenario. Ifthe backflush cannot be carried out successfully, the system displaysan appropriate message via the exporting parameter RETURN. If thebackflush was carried out successfully, the exporting parameter RETURNis filled with initial values. The backflush is ultimately carried out for a production lot. The costsare collected at the production lot. Meaning of the parameters: BFLUSHFLAGS: Control of the type and the scope of a backflush BFLUSHDATAGEN: Parameters for the backflush data independent of anyscenario BFLUSHDATAMTP: Parameter specifically for the production lot scenario SERIALNR: List of serial numbers RETURN: Return of an error code when the backflush could not be carriedout successfully. No COMMIT WORK is carried out in this module. Note that a COMMIT WORK is created directly after accessing this BAPI.This means that it is not possible to use several BAPIs which recorddata on the database in sequence and then to create only one COMMITWORK after the last BAPI. Should this happen, however, the second BAPIwill be terminated as such a chain of accesses is not supported by theprogram. Notes A production lot and a plant must be transferred. You must also enter a posting date and a document date. If the repetitive manufacturing profile is set so that an onlinecorrection is mandatory when withdrawal errors occur and if awithdrawal error does occur when backflushing, the backflush cannot becarried out and an appropriate error code is displayed in the RETURNparameter. If the repetitive manufacturing profile is set so that an onlinecorrection is optional when withdrawal errors occur and if a withdrawalerror does occur when backflushing, the system creates postprocessingrecords for the components which could not be withdrawn. Therefore,make sure that the creation of postprocessing records is allowed in therepetitive manufacturing profile. Otherwise the withdrawal errors arenot logged and there is no system-aided way of postposting thecomponents. The backflush number given by the system is returned to the caller viathe CONFIRMATION parameter. Description The backflush number is given by the system when carrying out abackflush and specifically identifies a backflush in the SAP system. Description The fields of this parameter provide information on the error whichoccurred when the backflush could not be carried out successfully. Thefield MESSAGE contains a detailed error description should the shorttext not provide enough space to describe the reason of the error. Description The individual parameters of this structure contain the data requiredfor the backflush which are independent of the selected scenario(process). The following parameters must be transferred: POSTDATE,,,,Posting date DOCDATE,,,,Document date The field PRODPLANT must also be filled. Depending on whether you arebackflushing a yield quantity or a scrap quantity, you have to fill ineither the field BACKFLQUANT or SCRAPQUANT. The field PLANORDER must be filled if the backflush is to be carriedout for one particular planned order. Description The individual parameters of this structure contain the dataspecifically required for the production by lot scenario. These includethe following parameters: PRODLOT,,,,Production lot number This parameter must be filled. WARNING: If only the parameter PRODLOT is transferred and severalplanned orders exist for this production lot, the system cannot carryout the backflush as it cannot select a planned order automatically. Insuch a case, enter the planned order as well as filling in the fieldsfor the production lot. Description The individual parameters of this structure control the type and/orscope of the confirmation to be posted within the confirmation processchosen via the selection of the BAPI.
- Parameter BCKFLTYPE
This parameter defines the type of confirmation to be posted. In thecase of a confirmation in the production lot scenario, the followingconfirmation types are allowed: 01,,Final confirmation 21,,Final confirmation (document-neutral cancellation)
- Parameters RP_SCRAPTYPE, ACTIVITIES_TYPE, COMPONENTS_TYPE
These parameters have no significance in the production lot scenario.Description Goods movements that are to be posted depending on the confirmations. Automatic goods movements can be posted with a confirmation. Thisinvolves the backflushing of components> and automatic goodsreceipt postings for an assembly>. If this data is to be supplementedor corrected, the goods movement data can be transferred in the Goods Movements> table. If a confirmation is assigned to at least one goods movement, there isno determination of automatic goods movements for the confirmation whenthe latter is saved. That is to say, the goods movements passed oncannot be regarded as additional goods movements to the onesautomatically posted. Instead they represent the replacement items forthem so to speak.Default Note Note that not all of the indicators of the Goods Movements> tablecan be used. For example, the NO_TRANSFER_REQ = X indicator is set toprevent the generation of a transfer requirement when the goods movementis carried out. However, this indicator has no effect - a transferrequirement is created nevertheless. Cause: The inventory management structure BAPI2017_GM_ITEM_CREATE isused to pass on goods movements to confirmation BAPIs. However, thisstructure contains some fields that have no relevance to confirmationsin repetitive manufacturing or are not supported. Generally, thecomplete MM functionality cannot be supported in the posting of goodsmovements via confirmations. This applies both to the confirmationdialog transactions and the confirmation BAPIs.Description If serial numbers have to be maintained for the finished product to bebackflushed, you can use this parameter to transfer the serial numbersto be used for posting the goods receipt of the finished product. Notethat, in certain circumstances, the number of serial numbers to betransferred must correspond exactly to the backflush quantity (thisdepends on the serial number settings in the SAP system). If, in such acase, too few serial numbers are transferred, the backflush cannot becarried out successfully.
|