Ansicht
Dokumentation

BAPI_REPMANCONF_CREATE_MTO - Execute Backflush in Sales Order Scenario

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   PERFORM Short Reference  
This documentation is copyright by SAP AG.

Functionality

A backflush is carried out for the make-to-order scenario. If the backflush is not successful an appropriate message is returned via the exporting parameter RETURN. If the backflush was carried out successfully, the exporting parameter RETURN is filled with initial values.

The backflush is carried out for a sales order. Depending on the stock category (valuated or nonvaluated), the costs are collected at a product 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 carried out successfully.

In this module, no COMMIT WORK is executed.

Note that after accessing this BAPI, a COMMIT WORK is directly transmitted. That is, it is not possible to use several recording backflush BAPIs in sequence and then only transmit one single COMMIT WORK after the last BAPI. If this should happen, however, the second BAPI will terminate as no such accessing chain is technically supported.

Notes

A sales order and/or a planned order must be transferred. A PDC backflush 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 set that a correction in dialog is mandatory in the occurrence of withdrawal errors and if a withdrawal error does exist in the backflush, then the backflush cannot be carried out and the system displays an appropriate error code in the RETURN parameter.

If in the corresponding repetitive manufacturing profile, you have set that a correction in dialog is optional in the occurrence of withdrawal errors and if a withdrawal error does exist in the backflush, the system creates postprocessing records for the components which cannot be withdrawn. Therefore, make sure that the creation of postprocessing records is allowed in the repetitive manufacturing profile. Otherwise, the withdrawal errors are not logged and it is not possible to use the system-supported automatic subsequent posting option.

Further information

Further information

Parameters

BFLUSHDATAGEN
BFLUSHDATAMTO
BFLUSHFLAGS
RETURN
SERIALNR

Exceptions

Function Group

2127

General Data in Customer Master   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

Length: 3164 Date: 20240523 Time: 154342     sap01-206 ( 56 ms )