CACS_VALIDATE_FFL_OBJ_DATA SAP Function module

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

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

Pattern for FM CACS_VALIDATE_FFL_OBJ_DATA - CACS VALIDATE FFL OBJ DATA

CALL FUNCTION 'CACS_VALIDATE_FFL_OBJ_DATA' "
  EXPORTING
    i_busobj_type =             " cacsbusobjtyp  Business Object Category that Triggers Commission
    i_busobj_id =               " cacsbusobjid  Identification of Triggering Business Object
    i_tri_obj_type =            " cacstriobj    Triggering Subobject Type
    i_tri_obj_id_ext =          " cacstriobjidext  External Identification of Triggering Subobject
  CHANGING
*   c_flg_error =               " cacscaseerror  Indicator: Commn Case Inconsistent (X = error, ' ' = ok)
    c_flg_reject =              " cacscasereject  Ind.: Commission Case Rejected (X=Rejected, ' '= Accepted)
*   c_constellation =           " char1         Single-Character Indicator
  EXCEPTIONS
    INVALID_CONSTELLATION = 1   "
    .  "  CACS_VALIDATE_FFL_OBJ_DATA

ABAP code example for Function Module CACS_VALIDATE_FFL_OBJ_DATA

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

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

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

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

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

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

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

CALL FUNCTION 'CACS_VALIDATE_FFL_OBJ_DATA'
  EXPORTING
    i_busobj_type =              ld_i_busobj_type
    i_busobj_id =                ld_i_busobj_id
    i_tri_obj_type =             ld_i_tri_obj_type
    i_tri_obj_id_ext =           ld_i_tri_obj_id_ext
  CHANGING
*   c_flg_error =                ld_c_flg_error
    c_flg_reject =               ld_c_flg_reject
*   c_constellation =            ld_c_constellation
  EXCEPTIONS
    INVALID_CONSTELLATION =      1
    .  "  CACS_VALIDATE_FFL_OBJ_DATA

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "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_c_flg_error
 
 TYPE CACSCASEERROR ,
ld_i_busobj_type
 
 TYPE CACSBUSOBJTYP ,
ld_c_flg_reject
 
 TYPE CACSCASEREJECT ,
ld_i_busobj_id
 
 TYPE CACSBUSOBJID ,
ld_c_constellation
 
 TYPE CHAR1 ,
ld_i_tri_obj_type
 
 TYPE CACSTRIOBJ ,
ld_i_tri_obj_id_ext
 
 TYPE CACSTRIOBJIDEXT .


ld_c_flg_error = 'Check type of data required'.
ld_i_busobj_type = 'Check type of data required'.
ld_c_flg_reject = 'Check type of data required'.
ld_i_busobj_id = 'Check type of data required'.
ld_c_constellation = 'Check type of data required'.
ld_i_tri_obj_type = 'Check type of data required'.
ld_i_tri_obj_id_ext = 'Check type of data required'.