SAP RSY_OBJECTS_CICO Function Module for Perform object checkout









RSY_OBJECTS_CICO is a standard rsy objects cico SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Perform object checkout 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 rsy objects cico FM, simply by entering the name RSY_OBJECTS_CICO into the relevant SAP transaction such as SE37 or SE38.

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



Function RSY_OBJECTS_CICO 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 'RSY_OBJECTS_CICO'"Perform object checkout
EXPORTING
* LANGUAGE = SY-LANGU "Language in which object is to be maintained
* MODE = 'SHOW' "Check out read only?
* CICO_REQUEST_NO = ' ' "Number of CICO request
* SUPPRESS_LANGUAGE_CHECK = ' ' "
* AUTHORITY_CHECK = 'X' "
* KEEP_ENQUEUES = ' ' "

IMPORTING
ERROR_OCCURED = "Error occurred, error table filled
PROCESSING_STATUS = "Processing status of a function

TABLES
OBJECTS = "List of objects to be checked out
ERRORS = "Error table: One entry per incorrect object
.



IMPORTING Parameters details for RSY_OBJECTS_CICO

LANGUAGE - Language in which object is to be maintained

Data type: SY-LANGU
Default: SY-LANGU
Optional: Yes
Call by Reference: No ( called with pass by value option)

MODE - Check out read only?

Data type: RPYGSGF-MODE
Default: 'SHOW'
Optional: Yes
Call by Reference: No ( called with pass by value option)

CICO_REQUEST_NO - Number of CICO request

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

SUPPRESS_LANGUAGE_CHECK -

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

AUTHORITY_CHECK -

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

KEEP_ENQUEUES -

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

EXPORTING Parameters details for RSY_OBJECTS_CICO

ERROR_OCCURED - Error occurred, error table filled

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

PROCESSING_STATUS - Processing status of a function

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

TABLES Parameters details for RSY_OBJECTS_CICO

OBJECTS - List of objects to be checked out

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

ERRORS - Error table: One entry per incorrect object

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

Copy and paste ABAP code example for RSY_OBJECTS_CICO 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:
lt_objects  TYPE STANDARD TABLE OF RPYGSCO, "   
lv_language  TYPE SY-LANGU, "   SY-LANGU
lv_error_occured  TYPE RPYGSGF-ERR_EXIST, "   
lv_mode  TYPE RPYGSGF-MODE, "   'SHOW'
lt_errors  TYPE STANDARD TABLE OF RPYGSER, "   
lv_processing_status  TYPE RPYGSGF-PROC_STAT, "   
lv_cico_request_no  TYPE RPYGSGF-CICO_REQNO, "   SPACE
lv_suppress_language_check  TYPE RPYGSGF, "   SPACE
lv_authority_check  TYPE RPYGSGF-FLAG, "   'X'
lv_keep_enqueues  TYPE RPYGSGF-FLAG. "   SPACE

  CALL FUNCTION 'RSY_OBJECTS_CICO'  "Perform object checkout
    EXPORTING
         LANGUAGE = lv_language
         MODE = lv_mode
         CICO_REQUEST_NO = lv_cico_request_no
         SUPPRESS_LANGUAGE_CHECK = lv_suppress_language_check
         AUTHORITY_CHECK = lv_authority_check
         KEEP_ENQUEUES = lv_keep_enqueues
    IMPORTING
         ERROR_OCCURED = lv_error_occured
         PROCESSING_STATUS = lv_processing_status
    TABLES
         OBJECTS = lt_objects
         ERRORS = lt_errors
. " RSY_OBJECTS_CICO




ABAP code using 7.40 inline data declarations to call FM RSY_OBJECTS_CICO

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 LANGU FROM SY INTO @DATA(ld_language).
DATA(ld_language) = SY-LANGU.
 
"SELECT single ERR_EXIST FROM RPYGSGF INTO @DATA(ld_error_occured).
 
"SELECT single MODE FROM RPYGSGF INTO @DATA(ld_mode).
DATA(ld_mode) = 'SHOW'.
 
 
"SELECT single PROC_STAT FROM RPYGSGF INTO @DATA(ld_processing_status).
 
"SELECT single CICO_REQNO FROM RPYGSGF INTO @DATA(ld_cico_request_no).
DATA(ld_cico_request_no) = ' '.
 
DATA(ld_suppress_language_check) = ' '.
 
"SELECT single FLAG FROM RPYGSGF INTO @DATA(ld_authority_check).
DATA(ld_authority_check) = 'X'.
 
"SELECT single FLAG FROM RPYGSGF INTO @DATA(ld_keep_enqueues).
DATA(ld_keep_enqueues) = ' '.
 


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!