on 04-25-2017 9:18 AM - last edited on 02-03-2024 11:22 PM by postmig_api_4
By design BPC consolidation monitor (V10.1) doesn't tell whether result data is empty or not after rules run, so it's possible ACDOCC is empty after a successful run of BPC consolidation task.
I am facing a similar issue, have you been able to solve it?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
I have exactly the same problem. Everything done by the book, according to Real-Time Consolidation, currency translation shows sccess message, but ACDOCC is empty and write back method is not triggered.
One think make me wonder. When I run currency translation I can see in "Display running processes" that when currently running process ends as green and Done the previous one turns from Done to Failed and in details of that run I can see:
Any hints/clues?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It seemed cache do sth wrong backend, can you do a cleanup backend?
Login Backend and Se38 and run “/UI5/APP_INDEX_CALCULATE” periodically to update client cache buster information.
And then type these 2 URL in the browser:
http://<server>:<port>/sap/epm/bpc/web/clearcache
http://<server>:<port>/sap/epm/bpc/web/resetcachebuster
Hi William,
I'm facing the same issue, I have used copy of standard class CL_RTC_ACDOCC_IPROV_WRITABLE and mapped it with virtual provider. But when we are running the currency translation from BPC, it's showing success message there but we are unable to see the data in ACDOCC table even I debugged it but the method 'IF_RSDRV_RPROV_WRITABLE~WRITE_DATA' is not getting triggered.
Is there any way to check why the method IF_RSDRV_RPROV_WRITABLE~WRITE_DATA is not triggered.
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
First you can check if there's ABAP dump backend with TCd ST22.
IF there's no error frontend and backend, we need to do debug stuff.
To DEBUG write back to ACDOCC, data generated by consolidation logic and passed to your write back interface.
Before you go to consolidation monitor to trigger logics, put an external break point at CL_UJXP_MONITOR_EMBEDDED->DO_POST, search 'start_job(…)' around line 480? Change parameter lf_synchronus to ‘X’ at debug runtime.
Then set breakpoint at beginning of CL_RTC_ACDOCC_IPROV_WRITABLE-> IF_RSDRV_RPROV_WRITABLE~WRITE_DATA. Notice this class is what you set as write interface while modeling your virtual provider.
If debug not go into writeback class, that means no data produced by BPC, if go into write back class, then try find in which step program jump out and the content of error message if existed.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
15 | |
3 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.