SAP FCJ_PREP_TRANSACTION_CHECK Function Module for
FCJ_PREP_TRANSACTION_CHECK is a standard fcj prep transaction check SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 fcj prep transaction check FM, simply by entering the name FCJ_PREP_TRANSACTION_CHECK into the relevant SAP transaction such as SE37 or SE38.
Function Group: FCJ_MAIN_FORM
Program Name: SAPLSAPLFCJ_MAIN_FORM
Main Program: SAPLSAPLFCJ_MAIN_FORM
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FCJ_PREP_TRANSACTION_CHECK 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 'FCJ_PREP_TRANSACTION_CHECK'".
EXPORTING
I_COMP_CODE = "Company Code
I_CAJO_NUMBER = "Cash Journal Number
I_TYP = "Business Transaction Type
IMPORTING
E_TRANSACT_NUMBER = "Number of Cash Journal Business Transaction
CHANGING
P_TRANSACT_NAME = "Cash Journal Business Transaction
P_TRANSACT_TAX_CODE = "Tax Code
P_TRANSACT_GL_ACCOUNT = "G/L Account
IMPORTING Parameters details for FCJ_PREP_TRANSACTION_CHECK
I_COMP_CODE - Company Code
Data type: BUKRSOptional: No
Call by Reference: Yes
I_CAJO_NUMBER - Cash Journal Number
Data type: CJNROptional: No
Call by Reference: Yes
I_TYP - Business Transaction Type
Data type: CJTRANSTYPOptional: No
Call by Reference: Yes
EXPORTING Parameters details for FCJ_PREP_TRANSACTION_CHECK
E_TRANSACT_NUMBER - Number of Cash Journal Business Transaction
Data type: CJTRANSNUMBOptional: No
Call by Reference: Yes
CHANGING Parameters details for FCJ_PREP_TRANSACTION_CHECK
P_TRANSACT_NAME - Cash Journal Business Transaction
Data type: CJTRANSTXTOptional: No
Call by Reference: Yes
P_TRANSACT_TAX_CODE - Tax Code
Data type: MWSKZOptional: No
Call by Reference: Yes
P_TRANSACT_GL_ACCOUNT - G/L Account
Data type: HKONTOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for FCJ_PREP_TRANSACTION_CHECK 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: | ||||
| lv_i_comp_code | TYPE BUKRS, " | |||
| lv_p_transact_name | TYPE CJTRANSTXT, " | |||
| lv_e_transact_number | TYPE CJTRANSNUMB, " | |||
| lv_i_cajo_number | TYPE CJNR, " | |||
| lv_p_transact_tax_code | TYPE MWSKZ, " | |||
| lv_i_typ | TYPE CJTRANSTYP, " | |||
| lv_p_transact_gl_account | TYPE HKONT. " |
|   CALL FUNCTION 'FCJ_PREP_TRANSACTION_CHECK' " |
| EXPORTING | ||
| I_COMP_CODE | = lv_i_comp_code | |
| I_CAJO_NUMBER | = lv_i_cajo_number | |
| I_TYP | = lv_i_typ | |
| IMPORTING | ||
| E_TRANSACT_NUMBER | = lv_e_transact_number | |
| CHANGING | ||
| P_TRANSACT_NAME | = lv_p_transact_name | |
| P_TRANSACT_TAX_CODE | = lv_p_transact_tax_code | |
| P_TRANSACT_GL_ACCOUNT | = lv_p_transact_gl_account | |
| . " FCJ_PREP_TRANSACTION_CHECK | ||
ABAP code using 7.40 inline data declarations to call FM FCJ_PREP_TRANSACTION_CHECK
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.Search for further information about these or an SAP related objects