SAP PT_ALL_CLASSES_SUPPORTING_IF Function Module for









PT_ALL_CLASSES_SUPPORTING_IF is a standard pt all classes supporting if 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 pt all classes supporting if FM, simply by entering the name PT_ALL_CLASSES_SUPPORTING_IF into the relevant SAP transaction such as SE37 or SE38.

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



Function PT_ALL_CLASSES_SUPPORTING_IF 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 'PT_ALL_CLASSES_SUPPORTING_IF'"
EXPORTING
* IM_INTERFACE_NAME = "

IMPORTING
EX_CLASS_NAMES = "

EXCEPTIONS
INTERFACE_NOT_EXISTING = 1 INTERFACE_IS_REALLY_CLASS = 2
.



IMPORTING Parameters details for PT_ALL_CLASSES_SUPPORTING_IF

IM_INTERFACE_NAME -

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

EXPORTING Parameters details for PT_ALL_CLASSES_SUPPORTING_IF

EX_CLASS_NAMES -

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

EXCEPTIONS details

INTERFACE_NOT_EXISTING -

Data type:
Optional: No
Call by Reference: Yes

INTERFACE_IS_REALLY_CLASS -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for PT_ALL_CLASSES_SUPPORTING_IF 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_ex_class_names  TYPE RLB_T_CLIF, "   
lv_im_interface_name  TYPE SEOCLSNAME, "   
lv_interface_not_existing  TYPE SEOCLSNAME, "   
lv_interface_is_really_class  TYPE SEOCLSNAME. "   

  CALL FUNCTION 'PT_ALL_CLASSES_SUPPORTING_IF'  "
    EXPORTING
         IM_INTERFACE_NAME = lv_im_interface_name
    IMPORTING
         EX_CLASS_NAMES = lv_ex_class_names
    EXCEPTIONS
        INTERFACE_NOT_EXISTING = 1
        INTERFACE_IS_REALLY_CLASS = 2
. " PT_ALL_CLASSES_SUPPORTING_IF




ABAP code using 7.40 inline data declarations to call FM PT_ALL_CLASSES_SUPPORTING_IF

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!