SAP CALENDAR_VISUAL_INFORMATION Function Module for
CALENDAR_VISUAL_INFORMATION is a standard calendar visual information 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 calendar visual information FM, simply by entering the name CALENDAR_VISUAL_INFORMATION into the relevant SAP transaction such as SE37 or SE38.
Function Group: SCA2
Program Name: SAPLSCA2
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CALENDAR_VISUAL_INFORMATION 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 'CALENDAR_VISUAL_INFORMATION'".
IMPORTING
ACTUAL_DATE = "Current Date
CALENDAR_INFORMATION = "
TABLES
* DAY_ATTRIBUTES = "
EXPORTING Parameters details for CALENDAR_VISUAL_INFORMATION
ACTUAL_DATE - Current Date
Data type: SCA2-DATUMOptional: No
Call by Reference: No ( called with pass by value option)
CALENDAR_INFORMATION -
Data type: ICAL_INFOOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for CALENDAR_VISUAL_INFORMATION
DAY_ATTRIBUTES -
Data type: CASDAYATTROptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CALENDAR_VISUAL_INFORMATION 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_actual_date | TYPE SCA2-DATUM, " | |||
| lt_day_attributes | TYPE STANDARD TABLE OF CASDAYATTR, " | |||
| lv_calendar_information | TYPE ICAL_INFO. " |
|   CALL FUNCTION 'CALENDAR_VISUAL_INFORMATION' " |
| IMPORTING | ||
| ACTUAL_DATE | = lv_actual_date | |
| CALENDAR_INFORMATION | = lv_calendar_information | |
| TABLES | ||
| DAY_ATTRIBUTES | = lt_day_attributes | |
| . " CALENDAR_VISUAL_INFORMATION | ||
ABAP code using 7.40 inline data declarations to call FM CALENDAR_VISUAL_INFORMATION
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 DATUM FROM SCA2 INTO @DATA(ld_actual_date). | ||||
Search for further information about these or an SAP related objects