VBWS_UOM_UPDATE_ALL SAP Function module

VBWS_UOM_UPDATE_ALL is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name VBWS_UOM_UPDATE_ALL into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: MWSD
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM VBWS_UOM_UPDATE_ALL - VBWS UOM UPDATE ALL

CALL FUNCTION 'VBWS_UOM_UPDATE_ALL' "
* EXPORTING
*   i_user = SY-UNAME           " sy-uname
*   i_tcode = SY-TCODE          " sy-tcode
*   i_class_value_update = SPACE  " am07m-xselk
*   i_material_update = SPACE   " am07m-xselk
*   i_type_of_block = 'E'       " tvgvi-spera
*   i_no_update_task = SPACE    " am07m-xselk
* TABLES
*   e_message =                 " matmess
  EXCEPTIONS
    UPDATE_ERROR = 1            "
    .  "  VBWS_UOM_UPDATE_ALL

ABAP code example for Function Module VBWS_UOM_UPDATE_ALL

The ABAP code below is a full code listing to execute function module VBWS_UOM_UPDATE_ALL including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
it_e_message  
 
 TYPE STANDARD TABLE OF MATMESS,"TABLES PARAM
wa_e_message
 
 LIKE LINE OF it_e_message
.


DATA(ld_i_user) = 'some text here'.

DATA(ld_i_tcode) = 'some text here'.


DATA(ld_i_class_value_update) = some text here


DATA(ld_i_material_update) = some text here
 

SELECT single SPERA 
  FROM TVGVI 
  INTO @DATA(ld_i_type_of_block).



DATA(ld_i_no_update_task) = some text here
 

"populate fields of struture and append to itab
append wa_e_message to it_e_message.
.

CALL FUNCTION 'VBWS_UOM_UPDATE_ALL'
* EXPORTING
*   i_user =                     ld_i_user
*   i_tcode =                    ld_i_tcode
*   i_class_value_update =       ld_i_class_value_update
*   i_material_update =          ld_i_material_update
*   i_type_of_block =            ld_i_type_of_block
*   i_no_update_task =           ld_i_no_update_task
* TABLES
*   e_message =                  it_e_message
  EXCEPTIONS
    UPDATE_ERROR =               1
    .  "  VBWS_UOM_UPDATE_ALL

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_i_user
 
 TYPE SY-UNAME ,
it_e_message
 
 TYPE STANDARD TABLE OF MATMESS ,
wa_e_message
 
 LIKE LINE OF it_e_message,
ld_i_tcode
 
 TYPE SY-TCODE ,
ld_i_class_value_update
 
 TYPE AM07M-XSELK ,
ld_i_material_update
 
 TYPE AM07M-XSELK ,
ld_i_type_of_block
 
 TYPE TVGVI-SPERA ,
ld_i_no_update_task
 
 TYPE AM07M-XSELK .


ld_i_user = 'some text here'. 

"populate fields of struture and append to itab
append wa_e_message to it_e_message.
ld_i_tcode = 'some text here'.

ld_i_class_value_update = some text here

ld_i_material_update = some text here

SELECT single SPERA 
  FROM TVGVI 
  INTO ld_i_type_of_block.


ld_i_no_update_task = some text here