Siebel Order Management Infrastructure Guide > Data Transfer Utilities Business Service >

Example of Defining Data Maps to Use with the DTU

This section shows how data mapping is defined to convert a quote into a sales order using the DTU. This is in essence Auto Quote function of the DTU. This example guides you though the mapping in the application.

The data copied over mainly consists of a three-level hierarchy:

• Header
• Line items
• Extended attributes (XA)

There are also other auxiliary entities such as payments, requested and promised scheduled lines. This example shows how header, line items and XA are mapped. Other entities are mapped like either line items or XA.

Finding the Data Map Object

You must find the data map object where the header, line items, and XA are mapped.

To find the data map object

1. Navigate to Administration - Application > Data Map Administration view.
2. In the Data Map Object list, select the record named QuoteToSalesOrder.

   The components of this data map object, including Header, Line Item, and XZ, appear in the Data Map Component list, below the Data Map Object list.

Mapping Headers

First, look at the mapping of the header component, to see how the quote header buscomp is mapped to the order header buscomp.

Notice that a calculation expression is used to look up the order type LOV to default the order type to sales order.

Two advanced options at the component level are of interest, because they are both important to improve performance:

• Cached Updates. Enables cached updates at the destination buscomp level. All updates at the order buscomp, and its descendant buscomps, are cached and issued in one batch to the database.
• Skip Order Management Signals. Because of this option, setting field values at the order buscomp does not trigger order management signals that usually would invoke pricing and eligibility workflows.

To view the header mapping

1. In the Data Map Component list, select the record named Header.
2. Look at the mapping in the Data Map field list.

   Notice that the record with Expression in the Source Type field has the expression LookupValue("FS_ORDER_TYPE","Sales Order"), which is used to default the order type to sales order.

3. Click the select button in the Advanced Options field of the Header record to see that Cached Updates and Skip Order Management Signals are selected as options.

Mapping Line Items

Next, look at the Line Item component.

The record defines its parent as Header, so it is invoked as a child of the Header component.

To improve performance, use simple buscomps instead of the line item buscomps used in the Siebel Call Center user interface. These improve performance because they are light-weight and, most important, because they are not defined as hierarchical buscomps.

Because they are not hierarchical, you must define their hierarchical parent fields in the mapping, using the Data Map Field records with Root Quote Item ID and Parent Quote Item ID in their Source field.

Both these records use the advanced option with the name ID Mapping Component to define the foreign keys to define hierarchical parent fields.

NOTE:  For backward compatibility, the application retains the advanced option MapId, which functions like ID Mapping Component.

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

To view the line item mapping

1. In the Data Map Component list, select the record named Line Item.
2. Look at Advanced Option and the mapping in the Data Map field list.

Mapping the Extended Attributes

Next, look at the XA component.

Note that deep XA buscomps are used. In Siebel Tools, these buscomps are defined as children of the header buscomps, not as children of line items. This improves performance, because one query can retrieve all grand-children XA attributes that belong to a quote. To mirror the Tools configuration, XA is defined as a child of Header in the Data Map Component.

As deep XA buscomps are defined as children of the header, we cannot rely on Siebel buscomp links to set the parent line item IDs, which are stored in the Object Id field. We also cannot literally take object ID from quote to order, as the quote XA object ID points to a quote item, and the order XA object ID points to an order line item. We need to use ID mapping to look up the foreign keys in the order side. This is realized by the advanced options:

• Name: ID Mapping Component
• Value: Line Item

NOTE:  For backward compatibility, the application retains the advanced option MapId, which functions like ID Mapping Component.

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

To view the line item mapping

1. In the Data Map Component list, select the record named XA.
2. Look at Advanced Option and the mapping in the Data Map field list.