SAP UJN_API_CHANGE_MPRO Function Module for BPC: Change Multiprovider BAPI









UJN_API_CHANGE_MPRO is a standard ujn api change mpro SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for BPC: Change Multiprovider BAPI 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 ujn api change mpro FM, simply by entering the name UJN_API_CHANGE_MPRO into the relevant SAP transaction such as SE37 or SE38.

Function Group: UJN_API_BI_IOBJ
Program Name: SAPLUJN_API_BI_IOBJ
Main Program: SAPLUJN_API_BI_IOBJ
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function UJN_API_CHANGE_MPRO 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 'UJN_API_CHANGE_MPRO'"BPC:  Change Multiprovider BAPI
  EXPORTING
   I_INFOPROV =  "InfoProvider
   IS_DETAILS =  "MultiProvider - Details
*  I_USE_SERVICE_USER = ABAP_TRUE "BPC: Generic indicator

TABLES
   IT_DIMS =  "MultiProvider - Details
   IT_IOBJS =  "MultiProvider - InfoObjects
   IT_DIM_IOBJS =  "MultiProvider - InfoObjects in the Dimensions
   IT_PARTINFOPROV =  "MultiProvider - InfoProvider Involved
   IT_PARTIOBJS =  "MultiProvider - InfoObject Identification
   ET_RETURN =  "Return Parameter
.



IMPORTING Parameters details for UJN_API_CHANGE_MPRO

I_INFOPROV - InfoProvider

Data type: BAPI6117-INFOPROV
Optional: No
Call by Reference: No ( called with pass by value option)

IS_DETAILS - MultiProvider - Details

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

I_USE_SERVICE_USER - BPC: Generic indicator

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

TABLES Parameters details for UJN_API_CHANGE_MPRO

IT_DIMS - MultiProvider - Details

Data type: BAPI6117DI
Optional: No
Call by Reference: Yes

IT_IOBJS - MultiProvider - InfoObjects

Data type: BAPI6117IO
Optional: No
Call by Reference: Yes

IT_DIM_IOBJS - MultiProvider - InfoObjects in the Dimensions

Data type: BAPI6117DIO
Optional: No
Call by Reference: Yes

IT_PARTINFOPROV - MultiProvider - InfoProvider Involved

Data type: BAPI6117PI
Optional: No
Call by Reference: Yes

IT_PARTIOBJS - MultiProvider - InfoObject Identification

Data type: BAPI6117PIO
Optional: No
Call by Reference: Yes

ET_RETURN - Return Parameter

Data type: BAPIRET2
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for UJN_API_CHANGE_MPRO 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_it_dims  TYPE STANDARD TABLE OF BAPI6117DI, "   
lv_i_infoprov  TYPE BAPI6117-INFOPROV, "   
lt_it_iobjs  TYPE STANDARD TABLE OF BAPI6117IO, "   
lv_is_details  TYPE BAPI6117, "   
lt_it_dim_iobjs  TYPE STANDARD TABLE OF BAPI6117DIO, "   
lv_i_use_service_user  TYPE UJ_FLG, "   ABAP_TRUE
lt_it_partinfoprov  TYPE STANDARD TABLE OF BAPI6117PI, "   
lt_it_partiobjs  TYPE STANDARD TABLE OF BAPI6117PIO, "   
lt_et_return  TYPE STANDARD TABLE OF BAPIRET2. "   

  CALL FUNCTION 'UJN_API_CHANGE_MPRO'  "BPC: Change Multiprovider BAPI
    EXPORTING
         I_INFOPROV = lv_i_infoprov
         IS_DETAILS = lv_is_details
         I_USE_SERVICE_USER = lv_i_use_service_user
    TABLES
         IT_DIMS = lt_it_dims
         IT_IOBJS = lt_it_iobjs
         IT_DIM_IOBJS = lt_it_dim_iobjs
         IT_PARTINFOPROV = lt_it_partinfoprov
         IT_PARTIOBJS = lt_it_partiobjs
         ET_RETURN = lt_et_return
. " UJN_API_CHANGE_MPRO




ABAP code using 7.40 inline data declarations to call FM UJN_API_CHANGE_MPRO

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 INFOPROV FROM BAPI6117 INTO @DATA(ld_i_infoprov).
 
 
 
 
DATA(ld_i_use_service_user) = ABAP_TRUE.
 
 
 
 


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!