SAP EQUIPMENT_MODIFY Function Module for NOTRANSL: Ändern eines (vollen) Equipments









EQUIPMENT_MODIFY is a standard equipment modify 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: Ändern eines (vollen) Equipments 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 equipment modify FM, simply by entering the name EQUIPMENT_MODIFY into the relevant SAP transaction such as SE37 or SE38.

Function Group: IBEQ
Program Name: SAPLIBEQ
Main Program: SAPLIBEQ
Appliation area: I
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function EQUIPMENT_MODIFY 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 'EQUIPMENT_MODIFY'"NOTRANSL: Ändern eines (vollen) Equipments
  EXPORTING
*  OLD_VEQUI =  "Previous data of (complete) equipment
*  READ_OLD = 'X' "Indicator for checking previous data
*  LOCK_OLD = 'X' "
*  CONV_NEW = 'X' "Indicator for (ALPHA-, MATN1-)Conversion
*  CHECK_NEW = 'X' "
*  INDIV_NEW = 'X' "
*  UPDATE_NEW = 'X' "
*  DIRECT_NEW = ' ' "
*  COMMIT_NEW = ' ' "

CHANGING
   NEW_VEQUI =  "Updated equipment data

EXCEPTIONS
   ERR_MODIFY = 1
.



IMPORTING Parameters details for EQUIPMENT_MODIFY

OLD_VEQUI - Previous data of (complete) equipment

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

READ_OLD - Indicator for checking previous data

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

LOCK_OLD -

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

CONV_NEW - Indicator for (ALPHA-, MATN1-)Conversion

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

CHECK_NEW -

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

INDIV_NEW -

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

UPDATE_NEW -

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

DIRECT_NEW -

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

COMMIT_NEW -

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

CHANGING Parameters details for EQUIPMENT_MODIFY

NEW_VEQUI - Updated equipment data

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

EXCEPTIONS details

ERR_MODIFY - General errors with Change (see docu)

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

Copy and paste ABAP code example for EQUIPMENT_MODIFY 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_new_vequi  TYPE V_EQUI, "   
lv_old_vequi  TYPE V_EQUI, "   
lv_err_modify  TYPE V_EQUI, "   
lv_read_old  TYPE C, "   'X'
lv_lock_old  TYPE C, "   'X'
lv_conv_new  TYPE C, "   'X'
lv_check_new  TYPE C, "   'X'
lv_indiv_new  TYPE C, "   'X'
lv_update_new  TYPE C, "   'X'
lv_direct_new  TYPE C, "   ' '
lv_commit_new  TYPE C. "   ' '

  CALL FUNCTION 'EQUIPMENT_MODIFY'  "NOTRANSL: Ändern eines (vollen) Equipments
    EXPORTING
         OLD_VEQUI = lv_old_vequi
         READ_OLD = lv_read_old
         LOCK_OLD = lv_lock_old
         CONV_NEW = lv_conv_new
         CHECK_NEW = lv_check_new
         INDIV_NEW = lv_indiv_new
         UPDATE_NEW = lv_update_new
         DIRECT_NEW = lv_direct_new
         COMMIT_NEW = lv_commit_new
    CHANGING
         NEW_VEQUI = lv_new_vequi
    EXCEPTIONS
        ERR_MODIFY = 1
. " EQUIPMENT_MODIFY




ABAP code using 7.40 inline data declarations to call FM EQUIPMENT_MODIFY

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.

 
 
 
DATA(ld_read_old) = 'X'.
 
DATA(ld_lock_old) = 'X'.
 
DATA(ld_conv_new) = 'X'.
 
DATA(ld_check_new) = 'X'.
 
DATA(ld_indiv_new) = 'X'.
 
DATA(ld_update_new) = 'X'.
 
DATA(ld_direct_new) = ' '.
 
DATA(ld_commit_new) = ' '.
 


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!