SAP K_ALLOCATIONS_MRULE_SUBSCREEN Function Module for









K_ALLOCATIONS_MRULE_SUBSCREEN is a standard k allocations mrule subscreen 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 k allocations mrule subscreen FM, simply by entering the name K_ALLOCATIONS_MRULE_SUBSCREEN into the relevant SAP transaction such as SE37 or SE38.

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



Function K_ALLOCATIONS_MRULE_SUBSCREEN 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 'K_ALLOCATIONS_MRULE_SUBSCREEN'"
EXPORTING
EVENT = "
ALLOCATION = "
ACTION_TYPE = "

IMPORTING
SUBSCREEN_MODULPOOL = "
SUBSCREEN_NUMBER = "Number of Subscreen
DATA_CHANGED = "

CHANGING
MRULE_STRUCT = "
.



IMPORTING Parameters details for K_ALLOCATIONS_MRULE_SUBSCREEN

EVENT -

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

ALLOCATION -

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

ACTION_TYPE -

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

EXPORTING Parameters details for K_ALLOCATIONS_MRULE_SUBSCREEN

SUBSCREEN_MODULPOOL -

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

SUBSCREEN_NUMBER - Number of Subscreen

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

DATA_CHANGED -

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

CHANGING Parameters details for K_ALLOCATIONS_MRULE_SUBSCREEN

MRULE_STRUCT -

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

Copy and paste ABAP code example for K_ALLOCATIONS_MRULE_SUBSCREEN 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_event  TYPE TRWPR-EVENT, "   
lv_mrule_struct  TYPE KALC_MRULE_STRUCTURE, "   
lv_subscreen_modulpool  TYPE SY-REPID, "   
lv_allocation  TYPE KALC_SUBSCREEN_INPUT, "   
lv_subscreen_number  TYPE SY-DYNNR, "   
lv_action_type  TYPE TACT-ACTVT, "   
lv_data_changed  TYPE SY-INPUT. "   

  CALL FUNCTION 'K_ALLOCATIONS_MRULE_SUBSCREEN'  "
    EXPORTING
         EVENT = lv_event
         ALLOCATION = lv_allocation
         ACTION_TYPE = lv_action_type
    IMPORTING
         SUBSCREEN_MODULPOOL = lv_subscreen_modulpool
         SUBSCREEN_NUMBER = lv_subscreen_number
         DATA_CHANGED = lv_data_changed
    CHANGING
         MRULE_STRUCT = lv_mrule_struct
. " K_ALLOCATIONS_MRULE_SUBSCREEN




ABAP code using 7.40 inline data declarations to call FM K_ALLOCATIONS_MRULE_SUBSCREEN

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 EVENT FROM TRWPR INTO @DATA(ld_event).
 
 
"SELECT single REPID FROM SY INTO @DATA(ld_subscreen_modulpool).
 
 
"SELECT single DYNNR FROM SY INTO @DATA(ld_subscreen_number).
 
"SELECT single ACTVT FROM TACT INTO @DATA(ld_action_type).
 
"SELECT single INPUT FROM SY INTO @DATA(ld_data_changed).
 


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!