SAP MDG_BS_MAT_CHECK_KEY_EXIST_IN Function Module for BTE : ALE Inbound MATMAS, IDoc Data (for ALE Distribution Unit)









MDG_BS_MAT_CHECK_KEY_EXIST_IN is a standard mdg bs mat check key exist in SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for BTE : ALE Inbound MATMAS, IDoc Data (for ALE Distribution Unit) 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 mdg bs mat check key exist in FM, simply by entering the name MDG_BS_MAT_CHECK_KEY_EXIST_IN into the relevant SAP transaction such as SE37 or SE38.

Function Group: MDG_BS_MAT_CHECK_KEY_EXIST
Program Name: SAPLMDG_BS_MAT_CHECK_KEY_EXIST
Main Program: SAPLMDG_BS_MAT_CHECK_KEY_EXIST
Appliation area: I
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function MDG_BS_MAT_CHECK_KEY_EXIST_IN 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 'MDG_BS_MAT_CHECK_KEY_EXIST_IN'"BTE : ALE Inbound MATMAS, IDoc Data (for ALE Distribution Unit)
EXPORTING
IDOC_HEADER = "Control Record (IDoc)
FLG_APPEND_STATUS = "Checkbox

TABLES
IDOC_DATA = "Data Record (IDoc)
IDOC_STATUS = "Status Record (IDoc)

EXCEPTIONS
ERROR = 1
.



IMPORTING Parameters details for MDG_BS_MAT_CHECK_KEY_EXIST_IN

IDOC_HEADER - Control Record (IDoc)

Data type: EDIDC
Optional: No
Call by Reference: Yes

FLG_APPEND_STATUS - Checkbox

Data type: XFELD
Optional: No
Call by Reference: Yes

TABLES Parameters details for MDG_BS_MAT_CHECK_KEY_EXIST_IN

IDOC_DATA - Data Record (IDoc)

Data type: EDIDD
Optional: No
Call by Reference: No ( called with pass by value option)

IDOC_STATUS - Status Record (IDoc)

Data type: BDIDOCSTAT
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

ERROR - Processing Error

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for MDG_BS_MAT_CHECK_KEY_EXIST_IN 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_error  TYPE STRING, "   
lt_idoc_data  TYPE STANDARD TABLE OF EDIDD, "   
lv_idoc_header  TYPE EDIDC, "   
lt_idoc_status  TYPE STANDARD TABLE OF BDIDOCSTAT, "   
lv_flg_append_status  TYPE XFELD. "   

  CALL FUNCTION 'MDG_BS_MAT_CHECK_KEY_EXIST_IN'  "BTE : ALE Inbound MATMAS, IDoc Data (for ALE Distribution Unit)
    EXPORTING
         IDOC_HEADER = lv_idoc_header
         FLG_APPEND_STATUS = lv_flg_append_status
    TABLES
         IDOC_DATA = lt_idoc_data
         IDOC_STATUS = lt_idoc_status
    EXCEPTIONS
        ERROR = 1
. " MDG_BS_MAT_CHECK_KEY_EXIST_IN




ABAP code using 7.40 inline data declarations to call FM MDG_BS_MAT_CHECK_KEY_EXIST_IN

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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!