SAP MB_SELECT_MAT_PHYSINV_PARCHECK Function Module for NOTRANSL: Pruefen Eingabeparameter









MB_SELECT_MAT_PHYSINV_PARCHECK is a standard mb select mat physinv parcheck 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: Pruefen Eingabeparameter 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 mb select mat physinv parcheck FM, simply by entering the name MB_SELECT_MAT_PHYSINV_PARCHECK into the relevant SAP transaction such as SE37 or SE38.

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



Function MB_SELECT_MAT_PHYSINV_PARCHECK 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 'MB_SELECT_MAT_PHYSINV_PARCHECK'"NOTRANSL: Pruefen Eingabeparameter
EXPORTING
IS_MBIF_CONTROL = "Control Structure for Function Module for Simulation MI31

TABLES
T_BAPIRET2 = "Return Parameter(s)
T_PLANT_RA = "BAPI Communication Structure: Range for Plant

EXCEPTIONS
PARAMETER_ERROR = 1 WRONG_FUNCTION = 2
.



IMPORTING Parameters details for MB_SELECT_MAT_PHYSINV_PARCHECK

IS_MBIF_CONTROL - Control Structure for Function Module for Simulation MI31

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

TABLES Parameters details for MB_SELECT_MAT_PHYSINV_PARCHECK

T_BAPIRET2 - Return Parameter(s)

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

T_PLANT_RA - BAPI Communication Structure: Range for Plant

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

EXCEPTIONS details

PARAMETER_ERROR - Parameter Error

Data type:
Optional: No
Call by Reference: Yes

WRONG_FUNCTION -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for MB_SELECT_MAT_PHYSINV_PARCHECK 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:
lt_t_bapiret2  TYPE STANDARD TABLE OF BAPIRET2, "   
lv_is_mbif_control  TYPE MBIF_CONTROL, "   
lv_parameter_error  TYPE MBIF_CONTROL, "   
lt_t_plant_ra  TYPE STANDARD TABLE OF BAPI_PHYSINV_PLANT_RA, "   
lv_wrong_function  TYPE BAPI_PHYSINV_PLANT_RA. "   

  CALL FUNCTION 'MB_SELECT_MAT_PHYSINV_PARCHECK'  "NOTRANSL: Pruefen Eingabeparameter
    EXPORTING
         IS_MBIF_CONTROL = lv_is_mbif_control
    TABLES
         T_BAPIRET2 = lt_t_bapiret2
         T_PLANT_RA = lt_t_plant_ra
    EXCEPTIONS
        PARAMETER_ERROR = 1
        WRONG_FUNCTION = 2
. " MB_SELECT_MAT_PHYSINV_PARCHECK




ABAP code using 7.40 inline data declarations to call FM MB_SELECT_MAT_PHYSINV_PARCHECK

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!