Update rules deactivated after transporting cube with zero elimination on

Hello,
The update rules were deactivated in the quality system after transporting the cube with the zero elimination flag switched on. However, the update rules in development were not deactivated when setting the zero elimination flag. So, the update rules in the "From" system were not deactivated. This only happened in the "To" System. Does anyone know why?
Thanks,
Maureen

If there is any change you did on cube, you need to re-activate your update rules.
Re-activate your UR and transport it. It should be ok.
Hope it helps..

Similar Messages

Cube compression WITH zero elimination option

We have tested turning on the switch to perform "zero elimination" when a cube is compressed. We have tested this with an older cube with lots of data in E table already, and also a new cube with the first compression. In both cases, at the oracle level we still found records where all of the key figures = zero. To us, this option did not seem to work. What are we missing? We are on Oracle 9.2.0.7.0 and BW 3.5 SP 17
Thanks, Peggy

Haven't looked at ZERO Elimination in detail in the latest releases to see if there have been changes, but here's my understanding based on the last time I dug into it -
When you run compression with zero elimination, the process first excluded any individual F fact table rows with all KFs = 0, then if any of the summarized F fact table rows had all KF = 0, that row was excluded ( you could have two facts with amounts that net to 0 in the same request or different requests where all other Dims IDs are equal) and not written to the E fact table. Then if an E fact table row was updated as a result of a new F fact table row being being merged in, the process checked to see if the updated row had all KF values = 0, and if so, deleted that updated row from the E fact table.
I don't beleive the compression process has ever gone thru and read all existing E fact table rows and deleted ones where all KFs = 0.
Hope that made sense. We use Oracle, and it is possible that SAP has done some things differently on different DBs. Its also possible, that the fiddling SAP had done over that last few years trying to use Oracle's MERGE functionality at different SP levels comes into play.
Suggestions -
I'm assuming that teh E fact table holds a significant percentage of rows have all KFs = 0. If it doesn't, it's not worth pursuing.
Contact SAP, perhaps they have a standalone pgm that deletes E fact table rows where all KFs = 0. It could be a nice tool to have.
If they don't have one, consider writing your own pgm that deletes the rows in question. You'll need to keep downstream impacts in mind, e.g. aggregates (would need to be refilled - probably not a big deal), and InfoProviders that receive data from this cube.
Another option would be to clone the cube, datamart the data to the new cube. Once in the new cube, compress with zero elimination - this should get rid of all your 0 KF rows. Then delete the contents of the original cube and datamart the cloned cube data back to the original cube.
You might be able to accomplish this same process by datamarting the orig cube's data to itself which might save some hoop jumping. Then you would have to run a selective deletion to get rid of the orig data, or perhaps if the datamarted data went thru the PSA, you could just delete all the orig data from the cube, then load datamarted data from the PSA. Once the new request is loaded, compress with zero elimination.
Now if you happen to have built all your reporting on the this cube to be from a MultiProvider on teh cube rather than directly form the this cube, you could just create anew cube, export the data to it, then swap the old and new cubes in the MultiProvider. This is one of the benefits of always using a MultiProvider on top of a cube for reporting (an SAP and consultant recommended practice) - you can literally swap underlying cubes with no impact to the user base.

Is there a update for adobe after effects compatible with the mac os x 10.9.5 ?

is there a update for adobe after effects compatible with the mac os x 10.9.5 ?

If you are using After Effects CS6 (11) or After Effects CC (12), then install the updates:
http://adobe.ly/AE_CC_1201_Mavericks

Compression with zero elimination (reverse postings)

I executed a compression with zero elimination in a custom InfoCube in order to avoid entries that only contain zero values as key figures (for example reverse posting) are contained in the InfoCube after compressing.
However, not all the entries where all the key figures are blank have been deleted.
This cube contains the following standard key figures:
-0DEB_CRE_DC;
-0DEB_CRE_LC;
-0DSCT_DAYS1;
There are also two other custom key figures, created as copy of 0DEB_CRE_LC.
Have you any suggestion?

