SAP ADS2KIPUPL_UPLOAD_COMPLETED Function Module for SPEC2000 IP Upload: Upload Completed









ADS2KIPUPL_UPLOAD_COMPLETED is a standard ads2kipupl upload completed SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for SPEC2000 IP Upload: Upload Completed 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 ads2kipupl upload completed FM, simply by entering the name ADS2KIPUPL_UPLOAD_COMPLETED into the relevant SAP transaction such as SE37 or SE38.

Function Group: ADS2KIPUPL_UL
Program Name: SAPLADS2KIPUPL_UL
Main Program: SAPLADS2KIPUPL_UL
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function ADS2KIPUPL_UPLOAD_COMPLETED 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 'ADS2KIPUPL_UPLOAD_COMPLETED'"SPEC2000 IP Upload: Upload Completed
EXPORTING
IS_HEADER = "Stores header information for IP data
I_UNAME = "SAP System, user logon name
I_MSG_RECORDED = "Messages have been recorded
I_PROFILE = "Upload Profile
* I_LOG_OBJKEY = "Object Key for Log (If initial, the object key is generated in the program)

EXCEPTIONS
ERROR_IN_MAIL = 1 ERROR_IN_EXPRESS = 2
.



IMPORTING Parameters details for ADS2KIPUPL_UPLOAD_COMPLETED

IS_HEADER - Stores header information for IP data

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

I_UNAME - SAP System, user logon name

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

I_MSG_RECORDED - Messages have been recorded

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

I_PROFILE - Upload Profile

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

I_LOG_OBJKEY - Object Key for Log (If initial, the object key is generated in the program)

Data type: BALNREXT
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

ERROR_IN_MAIL - Error Sending the Mail

Data type:
Optional: No
Call by Reference: Yes

ERROR_IN_EXPRESS - Error Sending the Express Message

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for ADS2KIPUPL_UPLOAD_COMPLETED 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_is_header  TYPE SPCIPHDR, "   
lv_error_in_mail  TYPE SPCIPHDR, "   
lv_i_uname  TYPE SYUNAME, "   
lv_error_in_express  TYPE SYUNAME, "   
lv_i_msg_recorded  TYPE BOOLE_D, "   
lv_i_profile  TYPE ADS2KIPUPL_PROFILE, "   
lv_i_log_objkey  TYPE BALNREXT. "   

  CALL FUNCTION 'ADS2KIPUPL_UPLOAD_COMPLETED'  "SPEC2000 IP Upload: Upload Completed
    EXPORTING
         IS_HEADER = lv_is_header
         I_UNAME = lv_i_uname
         I_MSG_RECORDED = lv_i_msg_recorded
         I_PROFILE = lv_i_profile
         I_LOG_OBJKEY = lv_i_log_objkey
    EXCEPTIONS
        ERROR_IN_MAIL = 1
        ERROR_IN_EXPRESS = 2
. " ADS2KIPUPL_UPLOAD_COMPLETED




ABAP code using 7.40 inline data declarations to call FM ADS2KIPUPL_UPLOAD_COMPLETED

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.

 
 
 
 
 
 
 


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!