Business Scenario

When there are many things to cross-reference, because there are repeated elements, the SmartMapper Wizard is preferred.

An order is mapped to a common data model so that it might be published out to the application. Some subscribers might be interested in doing billing, shipping, provisioning, or planning. All subscribers must know that a new sales order was booked.

Because there are many things to cross-reference on a sales order, and because there are repeated elements like order lines, the SmartMapper Wizard is used.

SmartMapper Solution

The SmartMapper Wizard maps several fields to produce output that is used to generate an OAG_SalesOrder.

The following steps show an overview of how SmartMapper works:
  1. The inbound message is taken from a Siebel application. 
    <OrderNumber>100</OrderNumber>
<AccountId>abc-123</AccountId>
<OrderDate>2003-01-31</OrderDate>
<LineItems>
   <LineNumber>10</LineNumber>
   <ProductId>101111</ProductId>
   <Quantity>3</Quantity>
</LineItems>
<LineItems>
   <LineNumber>20</LineNumber>
   <ProductId>101048</ProductId>
   <Quantity>1</Quantity>
</LineItems>
  2. The inbound order number is cross-referenced with the generated order number.

    OrderNumber

    [1] 100

    ID [1] cross-referenced with remote ID:

    1YrEz4qfZMI4v-Hjdxzzw4r-zzw

    AccountId

    [1] abc-123

    PartyId [1] z6ir7Zm8ZJhH7-jeStzzw4IUzzw cross-referenced with remote PartyId:

    Wc5jtvOUZMI4xUHjdyzzw4r-zzw

  3. An outbound message is created to be understood by other services on the integration backbone. 
    <Id>1YrEz4qfZMI4v-Hjdxzzw4r-zzw</Id>
<PartyId>Wc5jtvOUZMI4xUHjdyzzw4r-zzw</PartyId>
<DocumentDateTime>2003-01-31</DocumentDateTime>
<Line>
   <LineNumber>QvmSp5B3ZMI4xUHjdzzzw4r-zzw</LineNumber>
   <ItemId>cd6Nfd5IZMI4xUHje-zzw4r-zzw</ItemId>   
   <OrderQuantity>3</OrderQuantity>
</Line>