SAP KEO_GENERATING_REQUEST Function Module for









KEO_GENERATING_REQUEST is a standard keo generating request 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 keo generating request FM, simply by entering the name KEO_GENERATING_REQUEST into the relevant SAP transaction such as SE37 or SE38.

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



Function KEO_GENERATING_REQUEST 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 'KEO_GENERATING_REQUEST'"
EXPORTING
* MODE = '1' "
* RUN_DIRECT = ' ' "
CO_AREA = "Controlling Area
* APPLICATION = '1' "
* KEYDATE = SY-DATLO "Key Date
* ALT_HIERARCHY = "
* OVERWRITE = 'X' "
* SUFFIX = "
* BATCHFLAG = 'X' "Execute in the Background
* TESTRUN = 'X' "

IMPORTING
ACTION_BREAK_OFF = "

EXCEPTIONS
INPUT_ERROR = 1 ERROR_ENCRYPT_SETID = 2 GROUP_NOT_EXIST = 3 EO_NOT_ACTIVE = 4 ERROR_COMPLETENESS_INTERVAL = 5 BATCH_ERROR = 6
.



IMPORTING Parameters details for KEO_GENERATING_REQUEST

MODE -

Data type: KEO_GENTYPE
Default: '1'
Optional: Yes
Call by Reference: Yes

RUN_DIRECT -

Data type: FLAG
Default: SPACE
Optional: Yes
Call by Reference: Yes

CO_AREA - Controlling Area

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

APPLICATION -

Data type: KEO_APPLICATION
Default: '1'
Optional: Yes
Call by Reference: Yes

KEYDATE - Key Date

Data type: KEO_KEYDATE
Default: SY-DATLO
Optional: Yes
Call by Reference: Yes

ALT_HIERARCHY -

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

OVERWRITE -

Data type: FLAG
Default: 'X'
Optional: Yes
Call by Reference: Yes

SUFFIX -

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

BATCHFLAG - Execute in the Background

Data type: BATCHFLG
Default: 'X'
Optional: Yes
Call by Reference: Yes

TESTRUN -

Data type: TESTLAUF
Default: 'X'
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for KEO_GENERATING_REQUEST

ACTION_BREAK_OFF -

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

EXCEPTIONS details

INPUT_ERROR -

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

ERROR_ENCRYPT_SETID -

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

GROUP_NOT_EXIST - Group does not exist

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

EO_NOT_ACTIVE -

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

ERROR_COMPLETENESS_INTERVAL -

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

BATCH_ERROR -

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

Copy and paste ABAP code example for KEO_GENERATING_REQUEST 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_mode  TYPE KEO_GENTYPE, "   '1'
lv_input_error  TYPE KEO_GENTYPE, "   
lv_action_break_off  TYPE FLAG, "   
lv_run_direct  TYPE FLAG, "   SPACE
lv_co_area  TYPE KOKRS, "   
lv_error_encrypt_setid  TYPE KOKRS, "   
lv_application  TYPE KEO_APPLICATION, "   '1'
lv_group_not_exist  TYPE KEO_APPLICATION, "   
lv_keydate  TYPE KEO_KEYDATE, "   SY-DATLO
lv_eo_not_active  TYPE KEO_KEYDATE, "   
lv_alt_hierarchy  TYPE GRPNAME, "   
lv_error_completeness_interval  TYPE GRPNAME, "   
lv_overwrite  TYPE FLAG, "   'X'
lv_batch_error  TYPE FLAG, "   
lv_suffix  TYPE GRPSUFFIX, "   
lv_batchflag  TYPE BATCHFLG, "   'X'
lv_testrun  TYPE TESTLAUF. "   'X'

  CALL FUNCTION 'KEO_GENERATING_REQUEST'  "
    EXPORTING
         MODE = lv_mode
         RUN_DIRECT = lv_run_direct
         CO_AREA = lv_co_area
         APPLICATION = lv_application
         KEYDATE = lv_keydate
         ALT_HIERARCHY = lv_alt_hierarchy
         OVERWRITE = lv_overwrite
         SUFFIX = lv_suffix
         BATCHFLAG = lv_batchflag
         TESTRUN = lv_testrun
    IMPORTING
         ACTION_BREAK_OFF = lv_action_break_off
    EXCEPTIONS
        INPUT_ERROR = 1
        ERROR_ENCRYPT_SETID = 2
        GROUP_NOT_EXIST = 3
        EO_NOT_ACTIVE = 4
        ERROR_COMPLETENESS_INTERVAL = 5
        BATCH_ERROR = 6
. " KEO_GENERATING_REQUEST




ABAP code using 7.40 inline data declarations to call FM KEO_GENERATING_REQUEST

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.

DATA(ld_mode) = '1'.
 
 
 
DATA(ld_run_direct) = ' '.
 
 
 
DATA(ld_application) = '1'.
 
 
DATA(ld_keydate) = SY-DATLO.
 
 
 
 
DATA(ld_overwrite) = 'X'.
 
 
 
DATA(ld_batchflag) = 'X'.
 
DATA(ld_testrun) = 'X'.
 


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!