1. Order Management Infrastructure Guide
  2. Auto Match

Auto Match

Auto Match compares the input product instance to the customizable product definition. For each product or class that cannot be located in the definition of the relationship specified by the product instance, Auto Match searches for that product or class in another relationship under the same parent in the product definition hierarchy. If the product or class exists in one or more relationships, the product instance is updated so that the product or class is associated with the first of those relationships. If the product or class cannot be found in any relationship in the customizable product definition, the product or class is removed from the product instance. The details of each change made by Auto Match are added to the AutoMatchReport and returned as the output of the method with the modified product instance.

Arguments

Argument Description

SiebelMessage

[in] Product instance to be transformed by Auto Match.

AutoMatchReport

[in] Product instance that has been transformed by Auto Match.

Examples

Review the following Auto match method examples.

Service Profile Upgraded from SCE 6.x

The following example shows how this method is used when a service profile record is upgraded.

Note: In the following examples, a port is an instance of a relationship.

  1. The following diagram shows a service profile record that has been upgraded from SCE 6.x:

    In this image, Family Wireless Bundle has Wireless Service, Wireless Service, and Installation. Wireless Service has Nokia 6100. Wireless Service has Nokia 6800, Call Forwarding, and Installation.

  2. The customizable product definition was reimplemented as shown in the following diagram (rounded boxes represent a class).


    In this image, Family Wireless Bundle has Wireless Service and Installation. Wireless Service has CDMA Cell Phone, Calling Feature, and Installation.

  3. Auto match assigns the following port IDs without error, as shown in the following diagram.


    In this image, Family Wireless Bundle has Wireless Service, Wireless Service, and Installation. Wireless Service has Nokia 6100. Wireless Service has Nokia 6800, Call Forwarding, and Installation.
Note: The Installation component port IDs were assigned without ambiguity because each of their parent components only have one port that supports the Installation product. Also, the erroneous port ID originally assigned to the Nokia cell phones was replaced by the correct port ID without generating an error.

Service Profile Imported from a Legacy System

The following example shows how this method is used when a service profile is imported from a legacy system.

  1. The service profile record shown in the following diagram was imported from a legacy system.


    In this image, Local Line has DSL Service, Call Forwarding, and Installation. DSL Service has Voice Mail.

  2. The customizable product definition is shown in the following diagram.


    In this image, Local Line has Call Forwarding, Calling Feature, and Installation.

  3. Auto match does its best to assign port IDs, as shown in the following diagram.


    In this image, Local Line has Voice Mail, Call Forwarding, and Installation.
Note: The DSL Service component was deleted because it does not exist beneath Local Line. The Voice-Mail component was reparented and associated with the Calling Features class. The Call Forwarding component could have been associated with the product relationship or as a member of the Calling Features class. Hence, it was assigned to the first port found (the product relationship) and a warning message was issued.