SAP VBOB_MM_OB_INPUT_CHECK Function Module for NOTRANSL: Ursprungscharge: Eingabedaten prüfen









VBOB_MM_OB_INPUT_CHECK is a standard vbob mm ob input 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 NOTRANSL: Ursprungscharge: Eingabedaten prüfen 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 vbob mm ob input check FM, simply by entering the name VBOB_MM_OB_INPUT_CHECK into the relevant SAP transaction such as SE37 or SE38.

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



Function VBOB_MM_OB_INPUT_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 'VBOB_MM_OB_INPUT_CHECK'"NOTRANSL: Ursprungscharge: Eingabedaten prüfen
EXPORTING
XDARK = "

CHANGING
IMOB01 = "

EXCEPTIONS
ORDER_PURCH_INVALID = 1 OB_FOR_COMBINED_ORDER_EXISTS = 10 ORDER_INVALID = 2 ORDER_POS_INVALID = 3 PURCH_INVALID = 4 PURCH_POS_DELETED = 5 PURCH_POS_NOT_FOUND = 6 ORDERTYPE_INVALID = 7 STATUS_INVALID = 8 COMBINED_ORDERS_INVALID = 9
.



IMPORTING Parameters details for VBOB_MM_OB_INPUT_CHECK

XDARK -

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

CHANGING Parameters details for VBOB_MM_OB_INPUT_CHECK

IMOB01 -

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

EXCEPTIONS details

ORDER_PURCH_INVALID -

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

OB_FOR_COMBINED_ORDER_EXISTS - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

ORDER_INVALID -

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

ORDER_POS_INVALID -

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

PURCH_INVALID -

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

PURCH_POS_DELETED -

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

PURCH_POS_NOT_FOUND -

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

ORDERTYPE_INVALID -

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

STATUS_INVALID -

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

COMBINED_ORDERS_INVALID -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for VBOB_MM_OB_INPUT_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_xdark  TYPE C, "   
lv_imob01  TYPE MOB01, "   
lv_order_purch_invalid  TYPE MOB01, "   
lv_ob_for_combined_order_exists  TYPE MOB01, "   
lv_order_invalid  TYPE MOB01, "   
lv_order_pos_invalid  TYPE MOB01, "   
lv_purch_invalid  TYPE MOB01, "   
lv_purch_pos_deleted  TYPE MOB01, "   
lv_purch_pos_not_found  TYPE MOB01, "   
lv_ordertype_invalid  TYPE MOB01, "   
lv_status_invalid  TYPE MOB01, "   
lv_combined_orders_invalid  TYPE MOB01. "   

  CALL FUNCTION 'VBOB_MM_OB_INPUT_CHECK'  "NOTRANSL: Ursprungscharge: Eingabedaten prüfen
    EXPORTING
         XDARK = lv_xdark
    CHANGING
         IMOB01 = lv_imob01
    EXCEPTIONS
        ORDER_PURCH_INVALID = 1
        OB_FOR_COMBINED_ORDER_EXISTS = 10
        ORDER_INVALID = 2
        ORDER_POS_INVALID = 3
        PURCH_INVALID = 4
        PURCH_POS_DELETED = 5
        PURCH_POS_NOT_FOUND = 6
        ORDERTYPE_INVALID = 7
        STATUS_INVALID = 8
        COMBINED_ORDERS_INVALID = 9
. " VBOB_MM_OB_INPUT_CHECK




ABAP code using 7.40 inline data declarations to call FM VBOB_MM_OB_INPUT_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.

 
 
 
 
 
 
 
 
 
 
 
 


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!