Update rules issue

[Former Member]

Hello guys

I created some update rules and loaded data without any problem, but when i checked the rules recently they all have a red status button.

When i run a check it lists a number of Infoobjects and says that no routine has been created for the infoobject. I have loaded data with this update rule as recently as today so can anyone assist in what might be going wrong?

Thanks guys

[Former Member · Accepted solution]

Hi Ravi,

Is your cube getting data from another data target (ODS/Cube). Anythin changed in the base data target also deactivates the update rules.

Anyways, activate the update rules as described in my previous post.

Bye

Dinesh

(Do not forget to assign points!!)

[Former Member · Accepted solution]

When i try and activate it give me the routine error that i described earlier

[former_member188975 · Accepted solution]

Hi Ravi,

In your update rules, open up the update rule definition for any InfoObject which is Red and take a look at what the system is doing/mapping. My guess is that it is mapping to Routine, whereas it should be mapped to Sourec Char. Try changing this and see if it works.

Hope this helps...

[Former Member · Accepted solution]

Anyway,

if you are seeing this situation in your prod environment it's possible that some requests impacted to your UR !

Anyway, to solve to solve your issue, it's enough, for every red row, to do a correct mapping (with a source char or write some routine)!

Anyway, since this is (I think) an inactive version, you can switch it to the active one

Bye,

Roberto

[Former Member]

Hi Ravi.

Probably you have changed some InfoObj (type or navigational attribute or time dependent) of type char, or you have changed the InfoSource related. If you have changed an IO of type char you have also to check the status of the InfoCube. You can check in Transport system if you have transported some changes in IS or IO.

The last possible situation is if you have used Formulas in Update Rules and not ABAP routines. Formulas are not very stable, and are not recommended.

In particular use transaction RSU3 to check UR.

Ciao.

Riccardo

[Former Member]

Hi Ravi,

Creating a multiprovider will not deactivate/change the update rules. Did you make any of the attributes navigational OR added a new KF/Characteristic in your cube?.

Just assign all the fields in your update rules and then activate it. Remember you also need to assign the base & time characteristics in the update rules.

Hope this helps.

Bye

Dinesh

[Former Member]

No, I did not make any of the attributes navigational OR add a new KF/Characteristic in the cube. I did not touch the update rules until i saw that it was not active.

[Former Member]

Normally, if theres a mismatch or no routine when mapping in any of the fields i.e characteristics or key figures then all the key figures status is set in RED. Check you routines and also your characteristics and see there mapping to all in the structure.

[Former Member]

but i've used these rules for weeks with no problem until now

[Former Member]

Lets do some analysis.

If you havent changed or modified any of the routines, is there a possibility someone was working on them?

Then also please check whether the charcteristics are also mapped properly. as this also causes the RED status.

Then again, check and see if all the key figures have some mapping for the data thats coming in, also see why do some analysis like why the update rul is set inactive. Sometimes of dependencies between the datamarts also casue the rules to be set inactive.

[Former Member]

I created a multiprovider on the cube, could this be an issue?