OBJECT_CHECK_CRVS_B SAP Function module - PRT master: read short text and block object

OBJECT_CHECK_CRVS_B 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 OBJECT_CHECK_CRVS_B into the relevant SAP transaction such as SE37 or SE80.

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

Pattern for FM OBJECT_CHECK_CRVS_B - OBJECT CHECK CRVS B

CALL FUNCTION 'OBJECT_CHECK_CRVS_B' "PRT master: read short text and block object
* EXPORTING
*   called_from = 1             "               1=of document 2=of class
*   language = SY-LANGU         " sy-langu      Reading language for short texts
*   lock = SPACE                "               Block object
*   single = SPACE              "               Individual access via CL20/CL21
*   date_of_change =            " rmclf-datuv1
*   i_auth_chk = SPACE          " rmclf-kreuz
  IMPORTING
    fault_text =                "               Text for error message
    message_type =              "               Message type E,W,I or S
    no_auth =                   "               No authorization for object
    meins =                     " mara-meins
  TABLES
    otab =                      " rmclobtx      List of the PRT
  EXCEPTIONS
    FOREIGN_LOCK = 1            "               Data record blocked by other user
    OBJECT_NOT_FOUND = 2        "               PRT master is not available
    SYSTEM_FAILURE = 3          "               System error when blocking
    .  "  OBJECT_CHECK_CRVS_B

ABAP code example for Function Module OBJECT_CHECK_CRVS_B

The ABAP code below is a full code listing to execute function module OBJECT_CHECK_CRVS_B 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:
ld_fault_text  
 
 TYPE STRING
,
ld_message_type  
 
 TYPE STRING
,
ld_no_auth  
 
 TYPE STRING
,
ld_meins  
 
 TYPE MARA-MEINS
,
it_otab  
 
 TYPE STANDARD TABLE OF RMCLOBTX,"TABLES PARAM
wa_otab
 
 LIKE LINE OF it_otab
.


DATA(ld_called_from) = 'some text here'.

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

DATA(ld_lock) = 'some text here'.

DATA(ld_single) = 'some text here'.


DATA(ld_date_of_change) = 20210129


DATA(ld_i_auth_chk) = some text here
 

"populate fields of struture and append to itab
append wa_otab to it_otab.
.

CALL FUNCTION 'OBJECT_CHECK_CRVS_B'
* EXPORTING
*   called_from =                ld_called_from
*   language =                   ld_language
*   lock =                       ld_lock
*   single =                     ld_single
*   date_of_change =             ld_date_of_change
*   i_auth_chk =                 ld_i_auth_chk
  IMPORTING
    fault_text =                 ld_fault_text
    message_type =               ld_message_type
    no_auth =                    ld_no_auth
    meins =                      ld_meins
  TABLES
    otab =                       it_otab
  EXCEPTIONS
    FOREIGN_LOCK =               1
    OBJECT_NOT_FOUND =           2
    SYSTEM_FAILURE =             3
    .  "  OBJECT_CHECK_CRVS_B

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
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_fault_text
 
 TYPE STRING ,
ld_called_from
 
 TYPE STRING ,
it_otab
 
 TYPE STANDARD TABLE OF RMCLOBTX ,
wa_otab
 
 LIKE LINE OF it_otab,
ld_message_type
 
 TYPE STRING ,
ld_language
 
 TYPE SY-LANGU ,
ld_no_auth
 
 TYPE STRING ,
ld_lock
 
 TYPE STRING ,
ld_meins
 
 TYPE MARA-MEINS ,
ld_single
 
 TYPE STRING ,
ld_date_of_change
 
 TYPE RMCLF-DATUV1 ,
ld_i_auth_chk
 
 TYPE RMCLF-KREUZ .


ld_called_from = 'some text here'. 

"populate fields of struture and append to itab
append wa_otab to it_otab.
ld_language = 'Check type of data required'.
ld_lock = 'some text here'.
ld_single = 'some text here'.

ld_date_of_change = 20210129

ld_i_auth_chk = some text here