SAP BAPI_SERVICE_RSV_PROXY_UPLOAD Function Module for
BAPI_SERVICE_RSV_PROXY_UPLOAD is a standard bapi service rsv proxy upload SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 service rsv proxy upload FM, simply by entering the name BAPI_SERVICE_RSV_PROXY_UPLOAD into the relevant SAP transaction such as SE37 or SE38.
Function Group: CRM_SRV_LOG
Program Name: SAPLCRM_SRV_LOG
Main Program: SAPLCRM_SRV_LOG
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BAPI_SERVICE_RSV_PROXY_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_SERVICE_RSV_PROXY_UPLOAD'".
EXPORTING
* IV_UPLOAD_ID = "Unique Reference Number
* IV_LOGSYS = "Logical System
* IV_MM_POSTING_DATE = SY-DATUM "Date in CHAR format
* IV_TESTRUN = ' ' "Single-Character Flag
* IV_HEADER_GUID = "GUID Return Message Header
* IV_CALL_TRANSLATOR = ' ' "Single-Character Flag
TABLES
* IT_RESERVATION = "Structure for Time Confirmation CRM -> CATS
* IT_SERV_CHAR = "CRM Service Characteristics Needed to Create CO Object
* EXT_RETURN = "Return Parameter
IMPORTING Parameters details for BAPI_SERVICE_RSV_PROXY_UPLOAD
IV_UPLOAD_ID - Unique Reference Number
Data type: BAPICRMDH2-REF_IDOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_LOGSYS - Logical System
Data type: LOGSYSTEMOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_MM_POSTING_DATE - Date in CHAR format
Data type: DATEDefault: SY-DATUM
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_TESTRUN - Single-Character Flag
Data type: BAPIFLAG-BAPIFLAGDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_HEADER_GUID - GUID Return Message Header
Data type: BAPISDCOSV-CURRENT_OBJECT_IDOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_CALL_TRANSLATOR - Single-Character Flag
Data type: BAPIFLAG-BAPIFLAGDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BAPI_SERVICE_RSV_PROXY_UPLOAD
IT_RESERVATION - Structure for Time Confirmation CRM -> CATS
Data type: CRMT_SERVICE_RSVMATOptional: Yes
Call by Reference: Yes
IT_SERV_CHAR - CRM Service Characteristics Needed to Create CO Object
Data type: BAPISDCOSVOptional: Yes
Call by Reference: No ( called with pass by value option)
EXT_RETURN - Return Parameter
Data type: BAPIRET2Optional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BAPI_SERVICE_RSV_PROXY_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_iv_upload_id | TYPE BAPICRMDH2-REF_ID, " | |||
| lt_it_reservation | TYPE STANDARD TABLE OF CRMT_SERVICE_RSVMAT, " | |||
| lv_iv_logsys | TYPE LOGSYSTEM, " | |||
| lt_it_serv_char | TYPE STANDARD TABLE OF BAPISDCOSV, " | |||
| lt_ext_return | TYPE STANDARD TABLE OF BAPIRET2, " | |||
| lv_iv_mm_posting_date | TYPE DATE, " SY-DATUM | |||
| lv_iv_testrun | TYPE BAPIFLAG-BAPIFLAG, " SPACE | |||
| lv_iv_header_guid | TYPE BAPISDCOSV-CURRENT_OBJECT_ID, " | |||
| lv_iv_call_translator | TYPE BAPIFLAG-BAPIFLAG. " SPACE |
|   CALL FUNCTION 'BAPI_SERVICE_RSV_PROXY_UPLOAD' " |
| EXPORTING | ||
| IV_UPLOAD_ID | = lv_iv_upload_id | |
| IV_LOGSYS | = lv_iv_logsys | |
| IV_MM_POSTING_DATE | = lv_iv_mm_posting_date | |
| IV_TESTRUN | = lv_iv_testrun | |
| IV_HEADER_GUID | = lv_iv_header_guid | |
| IV_CALL_TRANSLATOR | = lv_iv_call_translator | |
| TABLES | ||
| IT_RESERVATION | = lt_it_reservation | |
| IT_SERV_CHAR | = lt_it_serv_char | |
| EXT_RETURN | = lt_ext_return | |
| . " BAPI_SERVICE_RSV_PROXY_UPLOAD | ||
ABAP code using 7.40 inline data declarations to call FM BAPI_SERVICE_RSV_PROXY_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 REF_ID FROM BAPICRMDH2 INTO @DATA(ld_iv_upload_id). | ||||
| DATA(ld_iv_mm_posting_date) | = SY-DATUM. | |||
| "SELECT single BAPIFLAG FROM BAPIFLAG INTO @DATA(ld_iv_testrun). | ||||
| DATA(ld_iv_testrun) | = ' '. | |||
| "SELECT single CURRENT_OBJECT_ID FROM BAPISDCOSV INTO @DATA(ld_iv_header_guid). | ||||
| "SELECT single BAPIFLAG FROM BAPIFLAG INTO @DATA(ld_iv_call_translator). | ||||
| DATA(ld_iv_call_translator) | = ' '. | |||
Search for further information about these or an SAP related objects