Application management : Tools : Enterprise Talk : Examples - import : Importing business objects - applying inheritance
Importing business objects - applying inheritance
When importing nested business objects, the business object hierarchy needs to defined in the import XML.
When you import a sub-order of an existing order without specifying the business object relationship, the import will fail. Consider the following example:
<UsrInternalWorkOrder>
<ParentOrderRef>2743.00</ParentOrderRef>
</UsrInternalWorkOrder>
In this example, because the business object hierarchy is not specified, the inheritance business logic is not applied and the import will fail because mandatory fields are not inherited from the existing order.
By specifying the business object relationship in your XML import definition, you ensure that the inheritance business logic is applied:
<UsrInternalWorkOrder>
<OrderNumber>2743.00</OrderNumber>
<UsrInternalWorkOrder>
<Description>Sub for 2743.00</Description>
</UsrInternalWorkOrder>
</UsrInternalWorkOrder>
In this example, the business object relationship is specified by nesting the XML. Consequently, the business logic is applied and the import will work.