Skip to Content
author's profile photo
Former Member

Update rule changes do not take effect

Hello everyone,

we are running BW 3.0B with the current patch levels.

Whenever we change an update rule for the cube and reactivate it the system responds with a success message.

However during the next data loads (after deleting all data out of the cubes) the changes in the update rules do not take effect.

I have tried to create a new infopackage for the load --> same result.

The only fix i have found so far is deleting the update rules and recreating them, which is starting to become a lot of work.

Did anyone ever have this problem? Any ideas what could be happening?

Thanks

Stephan Engler

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

3 Answers

  • author's profile photo
    Former Member
    May 04, 2004 at 09:51 PM

    Hi Stephan,

    I have faced the same problem as yours, did not find any elegant way to solve it.

    The crude way of deleting the update rule and recreating works.

    version: 3.0b.

    any cues are welcome.

    Thanks,

    Saket

    Add comment
    10|10000 characters needed characters exceeded

  • author's profile photo
    Former Member
    May 05, 2004 at 05:20 PM

    > Hello everyone,

    > we are running BW 3.0B with the current patch

    > levels.

    > Whenever we change an update rule for the cube and

    > reactivate it the system responds with a success

    > message.

    > However during the next data loads (after deleting

    > all data out of the cubes) the changes in the update

    > rules do not take effect.

    >

    > I have tried to create a new infopackage for the load

    > --> same result.

    >

    > The only fix i have found so far is deleting the

    > update rules and recreating them, which is starting

    > to become a lot of work.

    >

    > Did anyone ever have this problem? Any ideas what

    > could be happening?

    >

    Can you provide a specific example of the change you make? Is it to the update rule or to the transfer rule?

    - Stephen

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Its the update rule.

      say i change a formula from

      dateconv(substr(/bic/xxxx,0,8),'mm-dd-yy','')

      to

      dateconv(substr(/bic/xxxx,0,8),'dd-mm-yy','')

  • author's profile photo
    Former Member
    May 05, 2004 at 10:52 PM

    I don't know whether I am stating the obvious, but I always restart RSA1 transaction after making changes to Transfer or Update rules. I find (especially with transfer rules) that BW caches the program and restarting RSA1 forces the program buffer to be refreshed.

    I've not had to rebuild update rules to force a change in the update rules.

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      So it is the transfer rules you are having a problem with. After making a change to the transfer rules, and activating, do you go back in and re-activate a 2nd time?

      Are you seeing this behavior in both Dev and Production, or just Production?

      The reason I ask about re-activating a 2nd time, is that I have had a similiar issue, and usually going in and just re-re-activating the transfer rules (no, I didn't stutter) does the trick.

      We are on 3.0B also, but only up to SP15.

      - Stephen