SAP RTMATGRP_CALL_200 Function Module for Call Screen 100
RTMATGRP_CALL_200 is a standard rtmatgrp call 200 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Call Screen 100 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 rtmatgrp call 200 FM, simply by entering the name RTMATGRP_CALL_200 into the relevant SAP transaction such as SE37 or SE38.
Function Group: RTMATGRP
Program Name: SAPLRTMATGRP
Main Program: SAPLRTMATGRP
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RTMATGRP_CALL_200 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 'RTMATGRP_CALL_200'"Call Screen 100.
EXPORTING
HIERARCHIE = "Hierarchy ID
* MATGRP_HIER = "Article Hierarchy Properties
* HIER_DATA_TTY = "Table Type for Article-Hierarchy Table (Name)
* VKORG = "Sales Organization
* VTWEG = "Distribution Channel
* BWFLG = "BW Flag
* MULTIFLAG = " Mehrfachzuordnung Flag
* DATEFLAG = "Scheduling Flag
* HIERFLAG = "Spalten Nummer
* MATGRP_HIER_WA = "Hierarchy Structure
* MATGRP_HIERT_TA = "Table Type for Article-Hierarchy Table (Name)
* HIERY_DATE = "Validity of Assignment in Article Hierarchy
* DB_HIER_DATA = "Checkbox
* CATEGORY = "Hierarchy Node
* CATEGORY_DATE_FROM = "Validity Start Date of Assignment in Article Hierarchy
* SEL_NODE = "Hierarchy Node
* SEL_NODE_IN = "
* SELECT_ART = "Material Number
* AUTH_V_NODE = "Checkbox
* STATUS = "Article Hierarchy Status
IMPORTING Parameters details for RTMATGRP_CALL_200
HIERARCHIE - Hierarchy ID
Data type: WRF_MATGRP_HIER-HIER_IDOptional: No
Call by Reference: Yes
MATGRP_HIER - Article Hierarchy Properties
Data type: WRF_MATGRP_HIEROptional: Yes
Call by Reference: Yes
HIER_DATA_TTY - Table Type for Article-Hierarchy Table (Name)
Data type: WRF_HIERT_TTYOptional: Yes
Call by Reference: Yes
VKORG - Sales Organization
Data type: RMMW1-VKORGOptional: Yes
Call by Reference: Yes
VTWEG - Distribution Channel
Data type: RMMW1-VTWEGOptional: Yes
Call by Reference: Yes
BWFLG - BW Flag
Data type: WRF_MATGRP_HIER-BWFLGOptional: Yes
Call by Reference: Yes
MULTIFLAG - Mehrfachzuordnung Flag
Data type: WRF_MATGRP_HIER-MLTPFLGOptional: Yes
Call by Reference: Yes
DATEFLAG - Scheduling Flag
Data type: WRF_MATGRP_HIER-DATEFLGOptional: Yes
Call by Reference: Yes
HIERFLAG - Spalten Nummer
Data type: WRF_MATGRP_HIER-HIERFLGOptional: Yes
Call by Reference: Yes
MATGRP_HIER_WA - Hierarchy Structure
Data type: WRF_HIER_STYOptional: Yes
Call by Reference: Yes
MATGRP_HIERT_TA - Table Type for Article-Hierarchy Table (Name)
Data type: WRF_HIERT_TTYOptional: Yes
Call by Reference: Yes
HIERY_DATE - Validity of Assignment in Article Hierarchy
Data type: WRF_DATEOptional: Yes
Call by Reference: Yes
DB_HIER_DATA - Checkbox
Data type: XFELDOptional: Yes
Call by Reference: Yes
CATEGORY - Hierarchy Node
Data type: WRF_MATGRP_STRUC-NODEOptional: Yes
Call by Reference: Yes
CATEGORY_DATE_FROM - Validity Start Date of Assignment in Article Hierarchy
Data type: WRF_DATE_FROMOptional: Yes
Call by Reference: Yes
SEL_NODE - Hierarchy Node
Data type: WRF_MATGRP_STRUC-NODEOptional: Yes
Call by Reference: Yes
SEL_NODE_IN -
Data type: COptional: Yes
Call by Reference: Yes
SELECT_ART - Material Number
Data type: WRF_MATGRP_SKUOptional: Yes
Call by Reference: Yes
AUTH_V_NODE - Checkbox
Data type: XFELDOptional: Yes
Call by Reference: Yes
STATUS - Article Hierarchy Status
Data type: WRF_CATSTATEOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for RTMATGRP_CALL_200 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_hierarchie | TYPE WRF_MATGRP_HIER-HIER_ID, " | |||
| lv_matgrp_hier | TYPE WRF_MATGRP_HIER, " | |||
| lv_hier_data_tty | TYPE WRF_HIERT_TTY, " | |||
| lv_vkorg | TYPE RMMW1-VKORG, " | |||
| lv_vtweg | TYPE RMMW1-VTWEG, " | |||
| lv_bwflg | TYPE WRF_MATGRP_HIER-BWFLG, " | |||
| lv_multiflag | TYPE WRF_MATGRP_HIER-MLTPFLG, " | |||
| lv_dateflag | TYPE WRF_MATGRP_HIER-DATEFLG, " | |||
| lv_hierflag | TYPE WRF_MATGRP_HIER-HIERFLG, " | |||
| lv_matgrp_hier_wa | TYPE WRF_HIER_STY, " | |||
| lv_matgrp_hiert_ta | TYPE WRF_HIERT_TTY, " | |||
| lv_hiery_date | TYPE WRF_DATE, " | |||
| lv_db_hier_data | TYPE XFELD, " | |||
| lv_category | TYPE WRF_MATGRP_STRUC-NODE, " | |||
| lv_category_date_from | TYPE WRF_DATE_FROM, " | |||
| lv_sel_node | TYPE WRF_MATGRP_STRUC-NODE, " | |||
| lv_sel_node_in | TYPE C, " | |||
| lv_select_art | TYPE WRF_MATGRP_SKU, " | |||
| lv_auth_v_node | TYPE XFELD, " | |||
| lv_status | TYPE WRF_CATSTATE. " |
|   CALL FUNCTION 'RTMATGRP_CALL_200' "Call Screen 100 |
| EXPORTING | ||
| HIERARCHIE | = lv_hierarchie | |
| MATGRP_HIER | = lv_matgrp_hier | |
| HIER_DATA_TTY | = lv_hier_data_tty | |
| VKORG | = lv_vkorg | |
| VTWEG | = lv_vtweg | |
| BWFLG | = lv_bwflg | |
| MULTIFLAG | = lv_multiflag | |
| DATEFLAG | = lv_dateflag | |
| HIERFLAG | = lv_hierflag | |
| MATGRP_HIER_WA | = lv_matgrp_hier_wa | |
| MATGRP_HIERT_TA | = lv_matgrp_hiert_ta | |
| HIERY_DATE | = lv_hiery_date | |
| DB_HIER_DATA | = lv_db_hier_data | |
| CATEGORY | = lv_category | |
| CATEGORY_DATE_FROM | = lv_category_date_from | |
| SEL_NODE | = lv_sel_node | |
| SEL_NODE_IN | = lv_sel_node_in | |
| SELECT_ART | = lv_select_art | |
| AUTH_V_NODE | = lv_auth_v_node | |
| STATUS | = lv_status | |
| . " RTMATGRP_CALL_200 | ||
ABAP code using 7.40 inline data declarations to call FM RTMATGRP_CALL_200
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 HIER_ID FROM WRF_MATGRP_HIER INTO @DATA(ld_hierarchie). | ||||
| "SELECT single VKORG FROM RMMW1 INTO @DATA(ld_vkorg). | ||||
| "SELECT single VTWEG FROM RMMW1 INTO @DATA(ld_vtweg). | ||||
| "SELECT single BWFLG FROM WRF_MATGRP_HIER INTO @DATA(ld_bwflg). | ||||
| "SELECT single MLTPFLG FROM WRF_MATGRP_HIER INTO @DATA(ld_multiflag). | ||||
| "SELECT single DATEFLG FROM WRF_MATGRP_HIER INTO @DATA(ld_dateflag). | ||||
| "SELECT single HIERFLG FROM WRF_MATGRP_HIER INTO @DATA(ld_hierflag). | ||||
| "SELECT single NODE FROM WRF_MATGRP_STRUC INTO @DATA(ld_category). | ||||
| "SELECT single NODE FROM WRF_MATGRP_STRUC INTO @DATA(ld_sel_node). | ||||
Search for further information about these or an SAP related objects