SAP BAPI_ISUPROFILE_UPLOAD Function Module for Upload Profile Values
BAPI_ISUPROFILE_UPLOAD is a standard bapi isuprofile upload SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Upload Profile Values 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 isuprofile upload FM, simply by entering the name BAPI_ISUPROFILE_UPLOAD into the relevant SAP transaction such as SE37 or SE38.
Function Group: EEDM_BAPI_PROFILE_IMPORT
Program Name: SAPLEEDM_BAPI_PROFILE_IMPORT
Main Program: SAPLEEDM_BAPI_PROFILE_IMPORT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:
Function BAPI_ISUPROFILE_UPLOAD 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_ISUPROFILE_UPLOAD'"Upload Profile Values.
EXPORTING
* UPLOADINFO = "External reference
* SERVPROVSELF = "Own Service Provider in Data Exchange Process
* SERVPROV = "External Service Provider in Data Exchange Process
* IDOC_NUMBER = "IDoc Number
* XNOCOMMIT = "
* PACKAGESIZE = '1000' "
TABLES
PROFILEVALUES = "BAPI Upload Structure for Profile Values
* RETURN = "Return Parameter
* EXTENSIONIN = "Reference structure for BAPI parameters EXTENSIONIN/EXTENSIONOUT
* PROFHEADINTF = "Imported Profiles (Header Data)
IMPORTING Parameters details for BAPI_ISUPROFILE_UPLOAD
UPLOADINFO - External reference
Data type: BAPIISUPROVALUPDATAOptional: Yes
Call by Reference: No ( called with pass by value option)
SERVPROVSELF - Own Service Provider in Data Exchange Process
Data type: BAPIISUPROVALEXPCNTR-SERVPROVSELFOptional: Yes
Call by Reference: No ( called with pass by value option)
SERVPROV - External Service Provider in Data Exchange Process
Data type: BAPIISUPROVALEXPCNTR-SERVPROVOptional: Yes
Call by Reference: No ( called with pass by value option)
IDOC_NUMBER - IDoc Number
Data type: BAPIISUPROVALEXPCNTR-IDOC_NUMBEROptional: Yes
Call by Reference: No ( called with pass by value option)
XNOCOMMIT -
Data type: BAPIISUPROVALXNOCOMMITOptional: Yes
Call by Reference: No ( called with pass by value option)
PACKAGESIZE -
Data type: BAPIISUPROVALPACKAGESIZEDefault: '1000'
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BAPI_ISUPROFILE_UPLOAD
PROFILEVALUES - BAPI Upload Structure for Profile Values
Data type: BAPIISUPROVALOptional: No
Call by Reference: Yes
RETURN - Return Parameter
Data type: BAPIRET2Optional: Yes
Call by Reference: Yes
EXTENSIONIN - Reference structure for BAPI parameters EXTENSIONIN/EXTENSIONOUT
Data type: BAPIPAREXOptional: Yes
Call by Reference: Yes
PROFHEADINTF - Imported Profiles (Header Data)
Data type: BAPIISUPROFILEOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for BAPI_ISUPROFILE_UPLOAD 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: | ||||
lv_uploadinfo | TYPE BAPIISUPROVALUPDATA, " | |||
lt_profilevalues | TYPE STANDARD TABLE OF BAPIISUPROVAL, " | |||
lt_return | TYPE STANDARD TABLE OF BAPIRET2, " | |||
lv_servprovself | TYPE BAPIISUPROVALEXPCNTR-SERVPROVSELF, " | |||
lv_servprov | TYPE BAPIISUPROVALEXPCNTR-SERVPROV, " | |||
lt_extensionin | TYPE STANDARD TABLE OF BAPIPAREX, " | |||
lv_idoc_number | TYPE BAPIISUPROVALEXPCNTR-IDOC_NUMBER, " | |||
lt_profheadintf | TYPE STANDARD TABLE OF BAPIISUPROFILE, " | |||
lv_xnocommit | TYPE BAPIISUPROVALXNOCOMMIT, " | |||
lv_packagesize | TYPE BAPIISUPROVALPACKAGESIZE. " '1000' |
  CALL FUNCTION 'BAPI_ISUPROFILE_UPLOAD' "Upload Profile Values |
EXPORTING | ||
UPLOADINFO | = lv_uploadinfo | |
SERVPROVSELF | = lv_servprovself | |
SERVPROV | = lv_servprov | |
IDOC_NUMBER | = lv_idoc_number | |
XNOCOMMIT | = lv_xnocommit | |
PACKAGESIZE | = lv_packagesize | |
TABLES | ||
PROFILEVALUES | = lt_profilevalues | |
RETURN | = lt_return | |
EXTENSIONIN | = lt_extensionin | |
PROFHEADINTF | = lt_profheadintf | |
. " BAPI_ISUPROFILE_UPLOAD |
ABAP code using 7.40 inline data declarations to call FM BAPI_ISUPROFILE_UPLOAD
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 SERVPROVSELF FROM BAPIISUPROVALEXPCNTR INTO @DATA(ld_servprovself). | ||||
"SELECT single SERVPROV FROM BAPIISUPROVALEXPCNTR INTO @DATA(ld_servprov). | ||||
"SELECT single IDOC_NUMBER FROM BAPIISUPROVALEXPCNTR INTO @DATA(ld_idoc_number). | ||||
DATA(ld_packagesize) | = '1000'. | |||
Search for further information about these or an SAP related objects