SAP VBOB_MM_OB_CHECK_UCCHA Function Module for NOTRANSL: Ursprungscharge prüfen









VBOB_MM_OB_CHECK_UCCHA is a standard vbob mm ob check uccha 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 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 check uccha FM, simply by entering the name VBOB_MM_OB_CHECK_UCCHA 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_CHECK_UCCHA 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_CHECK_UCCHA'"NOTRANSL: Ursprungscharge prüfen
EXPORTING
XDARK = "
* I_ENQUEUE_OB_FLG = "DE-EN-LANG-SWITCH-NO-TRANSLATION

CHANGING
XMOB01 = "

EXCEPTIONS
NO_MATERIAL = 1 LOCK_ON_PLANT = 10 LOCK_SYSTEM_ERROR = 11 OB_WITH_DELETION_INDICATOR = 12 ENQUEUE_NOT_POSSIBLE = 13 OB_ALREADY_ASSIGNED_TO_PLANT = 14 NO_PLANT = 2 MATERIAL_NOT_FOUND = 3 PLANT_NOT_FOUND = 4 NO_BATCH_HANDLING = 5 BATCH_EXIST = 6 OB_FOR_REFERENCE_MISSING = 7 ORDER_OB_REFERENCE_EXISTING = 8 PURCH_OB_REFERENCE_EXISTING = 9
.



IMPORTING Parameters details for VBOB_MM_OB_CHECK_UCCHA

XDARK -

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

I_ENQUEUE_OB_FLG - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

CHANGING Parameters details for VBOB_MM_OB_CHECK_UCCHA

XMOB01 -

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

EXCEPTIONS details

NO_MATERIAL -

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

LOCK_ON_PLANT -

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

LOCK_SYSTEM_ERROR -

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

OB_WITH_DELETION_INDICATOR -

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

ENQUEUE_NOT_POSSIBLE -

Data type:
Optional: No
Call by Reference: Yes

OB_ALREADY_ASSIGNED_TO_PLANT - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

NO_PLANT -

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

MATERIAL_NOT_FOUND -

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

PLANT_NOT_FOUND -

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

NO_BATCH_HANDLING -

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

BATCH_EXIST -

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

OB_FOR_REFERENCE_MISSING -

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

ORDER_OB_REFERENCE_EXISTING -

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

PURCH_OB_REFERENCE_EXISTING -

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

Copy and paste ABAP code example for VBOB_MM_OB_CHECK_UCCHA 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_xmob01  TYPE MOB01, "   
lv_no_material  TYPE MOB01, "   
lv_lock_on_plant  TYPE MOB01, "   
lv_lock_system_error  TYPE MOB01, "   
lv_ob_with_deletion_indicator  TYPE MOB01, "   
lv_enqueue_not_possible  TYPE MOB01, "   
lv_ob_already_assigned_to_plant  TYPE MOB01, "   
lv_no_plant  TYPE MOB01, "   
lv_i_enqueue_ob_flg  TYPE C, "   
lv_material_not_found  TYPE C, "   
lv_plant_not_found  TYPE C, "   
lv_no_batch_handling  TYPE C, "   
lv_batch_exist  TYPE C, "   
lv_ob_for_reference_missing  TYPE C, "   
lv_order_ob_reference_existing  TYPE C, "   
lv_purch_ob_reference_existing  TYPE C. "   

  CALL FUNCTION 'VBOB_MM_OB_CHECK_UCCHA'  "NOTRANSL: Ursprungscharge prüfen
    EXPORTING
         XDARK = lv_xdark
         I_ENQUEUE_OB_FLG = lv_i_enqueue_ob_flg
    CHANGING
         XMOB01 = lv_xmob01
    EXCEPTIONS
        NO_MATERIAL = 1
        LOCK_ON_PLANT = 10
        LOCK_SYSTEM_ERROR = 11
        OB_WITH_DELETION_INDICATOR = 12
        ENQUEUE_NOT_POSSIBLE = 13
        OB_ALREADY_ASSIGNED_TO_PLANT = 14
        NO_PLANT = 2
        MATERIAL_NOT_FOUND = 3
        PLANT_NOT_FOUND = 4
        NO_BATCH_HANDLING = 5
        BATCH_EXIST = 6
        OB_FOR_REFERENCE_MISSING = 7
        ORDER_OB_REFERENCE_EXISTING = 8
        PURCH_OB_REFERENCE_EXISTING = 9
. " VBOB_MM_OB_CHECK_UCCHA




ABAP code using 7.40 inline data declarations to call FM VBOB_MM_OB_CHECK_UCCHA

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!