Use of Lookups in Conversion Mapping

Question Received: When we develop the data migration the data conversions will require lookup tables to allow translation of data from the legacy system to CC&B. Where would we specify the lookup tables? We think it may be in the Input Table Definition. Can the Constant Value or Predicate columns be used to specify a SQL statement or script that can translate a value via a lookup table? Does the lookup table have to be declared to the Mapper or does it just have to be in the Oracle database?

Answer: The Lookups and all other 'temporary' tables used as part of the conversion effort can be defined at either the input or staging table level, however if you are building them at the staging table level then you should use the standard CC&B ruling of prefixing the tables with 'CM_' . The Constant value can definitely be used to build SQL or PL/SQL components to be used for the mapping and these tables do not need to be defined within the mapper unless you are also planning on using the fields to perform simple mapping (much like you are able to do with the input tables).
Comments:

Post a Comment:
  • HTML Syntax: NOT allowed
About

Stuart Ramage

I am a Consulting Technical Manager for Oracle Corporation, and a member of the OU Black Belt Team, based in Hobart Tasmania.
I have worked in the Utility arena since 1999 on the Oracle UGBU product line, in a variety of roles including Conversion, Technical and Functional Architect.

Contact me on:

Search

Categories
Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today