Siebel Order Management Infrastructure Guide > Copy Service >

About Copy Service


The ISS Copy business service (or Copy service), provides a mechanism for copying data from one business object to another. The Administration - Application screen, then Data Map Administration views allow you to define the business components and fields to be copied in a given situation.

NOTE:  With Copy Service, data map object definitions are cached for each object manager. If you make changes to the definitions, you must restart the Siebel server.

Data Map Objects

Data map objects indicate the data that is being transferred from the source business object to the destination business object. You can use the Administration - Application screen, then Data Map Administration screen to define data map objects. Only Siebel administrators should have access to this screen. Data map objects are described in Table 53.

Table 53. Data Map Objects
Object
Description

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.

You can import or export data map objects as XML files through the Data Map Object applet menu items: XML Import, XML Export.

Data Map Components

Data map components define the mapping at the child business component level. Each data map object can contain multiple data map components. You can arrange data map components in a parent-child hierarchy, but you must specify a parent for all except one data map component. The parentless data map component is called the root data map component. Data map components are described in Table 54.

Table 54. Data Map Components
Component
Description

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 only one root data map component.

Inactive

Check this box to make the data map component inactive.

Advanced Options

Not available for Copy Service.

Data Map Fields

Data map fields define the field-to-field mapping, identifying the source and target fields. The source can be either a simple field or an expression. Data map fields are described in Table 55.

Table 55. Data Map Fields
Field
Description

Source Type/Destination Type

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

  • Field. A Siebel Buscomp field as defined in the SRF.
  • Expression. A Siebel calculation expression.

Source/Destination.

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

If the destination type is:

  • Field, it should be a Buscomp field name.
  • Expression, it should be a Siebel calculation expression.

    NOTE:  Parameter type is not available for Copy Service.

Source/Destination Multi-Value Link

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

NOTE:  Multi-value fields cannot be used for Copy Service.

Advanced Options

  • MapId. If MapId is defined, the destination ID is mapped based on the source instance ID for the mapping field.
  • SequenceField. If SequenceField is defined for the field, the sequence number is calculated from Copy service.
Siebel Order Management Infrastructure Guide Copyright © 2008, Oracle and/or its affiliates. All rights reserved. Legal Notices.