Split - error when mapping generated

Question

I have a mapping that uses a splitter to create 3 groups using the following conditions based on the value in the TYPE column:
Group A: TYPE >= 4
Group B: TYPE in (2, 3)
Group C: TYPE = 1
When I generate the mapping from the mapping designer, or deploy it, or debug it, the condition for group B is always wrong - it always generates TYPE = 1. I've tried editing the condition to have TYPE between 2 and 3, and TYPE = 2 OR TYPE = 3, but it makes no difference.
What's going on here? Is there any way to force OWB to generate this condition correctly, or do I just have to go and edit the PL/SQL after the mapping is deployed?
Thanks for any help,
Rachel

Answer 1

Rachel
You should not edit the generated code.
What version of OWB are you using. I have certainly found on 9.2.0.4 that OWB got "confused" and would not necessarily reflect the changes made to the mapping. Was very frustrating. Seems after a while it seems to recognise the changes. Persevere.
One possibility is to add a new splitter to the mapping, map the same attributes as the original splitter, and then add the actual conditions. Map the output from the splitter as normal and remove the old splitter. Just to confirm that the splitter is not confusing itself. Make a copy of the mapping before you do this.