So you're saying you have rows in your E fact table that were created as part of this particular compression run where all KFs = 0? That certainly doesn't sound right.
The zero elimination is a multi-step process -
first excluding rows from the F fact table where all KFs are 0, then excluding any summarized rows where all KF = 0, and then finally, deleting rows from E fact table that were updated resulting in all KFs = 0. Were any compressions run on this cube previously without zero elimination specified?
What DB?
There have been some problems with Oracle 9.2 merge function.
https://websmp201.sap-ag.de/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=613701&_NLANG=E
https://websmp201.sap-ag.de/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=639253&_NLANG=E

Compression pb with zero elimination

Hi,
In a BW3.1 SP22, We compress infocube with flag with zero elimination activated.
But occurrences having key figures null and which were just compressed are not deleted.
Few properties of this cube are :
     just cumulatives KF
     huge volume (approx 120 millions occurrences / 22 millions new non-deleted occurrences with all KF null)
     huge aggregates (biggest : 20 millions)
     partitioning by month (12)
     previously few requests were compressed without the flag « zero elimination » but obviously the occurrences described as non-deleted dont come from these old requests
In the same system, on others cubes with less datas, we tried to reproduce the case without success. In all scenarii we had tested, lines with KF nulls are correctly deleted.
We dont understand from where the problem could come.
If someone has an idea ...
Thanks by advance.

So you're saying you have rows in your E fact table that were created as part of this particular compression run where all KFs = 0? That certainly doesn't sound right.
The zero elimination is a multi-step process -
first excluding rows from the F fact table where all KFs are 0, then excluding any summarized rows where all KF = 0, and then finally, deleting rows from E fact table that were updated resulting in all KFs = 0. Were any compressions run on this cube previously without zero elimination specified?
What DB?
There have been some problems with Oracle 9.2 merge function.
https://websmp201.sap-ag.de/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=613701&_NLANG=E
https://websmp201.sap-ag.de/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=639253&_NLANG=E

Compression with zero-elimination

Hi experts,
"If you want to avoid the InfoCube containing entries whose key figures are zero values (in reverse posting for example) you can run a zero-elimination at the same time as the compression. In this case, the entries, where all the key figures are equal to 0, are deleted from the fact table"
I am looking for clarification regarding the note above.
I understand that Compressing the InfoCube eliminates the duplicate records by converting all request IDs to 0 and rolling up the key figures for records that have common values for all characteristics
If I have 1 record with more than 3 KFs for example; within those 3 KFs, 2 have the value 0.
Does compression with zero-elimination with only set the request id to 0, keeping the value 0 for the 2 KFs like before compression or do we will have blank space (deleted) insteadt?
Does the zero-elimination is only possible when all KFs in the same record are equal to 0?
Thanks.

Hi Blaiso ,
Zero Elimination means deleting the record from the cube after compression if and only if, the entire key figures of the particular record is zero. If there are two key figures A & B, A = 0, B = 10, then this record will not be deleted from the cube.
So the answer to your question is if in a particular record there are 3 KF with 1 as non zero then this record will not be deleted but request ID would be deleted .
Please check the below link for complete information on compression :
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c035d300-b477-2d10-0c92-f858f7f1b575?QuickLink=index&overridelayout=true
Hope it helps .
Thanks
Kamal Mehta

Compress infocube with zero elimination

Experts, Is that true you should always check "with zero elimination" when you compress infocubes? I was reading the famous SAP doc "How to Handle Inventory Management Scenarios in BW", the screen shots for cube compression does not have that checkbox checked. Does anybody know why?
Thanks!

Hello,
Using the zero elimination the entries where all key figures are equal to zero are deleted from the fact table during compression. You don't want that in Inventory Management.
Regards,
Jorge Diogo

Compress the Request with Zero Elimination

I delta load the transaction data into Infocube by InfoPackage and compress the Request ID manually without select 'with Zero Elimination'. Now I wanna Compress the request ID with Zero Elimination again. Could you give me some hits on that. Many Thanks .

