cancel
Showing results for 
Search instead for 
Did you mean: 

Exception CX_SY_NO_HANDLER encountered while data load

0 Kudos

Hi Everyone,

I tried to do a delta load from the PSA to a DSO via a DTP (the PSA contained 40 delta records) and received the following error:

Error analysis                                                                                    |

|    An exception occurred which is explained in detail below.                                     |

|    The exception, which is assigned to class 'CX_SY_NO_HANDLER', was not caught                  |

|     and                                                                                          |

|    therefore caused a runtime error.                                                             |

|    The reason for the exception is:                                                              |

|    An exception with the type CX_SY_CREATE_DATA_ERROR occurred, but was neither                  |

|    handled locally, nor declared in a RAISING clause                                             |

|                                                                                                  |

|    The occurrence of the exception is closely related to the occurrence of                       |

|    a previous exception "CX_SY_CREATE_DATA_ERROR", which was raised in the program               |

|     "CL_RSAR_PSA_API===============CP",                                                          |

|    specifically in line 27 of the (include) program                                              |

|     "CL_RSAR_PSA_API===============CM002".                                                       |

|    The cause of the exception was:                                                               |

|                                                                                                  |

|    Could not generate the data object; the type /BIC/WB0001923000 does not exist                 |

|                               

The data flow looks like this

Datasource -> Transformation 1 -> BI7 Info source -> Transformation 2 (with an end routine) -> DSO

I checked the code in the end routine of Transformation 2 and that seems to be fine.

This is the first time I encountered such a strange error so I'm not sure what to do next. Looking forward to your suggestions!

Akshay Pande

Accepted Solutions (1)

Accepted Solutions (1)

0 Kudos

Hi Everyone,

The issue is now fixed. The error was caused because of the automatic recofinguration of the start routine after migration. I made the transformation from scratch again, and editted the start routine according to BI7 flow.


After making new DTPs and setting a new init for the DSO the issue was resolved.


Thanks for all your suggestions!


Warmly

Akshay

Answers (2)

Answers (2)

0 Kudos

Some additional information regarding the error:

On running the DTP in simulation/debug mode I received the following specific error:

Could not generate the data object; the type /BIC/WB0001923000 does not exist

snitwipro
Active Participant
0 Kudos

Please try to activate the PSA table from SE14. Select activate and adjust database (save data) and then try again.

Regards

Sourav

0 Kudos

Hi Sourav,

Thanks for the suggestion. I went to SE14 and entered the PSA table name (<DS name>_DA) but I received the error "Object does not exist". I checked with all three object types and cross-checked the name to be correct in the "Manage" window header of the datasource.

What should I do?


Warmly

Akshay

RamanKorrapati
Active Contributor
0 Kudos

Hi Akshay,

When PSA name was doesn't exist means data source may not be in active.

Have checked in BW server, table SE14 with correct psa name?

Try to run this program - RSDS_DATASOURCE_ACTIVATE_ALL and later check at SE14 with psa name again.

Thanks

0 Kudos

Hi Raman,


OK I ran the program for my datasource. It was already active but I reactivated it anyway. I checked in SE14 and still got the same error.

I think there might be some issue with the transformation or routines because this flow was recently migrated from 3.x to 7.x, so that might be causing the problem. Let me investigate that. In the meantime, any suggestions would be helpful!

Warmly

Akshay

RamanKorrapati
Active Contributor
0 Kudos

Hi Akshay,

Please look at Authorisations with help of basis team. check t code SU53 and auth role S_RS_DS.

If possible with help of abap exerpt try to Debug at DTP level.

DTP Debug steps as follows in pdf.

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/b0038ad7-a0c7-2c10-cdbc-dd674682c...

Thanks