SAP CRS_PROXY_BAPI_EQUI_CHANGE2_OS Function Module for NOTRANSL: BAPI: Ändern Equipment









CRS_PROXY_BAPI_EQUI_CHANGE2_OS is a standard crs proxy bapi equi change2 os 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: BAPI: Ändern 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 crs proxy bapi equi change2 os FM, simply by entering the name CRS_PROXY_BAPI_EQUI_CHANGE2_OS into the relevant SAP transaction such as SE37 or SE38.

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



Function CRS_PROXY_BAPI_EQUI_CHANGE2_OS 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 'CRS_PROXY_BAPI_EQUI_CHANGE2_OS'"NOTRANSL: BAPI: Ändern Equipment
  EXPORTING
   IV_EQUIPMENT =  "Number of equipment to be changed
*  IV_VALID_DATE = SY-DATUM "Date on which installation location of equipment was changed
*  IV_VALID_TIME = SY-UZEIT "Time at which installation location of equipment was changed
*  IV_CURRENT_STATE =  "Generic Type
   IS_BAPI_EQUI =  "Equipment Master Data
   IS_BAPI_EQUIX =  "Transfer Structure for Equipment Master Data
   IS_BAPI_EQUZ =  "Equipment Time Segment
   IS_BAPI_EQUZX =  "Transfer Structure for Equipment Usage Period
   IS_BAPI_ILOA =  "BAPI Structure for ILOA Data of an Equipment to be Created

 IMPORTING
   EV_ABORT =  "Generic Type

TABLES
*  IT_BAPI_EQST =  "Equipment to BOM Link
*  IT_BAPISMJSTO =  "BAPI Structure Table Jsto Mobile Service
*  IT_BAPICUCFGV_EQ =  "Configuration Header data - Equipment/Serial number
*  IT_BAPICUINSV_EQ =  "Configuration instances - Equipment/Serial number
*  IT_BAPICUVALV_EQ =  "Configuration Values - Equipment/Serial number
*  ET_BAPIRET2 =  "Return Parameter
*  IT_BAPIADSMTP =  "BAPI Structure for E-Mail Addresses (Bus. Address Services)
*  IT_BAPI_EQKT =  "Equipment Short Texts
*  IT_BAPI_IHPA =  "Plant Maintenance: Partners
*  IT_BAPISTXTXH =  "BAPI CRS Structure for STXH (SAPscript Text)
*  IT_BAPISTXTXL =  "BAPI Structure for STX_LINES Structure
*  IT_BAPICUSADR =  "BAPI Structure: Customer Address
*  IT_BAPICUSTEL =  "BAPI Structure: Telephone (Business Address Services)
*  IT_BAPICUSFAX =  "BAPI Structure: Fax Numbers (Business Address Services)
*  IT_BAPISMJEST =  "BAPI Structure for Table Jest Mobile Service
.



IMPORTING Parameters details for CRS_PROXY_BAPI_EQUI_CHANGE2_OS

IV_EQUIPMENT - Number of equipment to be changed

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

IV_VALID_DATE - Date on which installation location of equipment was changed

Data type: BAPI_ITOB_PARMS-INST_DATE
Default: SY-DATUM
Optional: Yes
Call by Reference: Yes

IV_VALID_TIME - Time at which installation location of equipment was changed

Data type: BAPI_ITOB_PARMS-INST_TIME
Default: SY-UZEIT
Optional: Yes
Call by Reference: Yes

IV_CURRENT_STATE - Generic Type

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

IS_BAPI_EQUI - Equipment Master Data

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

IS_BAPI_EQUIX - Transfer Structure for Equipment Master Data

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

IS_BAPI_EQUZ - Equipment Time Segment

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

IS_BAPI_EQUZX - Transfer Structure for Equipment Usage Period

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

IS_BAPI_ILOA - BAPI Structure for ILOA Data of an Equipment to be Created

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

EXPORTING Parameters details for CRS_PROXY_BAPI_EQUI_CHANGE2_OS

EV_ABORT - Generic Type

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

TABLES Parameters details for CRS_PROXY_BAPI_EQUI_CHANGE2_OS

IT_BAPI_EQST - Equipment to BOM Link

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

IT_BAPISMJSTO - BAPI Structure Table Jsto Mobile Service

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

IT_BAPICUCFGV_EQ - Configuration Header data - Equipment/Serial number

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

IT_BAPICUINSV_EQ - Configuration instances - Equipment/Serial number

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

IT_BAPICUVALV_EQ - Configuration Values - Equipment/Serial number

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

ET_BAPIRET2 - Return Parameter

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

IT_BAPIADSMTP - BAPI Structure for E-Mail Addresses (Bus. Address Services)

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

IT_BAPI_EQKT - Equipment Short Texts

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

IT_BAPI_IHPA - Plant Maintenance: Partners

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

IT_BAPISTXTXH - BAPI CRS Structure for STXH (SAPscript Text)

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

IT_BAPISTXTXL - BAPI Structure for STX_LINES Structure

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

IT_BAPICUSADR - BAPI Structure: Customer Address

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

IT_BAPICUSTEL - BAPI Structure: Telephone (Business Address Services)

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

IT_BAPICUSFAX - BAPI Structure: Fax Numbers (Business Address Services)

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

