CA_CHECK_DATE SAP Function module - Authorization Check

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

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

Pattern for FM CA_CHECK_DATE - CA CHECK DATE

CALL FUNCTION 'CA_CHECK_DATE' "Authorization Check
  EXPORTING
    i_applk =                   " applk_bf      Application indicator for BTE
    i_orgunit =                 "               Char20
    i_user =                    " usnam         User Name
    i_program =                 " progname      ABAP Program Name
*   i_from_date =               " dats          Field of Type DATS
*   i_to_date =                 " dats          Field of Type DATS
  EXCEPTIONS
    NO_AUTHORITY_DATE = 1       "
    NO_AUTHORITY_PROG = 2       "
    WRONG_PARAMETER = 3         "
    .  "  CA_CHECK_DATE

ABAP code example for Function Module CA_CHECK_DATE

The ABAP code below is a full code listing to execute function module CA_CHECK_DATE 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_i_applk) = 'Check type of data required'.

DATA(ld_i_orgunit) = 'some text here'.

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

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

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

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

CALL FUNCTION 'CA_CHECK_DATE'
  EXPORTING
    i_applk =                    ld_i_applk
    i_orgunit =                  ld_i_orgunit
    i_user =                     ld_i_user
    i_program =                  ld_i_program
*   i_from_date =                ld_i_from_date
*   i_to_date =                  ld_i_to_date
  EXCEPTIONS
    NO_AUTHORITY_DATE =          1
    NO_AUTHORITY_PROG =          2
    WRONG_PARAMETER =            3
    .  "  CA_CHECK_DATE

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_i_applk
 
 TYPE APPLK_BF ,
ld_i_orgunit
 
 TYPE STRING ,
ld_i_user
 
 TYPE USNAM ,
ld_i_program
 
 TYPE PROGNAME ,
ld_i_from_date
 
 TYPE DATS ,
ld_i_to_date
 
 TYPE DATS .


ld_i_applk = 'Check type of data required'.
ld_i_orgunit = 'some text here'.
ld_i_user = 'Check type of data required'.
ld_i_program = 'Check type of data required'.
ld_i_from_date = 'Check type of data required'.
ld_i_to_date = 'Check type of data required'.