Skip to Content
0
Former Member
Nov 30, 2010 at 10:08 PM

Error Package Status

23 Views

Hi All;

Thanks for the help! First, a little background (BPC 7.5 Microsoft). We are running Ownership logic using BPC's consolidation engine. When the engine runs, by default, it runs for all entities. In the Stored Procedure there is not a variable to set for Entity. If you limit the query to one Entity, the consol engine resets the Entity memberset to all. The Stored Proc itself cannot be modified (it is BPC proprietary and cannot be viewed).

The Ownership logic works fine. However, if one Business Unit loads their data before other data is available for the Own calculation, the package status comes back with an error saying their is no data available for the calculation. This situation will be a normal scenario for the business and does not seem to be avoidable. We want the package status to come back marked as "Completed" and not as an "Error" in this situation.

So, now to the question, do you know how BPC determines to mark a package with a status error (maybe in a stored procedure)? Do you know if there is a way to modify the criteria BPC uses to allow the package to succeed under these circumstances? Or, maybe, if there is a way to conditionally alter the status after execution (looking at the results and changing the package status in the tblDTSlog table)?

The Ownership task in the package has already been modified (via Visual Studio) to continue processing the remaining logic if there is an error for the Ownership logic. The Ownership logic task has also been modified to force the execution result to be successful. Apparently BPC does not look to this when marking a package as having an error.

Please let me know what you think or if you have any suggestions outside of what I asked. Your help is very much appreciated!

Edited by: Jonathan Essig on Dec 1, 2010 1:01 AM

Edited the Stored Procedure for the LogConso and commented out the lines specific to the no data errors. This worked, but when I processed the application the SP was rebuilt so I'm back to where I started.