SAP VBOB_MM_OB_GET_UCCHA Function Module for NOTRANSL: Ursprungcharge zu Fertigungsauftrag / Bestellung finden









VBOB_MM_OB_GET_UCCHA is a standard vbob mm ob get 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: Ursprungcharge zu Fertigungsauftrag / Bestellung finden 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 get uccha FM, simply by entering the name VBOB_MM_OB_GET_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_GET_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_GET_UCCHA'"NOTRANSL: Ursprungcharge zu Fertigungsauftrag / Bestellung finden
EXPORTING
* XAUFNR = "
* XPOSNR = "
* XBSTNR = "
* XBSTPO = "
XDARK = "
XTRTYP = "

IMPORTING
XFOUND_FLG = "

CHANGING
XUCMAT = "
XUCCHA = "
XUCWRK = "
* XORCHA = "

TABLES
XPOSDAT = "Order Item
.



IMPORTING Parameters details for VBOB_MM_OB_GET_UCCHA

XAUFNR -

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

XPOSNR -

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

XBSTNR -

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

XBSTPO -

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

XDARK -

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

XTRTYP -

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

EXPORTING Parameters details for VBOB_MM_OB_GET_UCCHA

XFOUND_FLG -

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

CHANGING Parameters details for VBOB_MM_OB_GET_UCCHA

XUCMAT -

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

XUCCHA -

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

XUCWRK -

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

XORCHA -

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

TABLES Parameters details for VBOB_MM_OB_GET_UCCHA

XPOSDAT - Order Item

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

Copy and paste ABAP code example for VBOB_MM_OB_GET_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_xaufnr  TYPE MOB01-AUFNR, "   
lv_xucmat  TYPE MOB01-UCMAT, "   
lt_xposdat  TYPE STANDARD TABLE OF AFPO, "   
lv_xfound_flg  TYPE BOOLEAN, "   
lv_xposnr  TYPE MOB01-POSNR, "   
lv_xuccha  TYPE MOB01-UCCHA, "   
lv_xbstnr  TYPE MOB01-BSTNR, "   
lv_xucwrk  TYPE MOB01-UCWRK, "   
lv_xbstpo  TYPE MOB01-BSTPO, "   
lv_xorcha  TYPE MOB01-ORCHA, "   
lv_xdark  TYPE XFELD, "   
lv_xtrtyp  TYPE MOB01-TRTYP. "   

  CALL FUNCTION 'VBOB_MM_OB_GET_UCCHA'  "NOTRANSL: Ursprungcharge zu Fertigungsauftrag / Bestellung finden
    EXPORTING
         XAUFNR = lv_xaufnr
         XPOSNR = lv_xposnr
         XBSTNR = lv_xbstnr
         XBSTPO = lv_xbstpo
         XDARK = lv_xdark
         XTRTYP = lv_xtrtyp
    IMPORTING
         XFOUND_FLG = lv_xfound_flg
    CHANGING
         XUCMAT = lv_xucmat
         XUCCHA = lv_xuccha
         XUCWRK = lv_xucwrk
         XORCHA = lv_xorcha
    TABLES
         XPOSDAT = lt_xposdat
. " VBOB_MM_OB_GET_UCCHA




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

"SELECT single AUFNR FROM MOB01 INTO @DATA(ld_xaufnr).
 
"SELECT single UCMAT FROM MOB01 INTO @DATA(ld_xucmat).
 
 
 
"SELECT single POSNR FROM MOB01 INTO @DATA(ld_xposnr).
 
"SELECT single UCCHA FROM MOB01 INTO @DATA(ld_xuccha).
 
"SELECT single BSTNR FROM MOB01 INTO @DATA(ld_xbstnr).
 
"SELECT single UCWRK FROM MOB01 INTO @DATA(ld_xucwrk).
 
"SELECT single BSTPO FROM MOB01 INTO @DATA(ld_xbstpo).
 
"SELECT single ORCHA FROM MOB01 INTO @DATA(ld_xorcha).
 
 
"SELECT single TRTYP FROM MOB01 INTO @DATA(ld_xtrtyp).
 


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!