0% found this document useful (0 votes)
20 views

04 - Data Mapping

Uploaded by

abhishek040599
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
20 views

04 - Data Mapping

Uploaded by

abhishek040599
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 19

Data Mapping

Data Mapping

§ Is required when the external application cannot


accept or deliver data structured by a Siebel
integration object
Choices for Data Mapping

§ Internal to the Siebel application


§ Use the EAI Data Transformation Engine business
service
§ Create maps declaratively in the Siebel client
§ Use a custom business service
§ Create maps directly in scripts
§ External to the Siebel application
§ Incorporate data mapping into the external application
§ Not common
§ Use middleware to perform the mapping
EAI Data Transformation Engine

§ Is an EAI business service that transforms an


integration object instance from one structure to
another
§ Uses data transformation maps that:
§ Are created declaratively in the Siebel client
§ Are stored in the Siebel database
§ Is referred to as the EAI Data Mapping Engine in
picklists
§ Is often referred to as the Siebel Data Mapper
Data Map

§ Is a mapping between integration objects


representing source and target data structures
§ Is unidirectional
§ Separate maps are required for:
§ Source à Target
§ Target à Source
Data Map Continued

§ Consists of:
§ A source integration object (IO) to target IO mapping
§ Multiple source integration components (IC) to target
IC mappings
§ Multiple source integration component fields (ICF) to
target ICF mappings
Data Map Editor

§ Is used to examine, create, and modify data maps


§ Is a set of views in the Siebel client
§ Select Administration - Integration > Data Map Editor
Conditional Mapping

§ Mapping of integration components can be


conditional
§ Results in selective mapping of the integration
components in the source IO instance
§ Specified by a search specification
Creating a Data Map

1. Create an Integration Object Map

2. Auto-Map the Components

3. Create Integration Component Maps

4. Create Integration Field Maps

5. Validate the Map


1. Create an Integration Object Map

§ Create a new integration object map in the Data Map


Editor
§ Specify the source and target integration objects
2. Auto-Map the Components

§ Optionally, click the Auto-Map button to generate


mappings as follows
§ Root integration components are mapped regardless of
name
§ All other child components are mapped if names are
the same
§ Child components and fields are mapped:
§ If names are the same
§ Only if parent components are also mapped
3. Create Integration Component Maps

§ In the Integration Component Map list


§ Create a component map and enter a name for it
§ Select the source integration component to map
§ Select the target integration component to map
§ Enter the name of the parent integration component
map (if any)
§ Enter parameters for conditional mapping
§ Source Search Specification
§ Precondition: source component must meet for mapping to
occur
§ Postcondition: target component must meet for mapping
to occur
4. Create Integration Field Maps

§ In the Integration Field Map view


§ Create an integration field map
§ Select or enter a source expression, which can be:
§ A literal value, such as the name of a source field
§ Based on scripting to parse data or query for a specific
value
§ Select a target field name
Validate the Map

§ In the Data Map Editor select the integration object


map
§ Click the Validate button
Purging the Cache

§ Data maps are cached in the client application


§ After a map has been created or modified, the cache
must be cleared
§ To purge the cache:
§ Create a workflow with an EAI Data Mapping Engine
business service step
§ Set the method to Purge (requires no arguments)
§ Execute the workflow to clear the cache
Using a Data Map

§ Use the EAI Data Mapping Engine business service in


integration workflow to convert Siebel messages
§ Add the business step between the EAI Siebel Adapter
and EAI XML Converter
§ Set the method to Execute
§ Identify the map to use
§ Assign MapName input argument
EAI Value Maps

§ Support mapping of integration component fields


where the value of the fields differ between the
source and target application
§ Example: Country Names (Canada versus CA)
§ Example: Unit of measure (Each versus EA)
§ Are edited using the EAI Lookup list
§ Select Administration - Integration > EAI Value Maps
Using EAI Value Maps

§ Source expression in an integration field map can


reference the EAI value maps
§ Use the EAILookupSiebel function for inbound value
mapping
§ EAILookupSiebel(“<ValueMap>”,[<FieldName>],
[<DefaultValue>])
§ Use the EAILookupExternal function for outbound value
mapping
Custom Mapping

§ Uses a custom business service


§ Scripts must be written to specify the mapping
§ Consider using custom mapping when:
§ Complex mapping involving programmatic logic
§ External data is not easily described by an external
integration object
§ Otherwise, use the Siebel Data Mapper

You might also like