Has anyone experienced the issue where a task within a Package Link acts as though the previous task in the Link did not execute? For instance, we see this behavior sporadically in some of our BPC models. We have a Package Link wherein one task calculates Ending Balances for Balance Sheet Accounts. The very next task is meant to calculate the resulting monthly activity from those Balances and write the results to Cash Flow accounts.
But, *sometimes* the Cash Flow task generates large Monthly Activity in the first month, which seems to indicate that the previous task, the Ending Balances calculation, did not run. When we manually run the Cash Flow Data Manager package by itself immediately after the Package Link finishes, it appears to work.
If anyone has experienced this, is it an issue somehow with parallel processing or a delay in the update part of the previous task? Would a *COMMIT placed at the end of said task in the script logic help? I know that *COMMIT is not usually necessary because *ENDWHEN (and other keywords) automatically perform the same thing, but maybe it would ensure the update is complete before the next task in the Package Link runs?
Anyway, just reaching out to see if others have experienced this. Initial searching, both in the community as well as of SAP Notes didn't turn up anything promising.
We are on BPC version 10.0 for NetWeaver on HANA. BPC SP level 13, ABAP/Basis SP 11, HANABPC SP 7 (rel 800).
Thanks!
- John