SAP FRML192_EXPL_SCOPE_GET Function Module for NOTRANSL: RMS-FRM: Auflösungsbereiche









FRML192_EXPL_SCOPE_GET is a standard frml192 expl scope get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: RMS-FRM: Auflösungsbereiche processing and below is the pattern details for this FM, 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 frml192 expl scope get FM, simply by entering the name FRML192_EXPL_SCOPE_GET into the relevant SAP transaction such as SE37 or SE38.

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



Function FRML192_EXPL_SCOPE_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 'FRML192_EXPL_SCOPE_GET'"NOTRANSL: RMS-FRM: Auflösungsbereiche
IMPORTING
ET_EXPL_SCOPE = "DE-EN-LANG-SWITCH-NO-TRANSLATION

EXCEPTIONS
BUFFER_ERROR = 1
.



EXPORTING Parameters details for FRML192_EXPL_SCOPE_GET

ET_EXPL_SCOPE - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

EXCEPTIONS details

BUFFER_ERROR - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for FRML192_EXPL_SCOPE_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:
lv_buffer_error  TYPE STRING, "   
lv_et_expl_scope  TYPE FRMLTY_MOD_EXPL_SCOPE. "   

  CALL FUNCTION 'FRML192_EXPL_SCOPE_GET'  "NOTRANSL: RMS-FRM: Auflösungsbereiche
    IMPORTING
         ET_EXPL_SCOPE = lv_et_expl_scope
    EXCEPTIONS
        BUFFER_ERROR = 1
. " FRML192_EXPL_SCOPE_GET




ABAP code using 7.40 inline data declarations to call FM FRML192_EXPL_SCOPE_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!