on 03-13-2014 11:23 AM
When calling a BRF+ application the first time after its activation (from ABAP using API cl_fdt_factory=>if_fdt_factory~get_instance) there seems to be kind of a generation step which includes a (possibly implicite) DB-commit. At least that's my observation. is it possible to prevent this commit ?
Hi Christian
I've had a problem in the past where I needed to execute a BRF+ rule in an update task but the COMMIT WORK triggered by the BRF+ code generation caused a short dump (no commits are allowed in an update task). Is yours a similar problem?
SAP created a note to fix it for us and (from memory) it was this one: http://service.sap.com/sap/support/notes/1504376
Maybe this note will help you too?
Regards
Glen
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
88 | |
10 | |
10 | |
9 | |
6 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.