SAP CMS_RE_API_RE_MAINTAIN Function Module for Displays real estate from external appl(dailog mode)









CMS_RE_API_RE_MAINTAIN is a standard cms re api re maintain SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Displays real estate from external appl(dailog mode) 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 cms re api re maintain FM, simply by entering the name CMS_RE_API_RE_MAINTAIN into the relevant SAP transaction such as SE37 or SE38.

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



Function CMS_RE_API_RE_MAINTAIN 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 'CMS_RE_API_RE_MAINTAIN'"Displays real estate from external appl(dailog mode)
  EXPORTING
   I_AKTYP =  "Activity type
*  I_OBJID =  "Unique ID for Real Estate objects created in the system
*  I_OBJ_TYP =  "Real Estate Object Type ID
*  I_FLG_INIT = ' ' "Single-character flag
*  I_FLG_SAVE = 'X' "Indicator: Business partner safeguards himself
*  I_FLG_UPDTASK = 'X' "Data element for domain BOOLE: TRUE (='X') and FALSE (=' ')

 IMPORTING
   E_TAB_RC =  "Return Code and corresponding Message
.



IMPORTING Parameters details for CMS_RE_API_RE_MAINTAIN

I_AKTYP - Activity type

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

I_OBJID - Unique ID for Real Estate objects created in the system

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

I_OBJ_TYP - Real Estate Object Type ID

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

I_FLG_INIT - Single-character flag

Data type: BUS000FLDS-CHAR1
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_FLG_SAVE - Indicator: Business partner safeguards himself

Data type: BUS000FLDS-XSAVE
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_FLG_UPDTASK - Data element for domain BOOLE: TRUE (='X') and FALSE (=' ')

Data type: BOOLE-BOOLE
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for CMS_RE_API_RE_MAINTAIN

E_TAB_RC - Return Code and corresponding Message

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

Copy and paste ABAP code example for CMS_RE_API_RE_MAINTAIN 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_i_aktyp  TYPE TBZ0K-AKTYP, "   
lv_e_tab_rc  TYPE CMS_TAB_MSG_COL_MESSAGE, "   
lv_i_objid  TYPE CMS_RE_OBJ-OBJECT_ID, "   
lv_i_obj_typ  TYPE TCMS_RE_TYP-OBJECT_TYPE, "   
lv_i_flg_init  TYPE BUS000FLDS-CHAR1, "   SPACE
lv_i_flg_save  TYPE BUS000FLDS-XSAVE, "   'X'
lv_i_flg_updtask  TYPE BOOLE-BOOLE. "   'X'

  CALL FUNCTION 'CMS_RE_API_RE_MAINTAIN'  "Displays real estate from external appl(dailog mode)
    EXPORTING
         I_AKTYP = lv_i_aktyp
         I_OBJID = lv_i_objid
         I_OBJ_TYP = lv_i_obj_typ
         I_FLG_INIT = lv_i_flg_init
         I_FLG_SAVE = lv_i_flg_save
         I_FLG_UPDTASK = lv_i_flg_updtask
    IMPORTING
         E_TAB_RC = lv_e_tab_rc
. " CMS_RE_API_RE_MAINTAIN




ABAP code using 7.40 inline data declarations to call FM CMS_RE_API_RE_MAINTAIN

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 AKTYP FROM TBZ0K INTO @DATA(ld_i_aktyp).
 
 
"SELECT single OBJECT_ID FROM CMS_RE_OBJ INTO @DATA(ld_i_objid).
 
"SELECT single OBJECT_TYPE FROM TCMS_RE_TYP INTO @DATA(ld_i_obj_typ).
 
"SELECT single CHAR1 FROM BUS000FLDS INTO @DATA(ld_i_flg_init).
DATA(ld_i_flg_init) = ' '.
 
"SELECT single XSAVE FROM BUS000FLDS INTO @DATA(ld_i_flg_save).
DATA(ld_i_flg_save) = 'X'.
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_flg_updtask).
DATA(ld_i_flg_updtask) = 'X'.
 


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!