SAP GET_TOKEN Function Module for ready a part of a dataset









GET_TOKEN is a standard get token SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for ready a part of a dataset 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 get token FM, simply by entering the name GET_TOKEN into the relevant SAP transaction such as SE37 or SE38.

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



Function GET_TOKEN 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 'GET_TOKEN'"ready a part of a dataset
EXPORTING
P_SIGN = "

CHANGING
P_TOKEN = "
P_INPUT = "
.



IMPORTING Parameters details for GET_TOKEN

P_SIGN -

Data type:
Optional: No
Call by Reference: Yes

CHANGING Parameters details for GET_TOKEN

P_TOKEN -

Data type:
Optional: No
Call by Reference: Yes

P_INPUT -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for GET_TOKEN 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_p_sign  TYPE STRING, "   
lv_p_token  TYPE STRING, "   
lv_p_input  TYPE STRING. "   

  CALL FUNCTION 'GET_TOKEN'  "ready a part of a dataset
    EXPORTING
         P_SIGN = lv_p_sign
    CHANGING
         P_TOKEN = lv_p_token
         P_INPUT = lv_p_input
. " GET_TOKEN




ABAP code using 7.40 inline data declarations to call FM GET_TOKEN

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!