Change Pointer for MATMAS

[Former Member]

Hi, I want a complete Idoc for MATMAS when std. price (PR00) changes and want to add an entry in transaction BD52. When I try to add Table KONP and field name KBETR, it says that table KONP for object class MATERIAL does not exist. Any suggestions?

Thanks in advance!

[Former Member]

Pls check this & see if this is what you are looking for...

There should be an entry already in the BD52 table for MATMAS with the following values...

Object-MATERIAL

Table Name-MBEW

Field Name-STPRS

This is for the standard price field of material master...

Thanks,

Renjith

[Former Member]

MBEW-STPRS is standard purchasing price whilst KONP-KBETR is the standard customer price. I need the triggering effect on the customer price.

Thanks

[christian_wohlfahrt]

Hi Rune!

Surely you can't go for a MBEW field - here article valuation is handled, but not wholesales price PR00.

You can add a lot of relevant fields for change pointer for MATMAS-IDOC, but they all have in common, that object key of this change is an article number. This is different for the conditions. Here object key is KONH-KNUMH key. There has to be (simple) program logic to search for the corresponding article number -> with simple customizing you can't get this goal.

But a different (silly?) question: why do you want to have a MATMAS IDOC, if a condition has changed? There is no condition segment in MATMAS. You might trigger a lot of identical IDOCS, but no one will contain your changes.

Conditions are distributed with COND_A (or WP_PLU02 in retail).

But if you really want to have a MATMAS, create an own message, execution by own function module, there you can convert condition number into article number and trigger a MATMAS idoc (like BD10).

Regards,

Christian

[Former Member]

Thanks for the answer, I will dive deeper into it later.

I want a MATMAS Idoc because we have a legacy system that has to be updated when a change in material master occure. The update must contain all (mapped) data every time, and not just the changes. And the KONP-KBETR is one of the fields to watch for changes.

Thanks

[christian_wohlfahrt]

Hi,

sounds like you need to create some more segments for a Z-MATMAS / you might trigger two (or more) IDOCS based on one change. Otherwise you won't get masterdata and conditions.

Christian

[Former Member]

Hi, thanks for answers.

The triggering effect must be on the price, not the condition. So if someone changes the price, an Idoc for Matmas must be created. We now have this in effect on changes on Material Master.

Anyone?

[christian_wohlfahrt]

Yes, like I said before: create an own message, execution by own function module, there you can convert condition number into article number and trigger a MATMAS idoc (like BD10).

Maybe I should add: assign condition relevant fields to the message

[mandar_shete]

Hi,

Change pointer can activate for a pertucular message type from BD53.