Originally posted by: TarunB
A restrictive design will force re-development of the map each time you have another country, and eventually this will become unwieldy and will have ongoing support costs.
A more comprehensive solution would be to use control-break logic on the Country field, to create dynamic groups during map execution. Each group is then passed through a functional map to a simple RUN map, which performs the mapping and outputs a file with a unique name.
The second map is therefore run as many times as you have Country codes in your original file. This design will automatically deal with any number of countries without needing to be amended if you have more or less countries in the original file, and you won't need to know the list of countries beforehand.
Again, with WTX there are many ways to achieve the same intended result. It's all about getting there in the most efficient manner, whilst keeping development and support efforts at a reasonable level.
#IBMSterlingTransformationExtender#DataExchange#IBM-Websphere-Transformation-Extender