Business Processes and Rules: Siebel eBusiness Application Integration Volume IV > Data Mapping Using Scripts > Exception Handling Considerations >

Data Transformation Error Processing

This section describes how the Data Transformation Functions handle errors, and how the top-level error code returned by the data transformation business service invocation is determined.

• Framework errors occurring outside the Data Transformation Context. These errors are passed through without change to the CSSService script invocation mechanism. That mechanism takes control and returns an error of its choice. For example, if your map invokes a BusComp and the BusComp signals an error, an exception is thrown that will be ignored by the Data Mapping Engine but passed to the CSSService script invocation mechanism, which sets up the error state and returns an error from the business service invocation.
• Framework errors generated by Data Transformation Functions. These are caught by an exception handler that sets up the state in the output PropertySet and passes control to the CSSEAIDTEScriptService class. CSSEAIDTEScriptService sets the error code on the business service as in the state, transforming error symbols to error codes in the process. Error symbols are specific to the failure.
• User errors. These are processed the same way as errors generated by the Data Transformation Functions, except that you specify the error symbols and error text in your maps.