"ASSERT Condition" Error

[Former Member]

Hi,

In my earlier thread, had mentioned about developing an application with 2 views, view1 and view2. This was working fine. After this I added a pop-up attribute in view2 ref to IF_WD_WINDOW. Also added an action OK in view2. Didnt write any further code.

Now when I execute the application by clicking on a button view1, I find that the application gives an error:

The ASSERT condition was violated.

I removed the popup attribute and the OK action. But still getting the same error.

What does this error mean and how do we rectify it.

Please help.

Mick

[Former Member · Accepted solution]

Hi, Mick,

I had yesterday the same problem as yours: assert condition is violated.

Besides the cardinality, you should check the data type that you used to map the context node or attribute. According to what I found in internet, this error is caused by the populated value to context node or attribute.

For example, in my own case: the inputfield UI binds to a data element. The error shows up when the data element is defined as NUMC(2). When I changed it to Char(2), the error disappears.

I hope this can help you.

Best regards,

Fan

[Former Member · Accepted solution]

The probelm of the ASSERT error is solved. Dont exactly know what was the problem.But deleted the table in the view and then added it again. It worked.

However I have a new issue now. To the table I have added input fields. Therefore each cell of the table is an input field. However when the view is displayed, the cells of the tables are not editable, ie the user cannot enter any value in the cells.

How do we rectify this problem?

Mick

[pranav_nagpal2 · Accepted solution]

Hi Mick,

Only adding input fields in table cells wont make them editable you have to initialize it as well.. here is a sample code for same........

DATA lo_nd_cn_table TYPE REF TO if_wd_context_node.
DATA lt_table TYPE wd_this->elements_cn_table.
DATA ls_table TYPE wd_this->element_cn_table.


lo_nd_cn_table = wd_context->get_child_node( name = wd_this->wdctx_cn_table ).

do 5 times.
clear ls-table.
append ls_table to lt_table.
enddo.

lo_nd_cn_table->bind_table( lt_table ).

this code will make file rows editable...

regards

Pranav

[Former Member · Accepted solution]

Thanks Pranav. This solved the problem. Points awarded.

[pranav_nagpal2 · Accepted solution]

Welcome

[Former Member]

Hi,

I suggest you to check the Cardinality condition for whih you are binding .

The table or input field or any drop downs used in that views because of that you are getting the dumps

check if you are binding the values to the input field then cardinality should be 1:1

and if it is dropdwon by index then 0:n and if it is tabkle binding then bind it to 0:n .

check this condition mioght be one among them.

Regards,

Sana.

[pranav_nagpal2]

Hi Mick,

Please see in st22 for more details of this error... i have seen this error if cardinality of node is not correct or if the type mismatch in attibutes while passing the values.........

regards

Pranav

[Former Member]

Hi,

Mentioned are some details from ST22.

What happened?

In the running application program, the ASSERT statement recognized a

situation that should not have occurred.

The runtime error was triggered for one of these reasons:

- For the checkpoint group specified with the ASSERT statement, the

activation mode is set to "abort".

- Via a system variant, the activation mode is globally set to "abort"

for checkpoint groups in this system.

- The activation mode is set to "abort" on program level.

- The ASSERT statement is not assigned to any checkpoint group.

Information on where terminated

Termination occurred in the ABAP program "CL_WDR_TABLE_DATA_P

in "GET_VISIBLE_TABLE_DATA".

The main program was "SAPMHTTP ".

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

I have 3 input fields and 1 table on view2. There are 3 nodes on View2 in the View2 context, all with a cardinality of 1:1.

Please help.

[arjun_thakur]

Hi Mick,

Change the cardinality of the node which is binded with the table to 0:n.

Regards

Arjun

[Former Member]

Have tried changing the cardinality to 0:n for the node conatining the table in the view2 context. But still the same error.

Mick