SAP CSLAR_ALREAD Function Module for









CSLAR_ALREAD is a standard cslar alread 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 alread FM, simply by entering the name CSLAR_ALREAD 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_ALREAD 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_ALREAD'"
  EXPORTING
   PCOMM_ROUTING_INFO =  "CSL: Routing Information for Call: Abs.CI, Rel.CI, CPP, CPL
*  DATE_FROM = '00000000' "Application log: date
*  DATE_TO = SY-DATUM "Application log: date
*  TIME_FROM = '000000' "Application log: time
*  TIME_TO = SY-UZEIT "Application log: time
*  USER_ID = '*' "Application log: user name
*  EXTNUMBER = ' ' "Application Log: External ID

TABLES
   PCOMM_CALLED_CPPS =  "CSL: Physical Communication Partner: Key for Token Manager
   AL_HEADER =  "Application log: log header
   AL_MESSAGE =  "Application log: log message

EXCEPTIONS
   NO_CONNECTION = 1    NO_ENTRY = 2
.



IMPORTING Parameters details for CSLAR_ALREAD

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)

DATE_FROM - Application log: date

Data type: BALHDR-ALDATE
Default: '00000000'
Optional: Yes
Call by Reference: No ( called with pass by value option)

DATE_TO - Application log: date

Data type: BALHDR-ALDATE
Default: SY-DATUM
Optional: Yes
Call by Reference: No ( called with pass by value option)

TIME_FROM - Application log: time

Data type: BALHDR-ALTIME
Default: '000000'
Optional: Yes
Call by Reference: No ( called with pass by value option)

TIME_TO - Application log: time

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

USER_ID - Application log: user name

Data type: BALHDR-ALUSER
Default: '*'
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXTNUMBER - Application Log: External ID

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

TABLES Parameters details for CSLAR_ALREAD

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)

AL_HEADER - Application log: log header

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

AL_MESSAGE - Application log: log message

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

EXCEPTIONS details

NO_CONNECTION -

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

NO_ENTRY -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for CSLAR_ALREAD 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_no_connection  TYPE STRING, "   
lt_pcomm_called_cpps  TYPE STANDARD TABLE OF CSL_CPPKY, "   
lv_pcomm_routing_info  TYPE CSL_CRI, "   
lv_no_entry  TYPE CSL_CRI, "   
lt_al_header  TYPE STANDARD TABLE OF BALHDR, "   
lv_date_from  TYPE BALHDR-ALDATE, "   '00000000'
lv_date_to  TYPE BALHDR-ALDATE, "   SY-DATUM
lt_al_message  TYPE STANDARD TABLE OF BALM, "   
lv_time_from  TYPE BALHDR-ALTIME, "   '000000'
lv_time_to  TYPE BALHDR-ALTIME, "   SY-UZEIT
lv_user_id  TYPE BALHDR-ALUSER, "   '*'
lv_extnumber  TYPE BALHDR-EXTNUMBER. "   SPACE

  CALL FUNCTION 'CSLAR_ALREAD'  "
    EXPORTING
         PCOMM_ROUTING_INFO = lv_pcomm_routing_info
         DATE_FROM = lv_date_from
         DATE_TO = lv_date_to
         TIME_FROM = lv_time_from
         TIME_TO = lv_time_to
         USER_ID = lv_user_id
         EXTNUMBER = lv_extnumber
    TABLES
         PCOMM_CALLED_CPPS = lt_pcomm_called_cpps
         AL_HEADER = lt_al_header
         AL_MESSAGE = lt_al_message
    EXCEPTIONS
        NO_CONNECTION = 1
        NO_ENTRY = 2
. " CSLAR_ALREAD




ABAP code using 7.40 inline data declarations to call FM CSLAR_ALREAD

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 ALDATE FROM BALHDR INTO @DATA(ld_date_from).
DATA(ld_date_from) = '00000000'.
 
"SELECT single ALDATE FROM BALHDR INTO @DATA(ld_date_to).
DATA(ld_date_to) = SY-DATUM.
 
 
"SELECT single ALTIME FROM BALHDR INTO @DATA(ld_time_from).
DATA(ld_time_from) = '000000'.
 
"SELECT single ALTIME FROM BALHDR INTO @DATA(ld_time_to).
DATA(ld_time_to) = SY-UZEIT.
 
"SELECT single ALUSER FROM BALHDR INTO @DATA(ld_user_id).
DATA(ld_user_id) = '*'.
 
"SELECT single EXTNUMBER FROM BALHDR INTO @DATA(ld_extnumber).
DATA(ld_extnumber) = ' '.
 


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!