UPSCU_SET_EDITMODE SAP Function module

UPSCU_SET_EDITMODE is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name UPSCU_SET_EDITMODE into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: UPSCU
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM UPSCU_SET_EDITMODE - UPSCU SET EDITMODE

CALL FUNCTION 'UPSCU_SET_EDITMODE' "
  EXPORTING
    im_instid =                 " ups_instid    ALE Distribution Packet: ID for Instantiation
*   im_editmode = KUPS_DISPLAY  " ups_editmode  ALE Distribution Packet: Processing Type
*   flg_msgcollect = KUPS_FALSE  " xfeld        Collect messages
* TABLES
*   ex_messages =               " tupsbapiret2  Table Type of BAPIRET2
  EXCEPTIONS
    DISPLAY_ONLY = 1            "
    NO_AUTHORITY = 2            "               No Authorization
    FOREIGN_LOCK = 3            "               Object already locked
    SYSTEM_FAILED = 4           "               Error in lock management
    FAILING_INSTANCE = 5        "               Object Instance Not Available
    .  "  UPSCU_SET_EDITMODE

ABAP code example for Function Module UPSCU_SET_EDITMODE

The ABAP code below is a full code listing to execute function module UPSCU_SET_EDITMODE including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
it_ex_messages  
 
 TYPE STANDARD TABLE OF TUPSBAPIRET2,"TABLES PARAM
wa_ex_messages
 
 LIKE LINE OF it_ex_messages
.


DATA(ld_im_instid) = 'Check type of data required'.

DATA(ld_im_editmode) = 'Check type of data required'.

DATA(ld_flg_msgcollect) = 'Check type of data required'.
 

"populate fields of struture and append to itab
append wa_ex_messages to it_ex_messages.
.

CALL FUNCTION 'UPSCU_SET_EDITMODE'
  EXPORTING
    im_instid =                  ld_im_instid
*   im_editmode =                ld_im_editmode
*   flg_msgcollect =             ld_flg_msgcollect
* TABLES
*   ex_messages =                it_ex_messages
  EXCEPTIONS
    DISPLAY_ONLY =               1
    NO_AUTHORITY =               2
    FOREIGN_LOCK =               3
    SYSTEM_FAILED =              4
    FAILING_INSTANCE =           5
    .  "  UPSCU_SET_EDITMODE

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 3. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 4. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 5. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_im_instid
 
 TYPE UPS_INSTID ,
it_ex_messages
 
 TYPE STANDARD TABLE OF TUPSBAPIRET2 ,
wa_ex_messages
 
 LIKE LINE OF it_ex_messages,
ld_im_editmode
 
 TYPE UPS_EDITMODE ,
ld_flg_msgcollect
 
 TYPE XFELD .


ld_im_instid = 'Check type of data required'. 

"populate fields of struture and append to itab
append wa_ex_messages to it_ex_messages.
ld_im_editmode = 'Check type of data required'.
ld_flg_msgcollect = 'Check type of data required'.