SAP APPT_RULE_TEXT_GET Function Module for









APPT_RULE_TEXT_GET is a standard appt rule text get 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 appt rule text get FM, simply by entering the name APPT_RULE_TEXT_GET into the relevant SAP transaction such as SE37 or SE38.

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



Function APPT_RULE_TEXT_GET 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 'APPT_RULE_TEXT_GET'"
EXPORTING
* LANGUAGE = "SAP R/3 System, Current Language
* RULE = "Rule table
* RULE_ID = "

TABLES
TEXT = "

EXCEPTIONS
INVALID_RULE = 1 RULE_NOT_EXIST = 2
.



IMPORTING Parameters details for APPT_RULE_TEXT_GET

LANGUAGE - SAP R/3 System, Current Language

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

RULE - Rule table

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

RULE_ID -

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

TABLES Parameters details for APPT_RULE_TEXT_GET

TEXT -

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

EXCEPTIONS details

INVALID_RULE - Inconsistent Rule

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

RULE_NOT_EXIST - Incorrect Rule ID

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

Copy and paste ABAP code example for APPT_RULE_TEXT_GET 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:
lt_text  TYPE STANDARD TABLE OF SOLI, "   
lv_language  TYPE SYLANGU, "   
lv_invalid_rule  TYPE SYLANGU, "   
lv_rule  TYPE RULE_TAB, "   
lv_rule_not_exist  TYPE RULE_TAB, "   
lv_rule_id  TYPE SC_RULEID. "   

  CALL FUNCTION 'APPT_RULE_TEXT_GET'  "
    EXPORTING
         LANGUAGE = lv_language
         RULE = lv_rule
         RULE_ID = lv_rule_id
    TABLES
         TEXT = lt_text
    EXCEPTIONS
        INVALID_RULE = 1
        RULE_NOT_EXIST = 2
. " APPT_RULE_TEXT_GET




ABAP code using 7.40 inline data declarations to call FM APPT_RULE_TEXT_GET

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!