Example 3 - Identification of ambiguous parent relations

Export quantities for Supplier Allocations class, and ambiguous relation with Products.

Example 3

The possible paths from Supplier Allocations to Products are:

  • Supplier Allocations > Products At Suppliers > Products
  • Supplier Allocations > Products At Locations > Products
Note: The path from Supplier Allocations > Products At Locations > Products is selected, over the path through the Products At Suppliers, because Products At Locations is a component of Supplier Allocations allocation class, which has a higher priority as compared to a parent relation.

This table lists the mapping required to export Supplier Allocations and related classes:

Mapped field Description
Products.name Name of the related Products resource
Locations.name Name of the related Locations resource
Suppliers.name Name of the related Suppliers resource
Supplier Allocations.planned purchase Value of property "planned purchase for Supplier Allocations resource and bucket
Products At Suppliers.purchase Value of property “purchase” for Products At Suppliers resource and bucket
Products.Item Type Value for “Item Type” attribute from the relating Products resource
bucket.start Bucket start date

The Export process identifies the ‘Supplier Allocations’ as the common child class and export each mapped field values for Supplier Allocations resource and bucket in the planning horizon.

References to relating class fields are resolved to the resource from the perspective of each Supplier Allocations resource.

In this example:

  • Suppliers resource is a direct component of the ‘Supplier Allocations’ resource.
  • Locations and Products resources are components of Products At Locations, which is a direct component of the Supplier Allocations resource.