SAP IBAPI_EQUI_USERSTATUS_CHANGE Function Module for PM BAPI: Change User Status of an Equipment









IBAPI_EQUI_USERSTATUS_CHANGE is a standard ibapi equi userstatus 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 PM BAPI: Change User Status of an 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 ibapi equi userstatus change FM, simply by entering the name IBAPI_EQUI_USERSTATUS_CHANGE into the relevant SAP transaction such as SE37 or SE38.

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



Function IBAPI_EQUI_USERSTATUS_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 'IBAPI_EQUI_USERSTATUS_CHANGE'"PM BAPI: Change User Status of an Equipment
EXPORTING
EQUIPMENT = "Number of Equipment to be Installed
STATUS_PARAMETERS = "User Status Parameters

IMPORTING
USERSTATUS = "User Status Line
RETURN = "Return Parameter
.



IMPORTING Parameters details for IBAPI_EQUI_USERSTATUS_CHANGE

EQUIPMENT - Number of Equipment to be Installed

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

STATUS_PARAMETERS - User Status Parameters

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

EXPORTING Parameters details for IBAPI_EQUI_USERSTATUS_CHANGE

USERSTATUS - User Status Line

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

RETURN - Return Parameter

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

Copy and paste ABAP code example for IBAPI_EQUI_USERSTATUS_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_equipment  TYPE BAPI_ITOB_PARMS-EQUIPMENT, "   
lv_userstatus  TYPE ASTTX, "   
lv_return  TYPE BAPIRET2, "   
lv_status_parameters  TYPE BAPI_ITOB_USERSTATUS_MAINTAIN. "   

  CALL FUNCTION 'IBAPI_EQUI_USERSTATUS_CHANGE'  "PM BAPI: Change User Status of an Equipment
    EXPORTING
         EQUIPMENT = lv_equipment
         STATUS_PARAMETERS = lv_status_parameters
    IMPORTING
         USERSTATUS = lv_userstatus
         RETURN = lv_return
. " IBAPI_EQUI_USERSTATUS_CHANGE




ABAP code using 7.40 inline data declarations to call FM IBAPI_EQUI_USERSTATUS_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 EQUIPMENT FROM BAPI_ITOB_PARMS INTO @DATA(ld_equipment).
 
 
 
 


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!