SAP MPE_GET_BOMUSAGE_TYPE Function Module for Get BOM Usage Type
MPE_GET_BOMUSAGE_TYPE is a standard mpe get bomusage type SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Get BOM Usage Type 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 mpe get bomusage type FM, simply by entering the name MPE_GET_BOMUSAGE_TYPE into the relevant SAP transaction such as SE37 or SE38.
Function Group: MPE_BOMUSG
Program Name: SAPLMPE_BOMUSG
Main Program: SAPLMPE_BOMUSG
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MPE_GET_BOMUSAGE_TYPE 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 'MPE_GET_BOMUSAGE_TYPE'"Get BOM Usage Type.
EXPORTING
IT_BOMUSG = "BOM Usage Text
IMPORTING
ET_BOMUSGTXT = "Table type for BOM Usage
ET_ERROR = "Table Type for BAPIRET2
EXCEPTIONS
INAVLID_BOMUSAGE = 1
IMPORTING Parameters details for MPE_GET_BOMUSAGE_TYPE
IT_BOMUSG - BOM Usage Text
Data type: RPLM_TT_MP_BOMUSAGEOptional: No
Call by Reference: Yes
EXPORTING Parameters details for MPE_GET_BOMUSAGE_TYPE
ET_BOMUSGTXT - Table type for BOM Usage
Data type: MPET_BOMUSGOptional: No
Call by Reference: Yes
ET_ERROR - Table Type for BAPIRET2
Data type: TT_BAPIRET2Optional: No
Call by Reference: Yes
EXCEPTIONS details
INAVLID_BOMUSAGE - Inavlid BOMUsage
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for MPE_GET_BOMUSAGE_TYPE 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_it_bomusg | TYPE RPLM_TT_MP_BOMUSAGE, " | |||
| lv_et_bomusgtxt | TYPE MPET_BOMUSG, " | |||
| lv_inavlid_bomusage | TYPE MPET_BOMUSG, " | |||
| lv_et_error | TYPE TT_BAPIRET2. " |
|   CALL FUNCTION 'MPE_GET_BOMUSAGE_TYPE' "Get BOM Usage Type |
| EXPORTING | ||
| IT_BOMUSG | = lv_it_bomusg | |
| IMPORTING | ||
| ET_BOMUSGTXT | = lv_et_bomusgtxt | |
| ET_ERROR | = lv_et_error | |
| EXCEPTIONS | ||
| INAVLID_BOMUSAGE = 1 | ||
| . " MPE_GET_BOMUSAGE_TYPE | ||
ABAP code using 7.40 inline data declarations to call FM MPE_GET_BOMUSAGE_TYPE
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