SAP ASH_QMEL_OBJTYPE_GET Function Module for NOTRANSL: Bestimmung Objekttyp zur Meldung
ASH_QMEL_OBJTYPE_GET is a standard ash qmel objtype get 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: Bestimmung Objekttyp zur Meldung 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 ash qmel objtype get FM, simply by entering the name ASH_QMEL_OBJTYPE_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: ASH5
Program Name: SAPLASH5
Main Program: SAPLASH5
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ASH_QMEL_OBJTYPE_GET 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 'ASH_QMEL_OBJTYPE_GET'"NOTRANSL: Bestimmung Objekttyp zur Meldung.
EXPORTING
IP_QMNUM = "Declaration Number
IMPORTING
EP_OBJTYPE = "Object Type
EXCEPTIONS
NO_OBJTYPE_DETERMINED = 1
IMPORTING Parameters details for ASH_QMEL_OBJTYPE_GET
IP_QMNUM - Declaration Number
Data type: QMNUMOptional: No
Call by Reference: Yes
EXPORTING Parameters details for ASH_QMEL_OBJTYPE_GET
EP_OBJTYPE - Object Type
Data type: BORIDENT-OBJTYPEOptional: No
Call by Reference: Yes
EXCEPTIONS details
NO_OBJTYPE_DETERMINED -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for ASH_QMEL_OBJTYPE_GET 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_ip_qmnum | TYPE QMNUM, " | |||
| lv_ep_objtype | TYPE BORIDENT-OBJTYPE, " | |||
| lv_no_objtype_determined | TYPE BORIDENT. " |
|   CALL FUNCTION 'ASH_QMEL_OBJTYPE_GET' "NOTRANSL: Bestimmung Objekttyp zur Meldung |
| EXPORTING | ||
| IP_QMNUM | = lv_ip_qmnum | |
| IMPORTING | ||
| EP_OBJTYPE | = lv_ep_objtype | |
| EXCEPTIONS | ||
| NO_OBJTYPE_DETERMINED = 1 | ||
| . " ASH_QMEL_OBJTYPE_GET | ||
ABAP code using 7.40 inline data declarations to call FM ASH_QMEL_OBJTYPE_GET
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 OBJTYPE FROM BORIDENT INTO @DATA(ld_ep_objtype). | ||||
Search for further information about these or an SAP related objects