Functionality
A backflush is carried out for the make-to-stock scenario. If thebackflush is not completed successfully, an appropriate message istransmitted via the exporting parameter RETURN. If the backflush wascarried out successfully, the exporting parameter RETURN is filled withinitial values.
The backflush is carried out for a material. The costs are assigned toa product cost collector.
Meaning of the parameters:

• BFLUSHFLAGS: Control of the type and scope of the a backflush.


• BFLUSHDATAGEN: Parameter of the backflush data independent of the
scenario.

• BFLUSHDATAMTS: Parameter sepcifically for the make-to-stock scenario.


• SERIALNR: List of serial numbers.


• RETURN: Return of an error code when the backflush could not carried
out successfully.
In this module, no COMMIT WORK is executed.

Notes
Note that a COMMIT WORK is initiated directly after accessing thisBAPI. This means that it is not possible to use several recordingbackflush BAPIs in sequence and then initiate one single COMMIT WORKafter the last BAPI. Should this happen, the second BAPI will beterminated as the program does not support accessing the BAPI insequence.
A material and a plant or a planned order must be transferred. A PDCbackflush number must also be transferred.
The entry of a posting date and a document date is also mandatory.
If, in the repetitive manufacuturing profile, you have defined that acorrection in dialog is mandatory should withdrawal errors occur andshould an error actually occur in the backflush, the backflush cannotbe carried out and an appropriate error code is displayed in the RETURNparameter.
If, in the repetitive manufacuturing profile, you have defined that acorrection in dialog is optional should withdrawal errors occur andshould an error actually occur in the backflush, postprocessing recordsare created for the components that cannot be withdrawn. Make sure thatthe creation of postprocessing records is allowed in the repetitivemanufacturing profile. Otherwise, the withdrawal errors are not loggedand there is no way of reposting them automatically in the system.

Description
The fields of this parameter provide information on the error whichoccurred if the backflush could not be completed successfully. Thefield MESSAGE contains a detailed description of the error if the shorttext of the error is not sufficient to describe the reason for theerror.

Description
The individual parameteres of this structure contain the data requiredfor backflushing which is independent of the selected scenario(process). The following parameters must be transferred:
PDC_NUMBER,,PDC backflush number
POSTDATE,,Posting date
DOCDATE,,,,Document date
The fields PRODPLANT or PLANPLANT must also be filled. Depending onwhether you are backflushing yield or scrap, one of the fieldsBACKFLQUANT or SCRAPQUANT has to be filled. When backflushing componentscrap or excess component consumption or when executing a separatedactivity backflush, the field BACKFLQUANT must be filled with thequantity to be used as the reference quantity for determining thecomponents or the activities.
The field PLANORDER must be filled if the backflush is to be carriedout for a specific planned order. Otherwise, you have to fill at leastthe field MATNR with the material number of the assembly to bebackflushed.
WARNING: If no production version (PROVERSION) is transferred andseveral production versions exist for the given material in the givenplant, the backflush cannot be carried out successfully as the systemcannot determine a specific production version.

Description
The individual parameters of this structure contain the data requiredfor the backflush which is specifically required for the make-to-stockscenario. This includes the parameter:
REPPOINT,,,,Reporting point (milestone operation number in routing)
This parameter must be filled if a reporting point backflush is to becarried out or if a separated activity backflush, a separated goodsissue backflush or a separated component scrap backflush with referenceto a reporting point is to be carried out.

Description
The individual parameters of this structure control the type or thescope of the backflush to be posted in the backflushing processselected as a result of the BAPI selection.


• Parameter BCKFLTYPE

This parameter determines the type of the backflush to be posted. Thefollowing backflush types are allowed when backflushing in amake-to-stock scenario:
01,,Final backlfush
02,,Reporting point backflush
10,,Separated activity backflush
11,,Separated component consumption backflush
12,,Separated component scrap backflush
If the value 02 (reporting point backflush) is transferred with theparameter, a reporting point has to be transferred in structureBFLUSHDATAMTS using parameter REPPOINT.

• Parameter RP_SCRAPTYPE

This parameter determines the type of a reporting point backflush. Ithas to be filled if the value 02 is transferred with parameterBCKFLTYPE and a scrap posting is to be carried out. That is, when avalue is transferred to field SCRAPQUANT of parameter BFLUSHDATAGEN.The possible values of parameter RP_SCRAPTYPE include:
1,,Scrap at the specified reporting point
2,,Scrap up to the specified reporting point
3,,Excess component consumption at reporting point
If a value is required for this parameter but no value was transferred,the value 1 is set as a default value.

• Parameter ACTIVITIES_TYPE

This parameter determines the type of a separated activity backflush.It only has to be filled when the value 10 is transferred withparameter BCKFLTYPE. The possible values of the parameter include:
1,,Activities of all operations
2,,Only activities for the specified reporting point
3,,Only activities of the operations after the last reporting point
If a value is required for this parameter but no value is transferred,the value 1 is set as a default value. For the values 2 and 3, areporting point has to be transferred with parameterBFLUSHDATAMTS-REPPOINT.

• Parameter COMPONENTS_TYPE

This parameter determines the type of a separated goods issue postingor a separated component scrap posting. It only has to be filled whenthe values 11 or 12 are transferred. The possible values of theparameter include:
1,,Components of all operations
2,,Only components for the specified reporting point
3,,Only components after the last reporting point
If a value is required for this parameter but no value was transferred,the value 1 is set as a default value. For values 2 and 3, a reportingpoint has to be transferred with parameter BFLUSHDATAMTS-REPPOINT.

Description
If the finished product to be backflushed takes part in the serialnumber assignment option, you can use this parameter to transfer theserial numbers with which the goods receipt for the finished product isto be posted. Please note that in certain circumstances the number ofserial numbers transferred must correspond exactly to the backflushquantity (this depends on the serial number settings in the SAP system).If, in this case, not enough serial numbers are transferred, thebackflush cannot be carried out successfully.