Siebel Application Deployment Manager Guide > Creating a Siebel ADM Package > Process of Creating Siebel ADM Deployment Units from Database Types >

About ADM Data Type Relationships

This topic is part of Process of Creating Siebel ADM Deployment Units from Database Types.

Creating Application Deployment Manager (ADM) data type relationships is only necessary if certain data types must be deployed before other types. Creating this relationship makes sure that related data types are deployed as a single transaction to the target system. If any of the related data types are not applied correctly, then all related data types are not migrated to the target system.

ADM data type relationships are relationships between data types; that is, there are also relationships between different entities internally within data types. These relationships are defined within the Integration Object for a data type. For descriptions on creating or removing data type relationships, see Creating ADM Data Type Relationships.

Example of ADM Data Type Relationship

An example of an ADM data type relationship is as follows: a List of Values (LOV) with a State Model configured on that LOV. Therefore, the LOV must be governed by a State Model.

To set up this relationship in ADM, add the LOV data type as a child record to the State Model data type.

When this relationship is set up, the records of the LOV (LOV Type record and LOV value records) are inserted into the database first followed by the State Model records. If there is an error in moving either the State Model or the LOV records, then both are not allowed to exist separately on the target system. If the State Model encounters a database error, then the previously inserted LOV records are removed (rolled back) so that the errors are corrected and the session can be retried.