Going Live with Siebel Business Applications > Migrating Customizations Between Applications >
About ADM Deployment Filters
Application Deployment Manager (ADM) deployment filters allow the migration of specially selected records of a particular data type. Creating ADM deployment filters is a part of creating ADM deployment projects.
For information on creating deployment filters in deployment projects, see Creating ADM Deployment Filters.
ADM deployment filters can also be set or modified when creating deployment sessions. See Creating Deployment Sessions Using ADM for further information on this task.
The deployment filter applies to the primary business component defined within an integration object, and can be set on any field defined on the primary business component and present in the integration object. Each data type is represented by a Siebel integration object. See Creating Integration Objects for ADM for further information on Siebel integration objects. For detailed information on business components, see Configuring Siebel Business Applications.
Filtering is also possible on the child business components to exclude or include certain records. See the end of this topic for an example
The format for the deployment filter value entered into the Filter field of the data type record is as follows:
Field_Name = The name of the field on which to filter records. For a list of available fields for each data type, click the select button in the Field List field. Make sure the field name is enclosed in brackets.
operator = A standard Siebel query operator that defines the filter. For example,
=. For a list of Siebel query operators, see Using Siebel Tools.
= The criterion by which to filter the field name. The wild card character can be used as part of the criterion. For example, names beginning with
'A*'. The filter criterion is case-sensitive and must be enclosed in quotes.
NOTE: Use multiple filters for one data type by using the logical AND or OR operators.
Some deployment filter examples follow:
[Name] like 'ABC*' or [Name] = 'My StateModel'
This example filters the data type State Models using the Name field. The primary business component for State Models is State Model, the field containing the state model name is Name.
[Activation Date]>'12/29/2001 14:58:29'
This example filters the data type Assignment Rules using the Activation Date field. All assignment rules with a start date greater than 12/29/2001 are filtered for migration.
[Value]='ACCOUNT_STATUS' AND [List Of Values Child (UDA).Language] ='ENU'
This example filters the data type LOV using the Value field and the child business component List of Values Child (UDA).Language. The filter only allows deployment of the English language LOVs for the ACCOUNT_STATUS LOV type.