Siebel Order Management Infrastructure Guide > Projected Asset Cache >

About Projected Asset Cache

The Projected Asset Cache is a persistent business service that loads all assets, open orders, and quote line items matching a specified search specification into memory using the most efficient SQL queries possible. Projected Asset Cache is used by the Compound Product Validation. It is used by Network Validation to populate the network nodes pick applet. It is also used by Compatibility for cross-product compatibility checking. The Projected Asset Cache can be used by any application that needs a consolidated view of product instances across the quote-to-order-to-asset lifecycle.

Projected Asset Cache automatically converts between the different field names in the Quote, Order, and Asset business components. The cache is always stored and queried using the Asset field names. Open Order and Quote line items are applied to the existing assets to generate a future projected state of the assets for a specified date.

The Projected Asset Cache business service supports multiple concurrent cache instances. When the cache is initialized, a unique identifier is returned. Subsequent queries must specify the identifier of the cache to query.

There are two key functions to the Projected Asset Cache:

Retrieve Data

To retrieve data, the Projected Asset Cache queries the following business components:

  • Quote Item
    • Quote Item XA
  • Order Entry - Line Item
    • Order Item XA
  • Asset Mgmt - Asset
    • Asset Mgmt - Asset XA

Within these business components, Projected Asset Cache limits the retrieval of data to only those fields and attributes required by the rules checkers. To find this information, the Projected Asset Cache:

  • Loads all the Asset records
  • Finds all open orders associated with these Asset records
  • Loads all quote line items for the current quote associated with the Compound Product.

The Projected Asset Cache then uses a predefined Field Mapping Service business service to translate the field names among business components.

Build the Future Requested State

After retrieving the data, the Projected Asset Cache builds the future requested state of the product instances. It takes into consideration all assets matching the search specification and applies all open orders due to complete prior to the specified date. It then applies the current quote or order to generate the future requested state.

The array of projected assets generated is stored in the business service. It is available for performing validations until it is released or a new initialization of the Projected Asset Cache occurs.

Because the Projected Asset Cache can include any field in the Asset Mgmt - Asset business component, and because it also includes data from the Quote Item and Order Line Item business components, the fields must be mapped across three different business components.

This mapping is done by the Field Mapping Service business service. You add mappings by creating new user properties on the Field Mapping Service business service.

Table 48 gives an example of one field mapping, which translates the Service Point Serial Number field in the Asset Mgmt - Asset business component to the corresponding field in the Quote Item business component and in the Order Entry - Line Item business component.

Table 48. Sample of Field Mappings

Asset Mgmt - Asset:Quote Item Map 2

[Service Point Serial Number]:[Service Point]

Asset Mgmt - Asset:Order Entry - Line Items Map 2

[Service Point Serial Number]:[Service Point]

NOTE:  If you add custom fields to the business components from which the Projected Asset Cache retrieves data, and you want to use these fields either in simple expression rules or custom rules as part of a custom business service, you must add new field mappings.

Siebel Order Management Infrastructure Guide Copyright © 2006, Oracle. All rights reserved.