hi,
There're two programs that work for me.
1. RSCDS_MERGE_DUPL_REF_POINTS - this is to actually compress the records.
2. RSCDS_NULLELIM : - To remove the records with 0 value i.e. null Elimination
Although, SAP doesn't recommend using them if your compression is working fine.
You may want to try them in your non-production system first.
-RMP

Update rules deactivating

Hello All,
In the my productive BW system, a set of update rules became inactive. They were active one day - inactive the next. The system is closed, and no transports moved. No one opened the system. When I double-click on the update rules, it says the rules were modified by 'IMPACT' (what I usually see when I change a data target), at a certain time in the morning - and that - sure enough - they were deactivated due to a change in the data target.
To fix the problem, I had my Basis team open the system and I reactivated manually. There no issues here - the rules just reactivated. Further, the rules from the supposedly changed data target were active - meaning the data target did not, in fact, change. I am on BW 3.5, SP 20.
1. Has anything like this ever happened to anyone else?
2. Does anyone have an explanation for how this could occur?
3. Is there a log that either I or Basis could go to to try and see what happened?
4. Does anyone have any advice about what else I can try to do to diagnose this issue?
Thanks.
Dave

Hi,
There are circumstances where your IPs fails with error " Inactive update rules "
Like,
Suppose a load was running and u cancelled it but the processing of packets is progressing.
In the mean while if you repeat the same IP, then we will be getting this error as "Inactive update rules". This is because your update rules are being used by its previous load.
To avoid this, you have to wait till the processing of old load is over. After that if you repeat, It will become successful.
At any point of time same update rules cannot be used in parallel.
Hope it will be useful.
Regards,
Vamsi
*Assign points if useful.

Updates rules inactive after add KF

Hi experts,
we have to add aditional key figures to a infocube that is already in Q and P systems (with data).
Now we are not being able to transport the update rules to those systems.
Correct me if i'm wrong but if you add aditional characteristic's or key figures you don't need to delete data in the infoproviders in the ohter systems.
we have already try to transport:
cube and then update rules;
all together cube and update rules
in both cases it fails.
thanks in advance for any sugestion

Varadarajan, our database is in SQL the spaces requirements that you refer are the same for this scenario? The fact table for this infop is 43G in Q system and our database have enough space.
am i making this analysis ok including the Db space?
Praveen the update rules are not datamart's.
The transport ends with a 8 code and for each update rule inlcude gives the message:
Update rules 2237DNCKOFJ13SFIK2PT581MQ read in version M
Error when activating update rule 2237DNCKOFJ13SFIK2PT581MQ
Sadeesh, all necessary objects are in the destiny system and no modifications were made at infosource/data source level.
Thank you all for the answers.

Update rules - Activation error - in cube 0PAPA_C02

Hi All,
When i am activating the update rules of 0PAPA_C02 cube, i am encounting the following error for key fig "Headcount Change FTE Employee".
Empty or invalid formula 8RFPFLULBJGBAO07IDMZGMPXR.
Please let me know your thoughts.
Thanks & Regards,
Eswari.

Hi,
And also make sure that <b>all</b> target fields has proper maapings. i.e either a direct assignment with source field,or routine or formula or constant. Some times sytem shows a routine as update method but blank routine. It happens after,when you include a field to data target or coping the update rules.
Most of the time, you can solve this type of error by studing very carefully the existing mappings(routines,formulas).
With rgds,
Anil Kumar Sharma .P

Update rules deactivated only has to open the system..

Hello Experts,
-- ODS and update rules are already in Production.
-- I have made changes to the ODS by adding new Infobjects.
-- activated the update rules.
-- When the ODS and update rules are transported. Update rules get deactivated
-- And a message 'Data target changed, suggestion for the update rules generated'
Detailed message:
Data target was changed. Suggestion for update rules generated
Message no. RSAU287
CAUSE&
The data target has been changed (for example, InfoObjects have been added or deleted).
System response
The update rules have been set to inactive.
Procedure
Check the proposal for the update rules: Newly added key figures or characteristics are updated directly using the source-InfoObject from the InfoSource if the InfoSource contains these InfoObjects. Otherwise, the calculation type is set to 'Routine'. Newly added key figures, data fields, or attributes are set to 'No Update'.
The rules for key figures and for characteristics must be checked and adjusted appropriately.
Detailed message end.........
-- Do not get activated by retransporting. or doing a fresh request of the update rules.
-- Currently the only I can see by opening the system and activating them. Wondering if we have any other alternatives to activate these update rules for the ODS
Any solutions:
-- Wondering if I am missing some procedure to transport.
-- Please feel free to post your views / suggestion in case you had a similar situation before.
Many thanks in advance,
BWer
Message was edited by: BWer

