Example of How the Entity Relationship Designer Filters Business Components

The following image shows an example entity relationship diagram that contains two entities (Entity A and Entity C) and one relationship.

Example of an Entity Relationship Diagram: This image is described in the surrounding text.

The following table describes the business components that are available to bind to Entity C. The business components that are available to bind depends on how the Entity Relationship Designer filters them.

Entity A	Relationship	Entity C	Business Components Available for Binding
Unbound	Any	Unbound	All business components are available for binding.
Bound	one-to-one	Unbound	A business component that contains a join to the primary table of the business component that is bound to Entity A is available for binding.
Bound	one-to-many	Unbound	The following business components are available for binding: A business component that contains a link to the business component that is bound to Entity A, where the business component bound to Entity A is the parent. A business component that contains a join to the primary table of the business component that is bound to Entity A.
Bound	many-to-one	Unbound	The following business components are available for binding: A business component whose primary table is the table that is joined to the business component that is bound to Entity A. A business component that contains a link with the business component that is bound to Entity A, where the business component bound to Entity A is the child.
Bound	many-to-many	Unbound	A business component that is in the intersection of the one-to-many and many-to-one examples that this topic describes is available for binding.