SAP CSLAR_TKCHANGE Function Module for

Search SAP Function Modules

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

Function Group: SCLA
Program Name: SAPLSCLA
Main Program: SAPLSCLA
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function CSLAR_TKCHANGE 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 'CSLAR_TKCHANGE'"
  EXPORTING
   PCOMM_ROUTING_INFO =  "CSL: Routing Information for Call: Abs.CI, Rel.CI, CPP, CPL
   BNAME =  "SAP System, User Logon Name
*  PUCOMM = 'DELE' "Screens, Function Code Triggered by PAI

TABLES
*  RET_TAB =  "Return Parameters
   PCOMM_CALLED_CPPS =  "CSL: Physical Communication Partner: Key for Token Manager
*  TO_CHANGE_TOKEN =  "CSL: Assignment Token Manager to Token

EXCEPTIONS
   NO_CONNECTION = 1    NO_ALOBJECT = 2    INTERNAL_ERROR = 3 

.

IMPORTING Parameters details for CSLAR_TKCHANGE

PCOMM_ROUTING_INFO - CSL: Routing Information for Call: Abs.CI, Rel.CI, CPP, CPL

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

BNAME - SAP System, User Logon Name

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

PUCOMM - Screens, Function Code Triggered by PAI

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

TABLES Parameters details for CSLAR_TKCHANGE

RET_TAB - Return Parameters

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

PCOMM_CALLED_CPPS - CSL: Physical Communication Partner: Key for Token Manager

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

TO_CHANGE_TOKEN - CSL: Assignment Token Manager to Token

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

EXCEPTIONS details

NO_CONNECTION -

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

NO_ALOBJECT -

Data type:
Optional: No
Call by Reference: Yes

INTERNAL_ERROR -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for CSLAR_TKCHANGE 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.

ABAP code using 7.40 inline data declarations to call FM CSLAR_TKCHANGE

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