SAP G_PP_GL_SET Function Module for









G_PP_GL_SET is a standard g pp gl set 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 g pp gl set FM, simply by entering the name G_PP_GL_SET into the relevant SAP transaction such as SE37 or SE38.

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



Function G_PP_GL_SET 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 'G_PP_GL_SET'"
EXPORTING
BUSINESS_AREA_ON = "
ACTUAL_ON = "
LOCAL_CURR_ONLY = "
* GL_BUKRS = "
* GL_RVERS = "
* GL_LEDGER = "
* GL_RYEAR = "
.



IMPORTING Parameters details for G_PP_GL_SET

BUSINESS_AREA_ON -

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

ACTUAL_ON -

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

LOCAL_CURR_ONLY -

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

GL_BUKRS -

Data type: GLU1-BUKRS
Optional: Yes
Call by Reference: Yes

GL_RVERS -

Data type: GLU1-RVERS
Optional: Yes
Call by Reference: Yes

GL_LEDGER -

Data type: GLU1-RLDNR
Optional: Yes
Call by Reference: Yes

GL_RYEAR -

Data type: GLU1-RYEAR
Optional: Yes
Call by Reference: Yes

Copy and paste ABAP code example for G_PP_GL_SET 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_business_area_on  TYPE CHAR1, "   
lv_actual_on  TYPE CHAR1, "   
lv_local_curr_only  TYPE CHAR1, "   
lv_gl_bukrs  TYPE GLU1-BUKRS, "   
lv_gl_rvers  TYPE GLU1-RVERS, "   
lv_gl_ledger  TYPE GLU1-RLDNR, "   
lv_gl_ryear  TYPE GLU1-RYEAR. "   

  CALL FUNCTION 'G_PP_GL_SET'  "
    EXPORTING
         BUSINESS_AREA_ON = lv_business_area_on
         ACTUAL_ON = lv_actual_on
         LOCAL_CURR_ONLY = lv_local_curr_only
         GL_BUKRS = lv_gl_bukrs
         GL_RVERS = lv_gl_rvers
         GL_LEDGER = lv_gl_ledger
         GL_RYEAR = lv_gl_ryear
. " G_PP_GL_SET




ABAP code using 7.40 inline data declarations to call FM G_PP_GL_SET

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 BUKRS FROM GLU1 INTO @DATA(ld_gl_bukrs).
 
"SELECT single RVERS FROM GLU1 INTO @DATA(ld_gl_rvers).
 
"SELECT single RLDNR FROM GLU1 INTO @DATA(ld_gl_ledger).
 
"SELECT single RYEAR FROM GLU1 INTO @DATA(ld_gl_ryear).
 


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!