cancel
Showing results for 
Search instead for 
Did you mean: 

ASSERTION_FAILED

Former Member
0 Kudos

Hi all,

I have made some changes in the existing transformation.

1) Before, Say Extractor A -> DSO B.(there were 10 fields and start routine, 1:1 char routines and end routine).

2) Now, Say Extractor A -> DSO C.(only 5 fields from above is used, start routine is same as above, 1:1 routine is same and in end routine i have removed fields which are not required).

Now when i activate the 2) transformation i am getting error as ASSERTION_FAILED.

In ST22,

Information on where terminated

Termination occurred in the ABAP program "CL_RSTRAN_GEN_STEP_CONVERT====CP" -

in "GET_META_OBJECT_".

The main program was "RSAWBN_START ".

In the source code you have the termination point in line 29

of the (Include) program "CL_RSTRAN_GEN_STEP_CONVERT====CM003".

Can any please guide me what could be the problem??

Thanks,

Sowrabh

Accepted Solutions (0)

Answers (4)

Answers (4)

former_member188080
Active Contributor
0 Kudos

check below notes

[OSS Note 1050275 - ASSERTION_FAILED in CL_RSTRAN_FOBU_APPL->GET_CODE|https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1050275] (relevant to prior to BI 7 SP14)

[OSS Note 1115923 - Check or transfer of empty formulas causes runtime error|https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1115923] (relevant to prior to BI 7 SP17).

Thanks and regards

Kiran

KamalMehta
Advisor
Advisor
0 Kudos

Hi Srinivas,

As suggested above by Raman you should check all the routine definition once again. Do a syntax check for all of them .

Also Check note 1030987.

Thanks

Kamal

RamanKorrapati
Active Contributor
0 Kudos

hi srinivas,

Check below doc, whether its helps you or not.

http://scn.sap.com/docs/DOC-43421

Check this note to - 1094266

please do the syntax for routines, there might be something went wrong. please checks and try to activate.

Thanks

abdullahqureshi
Contributor
0 Kudos

Hi,

Faced the same issue when made some changes in existing transformation.

We solved this issue by deleting the existing transformation and create a new transformation then activate it.This time no such type of error.

Regards,
Abdullah