Siebel Data Maps : Making Integration Easy

Hello All,

let us explore the Use of Integration Data Maps in this Post.

Integration data maps make it possible to map two IO's i.e. enables to pass fields value from one IO to other, irrespective of the level of Hierarchy.

Recently I had a requirement wherein i had to Update Users Opt In Preference for Receiving Emails and capture date of this activity, also there were multiple contacts with same mobile numbers.

This can be achieved Via multiple ways .

1. From the view of a Developer relatively new to Siebel , 

• Create a BS 
• Search for the contact with the given Input
• Loop through it, and Update the records

2. From the view of a Senior Developer,

• Create a Workflow 
• Search for Record using Siebel Operation, Find Record 
• Use Looping via Next Record Method
• Update the Record

3. From the view of Siebel Integration Developer

• Create a Workflow
• Create a IO/Use Existing IO based on Contact
• Search Using EAI Siebel Adapter
• Use Data map with Same Source and Destination IO, and Provide the value in Destination IO
• Get the Output of Data Mapping , and Upset using EAI Siebel Adapter 

I used the 3rd Approach and sample Workflow Looked like,

To call data map we need to Use

BS: EAI Data Transformation
Method: Execute

Input:
Map Name: Name of Data Map
SiebelMessage: The Hierarchy from EAI Siebel Adapter

if we need to pass any Values from Workflow like Process Properties or Literal Values to Data Map we can pass these by Defing those in Input
and can be used in Data Map with and & symbol i.e. [&ProcessPropertyName]