Originally posted by: raj1

if the restriction is failed in the system which is in production ,how should we handle this without touching the type tree
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender
#DataExchange

Originally posted by: SystemAdmin

Do you mean, if the input fails against a restriction in the type tree, how should you handle the bad data?
#IBMSterlingTransformationExtender
#DataExchange
#IBM-Websphere-Transformation-Extender

Originally posted by: raj1

Yes,you are more clear about my question.Answer me.
#IBM-Websphere-Transformation-Extender
#DataExchange
#IBMSterlingTransformationExtender

Originally posted by: SystemAdmin

Say please.
#DataExchange
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender

Originally posted by: jvanboga

Assuming we can't update the type tree, in our shop when we receive a file that contains a value that isn't allowed, not part of the restriction list, the map fails and the file is referred to a business analyst. The analyst the works with the Trading Partner to get it fixed. Until the system gets a corrected file the data is considered non-compliant and will not be processed. Sometimes we get a new file, sometimes the BA fixes the bad file.

We have different ways of dealing with internal files. Regardless, it seems like how you deal with this type of issue is up to your company.

jvanboga

PS: If you can update your type tree you could make the field a choice group. Once choice is for values on the restriction list the other for those that aren't.

Message was edited by: jvanboga
#IBM-Websphere-Transformation-Extender
#DataExchange
#IBMSterlingTransformationExtender

Originally posted by: raj1

Thanks verymuch,ivanboga, for such a wonderful explanation.
#DataExchange
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender

Originally posted by: SystemAdmin

Raji,

Idiosyncrasies on being told what to do (Answer me!), I neglected to respond, but…

We capture bad data using the “REJECT()” function with the RESTART attribute.

If you have an input of a file of records, you put the RESTART attribute on the record level. This means, that if one of the records fails because a value in it is not in the restriction list, that record will not process, but all good records will. So you have the normal output card that will process the good records, but you build a second output card with a blob of text with (S) as the range, and put REJECT(records:inputfile). Then all the rejected records go to this output card, while all the good ones get processed normally. If this is X12 data, you won’t have to touch the type tree, only the map and redeploy the system. If the type tree is proprietary, you may have to put the “restart” attribute on if it is set to off.
#IBM-Websphere-Transformation-Extender
#DataExchange
#IBMSterlingTransformationExtender

Originally posted by: raj1

Thanks rep, thanks verymuch for a elaborate explanation
#IBMSterlingTransformationExtender
#DataExchange
#IBM-Websphere-Transformation-Extender