Originally posted by: RichMcFate
The message is entirely dependent upon the input data and type tree. The mapping rules are not relevant.
If the map is unable to find all required components of the input card root object, then it reports, "One or more inputs is invalid." If it can find instances of all required objects, but then discovers data that it doesn't recognize, it reports, "Input valid but unknown data found."
In your case, I suspect the HEADER object is required and the range of the DETAIL group is specified as (s) or (1:s). So when the bad numeric object was in the HEADER, the map failed to find a valid required object (the HEADER) so it reported that one or more inputs was invalid. In the case where the bad value was in a DETAIL object, the map had already found a HEADER and, either the DETAIL was specified as (s), which means that it isn't required, or the bad value was after the first DETAIL group. In either of those two cases, all required objects had been found, so the input was valid but everything after the bad value was unrecognized. So it reported that the input was valid but there was unknown data following the part that it recognized.
Hope this helps,
Rich
#DataExchange#IBMSterlingTransformationExtender#IBM-Websphere-Transformation-Extender