SAP MALG_EXISTENCE_CHECK Function Module for Check if Table MALG Exists
MALG_EXISTENCE_CHECK is a standard malg existence check SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Check if Table MALG Exists 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 malg existence check FM, simply by entering the name MALG_EXISTENCE_CHECK into the relevant SAP transaction such as SE37 or SE38.
Function Group: MG51
Program Name: SAPLMG51
Main Program: SAPLMG51
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MALG_EXISTENCE_CHECK 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 'MALG_EXISTENCE_CHECK'"Check if Table MALG Exists.
EXPORTING
PI_LAYGR = "Layout Module
* PI_LMVER = "Layout Module Version
* PI_LMVAR = "Variant for Layout Module Version
EXCEPTIONS
NOT_FOUND = 1
IMPORTING Parameters details for MALG_EXISTENCE_CHECK
PI_LAYGR - Layout Module
Data type: MALG-LAYGROptional: No
Call by Reference: Yes
PI_LMVER - Layout Module Version
Data type: MALG-LMVEROptional: Yes
Call by Reference: Yes
PI_LMVAR - Variant for Layout Module Version
Data type: MALG-LMVAROptional: Yes
Call by Reference: Yes
EXCEPTIONS details
NOT_FOUND - Entry not found
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for MALG_EXISTENCE_CHECK 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_pi_laygr | TYPE MALG-LAYGR, " | |||
| lv_not_found | TYPE MALG, " | |||
| lv_pi_lmver | TYPE MALG-LMVER, " | |||
| lv_pi_lmvar | TYPE MALG-LMVAR. " |
|   CALL FUNCTION 'MALG_EXISTENCE_CHECK' "Check if Table MALG Exists |
| EXPORTING | ||
| PI_LAYGR | = lv_pi_laygr | |
| PI_LMVER | = lv_pi_lmver | |
| PI_LMVAR | = lv_pi_lmvar | |
| EXCEPTIONS | ||
| NOT_FOUND = 1 | ||
| . " MALG_EXISTENCE_CHECK | ||
ABAP code using 7.40 inline data declarations to call FM MALG_EXISTENCE_CHECK
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 LAYGR FROM MALG INTO @DATA(ld_pi_laygr). | ||||
| "SELECT single LMVER FROM MALG INTO @DATA(ld_pi_lmver). | ||||
| "SELECT single LMVAR FROM MALG INTO @DATA(ld_pi_lmvar). | ||||
Search for further information about these or an SAP related objects