SAP OIB_MM_GET_MSEG_KEY Function Module for Gets the values of keys for MSEG table
OIB_MM_GET_MSEG_KEY is a standard oib mm get mseg key SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Gets the values of keys for MSEG table 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 oib mm get mseg key FM, simply by entering the name OIB_MM_GET_MSEG_KEY into the relevant SAP transaction such as SE37 or SE38.
Function Group: OIB_MM
Program Name: SAPLOIB_MM
Main Program: SAPLOIB_MM
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function OIB_MM_GET_MSEG_KEY 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 'OIB_MM_GET_MSEG_KEY'"Gets the values of keys for MSEG table.
IMPORTING
E_MBLNR = "Number of Material Document
E_MJAHR = "Material Document Year
E_ZEILE = "Item in Material Document
EXPORTING Parameters details for OIB_MM_GET_MSEG_KEY
E_MBLNR - Number of Material Document
Data type: EKBE-BELNROptional: No
Call by Reference: Yes
E_MJAHR - Material Document Year
Data type: EKBE-GJAHROptional: No
Call by Reference: Yes
E_ZEILE - Item in Material Document
Data type: EKBE-BUZEIOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for OIB_MM_GET_MSEG_KEY 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_e_mblnr | TYPE EKBE-BELNR, " | |||
| lv_e_mjahr | TYPE EKBE-GJAHR, " | |||
| lv_e_zeile | TYPE EKBE-BUZEI. " |
|   CALL FUNCTION 'OIB_MM_GET_MSEG_KEY' "Gets the values of keys for MSEG table |
| IMPORTING | ||
| E_MBLNR | = lv_e_mblnr | |
| E_MJAHR | = lv_e_mjahr | |
| E_ZEILE | = lv_e_zeile | |
| . " OIB_MM_GET_MSEG_KEY | ||
ABAP code using 7.40 inline data declarations to call FM OIB_MM_GET_MSEG_KEY
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 BELNR FROM EKBE INTO @DATA(ld_e_mblnr). | ||||
| "SELECT single GJAHR FROM EKBE INTO @DATA(ld_e_mjahr). | ||||
| "SELECT single BUZEI FROM EKBE INTO @DATA(ld_e_zeile). | ||||
Search for further information about these or an SAP related objects