SAP VBOB_MM_OB_ORDER_CHECK Function Module for NOTRANSL: Auftrag für Ursprungscharge prüfen

Search SAP Function Modules

VBOB_MM_OB_ORDER_CHECK is a standard vbob mm ob order 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: Auftrag für Ursprungscharge 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 order check FM, simply by entering the name VBOB_MM_OB_ORDER_CHECK into the relevant SAP transaction such as SE37 or SE38.

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

Function VBOB_MM_OB_ORDER_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_ORDER_CHECK'"NOTRANSL: Auftrag für Ursprungscharge prüfen
  EXPORTING
   AUFNR =  "
   XDARK =  "
   TRTYP =  "

 IMPORTING
   ECAUFV =  "Generated Table for View CAUFV
   ESTATS =  "Status Profile

EXCEPTIONS
   ORDER_INVALID = 1    STATUS_INVALID = 2    ORDERTYPE_INVALID = 3    COMBINED_ORDERS_INVALID = 4    OB_FOR_COMBINED_ORDER_EXISTS = 5 

.

IMPORTING Parameters details for VBOB_MM_OB_ORDER_CHECK

AUFNR -

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

XDARK -

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

TRTYP -

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

EXPORTING Parameters details for VBOB_MM_OB_ORDER_CHECK

ECAUFV - Generated Table for View CAUFV

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

ESTATS - Status Profile

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

EXCEPTIONS details

ORDER_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)

ORDERTYPE_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

OB_FOR_COMBINED_ORDER_EXISTS -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for VBOB_MM_OB_ORDER_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.

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