Load Master data attributes error
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?