Excluding Standard price from MATMAS05 while processing Inbound/Outbound IDOC

[former_member203117]

Dear Team,

When replicating my material from Hub to ECC using IDOC (MATMAS05), I want to exclude the validations of standard price, Item proposal and Valuation type. Since the validations of these three data is creating errors and my IDOC is not getting posted.

Any help will be sincerely appreciated.

Regards,

Tushar.

[former_member192358 · Accepted solution]

Hi Tushar,

had to correct my last statement based on some discussion with our experts. The question above - why do MDG and ECC behave different for creation is still a valid one.

Let's take the field standard price as an example.

1) Create:

a) since it can be a mandatory field, depending on customizing,  MDG can create that field and send it via IDOC and it shall be sucessfully posted in ECC.

b) Or you don't want to send it - then safest bet is to remove it from the screen, and from governance scope.

2) Change:

a) make sure that after the initial creation on MDG side that field is never touched /changed again. Take it off the UI or make it read-only. Since the IDOC sends based on the active data, it will try to send the original value - which may have changed on ECC and on ECC the field may not be changed by MM-based transactions maintain_material_dark anyhow. The safest way is to use the BADI during the IDOC inbound on ECC - there you can find out if material already exists and then you can set the "no data" indicator for all fields that you don't want to be updated via MDG.

b) since you never sent it during create same for change

3) Receiving System: on the receiving system there could be e.g. monthly calculation runs that update prices. Therefore the values on the MDG hub may not be the same because here we keep the initial value. You could use e.g. a BCV/Sidepanel query to display the values for a given target system.

We also discussed taking the fields out of the IDOC - but for case a) sending it in create and then never again - this can get tricky.

That should work for the other fields as well in the described MDG-Hub mode.

If you use Co-Deployment it could get more tricky if there are open change-requests. Then you will run into issues with the snapshot data in MDG which gets rather complex to solve.

BR, (the other) Ingo

[former_member203117]

Dear Team,

Any ideas would be sincerely appreciated.

Regards,

Tushar.

[d024348]

Hi, I understand that you want to avoid validation errors during IDoc inbound in the target system.

If the data is consistent in the hub, how can there be validation errors in the target system? Are they custom coded (via BADI), or are they different field control settings in transaction OMSR, or do they result from some other difference in the system setup/customizing?

It's not possible to deactivate single checks during IDoc inbound, a material is consistent or it isn't.

Regards, Ingo

[former_member203117]

HI Ingo,

The standard price is calculated later in the ECC. When a material is created the standard price is not available.

Thanks & Regards,

Tushar.

[d024348]

Yes, but my question was: If the material is inconsistent without a standard price in the target, how can it be consistent without a standard price in the hub?

Regards, Ingo Bruß

[former_member203117]

Hi,

After creation of the Material, Later when the standard price is available a change is triggered.

Regards,

Tushar.