cancel
Showing results for 
Search instead for 
Did you mean: 

Table Popin is not getting displayed

Former Member
0 Kudos

Hi Experts,

I have trouble using a table popin.

I read the tutorial Context Debugger Tool for Web Dynpro ABAP (https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/0d4c303f-0d01-0010-79bc-8b0ae9be5030)

and created it manually.

Everything works fine except for the table popin.

It is not getting displayed.

I also had a look at the WDR_TEST_TABLE Application and there the poping works, so it cannot be a systemProblem.

The method for opening the popin does not throw any error.

Does anybody have a hint where to look ?

I also read serveral posts here and read serveral other tutorials but cannot find a significant difference to my sourcecode.

Thanks in advance for any input,

Matthias

Edited by: Matthias Drescher on Oct 8, 2009 12:54 PM

Just a typo

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

hi,

If your coding is write please check this :

1. Whether you have created an Attibute inside your Node binded to table and binded this attribute with selectedPopin property of table.

2. Check whether you are setting this context Attribute's value equal to TablePopin Id when you are trying to open the popin.

3. Check whether you have written something like this on the selection of Row to open the POpin :

*set the Attribute CA_POP with the Table popin id which in my case is TABLEPOPiIN.

Here CA_POP is binded with selectedPopin property of table.

DATA lo_nd_cn_popin TYPE REF TO if_wd_context_node.

DATA lo_el_cn_popin TYPE REF TO if_wd_context_element.

DATA ls_cn_popin TYPE wd_this->element_cn_popin.

DATA lv_ca_pop LIKE ls_cn_popin-ca_pop.

  • navigate from <CONTEXT> to <CN_POPIN> via lead selection

lo_nd_cn_popin = wd_context->get_child_node( name = wd_this->wdctx_cn_popin ).

  • get element via lead selection

lo_el_cn_popin = lo_nd_cn_popin->get_element( ).

  • get single attribute

lo_el_cn_popin->set_attribute(

  • EXPORTING

name = `CA_POP`

  • IMPORTING

value = 'TABLEPOPIN' ).

Answers (2)

Answers (2)

thomas_jung
Developer Advocate
Developer Advocate
0 Kudos

Just a note. You dont' really need to build this context debugger into your application. The ABAP debugger has a special Web Dynpro tool that displays the context (as well as controllers and views) in specialized tools. This can all be accessed at runtime without anything special added to your component via the normal ABAP debugger.

Former Member
0 Kudos

Hi Thomas,

can you provide me a Link for that ? (documentation)

remember: Ich have no EnhP2 ggg

Best regards, Matthias aka MettyD

thomas_jung
Developer Advocate
Developer Advocate
0 Kudos

This functionality I describe has been available since NetWeaver 7.0 SP 9, so it isn't anything you need an Enhancement Package for. You can find the steps in the online help:

http://help.sap.com/saphelp_nw70ehp1/helpdata/en/48/74d50bd1431b5ae10000000a42189c/frameset.htm

In particular the last section of that help page describes how to switch to the Web Dynpro tool in the debugger.

Former Member
0 Kudos

Thank you very very much ! This helps a lot.. I´ll test ist in detail tomorrow @ work !

Former Member
0 Kudos

Thanks a lot.

I forgot the binding of the selected popin to the node attribute headbang