SAP MATNR_GET_ORIG_RANGE Function Module for
MATNR_GET_ORIG_RANGE is a standard matnr get orig range 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 matnr get orig range FM, simply by entering the name MATNR_GET_ORIG_RANGE into the relevant SAP transaction such as SE37 or SE38.
Function Group: MGV_NUMBER_TOOLS
Program Name: SAPLMGV_NUMBER_TOOLS
Main Program: SAPLMGV_NUMBER_TOOLS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MATNR_GET_ORIG_RANGE 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 'MATNR_GET_ORIG_RANGE'".
EXPORTING
SELOPT_NAME = "ABAP/4: Name of SELECT-OPTION / PARAMETER
TABLES
S_RANGE = "Ranges table for external material numbers
EXCEPTIONS
RANGE_NOT_FOUND = 1
IMPORTING Parameters details for MATNR_GET_ORIG_RANGE
SELOPT_NAME - ABAP/4: Name of SELECT-OPTION / PARAMETER
Data type: RSSCR_NAMEOptional: No
Call by Reference: Yes
TABLES Parameters details for MATNR_GET_ORIG_RANGE
S_RANGE - Ranges table for external material numbers
Data type: MGV_MATNR_EXT_RANGEOptional: No
Call by Reference: Yes
EXCEPTIONS details
RANGE_NOT_FOUND -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for MATNR_GET_ORIG_RANGE 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: | ||||
| lt_s_range | TYPE STANDARD TABLE OF MGV_MATNR_EXT_RANGE, " | |||
| lv_selopt_name | TYPE RSSCR_NAME, " | |||
| lv_range_not_found | TYPE RSSCR_NAME. " |
|   CALL FUNCTION 'MATNR_GET_ORIG_RANGE' " |
| EXPORTING | ||
| SELOPT_NAME | = lv_selopt_name | |
| TABLES | ||
| S_RANGE | = lt_s_range | |
| EXCEPTIONS | ||
| RANGE_NOT_FOUND = 1 | ||
| . " MATNR_GET_ORIG_RANGE | ||
ABAP code using 7.40 inline data declarations to call FM MATNR_GET_ORIG_RANGE
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.Search for further information about these or an SAP related objects