Name

Data map object name. Enter a unique name.

Source Business Object

Source business object name. You must define this name in the Siebel Repository file.

Destination Business Object

Destination business object name. You can specify the same business object as both source and destination business object.

Inactive

Check this box to make the data map object inactive.

Name

Data map component name. Enter a unique name for each data map component in a data map object.

Source/Destination Business Component

Source or destination business component name.

If you specify a parent for this data map component, you must define this business component in the Siebel repository file as a child of the source or destination business object to which the parent data map component is mapped.

Parent

Parent data map component name.

If you:

• Specify a parent, the parent is mapped to particular source and destination business components. Generally, you map the child data map component to a child of those source and destination business components.
• Do not want to specify a parent, leave it empty to indicate that this is the root data map component. Each data map object can have one or more root data map components.

Inactive

Check this box to make the data map component inactive.

Source Search Specification/Source Sort Specification

Defines the source Buscomp search spec and sort spec. The value can be a literal search spec/sort spec string. It can also contain a named parameter. See Using Named Parameters in DTU. For example:

[Id] = [&ContactId]

where ContactId is a named parameter. At run time, only named parameters are replaced by their string values.

Source Record Row Number

One can selectively transfer only a subset of source Buscomp records. This can be defined in three formats:

• Start-End
• Start-
• Number

For example, 0-5, 4-, 0.

NOTE:  The row number starts at 0.

Operation Override

This option allows one to override the operation at the component level. For example, if the current operation is Insert, you can use this option to set some component to operate Update instead.

No Association

Y/N. Applicable to buscomps that have association list. By default, it is Y. Data Transfer Utilities first try to locate the desired destination record in the associate list. If successful, the located record is associated. Otherwise, a new record is created.

If N, association of existing records is not attempted. A new record is created instead.

Cached Updates

The valid values include:

• Source Component
• Destination Component
• Source/Destination Component

This is a performance enhancement option that defers sending SQL statements to the database until they can be sent together. Since none of the SQL statements is sent until the end, subsequent steps in the block cannot be dependant on a previous step having been committed to the database.

When you turn on this option, make sure to confirm all SQL statements are generated correctly and there is no inter-dependency.

Field Validation

Y/N. By default it is Y.

By default, setting field values in a Siebel BusComp triggers field value validation. If you have a bounded picklist, the new value is validated against the picklist and the fields in the pick maps are set. Disabling field validation also turns off picklists. It is a performance enhancement option.

Source Filter Specification

An expression in Siebel search specification syntax that is used to filter out records at the runtime. Only source records whose filter specification evaluates to be true are transferred.

Filter specification differs from search specification in that search specification is imposed at the database query, and filter specification is imposed while looping through the records.

Disable Order Management Signals

The valid values include

• Source Component
• Destination Component
• Source/Destination Components

When the Disable Order Management Signals option is imposed on the source or destination components, buscomp operations on those buscomps do not trigger order management signals during the data transfer process.

Source Type/Destination Type

Type of the source/destination field. Can be: Field, Expression, or Parameter:

• Field. A Siebel Buscomp field as defined in the .srf file.
• Parameter. A named parameter. The parameter must be prefixed with an ampersand (&). See Using Named Parameters in DTU. For example:

  &ContactId

• Expression. A Siebel calculation expression. See Calculation Expressions in DTU.

Source/Destination.

The contents of these fields depends on the source and destination type.

If the type is:

• Field, use Buscomp field name.
• Expression, use a Siebel calculation expression.
• Parameter, use a named parameter.

If the destination field is a calculated expression, then the record is not used to update the destination Buscomp. Instead, the result of the expression, evaluated at run time, is written back into the source field at the end of the data transfer operation of the component.

If the Source is:

• A Buscomp field, then source Buscomp is updated.
• A Parameter, the corresponding named parameter value is updated.
• An Expression, nothing happens.

Key

Matches the destination records with source records.

For example, the Update operation updates the record in the destination business component whose key destination fields all match those of the corresponding source fields.

Each data map component in general contains at least one key field.

When there is no key defined, if the operation is:

• Insert, DTU would proceed without checking if a duplicate record with the same key fields already exists.
• Update, it would update the current destination record.

If the destination business component is populated with an associated list business component, at least one key field is required.

Source/Destination Multi-Value Link

This link indicates that the source and destination fields are multi-value fields.

Data is transferred from one multi-value field to another by dividing data map fields into several subcomponents. All entries with the same source and destination multi-value link constitute a subcomponent. Specify a key for each subcomponent.

NOTE:  Data transfer from a multi-value field to a single-value field is not allowed.

Field Validation

Possible values are Y/N. The default is Y.

For more information, see the Field Value component in Table 56. If Field Validation option is defined at both component and field levels, the field level definition wins.

Sequence Field

Possible values are Y/N. The default value is N.

If the value is Y, a sequence number starting from 1 and increased by 1 is assigned to the destination field in each record.

Id Mapping Component

The option is used to re-wire foreign keys. The valid values are the names of data map components in the data map object. At run time, the source ID to destination ID mapping of the named data map component defines the foreign key mapping used by the data map field.

For example, when you copy from quote item to order item in a data map component Items, the hierarchical parent ID of a quote item cannot be literally copied to the order item parent ID. It needs to be re-wired to the corresponding order item ID. The ID mapping component must be Items, as the quote to order ID mapping is used to look up the order parent ID field using the value of the quote parent ID field.

For related information, see About Working with Hierarchical Business Components.