SAP BAPI_ISU_POD_PROXY_UPLOAD Function Module for NOTRANSL: Proxy BAPI for upload IS-U connection objects
BAPI_ISU_POD_PROXY_UPLOAD is a standard bapi isu pod 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 for NOTRANSL: Proxy BAPI for upload IS-U connection objects 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 isu pod proxy upload FM, simply by entering the name BAPI_ISU_POD_PROXY_UPLOAD into the relevant SAP transaction such as SE37 or SE38.
Function Group: IBSSI_CRM_TO_PROXYS
Program Name: SAPLIBSSI_CRM_TO_PROXYS
Main Program: SAPLIBSSI_CRM_TO_PROXYS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BAPI_ISU_POD_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_ISU_POD_PROXY_UPLOAD'"NOTRANSL: Proxy BAPI for upload IS-U connection objects.
EXPORTING
UPLOAD_BDOC_ID = "Upload BDoc ID
UPLOAD_BDOC_TYPE_ID = "Upload BDoc Type ID
TABLES
MESSAGE_EXT = "Middleware Transaction Container Structure
IMPORTING Parameters details for BAPI_ISU_POD_PROXY_UPLOAD
UPLOAD_BDOC_ID - Upload BDoc ID
Data type: BAPICRMDH2-REF_IDOptional: No
Call by Reference: No ( called with pass by value option)
UPLOAD_BDOC_TYPE_ID - Upload BDoc Type ID
Data type: BAPICRMDH2-REF_IDOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BAPI_ISU_POD_PROXY_UPLOAD
MESSAGE_EXT - Middleware Transaction Container Structure
Data type: BAPIMTCSOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for BAPI_ISU_POD_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: | ||||
| lt_message_ext | TYPE STANDARD TABLE OF BAPIMTCS, " | |||
| lv_upload_bdoc_id | TYPE BAPICRMDH2-REF_ID, " | |||
| lv_upload_bdoc_type_id | TYPE BAPICRMDH2-REF_ID. " |
|   CALL FUNCTION 'BAPI_ISU_POD_PROXY_UPLOAD' "NOTRANSL: Proxy BAPI for upload IS-U connection objects |
| EXPORTING | ||
| UPLOAD_BDOC_ID | = lv_upload_bdoc_id | |
| UPLOAD_BDOC_TYPE_ID | = lv_upload_bdoc_type_id | |
| TABLES | ||
| MESSAGE_EXT | = lt_message_ext | |
| . " BAPI_ISU_POD_PROXY_UPLOAD | ||
ABAP code using 7.40 inline data declarations to call FM BAPI_ISU_POD_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_upload_bdoc_id). | ||||
| "SELECT single REF_ID FROM BAPICRMDH2 INTO @DATA(ld_upload_bdoc_type_id). | ||||
Search for further information about these or an SAP related objects