SAS Data Integration Studio, DataFlux Data Management Studio, SAS/ACCESS, SAS Data Loader for Hadoop and others

Transformation Error Code

Occasional Contributor
Posts: 10

Transformation Error Code


As per our requirement we need to capture the each transformation error and we need to log it to the Error Table.

Please guide me how to get the Transformation error Code from the SAS DI tool.

I am using SAS DI 4.21 version tool.




Posts: 7,366

Re: Transformation Error Code

The following paper might contain what you need:

Super Contributor
Posts: 349

Re: Transformation Error Code

Hi Kandasamy,

You can try using following ...

1)Status handling

2)As status handling tab is not present in some of the transformation,you can use Return code check transformation for capturing error code.

3)You can also write user written code.

Hope this helps...



Respected Advisor
Posts: 3,902

Re: Transformation Error Code

Make sure that you understand the requirement correctly! SAS DI studio let's you create a job flow as SAS Metadata. Based on this metadata SAS code gets generated. What will be executed is SAS code.

If SAS code throws an error (eg. there is a syntax error in a expression defined in a transformation) then it's kind-of too late to try and capture this error and write it to an error table (as this capturing code would come after the error occured). A syntax error is a syntax error - how code behaves after that is unpredictable.

What you can do is define conditions (eg: lookup table does not exist) and actions (eg. logging the condition in an error table).

Thanks for the question! I didn't realize what the Return Code Check transformation is used for. Was good to have a read in the docu.

The paper Art posted: That could be a way to capture rejected rows when loading into a SAS dataset with integrity constraints turned on (using audit trails: I personally feel that when this level of control is needed then it's possibly time to think about loading data into a data base like Teradata or Oracle.

Ask a Question
Discussion stats
  • 3 replies
  • 4 in conversation