IT_BAPISMJEST - BAPI Structure for Table Jest Mobile Service

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

Copy and paste ABAP code example for CRS_PROXY_BAPI_EQUI_CHANGE2_OS 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_ev_abort  TYPE C, "   
lt_it_bapi_eqst  TYPE STANDARD TABLE OF BAPI_EQST1, "   
lv_iv_equipment  TYPE BAPI_ITOB_PARMS-EQUIPMENT, "   
lt_it_bapismjsto  TYPE STANDARD TABLE OF BAPISMJSTO, "   
lt_it_bapicucfgv_eq  TYPE STANDARD TABLE OF BAPICUCFGV_EQ, "   
lt_it_bapicuinsv_eq  TYPE STANDARD TABLE OF BAPICUINSV_EQ, "   
lt_it_bapicuvalv_eq  TYPE STANDARD TABLE OF BAPICUVALV_EQ, "   
lt_et_bapiret2  TYPE STANDARD TABLE OF BAPIRET2, "   
lt_it_bapiadsmtp  TYPE STANDARD TABLE OF BAPIADSMTP, "   
lt_it_bapi_eqkt  TYPE STANDARD TABLE OF BAPI_EQKT1, "   
lv_iv_valid_date  TYPE BAPI_ITOB_PARMS-INST_DATE, "   SY-DATUM
lt_it_bapi_ihpa  TYPE STANDARD TABLE OF BAPI_IHPA, "   
lv_iv_valid_time  TYPE BAPI_ITOB_PARMS-INST_TIME, "   SY-UZEIT
lt_it_bapistxtxh  TYPE STANDARD TABLE OF BAPISTXTXH, "   
lv_iv_current_state  TYPE C, "   
lv_is_bapi_equi  TYPE BAPI_EQUI1, "   
lt_it_bapistxtxl  TYPE STANDARD TABLE OF BAPISTXTXL, "   
lv_is_bapi_equix  TYPE BAPI_EQUIX_R3_OS, "   
lt_it_bapicusadr  TYPE STANDARD TABLE OF BAPICUSADR, "   
lv_is_bapi_equz  TYPE BAPI_EQUZ1, "   
lt_it_bapicustel  TYPE STANDARD TABLE OF BAPICUSTEL, "   
lv_is_bapi_equzx  TYPE BAPI_EQUZX_R3_OS, "   
lt_it_bapicusfax  TYPE STANDARD TABLE OF BAPICUSFAX, "   
lv_is_bapi_iloa  TYPE BAPI_ILOA1, "   
lt_it_bapismjest  TYPE STANDARD TABLE OF BAPISMJEST. "   

  CALL FUNCTION 'CRS_PROXY_BAPI_EQUI_CHANGE2_OS'  "NOTRANSL: BAPI: Ändern Equipment
    EXPORTING
         IV_EQUIPMENT = lv_iv_equipment
         IV_VALID_DATE = lv_iv_valid_date
         IV_VALID_TIME = lv_iv_valid_time
         IV_CURRENT_STATE = lv_iv_current_state
         IS_BAPI_EQUI = lv_is_bapi_equi
         IS_BAPI_EQUIX = lv_is_bapi_equix
         IS_BAPI_EQUZ = lv_is_bapi_equz
         IS_BAPI_EQUZX = lv_is_bapi_equzx
         IS_BAPI_ILOA = lv_is_bapi_iloa
    IMPORTING
         EV_ABORT = lv_ev_abort
    TABLES
         IT_BAPI_EQST = lt_it_bapi_eqst
         IT_BAPISMJSTO = lt_it_bapismjsto
         IT_BAPICUCFGV_EQ = lt_it_bapicucfgv_eq
         IT_BAPICUINSV_EQ = lt_it_bapicuinsv_eq
         IT_BAPICUVALV_EQ = lt_it_bapicuvalt_eq
         ET_BAPIRET2 = lt_et_bapiret2
         IT_BAPIADSMTP = lt_it_bapiadsmtp
         IT_BAPI_EQKT = lt_it_bapi_eqkt
         IT_BAPI_IHPA = lt_it_bapi_ihpa
         IT_BAPISTXTXH = lt_it_bapistxtxh
         IT_BAPISTXTXL = lt_it_bapistxtxl
         IT_BAPICUSADR = lt_it_bapicusadr
         IT_BAPICUSTEL = lt_it_bapicustel
         IT_BAPICUSFAX = lt_it_bapicusfax
         IT_BAPISMJEST = lt_it_bapismjest
. " CRS_PROXY_BAPI_EQUI_CHANGE2_OS




ABAP code using 7.40 inline data declarations to call FM CRS_PROXY_BAPI_EQUI_CHANGE2_OS

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_iv_equipment).
 
 
 
 
 
 
 
 
"SELECT single INST_DATE FROM BAPI_ITOB_PARMS INTO @DATA(ld_iv_valid_date).
DATA(ld_iv_valid_date) = SY-DATUM.
 
 
"SELECT single INST_TIME FROM BAPI_ITOB_PARMS INTO @DATA(ld_iv_valid_time).
DATA(ld_iv_valid_time) = SY-UZEIT.
 
 
 
 
 
 
 
 
 
 
 
 
 


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!