on 2024 Oct 07 11:26 PM
Hello experts,
We are using SAP standard function module "COBL_CODINGBLOCK_CHECK" in custom ABAP RAP application to validate the accounting lines, but application gets crashed during the validation phase with error saying BEHAVIOR_ILLEGAL_STATEMENT.
Statement "EXPORT TO DATABASE" is not allowed with this status.
Actually, function module "COBL_CODINGBLOCK_CHECK" internally calls the function module “FM_ACCOUNT_DERIVE” which tries to save the fund management derivation rule (FMDERIVE) trace log in data cluster (TABADRX) using statement "EXPORT TO DATABASE".
We know that database commands are not allowed in RAP Early Save Phase and only allowed in RAP Late Save Phase.
We can perform coding block check during RAP Late Save Phase, but then error messages would not be shown in UI, so it must be done in RAP Early Save Phase.
Do you have any suggestion how to resolve this issue?
Request clarification before answering.
Hi @abaper007,
According to the document below, by using saver class CL_ABAP_BEHAVIOR_SAVER_FAILED instead of the default CL_ABAP_BEHAVIOR_SAVER, save_modified method will include failed and reported parameters.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
77 | |
30 | |
9 | |
8 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.