Repository Manager Guide

Back Next

Design Object Dependencies

The following table describes dependencies between design objects.

Object Type	Dependencies
system	none
base object	columns match configuration validation rules If staging table lookups, match paths, and validation rules refer to other design objects. then such design objects are required dependencies. A foreign key does not imply a required dependency to the related design object. The foreign key is imported only if both design objects are imported. Before importing, the user is informed of any foreign keys that are not imported.
staging table	base object, columns, system
landing table	columns
query	Any design objects used in a query (such as base objects)
package	query
mapping	landing tables staging tables
cleanse function	Any other cleanse functions used. If a cleanse function imports one function from a custom Java library, all functions from that library are imported.
Hierarchy Manager	base objects and packages used in the configuration
business entities	base objects
business entity field	base object column parent business entity node
business entity child base object	relationship between parent base object and child base object
business entity referenceOne and referenceMany element	referenced base object
business entity service	inputs that are generated from business entity
writeCO business entity service	business entity definitions
searchCO business entity service	business entity definitions
business entities based on Hierarchy Manager enabled base objects	Hierarchy Manager items such as hierarchies and relationship types