SAP EQUIPMENT_RFC_MOVE Function Module for Move Equipment









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

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



Function EQUIPMENT_RFC_MOVE 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_RFC_MOVE'"Move Equipment
EXPORTING
* SOURCE_EQUI = "Equipment Number
* DESTINATION_EQUI = "Superordinate Equipment
* DESTINATION_IFLO = "Functional Location

IMPORTING
NEW_SOURCE_EQUI = "Equipment Number
NEW_DESTINATION_EQUI = "Superordinate Equipment
NEW_DESTINATION_IFLO = "Functional Location
POPUP_OK_CODE = "Function Code That Triggered PAI
OLD_SUPERIOR_EQUIPMENT = "Superordinate Equipment
OLD_SUPERIOR_LOCATION = "Superior functional location
.



IMPORTING Parameters details for EQUIPMENT_RFC_MOVE

SOURCE_EQUI - Equipment Number

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

DESTINATION_EQUI - Superordinate Equipment

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

DESTINATION_IFLO - Functional Location

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

EXPORTING Parameters details for EQUIPMENT_RFC_MOVE

NEW_SOURCE_EQUI - Equipment Number

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

NEW_DESTINATION_EQUI - Superordinate Equipment

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

NEW_DESTINATION_IFLO - Functional Location

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

POPUP_OK_CODE - Function Code That Triggered PAI

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

OLD_SUPERIOR_EQUIPMENT - Superordinate Equipment

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

OLD_SUPERIOR_LOCATION - Superior functional location

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

Copy and paste ABAP code example for EQUIPMENT_RFC_MOVE 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_source_equi  TYPE V_EQUI-EQUNR, "   
lv_new_source_equi  TYPE V_EQUI-EQUNR, "   
lv_destination_equi  TYPE V_EQUI-HEQUI, "   
lv_new_destination_equi  TYPE V_EQUI-HEQUI, "   
lv_destination_iflo  TYPE V_EQUI-TPLNR, "   
lv_new_destination_iflo  TYPE V_EQUI-TPLNR, "   
lv_popup_ok_code  TYPE SY-UCOMM, "   
lv_old_superior_equipment  TYPE V_EQUI-HEQUI, "   
lv_old_superior_location  TYPE IFLO-TPLMA. "   

  CALL FUNCTION 'EQUIPMENT_RFC_MOVE'  "Move Equipment
    EXPORTING
         SOURCE_EQUI = lv_source_equi
         DESTINATION_EQUI = lv_destination_equi
         DESTINATION_IFLO = lv_destination_iflo
    IMPORTING
         NEW_SOURCE_EQUI = lv_new_source_equi
         NEW_DESTINATION_EQUI = lv_new_destination_equi
         NEW_DESTINATION_IFLO = lv_new_destination_iflo
         POPUP_OK_CODE = lv_popup_ok_code
         OLD_SUPERIOR_EQUIPMENT = lv_old_superior_equipment
         OLD_SUPERIOR_LOCATION = lv_old_superior_location
. " EQUIPMENT_RFC_MOVE




ABAP code using 7.40 inline data declarations to call FM EQUIPMENT_RFC_MOVE

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 EQUNR FROM V_EQUI INTO @DATA(ld_source_equi).
 
"SELECT single EQUNR FROM V_EQUI INTO @DATA(ld_new_source_equi).
 
"SELECT single HEQUI FROM V_EQUI INTO @DATA(ld_destination_equi).
 
"SELECT single HEQUI FROM V_EQUI INTO @DATA(ld_new_destination_equi).
 
"SELECT single TPLNR FROM V_EQUI INTO @DATA(ld_destination_iflo).
 
"SELECT single TPLNR FROM V_EQUI INTO @DATA(ld_new_destination_iflo).
 
"SELECT single UCOMM FROM SY INTO @DATA(ld_popup_ok_code).
 
"SELECT single HEQUI FROM V_EQUI INTO @DATA(ld_old_superior_equipment).
 
"SELECT single TPLMA FROM IFLO INTO @DATA(ld_old_superior_location).
 


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!