About Many-to-Many Relationships for Custom Objects
By default, all relationships between Custom Objects 01, 02, and 03 and other record types are many-to-many. However, for all other custom object record types (for example, Custom Object 04), any relationship between the custom object record type and any other record type (including other custom object record types) is one-to-many by default.
You can create many-to-many relationships for custom object record types by using another custom object record type as an intersection table.
Example of Creating a Many-to-Many Relationship
Your company owns and manages conference centers, and provides conferencing facilities to other companies, government clients, and so on. You want to use a custom object record type to track information about events and another custom object record type to track information about the rooms that are used for each event. Each room is used for many events, and each event can use a number of rooms, so that you must have a many-to-many relationship between the record types.
To create this many-to-many relationship, you can use a third custom object record type as an intersection table to track information about each room booking, or session. You can then create a one-to-many relationship between rooms and sessions, and a one-to-many relationship between events and sessions, which gives you a many-to-many relationship between rooms and events.
The following procedure describes how to configure the record types and relationships for this example. Custom Objects 04, 05, and 06 are used for the new record types.
To configure a many-to-many relationship
NOTE: In addition to the configuration changes described in the preceding procedure, you can customize the new record types in the same way that you customize other record types. For information about customizing record types, see Record Type Application Customization Page.
|Published 5/4/2012||Copyright © 2005, 2012, Oracle. All rights reserved. Legal Notices.|