SAP BAPI_BMUOM_REPLICATE Function Module for Distribute batch-specific material units of measure









BAPI_BMUOM_REPLICATE is a standard bapi bmuom replicate SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Distribute batch-specific material units of measure processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.


See here to view full function module documentation and code listing for bapi bmuom replicate FM, simply by entering the name BAPI_BMUOM_REPLICATE into the relevant SAP transaction such as SE37 or SE38.

Function Group: VBWU
Program Name: SAPLVBWU
Main Program: SAPLVBWU
Appliation area: M
Release date: 15-Oct-2004
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function BAPI_BMUOM_REPLICATE pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.
CALL FUNCTION 'BAPI_BMUOM_REPLICATE'"Distribute batch-specific material units of measure
  EXPORTING
*  REQUESTCHANGES =  "Request changes from eng. change mgmt
*  CHANGEPOINTERSELECTION =  "Parameters for Selecting Change Pointers
*  NOCOMMIT =  "COMMIT Control at BAPI Interface
*  TESTRUN =  "Switch to Simulation Session for Write BAPIs

TABLES
*  MATERIAL =  "Selection parameters for mat.
*  UOMUSAGE =  "Selection parameters for using units of measure
*  RECIPIENTS =  "Receiving Systems (Logical Systems)
*  REPLICATEDOBJECTS =  "Replicated object instances
*  RETURN =  "Confirmations
.



IMPORTING Parameters details for BAPI_BMUOM_REPLICATE

REQUESTCHANGES - Request changes from eng. change mgmt

Data type: BAPI_BMUOM_DATA-RQSTCHNG
Optional: Yes
Call by Reference: No ( called with pass by value option)

CHANGEPOINTERSELECTION - Parameters for Selecting Change Pointers

Data type: BAPI_BMUOM_CHANGEPOINTER_SEL
Optional: Yes
Call by Reference: No ( called with pass by value option)

NOCOMMIT - COMMIT Control at BAPI Interface

Data type: BAPI_BMUOM_DATA-NOCOMMIT
Optional: Yes
Call by Reference: No ( called with pass by value option)

TESTRUN - Switch to Simulation Session for Write BAPIs

Data type: BAPI_BMUOM_DATA-TESTRUN
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for BAPI_BMUOM_REPLICATE

MATERIAL - Selection parameters for mat.

Data type: BAPI_BMUOM_MATERIAL_RANGE
Optional: Yes
Call by Reference: No ( called with pass by value option)

UOMUSAGE - Selection parameters for using units of measure

Data type: BAPI_BMUOM_UOMUSAGE_RANGE
Optional: Yes
Call by Reference: No ( called with pass by value option)

RECIPIENTS - Receiving Systems (Logical Systems)

Data type: BAPI_RECEIVER
Optional: Yes
Call by Reference: No ( called with pass by value option)

REPLICATEDOBJECTS - Replicated object instances

Data type: BAPI_BMUOM_REPL_OBJECTS
Optional: Yes
Call by Reference: No ( called with pass by value option)

RETURN - Confirmations

Data type: BAPIRET2
Optional: Yes
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for BAPI_BMUOM_REPLICATE Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.

DATA:
lt_material  TYPE STANDARD TABLE OF BAPI_BMUOM_MATERIAL_RANGE, "   
lv_requestchanges  TYPE BAPI_BMUOM_DATA-RQSTCHNG, "   
lt_uomusage  TYPE STANDARD TABLE OF BAPI_BMUOM_UOMUSAGE_RANGE, "   
lv_changepointerselection  TYPE BAPI_BMUOM_CHANGEPOINTER_SEL, "   
lv_nocommit  TYPE BAPI_BMUOM_DATA-NOCOMMIT, "   
lt_recipients  TYPE STANDARD TABLE OF BAPI_RECEIVER, "   
lv_testrun  TYPE BAPI_BMUOM_DATA-TESTRUN, "   
lt_replicatedobjects  TYPE STANDARD TABLE OF BAPI_BMUOM_REPL_OBJECTS, "   
lt_return  TYPE STANDARD TABLE OF BAPIRET2. "   

  CALL FUNCTION 'BAPI_BMUOM_REPLICATE'  "Distribute batch-specific material units of measure
    EXPORTING
         REQUESTCHANGES = lv_requestchanges
         CHANGEPOINTERSELECTION = lv_changepointerselection
         NOCOMMIT = lv_nocommit
         TESTRUN = lv_testrun
    TABLES
         MATERIAL = lt_material
         UOMUSAGE = lt_uomusage
         RECIPIENTS = lt_recipients
         REPLICATEDOBJECTS = lt_replicatedobjects
         RETURN = lt_return
. " BAPI_BMUOM_REPLICATE




ABAP code using 7.40 inline data declarations to call FM BAPI_BMUOM_REPLICATE

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

 
"SELECT single RQSTCHNG FROM BAPI_BMUOM_DATA INTO @DATA(ld_requestchanges).
 
 
 
"SELECT single NOCOMMIT FROM BAPI_BMUOM_DATA INTO @DATA(ld_nocommit).
 
 
"SELECT single TESTRUN FROM BAPI_BMUOM_DATA INTO @DATA(ld_testrun).
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!