BWer,
If you collect your transport in a big lump of a single transport, the tranport connection may not organize it in the order of the proper dependency, so it is best to split it to separate transports as stated above to ensure the proper dependencies.
To fix the issue right now, you can either
1) take another transport through of only the updated / activated update rule or
2) if you know what you are doing and if the client is okay with it, open the system, activate the update rule and when prompted for a transport, create a new one and go to SE10 to clean up that repair transport by deleting the subtasks.
I would probably recommend option 1 for you. I only do option 2 if it is an emergency and there is no transport window for another week or longer or it just simply cannot wait.

Update rule arrow across the cube

Hi Experts,
When i went to look at the dataflow for a cube, i found that it has got an update rule icon running across.. May i know what does that mean and how it appears like that please.
DV
null

Hi,
they're many scenarios....
a simple one would be to change a characteristic value let's say you want to change all records with CHAR_1 = 'A' to CHAR_1 = 'B'.
you would do the following:
- generate export DS on your cube
- create Urules from your cube to your cube; set constant update on CHAR_1 = 'B' and all the rest one_to_one update
- fire an IPack with selection CHAR_1 = 'A' to be extracted from (and loaded to) your cube (you can even go via PSA and change your data manually)...
- after the load, selective delete your cube where CHAR_1 = 'A'.
more sophisticated would be to post a reverse record (all keyfigs x -1) if you want to avoid the selective deletion...
they're many more....
hope this helps...
Olivier.

Cannot update data from DSO to Cube with further update in process chain

Hi Guys,
              This is the message am getting when am trying to update to cube by process further update with process chain.Process fails at further update with the following below message.
However at DSO level i can see the data mart status but no request at cube level.
Error Message:
Cannot update request REQU_D57WAP7Z2WAI1CG5Y5OQ5W7JR in data target
    Message no. RSM1523
Diagnosis
    System checks show that request REQU_D57WAP7Z2WAI1CG5Y5OQ5W7JR cannot be
    updated to a data target.
    The system checked whether
    o   request REQU_D57WAP7Z2WAI1CG5Y5OQ5W7JR is already in the data target
    o   the data target has active update rules for the InfoSource
    o   the data target was selected for updating
    o   locks exist
    o   for a DataStore object as a data target, that the request was
        updated in the correct order, if the DataStore object stipulates
When i check the monitor screen under status tab it says "A caller 01, 02 or equal to or greater than 20 contains an error meesage" and under details tab "Data Package 1 : arrived in BW ; Processing : Data packet not yet processed "
Regards,
Krishna.
Edited by: krishna Krishna on Mar 4, 2009 6:37 PM

Hi
It seems you used infopack when you select update data inot datatarget then system prompts you a infopack.That's the infopack which is generated by system being used in process chain variant to update data into datatarget.
Create new infopack/ DTP manually then use that infoapck/DTP on the process chain variant then try.
Chandu.

No changes in Update rules even after changes in Communicatin struct

Hello All,
I have made changes to a transfer structure i.e. I added a field in the Communication structure and mapped in the transfer structure. I was expecting the update rule to be deactivated after this. But the Update rule is activated. Because of this I am not able to accomodate my new infoObject in the update rule. What might be the problem?
Regards,
KP

Hi KK PP,
Update rules are only pertained to Data targets,These helps to map the object to the Infosource using a rule.If you change the transfet structure or communication structure it will not effect update rules.If you add some object to your data target then update rules will be changed.
Regards
Karthik

Update rules deactivated after transporting cube with zero elimination on

Similar Messages

Maybe you are looking for