cancel
Showing results for 
Search instead for 
Did you mean: 

Tricky! Change of navi-attribute values in ABAP and use in selections

Former Member
0 Kudos

Hi gurus,

now I have a teaser that really keeps me busy, and which might be interesting for some of you:

we use several statuses in our <u>Demand Planning in SCM 5.0</u>, some of which can be switched by using a user-function macro which just basically is a ABAP function module that <u>changes navigation attribute values directly on the database</u>, meaning in the master data tables of the respective characteristic.

Now, the code works, the values are changed accordingly, leaving the data set in object status "active" - <b>BUT</b>:

<i>when we call a selection, it still shows the old values, even after activating master data or running the attribute change run!</i>

This is not what we expected. Our wish was, that once the table was updated with the correct field values, we would also see them in our selections.

<u>Details:</u>

we have two statuses as navi-attributes to an article:

<i>DP:</i> YES/NO, and

<i>oDP:</i> YES/NO

Combinations originally are: <i>DP</i> YES/<i>oDP</i> NO

After the status change macro, the table shows the following, as expected:

<i>DP</i> NO/<i>oDP</i> YES

As we have two selections, one on DP status "YES", the other one on oDP status "YES", we would like to see the article vanish in the first selection and show up in the other one...

Does anybody have an idea what is wrong and what we can do to have to proper navi-attribute values from the master data table in the selection? Does the selection not read from the database but from a buffer?

Looking forward to your answers,

Klaus

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

OK folks,

I made the respective changes in the coding, and hohoho, the stuff works. You do not even have to activate or have the change-run after the direct update on the table. SWEET!

So, one problem down, more to come...

Cheers,

Klaus

Former Member
0 Kudos

Yes,

I have run this report, also used the respective transaction.

But as I mentioned, I checked also the SIDs in the master data table, and they were wrong. So the function module changed only the entries in the P-table, the X-table with the SIDs was not touched at all.

I will have the code updated, test it and then come back to you guys.. my feeling is that the problem is not so tricky at all....

Cheers,

Klaus

Former Member
0 Kudos

Hi Klaus,

Are you using the program 'RSDDS_AGGREGATES_MAINTAIN' for activating the master data?

Regards,

Siva.

Former Member
0 Kudos

Hi Klaus,

Tricky indeed....

I think you did but never know... : did you check in the table that your the object version is on "A" (active) after applying the hierarchie / attribute change run ? Sometimes it doesn't work....

Fabrice

Former Member
0 Kudos

Hi Fabrice,

yes indeed, I did check the object version, and it is A.

Problem is, the function module changes the data record which is "A" anyway. So the changed data record is active - however, I just had a look at the SID master data table, and it looks that direct changes to the P-table do not affect the X-table where the SIDs are stored. So I guess I will also have to update the X-table with the correct SID-values.

If this works, I let you know. We will be using this change by ABAP quite often, it is rather useful.

Regards and thanks for your prompt reply,

Klaus