SAP KALT_CALL_SCREEN_0100 Function Module for









KALT_CALL_SCREEN_0100 is a standard kalt call screen 0100 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 kalt call screen 0100 FM, simply by entering the name KALT_CALL_SCREEN_0100 into the relevant SAP transaction such as SE37 or SE38.

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



Function KALT_CALL_SCREEN_0100 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 'KALT_CALL_SCREEN_0100'"
EXPORTING
I_TAB = "
I_ALART = "
I_IPKNZ = "
.



IMPORTING Parameters details for KALT_CALL_SCREEN_0100

I_TAB -

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

I_ALART -

Data type: T811C-ALART
Optional: No
Call by Reference: Yes

I_IPKNZ -

Data type: T811C-IPKNZ
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for KALT_CALL_SCREEN_0100 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_i_tab  TYPE T811C-TAB, "   
lv_i_alart  TYPE T811C-ALART, "   
lv_i_ipknz  TYPE T811C-IPKNZ. "   

  CALL FUNCTION 'KALT_CALL_SCREEN_0100'  "
    EXPORTING
         I_TAB = lv_i_tab
         I_ALART = lv_i_alart
         I_IPKNZ = lv_i_ipknz
. " KALT_CALL_SCREEN_0100




ABAP code using 7.40 inline data declarations to call FM KALT_CALL_SCREEN_0100

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 TAB FROM T811C INTO @DATA(ld_i_tab).
 
"SELECT single ALART FROM T811C INTO @DATA(ld_i_alart).
 
"SELECT single IPKNZ FROM T811C INTO @DATA(ld_i_ipknz).
 


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!