SAP PM_OBJECT_RFC_ACTIVITY Function Module for NOTRANSL: Status für Instandhaltungsobjekt setzen









PM_OBJECT_RFC_ACTIVITY is a standard pm object rfc activity 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: Status für Instandhaltungsobjekt setzen 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 pm object rfc activity FM, simply by entering the name PM_OBJECT_RFC_ACTIVITY 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 PM_OBJECT_RFC_ACTIVITY 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 'PM_OBJECT_RFC_ACTIVITY'"NOTRANSL: Status für Instandhaltungsobjekt setzen
EXPORTING
ST_VRGNG = "Business Transaction
* TPLNR = "Functional Location
* EQUNR = "Equipment Number

IMPORTING
NEW_TPLNR = "Functional Location
NEW_EQUNR = "Equipment
POPUP_OK_CODE = "Function Code That Triggered PAI

TABLES
* LOCATIONS = "Functional Locations
* EQUIPMENTS = "Equipment

EXCEPTIONS
STATUS_NOT_SUPPORTED = 1
.



IMPORTING Parameters details for PM_OBJECT_RFC_ACTIVITY

ST_VRGNG - Business Transaction

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

TPLNR - Functional Location

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

EQUNR - Equipment Number

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

EXPORTING Parameters details for PM_OBJECT_RFC_ACTIVITY

NEW_TPLNR - Functional Location

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

NEW_EQUNR - Equipment

Data type: V_EQUI-EQUNR
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)

TABLES Parameters details for PM_OBJECT_RFC_ACTIVITY

LOCATIONS - Functional Locations

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

EQUIPMENTS - Equipment

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

EXCEPTIONS details

STATUS_NOT_SUPPORTED - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for PM_OBJECT_RFC_ACTIVITY 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_st_vrgng  TYPE TJ01-VRGNG, "   
lt_locations  TYPE STANDARD TABLE OF IFLO_TPLNR, "   
lv_new_tplnr  TYPE IFLOT-TPLNR, "   
lv_status_not_supported  TYPE IFLOT, "   
lv_tplnr  TYPE IFLO-TPLNR, "   
lv_new_equnr  TYPE V_EQUI-EQUNR, "   
lt_equipments  TYPE STANDARD TABLE OF EQUI_EQUNR, "   
lv_equnr  TYPE V_EQUI-EQUNR, "   
lv_popup_ok_code  TYPE SY-UCOMM. "   

  CALL FUNCTION 'PM_OBJECT_RFC_ACTIVITY'  "NOTRANSL: Status für Instandhaltungsobjekt setzen
    EXPORTING
         ST_VRGNG = lv_st_vrgng
         TPLNR = lv_tplnr
         EQUNR = lv_equnr
    IMPORTING
         NEW_TPLNR = lv_new_tplnr
         NEW_EQUNR = lv_new_equnr
         POPUP_OK_CODE = lv_popup_ok_code
    TABLES
         LOCATIONS = lt_locations
         EQUIPMENTS = lt_equipments
    EXCEPTIONS
        STATUS_NOT_SUPPORTED = 1
. " PM_OBJECT_RFC_ACTIVITY




ABAP code using 7.40 inline data declarations to call FM PM_OBJECT_RFC_ACTIVITY

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 VRGNG FROM TJ01 INTO @DATA(ld_st_vrgng).
 
 
"SELECT single TPLNR FROM IFLOT INTO @DATA(ld_new_tplnr).
 
 
"SELECT single TPLNR FROM IFLO INTO @DATA(ld_tplnr).
 
"SELECT single EQUNR FROM V_EQUI INTO @DATA(ld_new_equnr).
 
 
"SELECT single EQUNR FROM V_EQUI INTO @DATA(ld_equnr).
 
"SELECT single UCOMM FROM SY INTO @DATA(ld_popup_ok_code).
 


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!