Ansicht
Dokumentation
BAPI_REPMANCONF1_CREATE_MTO - Carry Out Confirmation in MTO Production Scenario
General Data in Customer Master Fill RESBD Structure from EBP Component StructureThis documentation is copyright by SAP AG.
Functionality
A confirmation process is carried out for the make-to-order scenario. If the confirmation is not successful, the system displays an appropriate message via the exporting parameter RETURN. If the confirmation is carried out successfully, the exporting parameter RETURN is populated with initial values.
The confirmation process is carried out for a sales order. Depending on the stock category (valuated or nonvaluated), the costs are collected on either a product cost collector or the sales order.
Goods movements that are posted together with a confirmation can also be passed on. If no goods movements are specified for a confirmation, they are determined according to the standard logic for backflushes relating to a confirmation.
You also have the option of classifying the goods receipt batch.
Meaning of the parameters:
BFLUSHFLAGS: Control of the type and scope of a confirmation
BFLUSHDATAGEN: Parameters for the scenario-dependent confirmation data
BFLUSHDATAMTO: Parameter specifically for the make-to-order scenario
SERIALNR: List of serial numbers
GOODSMOVEMENTS: Table of goods issues
CHARACTERISTICS_BATCH: Table of batch characteristics
RETURN: Return of an error code if the confirmation could not be carried out successfully
Example
Notes
No COMMIT WORK is executed in this module.
Note that immediately after the invocation of this BAPI, a COMMIT WORK is issued. This means that it is not possible to use several writing confirmation BAPIs in sequence and then only issue one single COMMIT WORK after the last BAPI. Should this nevertheless happen, the second BAPI is terminated because the program does not allow such a chain of calls.
A sales order and/or a planned order must be passed on.
The entry of a posting date and a document date is likewise mandatory.
If the associated repetitive manufacturing profile is set up in such a way that correction in dialog is mandatory in the event of withdrawal errors and if a withdrawal error occurs in the confirmation, the confirmation cannot be carried out and an appropriate error code is recorded in the RETURN parameter.
If the associated repetitive manufacturing profile is set up in such a way that a correction in dialog is optional in the event of withdrawal errors and if withdrawal errors occur in the confirmation, postprocessing records are generated for the non-withdrawable components. Therefore, make sure that the generation of postprocessing records is allowed in the repetitive manufacturing profile. Otherwise, the withdrawal errors are not logged and system-supported automatic subsequent posting is not possible.
The confirmation number assigned by the system is returned to the invoker via the CONFIRMATION parameter.
Further information
Parameters
/CWM/BFLUSHDATAGEN/CWM/GOODSMOVEMENTS
BFLUSHDATAGEN
BFLUSHDATAMTO
BFLUSHFLAGS
CHARACTERISTICS_BATCH
CONFIRMATION
GOODSMOVEMENTS
RETURN
SERIALNR
Exceptions
Function Group
2142General Material Data General Data in Customer Master
This documentation is copyright by SAP AG.
Length: 4283 Date: 20240523 Time: 153125 sap01-206 ( 80 ms )