FCJ_CHECK_TRANSACTION SAP Function module

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

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

Pattern for FM FCJ_CHECK_TRANSACTION - FCJ CHECK TRANSACTION

CALL FUNCTION 'FCJ_CHECK_TRANSACTION' "
  EXPORTING
    i_comp_code =               " tcj_c_journals-comp_code
    i_cajo_number =             " tcj_c_journals-cajo_number
    i_comp_name =               " butxt
    i_cajo_name =               " tcj_cj_names-cajo_name
    i_typ =                     " cjtranstyp
    i_document_status =         " cjdocstat
*   i_means_of_payment =        " cjmofpaym     Cash Journal Means of Payment
*   i_xmitk =                   " boolean
*   i_saknr =                   " saknr
  CHANGING
    p_transact_name =           " cjtranstxt
*   p_transact_type =           " cjtranstyp    Business Transaction Type
    p_transact_tax_code =       " mwskz         Tax Code
    p_transact_gl_account =     " hkont         G/L Account
*   p_man_tax_code =            " boolean       Boolean Variable (X=True, -=False, Space=Unknown)
*   p_transact_name_changed =   " boolean       Boolean Variable (X=True, -=False, Space=Unknown)
*   p_umskz =                   " umskz
    .  "  FCJ_CHECK_TRANSACTION

ABAP code example for Function Module FCJ_CHECK_TRANSACTION

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

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

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

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

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

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

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

SELECT single COMP_CODE 
  FROM TCJ_C_JOURNALS 
  INTO @DATA(ld_i_comp_code).

 

SELECT single CAJO_NUMBER 
  FROM TCJ_C_JOURNALS 
  INTO @DATA(ld_i_cajo_number).


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

SELECT single CAJO_NAME 
  FROM TCJ_CJ_NAMES 
  INTO @DATA(ld_i_cajo_name).


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

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

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

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

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

CALL FUNCTION 'FCJ_CHECK_TRANSACTION'
  EXPORTING
    i_comp_code =                ld_i_comp_code
    i_cajo_number =              ld_i_cajo_number
    i_comp_name =                ld_i_comp_name
    i_cajo_name =                ld_i_cajo_name
    i_typ =                      ld_i_typ
    i_document_status =          ld_i_document_status
*   i_means_of_payment =         ld_i_means_of_payment
*   i_xmitk =                    ld_i_xmitk
*   i_saknr =                    ld_i_saknr
  CHANGING
    p_transact_name =            ld_p_transact_name
*   p_transact_type =            ld_p_transact_type
    p_transact_tax_code =        ld_p_transact_tax_code
    p_transact_gl_account =      ld_p_transact_gl_account
*   p_man_tax_code =             ld_p_man_tax_code
*   p_transact_name_changed =    ld_p_transact_name_changed
*   p_umskz =                    ld_p_umskz
    .  "  FCJ_CHECK_TRANSACTION

IF SY-SUBRC EQ 0.
  "All OK
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_p_transact_name
 
 TYPE CJTRANSTXT ,
ld_i_comp_code
 
 TYPE TCJ_C_JOURNALS-COMP_CODE ,
ld_p_transact_type
 
 TYPE CJTRANSTYP ,
ld_i_cajo_number
 
 TYPE TCJ_C_JOURNALS-CAJO_NUMBER ,
ld_p_transact_tax_code
 
 TYPE MWSKZ ,
ld_i_comp_name
 
 TYPE BUTXT ,
ld_p_transact_gl_account
 
 TYPE HKONT ,
ld_i_cajo_name
 
 TYPE TCJ_CJ_NAMES-CAJO_NAME ,
ld_p_man_tax_code
 
 TYPE BOOLEAN ,
ld_i_typ
 
 TYPE CJTRANSTYP ,
ld_p_transact_name_changed
 
 TYPE BOOLEAN ,
ld_i_document_status
 
 TYPE CJDOCSTAT ,
ld_p_umskz
 
 TYPE UMSKZ ,
ld_i_means_of_payment
 
 TYPE CJMOFPAYM ,
ld_i_xmitk
 
 TYPE BOOLEAN ,
ld_i_saknr
 
 TYPE SAKNR .


ld_p_transact_name = 'Check type of data required'.

SELECT single COMP_CODE 
  FROM TCJ_C_JOURNALS 
  INTO ld_i_comp_code.

ld_p_transact_type = 'Check type of data required'.

SELECT single CAJO_NUMBER 
  FROM TCJ_C_JOURNALS 
  INTO ld_i_cajo_number.

ld_p_transact_tax_code = 'Check type of data required'.
ld_i_comp_name = 'Check type of data required'.
ld_p_transact_gl_account = 'Check type of data required'.

SELECT single CAJO_NAME 
  FROM TCJ_CJ_NAMES 
  INTO ld_i_cajo_name.

ld_p_man_tax_code = 'Check type of data required'.
ld_i_typ = 'Check type of data required'.
ld_p_transact_name_changed = 'Check type of data required'.
ld_i_document_status = 'Check type of data required'.
ld_p_umskz = 'Check type of data required'.
ld_i_means_of_payment = 'Check type of data required'.
ld_i_xmitk = 'Check type of data required'.
ld_i_saknr = 'Check type of data required'.