Functionality
A backflush is carried out for the make-to-order scenario. If thebackflush is not successful an appropriate message is returned via theexporting parameter RETURN. If the backflush was carried outsuccessfully, the exporting parameter RETURN is filled with initialvalues.
The backflush is carried out for a sales order. Depending on the stockcategory (valuated or nonvaluated), the costs are collected at aproduct cost collector or the sales order.
Meaning of the parameters:
BFLUSHFLAGS: Controls the type and the scope of a backflush
BFLUSHDATAGEN: Parameter for the scenario-independent backflush data
BFLUSHDATAMTO: Parameter for the make-to-order scenario
SERIALNR: List of serial numbers
RETURN: Return of an error code if the backflush could not be carriedout successfully.
In this module, no COMMIT WORK is executed.
Note that after accessing this BAPI, a COMMIT WORK is directlytransmitted. That is, it is not possible to use several recordingbackflush BAPIs in sequence and then only transmit one single COMMITWORK after the last BAPI. If this should happen, however, the secondBAPI will terminate as no such accessing chain is technicallysupported.

Notes
A sales order and/or a planned order must be transferred. A PDCbackflush number also has to be transferred.
The entry of a posting date and a document date is also mandatory.
If in the corresponding repetitive manufacturing profile, you have setthat a correction in dialog is mandatory in the occurrence ofwithdrawal errors and if a withdrawal error does exist in thebackflush, then the backflush cannot be carried out and the systemdisplays an appropriate error code in the RETURN parameter.
If in the corresponding repetitive manufacturing profile, you have setthat a correction in dialog is optional in the occurrence of withdrawalerrors and if a withdrawal error does exist in the backflush, thesystem creates postprocessing records for the components which cannotbe withdrawn. Therefore, make sure that the creation of postprocessingrecords is allowed in the repetitive manufacturing profile. Otherwise,the withdrawal errors are not logged and it is not possible to use thesystem-supported automatic subsequent posting option.

Description
The fields of these parameters provide information on the errors whichoccurred when the backflush could not be carried out successfully. Thefield MESSAGE contains a detailed error description if the short textof the error is not sufficient to describe the reason for the error.

Description
The individual parameters of this structure contain the necessary datafor the backflush which is independent of the scenario selected(process). The following parameters must be transferred in every case:
PDC_NUMBER,,PDC Backflush number
POSTDATE,,,,Posting date
DOCDATE,,,,Document date
The fields PRODPLANT or PLANPLANT also have to be filled. Depending onwhether you are dealing with a yield backflush or a scrap backflush,one of the fields BACKFLQUANT or SCRAPQUANT has to be filled.
The field PLANORDER must be filled if the backflush if to be carriedout for a specific planned order.

Description
The individual parameters of this structure contain the necessary datafor the backflush specifically required for the make-to-order scenario.This includes the following parameters:
SORDER,,,,Sales order number
SORDERITEM,,Sales order item
These parameters must be filled if no planned order is transferred inthe parameter PLANORDER.
WARNING: If only the parameters SORDER and SORDERITEM are transferredand several planned orders exist for this sales order, the backflushcannot be carried out as the system cannot select any of the plannedorders automatically. In such a case, transfer either the appropriateplanned order or the planned order in addition to the fields for thesales order.

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 backflush to be posted. Thefollowing backflush types are allowed when backflushing in amake-to-stock scenario:
01,,Final backflush

• Parameters RP_SCRAPTYPE, ACTIVITIES_TYPE, COMPONENTS_TYPE

These parameters have no significance for the make-to-order scenario.

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.