Question:
Good morning
I have an Infopackage defined for full load of a transaction Cube (e.g. FI_AR_1) where I selected "delete existing requests .. selection same or more comprehensive".
When run manually the load happens as expected (previous full load is deleted from cube) but when run as part of the process chain, the infopackage no longer does hte delete existing request (I get new full on top of previous full request).
Then I tried to add a step to the process chain (garbage bin) to "delete overalpping from cube" after my infopack run (with option). Still no luck, previous full loads are not deleted... So all records are double loaded (triple loaded next time).
Any thoughts?
Thanks,
Kathy
Answer:
Hi
Few things to Check out for as a part of sanity check.
The requests that are deleted or cancelled in the InfoCube must still be available in the PSA.
If there is a considerable time difference between the user's local time zone and the UTC time zone (Greenwich Mean Time), it may appear that requests from the adjacent date are deleted (or not deleted).
Request is not compressed because the request number is no longer transparent.
Hope it Helps
_________________
Chetan
@ CP...
Answer:
Hi Chetan
Thank you for your feedback and suggestions.
The 3 items that you mentionned are not the problem in my case; especially since the deletion works when loading from Infopackage.
The issues seems to be specific to process chains.
Why is the deletion of overlapping requests working when loading from Infopack but not from Process chain?
Or is there something funky like "Am I forgetting a setting in infoPack? e.g. if you have delete overlapping request set in the process chain, do you need to remove that setting from InfoPack?"
Thanks,
Kathy
Answer:
Hi Chetan
Thank you for your feedback and suggestions.
The 3 items that you mentionned are not the problem in my case; especially since the deletion works when loading from Infopackage.
The issues seems to be specific to process chains.
Why is the deletion of overlapping requests working when loading from Infopack but not from Process chain?
Or is there something funky like "Am I forgetting a setting in infoPack? e.g. if you have delete overlapping request set in the process chain, do you need to remove that setting from InfoPack?"
Thanks,
Kathy
Hi
What version and SP leverl of BW r u presently working on??
_________________
Chetan
@ CP...
Answer:
Katy2004
In your process chain, you need to add one step to delete previous request. This step is named: Delete Overlapping Requests from InfoCube
Gilm
Answer:
Thanks for sharing.
- I am on BW 3.1 support pack 15
- I already had that delete step, just to veridy, do you put that step after the infopackage load? Can you still have the index drop/recreate step?
FYI I also checked oss note 792357 -Reversal requests and automatic deletion
Thanks,
Kathy2004
Answer:
Hi kathy204,
Gilm is right, I had the same problem the first time I set up process chains.
The delete step is after the Info package load. Use Delete Selections same as the info package. It worked for me all the best.
Cheers,
TC
Answer:
Thanks for sharing.
- I am on BW 3.1 support pack 15
- I already had that delete step, just to veridy, do you put that step after the infopackage load? Can you still have the index drop/recreate step?
FYI I also checked oss note 792357 -Reversal requests and automatic deletion
Thanks,
Kathy2004
Hi,
Process Chain -Standard Procedure
Start
Delete Index
Load Data
Build Index
Create Database statistics
Delete Overlapping Requests from Infocube
Roll up Filled Aggregates
Compression
FYI-The processes Delete Indexes (before the InfoPackage) and Build Index (after the InfoPackage) are automatically inserted into your process chain
Hope it Helps
_________________
Chetan
@ CP...