SAP ARCHIVELINK_URL_GENERATE Function Module for









ARCHIVELINK_URL_GENERATE is a standard archivelink url generate 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 archivelink url generate FM, simply by entering the name ARCHIVELINK_URL_GENERATE into the relevant SAP transaction such as SE37 or SE38.

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



Function ARCHIVELINK_URL_GENERATE 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 'ARCHIVELINK_URL_GENERATE'"
EXPORTING
INPUT = "
* SCRIPT = "
* CERTIFICATE = ' ' "
* HTTP_SERVER = "
* DURATION = '020000' "
* SIGNATURE = 'X' "
* SECURITY = "

IMPORTING
ABSOLUTE_URI = "
EOSTR_SIGNED_DATA_L = "

TABLES
* PATTERN = "
* IT_OSTR_SIGNED_DATA = "

EXCEPTIONS
ERROR_SIGNATURE = 1 ERROR_PARAMETER = 2 UNDEFINED = 3
.



IMPORTING Parameters details for ARCHIVELINK_URL_GENERATE

INPUT -

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

SCRIPT -

Data type: SAPB-SCRIPT
Optional: Yes
Call by Reference: No ( called with pass by value option)

CERTIFICATE -

Data type: TOAOM-AR_STATUS
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

HTTP_SERVER -

Data type: TOAAR-HTTP_SERV
Optional: Yes
Call by Reference: No ( called with pass by value option)

DURATION -

Data type: SY-UZEIT
Default: '020000'
Optional: Yes
Call by Reference: No ( called with pass by value option)

SIGNATURE -

Data type: TOAOM-AR_STATUS
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

SECURITY -

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

EXPORTING Parameters details for ARCHIVELINK_URL_GENERATE

ABSOLUTE_URI -

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

EOSTR_SIGNED_DATA_L -

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

TABLES Parameters details for ARCHIVELINK_URL_GENERATE

PATTERN -

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

IT_OSTR_SIGNED_DATA -

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

EXCEPTIONS details

ERROR_SIGNATURE -

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

ERROR_PARAMETER -

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

UNDEFINED -

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

Copy and paste ABAP code example for ARCHIVELINK_URL_GENERATE 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_input  TYPE HTTP_API, "   
lt_pattern  TYPE STANDARD TABLE OF OAPATTERN, "   
lv_absolute_uri  TYPE SAPB-URI, "   
lv_error_signature  TYPE SAPB, "   
lv_script  TYPE SAPB-SCRIPT, "   
lv_error_parameter  TYPE SAPB, "   
lv_eostr_signed_data_l  TYPE SSFPARMS-SIGDATALEN, "   
lt_it_ostr_signed_data  TYPE STANDARD TABLE OF SSFBIN, "   
lv_undefined  TYPE SSFBIN, "   
lv_certificate  TYPE TOAOM-AR_STATUS, "   SPACE
lv_http_server  TYPE TOAAR-HTTP_SERV, "   
lv_duration  TYPE SY-UZEIT, "   '020000'
lv_signature  TYPE TOAOM-AR_STATUS, "   'X'
lv_security  TYPE TOAOM. "   

  CALL FUNCTION 'ARCHIVELINK_URL_GENERATE'  "
    EXPORTING
         INPUT = lv_input
         SCRIPT = lv_script
         CERTIFICATE = lv_certificate
         HTTP_SERVER = lv_http_server
         DURATION = lv_duration
         SIGNATURE = lv_signature
         SECURITY = lv_security
    IMPORTING
         ABSOLUTE_URI = lv_absolute_uri
         EOSTR_SIGNED_DATA_L = lv_eostr_signed_data_l
    TABLES
         PATTERN = lt_pattern
         IT_OSTR_SIGNED_DATA = lt_it_ostr_signed_data
    EXCEPTIONS
        ERROR_SIGNATURE = 1
        ERROR_PARAMETER = 2
        UNDEFINED = 3
. " ARCHIVELINK_URL_GENERATE




ABAP code using 7.40 inline data declarations to call FM ARCHIVELINK_URL_GENERATE

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 URI FROM SAPB INTO @DATA(ld_absolute_uri).
 
 
"SELECT single SCRIPT FROM SAPB INTO @DATA(ld_script).
 
 
"SELECT single SIGDATALEN FROM SSFPARMS INTO @DATA(ld_eostr_signed_data_l).
 
 
 
"SELECT single AR_STATUS FROM TOAOM INTO @DATA(ld_certificate).
DATA(ld_certificate) = ' '.
 
"SELECT single HTTP_SERV FROM TOAAR INTO @DATA(ld_http_server).
 
"SELECT single UZEIT FROM SY INTO @DATA(ld_duration).
DATA(ld_duration) = '020000'.
 
"SELECT single AR_STATUS FROM TOAOM INTO @DATA(ld_signature).
DATA(ld_signature) = 'X'.
 
 


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!