SAP MATGRP_START Function Module for NOTRANSL: Artikelhierarchie-Aufruf
MATGRP_START is a standard matgrp start 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: Artikelhierarchie-Aufruf 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 matgrp start FM, simply by entering the name MATGRP_START into the relevant SAP transaction such as SE37 or SE38.
Function Group: MATGRP
Program Name: SAPLMATGRP
Main Program: SAPLMATGRP
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MATGRP_START 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 'MATGRP_START'"NOTRANSL: Artikelhierarchie-Aufruf.
EXPORTING
HIERARCHIE = "Hierarchy ID
* CATEGORY = "Hierarchy Node
* STATUS = "Article Hierarchy Status
IMPORTING Parameters details for MATGRP_START
HIERARCHIE - Hierarchy ID
Data type: MATGRP_HIER-HIER_IDOptional: No
Call by Reference: Yes
CATEGORY - Hierarchy Node
Data type: MATGRP_STRUC-NODEOptional: Yes
Call by Reference: Yes
STATUS - Article Hierarchy Status
Data type: MATGRP_HIER-STATUSOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for MATGRP_START 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 MATGRP_HIER-HIER_ID, " | |||
| lv_category | TYPE MATGRP_STRUC-NODE, " | |||
| lv_status | TYPE MATGRP_HIER-STATUS. " |
|   CALL FUNCTION 'MATGRP_START' "NOTRANSL: Artikelhierarchie-Aufruf |
| EXPORTING | ||
| HIERARCHIE | = lv_hierarchie | |
| CATEGORY | = lv_category | |
| STATUS | = lv_status | |
| . " MATGRP_START | ||
ABAP code using 7.40 inline data declarations to call FM MATGRP_START
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 MATGRP_HIER INTO @DATA(ld_hierarchie). | ||||
| "SELECT single NODE FROM MATGRP_STRUC INTO @DATA(ld_category). | ||||
| "SELECT single STATUS FROM MATGRP_HIER INTO @DATA(ld_status). | ||||
Search for further information about these or an SAP related objects