SAP ALM_ME_EQUIPMENT_CHANGE Function Module for Change equipment









ALM_ME_EQUIPMENT_CHANGE is a standard alm me equipment change SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Change equipment 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 alm me equipment change FM, simply by entering the name ALM_ME_EQUIPMENT_CHANGE into the relevant SAP transaction such as SE37 or SE38.

Function Group: ALM_ME_TOB_ITEM
Program Name: SAPLALM_ME_TOB_ITEM
Main Program: SAPLALM_ME_TOB_ITEM
Appliation area: I
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function ALM_ME_EQUIPMENT_CHANGE 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 'ALM_ME_EQUIPMENT_CHANGE'"Change equipment
  EXPORTING
*  USER =  "User Name
*  EQUIPMENT_HEADER =  "Header Data for Technical Object

TABLES
   INSTALLATION_CHANGE =  "Installation / Dismantling of Equipment in Technical Object
*  USER_STATUS =  "
*  CLASSIFICATION_VALUES =  "
*  EQUIPMENT_PARTNERS =  "Partner Key
*  EQUIPMENT_ADDDETAILS =  "Additional Attributes in the Header Data of Technical Object
   RETURN =  "Return Parameters
*  X4_EQUIPMENT_GIS =  "
.



IMPORTING Parameters details for ALM_ME_EQUIPMENT_CHANGE

USER - User Name

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

EQUIPMENT_HEADER - Header Data for Technical Object

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

TABLES Parameters details for ALM_ME_EQUIPMENT_CHANGE

INSTALLATION_CHANGE - Installation / Dismantling of Equipment in Technical Object

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

USER_STATUS -

Data type: ALM_ME_USER_STATUS_CHANGES
Optional: Yes
Call by Reference: Yes

CLASSIFICATION_VALUES -

Data type: MAM_30_CLASSVALUES
Optional: Yes
Call by Reference: Yes

EQUIPMENT_PARTNERS - Partner Key

Data type: ALM_ME_PARTNER_KEY_STRUCT
Optional: Yes
Call by Reference: Yes

EQUIPMENT_ADDDETAILS - Additional Attributes in the Header Data of Technical Object

Data type: ALM_ME_ADD_HEADER_DATA
Optional: Yes
Call by Reference: Yes

RETURN - Return Parameters

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

X4_EQUIPMENT_GIS -

Data type: MAM_30_GIS_DATA
Optional: Yes
Call by Reference: Yes

Copy and paste ABAP code example for ALM_ME_EQUIPMENT_CHANGE 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_user  TYPE ALM_ME_USER_DATA-USERID, "   
lt_installation_change  TYPE STANDARD TABLE OF ALM_ME_TOB_INST_UNINST, "   
lt_user_status  TYPE STANDARD TABLE OF ALM_ME_USER_STATUS_CHANGES, "   
lv_equipment_header  TYPE MAM_25_TOB_HEADER, "   
lt_classification_values  TYPE STANDARD TABLE OF MAM_30_CLASSVALUES, "   
lt_equipment_partners  TYPE STANDARD TABLE OF ALM_ME_PARTNER_KEY_STRUCT, "   
lt_equipment_adddetails  TYPE STANDARD TABLE OF ALM_ME_ADD_HEADER_DATA, "   
lt_return  TYPE STANDARD TABLE OF BAPIRET2, "   
lt_x4_equipment_gis  TYPE STANDARD TABLE OF MAM_30_GIS_DATA. "   

  CALL FUNCTION 'ALM_ME_EQUIPMENT_CHANGE'  "Change equipment
    EXPORTING
         USER = lv_user
         EQUIPMENT_HEADER = lv_equipment_header
    TABLES
         INSTALLATION_CHANGE = lt_installation_change
         USER_STATUS = lt_user_status
         CLASSIFICATION_VALUES = lt_classification_values
         EQUIPMENT_PARTNERS = lt_equipment_partners
         EQUIPMENT_ADDDETAILS = lt_equipment_adddetails
         RETURN = lt_return
         X4_EQUIPMENT_GIS = lt_x4_equipment_gis
. " ALM_ME_EQUIPMENT_CHANGE




ABAP code using 7.40 inline data declarations to call FM ALM_ME_EQUIPMENT_CHANGE

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 USERID FROM ALM_ME_USER_DATA INTO @DATA(ld_user).
 
 
 
 
 
 
 
 
 


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!