Load Master data attributes error

[Former Member]

Hi all

We are currently loading 0PM_ORDER and 0NOTIFICATN. In 0PM_ORDER we have 0NOTIFICATN as navigational attribute and in 0NOTIFICATN we have 0PM_ORDER as a navigational attribute. Sometimes both documents are new and as a result will the 0PM_ORDER not load becuase 0NOTIFICATN does not exist and vice versa. If you try to load 0NOTIFICATN it generates an error stating that the SID does not exist for 0PM_ORDER. So we found ourselves in a catch 22 situation.

Is there a way to check for individual navigation attributes instead of using the generic update type in the scheduler?

Thanks

Karin

[Former Member]

I have made one of the attributes display and it solved the problem. Thank you all for your contribution.

[m_verbaan2]

Hi Karin,

From my POV you can do 2 things:

- disable Master Data check (but then you possibly clash with the companies BI strategy/foundations)

- write an abap routine (transformation of transfer rules) in which you check the existence of the PM order or Notification in the MD table (/BI0/PPM_ORDER resp. /BI0/PNOTIFICATN) in A or M version-> if not, skip the record or (even better) populate it with e.g. XXXXXXXXXX. This value will be overwritten the next time. If you skip the record the transactional data load might fail as well because of SID error.

Hope this helps!

Grtx

Marco

[Former Member]

Hi Marco

Thank you for the great assistance - just please elaborate on the "disable Master Data check". Are you referring to the check in the infopackage that will do it for all?

[m_verbaan2]

Hi Karin,

NP, glad to help you out...

Yep, the check in the InfoPackage on Update-tab....but logically this will have effect on all attributes loaded.

Grtx

Marco

[Former Member]

Hi,

If you make notification number as navigation attribute then it will create issues as it will try to create SID's for PM while loading the data and vice versa.

May be you can try to remove PM orders from the navigation of Notification number and make it display only and see what happenes.

Another soln is tricky but should work.

Load the notification numbers first only to the notification number infoobject by any mean and activate this master data.This could be through the a new DSO between the existing data source and master data.

I hope there will be attributes for notification number as well.

Once notification is loaded then load the master data for PM Orders and then load the master data again for notification infoobject from the data source through another DSO.

This may be tough in the case of delta as you will have to go for the same data load twice to the master data object.

In this case you can have to TWO DSO's in between the master data object and the data source one only for notification number and another one for all the its attributes.

Load the same delta from the data source to the bothe DSO.

Use the one with only notification number to load before the PO orders load to the notification infoobject and load the data from nother DSO with attributes after the PM loads have happened into the notification number objects.

You can wait for other replies as well if you are looking for easy solution.

Thanks

Ajeet

[Former Member]

Thanks Ajeet - awarded points