fixed and value mapping
I have gone through fixed and value mapping what i understood is correct or not?
fixed mapping depending on value of source we can map values between source and target/
value mapping depending on value of target we map between two
Sarvesh Singh replied
Fixed Value Mapping: Fixed Value is very useful when you have lots of conditions coming in one source fields during mapping, then to avoid the IfThenElse or UDF we go for Fixed Value mapping.
Example: if your source field contains 01 or 02 or 03 or.....12 and you want the result as JAN or FEB or MAR or ......... DEC.
Advantage: Using fixed value table you can see the result immediately in the mapping.
Disadvantage: If you have used the same fixed value mapping at several places in you mapping then in case of any change in fixed values you have to make the changes at several places. So in short fixed value mapping is not good from the maintenance point of view.
Value Mapping: Value Mapping also works in the same way as fixed value mapping, only the thing is you will get the result at run time only. And you have to define the value mapping in Integration directory.
Advantage: If you have used the same value mapping at several places in you mapping then in case of any changes in values you don't have to make the changes in you mapping, just make the changes in in value mapping in Integration Directory, that's it.
Disadvantage: you can't the see the result immediately in mapping. Results can be seen only at run time.
I hope this will give you a clear picture between Fixed Value & Value Mapping.