Context binding error in Dynamic UI element creation

Hi,
I am new to Webdynpro. I am trying to build an app for dynamic table data in an ALV,so creating an input field for table name dynamically.
I am facing a issue while binding the dynamic input field to the dynamically created context node attribute. The error description is: ERROR: Error in INPUT_FIELD "IF" of view "ZVK_DYNAMIC1.MAIN": Context binding of property VALUE cannot be resolved: The MAIN.1.INPUT node does not contain any elements (termination: RABAX_STATE).
Following is the code written in wdinit( ) method and wdmodifyview( ) method of the view controller.
METHOD wddoinit .
   DATA: lr_root_node_info TYPE REF TO if_wd_context_node_info.
   DATA: lr_input_node_info TYPE REF TO if_wd_context_node_info.
   DATA: ls_attribute_info TYPE wdr_context_attribute_info.
   lr_root_node_info = wd_context->get_node_info( ). " get the root node
   CALL METHOD lr_root_node_info->add_new_child_node
     EXPORTING
       name                         = 'INPUT'
       is_multiple                  = abap_false
       is_multiple_selection        = abap_false
*      is_initialize_lead_selection = abap_false
     RECEIVING
       child_node_info              = lr_input_node_info.
   CLEAR ls_attribute_info.
   ls_attribute_info-name          = 'TABLE_NAME'.
   ls_attribute_info-type_name     = 'STRING'.
   CALL METHOD lr_input_node_info->add_attribute
     EXPORTING
       attribute_info = ls_attribute_info.
ENDMETHOD.
METHOD wddomodifyview .
   DATA: lr_ui_root     TYPE REF TO if_wd_view_element.
   DATA: lr_container   TYPE REF TO cl_wd_uielement_container.
   DATA: lr_input_field TYPE REF TO cl_wd_input_field.
   DATA: lr_flow_data   TYPE REF TO cl_wd_flow_data.
   IF first_time EQ 'X'.
     lr_container ?= view->get_element( 'ROOTUIELEMENTCONTAINER' ).
     CALL METHOD cl_wd_input_field=>new_input_field
       EXPORTING
*       activate_access_key        =
*       alignment = E_ALIGNMENT-AUTO
*       bind_alignment             =
*       bind_display_as_text       =
*       bind_display_only          =
*       bind_enabled               =
*       bind_ime_mode              =
*       bind_input_prompt          =
*       bind_length                =
*       bind_password_field        =
*       bind_read_only             =
*       bind_state =
*       bind_style_class_name      =
*       bind_suggest_filter_method =
*       bind_suggest_values        =
*       bind_suppress_value_help   =
*       bind_text_direction        =
*       bind_tooltip               =
         bind_value = 'INPUT.TABLE_NAME'
*       bind_visible               =
*       bind_width =
*       context_menu_behaviour     = E_CONTEXT_MENU_BEHAVIOUR-INHERIT
*       context_menu_id            =
*       date_picker_reference_id   =
*       display_as_text            =
*       display_only               =
*       enabled    = 'X'
*       explanation                =
         id         = 'IF'
*       ime_mode   = E_IME_MODE-AUTO
*       input_prompt               =
*       length     = '20'
*       multi_field_suggest        =
*       no_history =
*       on_enter   =
*       on_table_paste             =
*       password_field             =
*       read_only =
*       state      = E_STATE-NORMAL
*       style_class_name           =
*       suggest_filter_method      =
*       suggest_values             =
*       suppress_value_help        =
*       text_direction             = E_TEXT_DIRECTION-INHERIT
*       tooltip    =
*       view       =
*       visible    = E_VISIBLE-VISIBLE
*       width      =
       RECEIVING
         control    = lr_input_field.
     CALL METHOD cl_wd_flow_data=>new_flow_data
       EXPORTING
*       cell_design = E_CELL_DESIGN-PADLESS
         element = lr_input_field
*       id      =
*       v_gutter    = E_V_GUTTER-NONE
       RECEIVING
         control = lr_flow_data.
     CALL METHOD lr_input_field->set_layout_data
       EXPORTING
         the_layout_data = lr_flow_data.
     CALL METHOD lr_container->add_child
       EXPORTING
*       index     =
         the_child = lr_input_field.
   ENDIF.
ENDMETHOD.
Please help.

Hi Vishal,
Actually, for an input field the node should be with cardinality either 1...1 / 1...n. i.e. at least one element should exist. So you need to pass "is_mandatory = abap_true" while creating node.
Please modify your code as below
CALL METHOD lr_root_node_info->add_new_child_node
     EXPORTING
       name                         = 'INPUT'
       is_mandatory = abap_true
       is_multiple                  = abap_false
       is_multiple_selection        = abap_false
*      is_initialize_lead_selection = abap_false
     RECEIVING
       child_node_info              = lr_input_node_info.
Hope this helps you.
Regards,
Rama

Similar Messages

Performance will go down in case of Dynamic UI element Creation.

Performance will go down in case of Dynamic UI element Creation

suryar wrote:
Performance will go down in case of Dynamic UI element Creation
hi,
is this an information or a question?
Please be more specific so that your queries can be answered quickly
Regards,
Sahai.S

Property binding of a dynamic UI element

Hi all,
It is no problem to define property binding of a UI element statically (see [Example|http://wiki.sdn.sap.com/wiki/display/WDABAP/SimpleapplicationtochangepropertiesofUIElementsduringruntimeinWebDynpro+ABAP])
But, how can I define property binding for a UI element which I create at runtime? I can't find any statement to tell the UI element (for example CL_WD_INPUT_FIELD) that it should use property binding.
Any ideas?
Best regards
Oliver

Hi Prashant
I already use bind_value (it has the complete path to the attribute).
The attribute value is shown correctly, but the visibility doesn't work.
Keep in mind that I do not want to create a dedicated context attribute for visibility. I want to use the property of the context attribute.
At time of dynamic context creation, I use the following statement to set the value of the context attribute property:
DATA l_attribute_name TYPE string.
      l_attribute_name = <fs_context_attribute_info>-name.
      CALL METHOD lr_context_element->set_attribute_property
        EXPORTING
          attribute_name = l_attribute_name
          property       = lr_context_element->e_property-visible
          value          = l_visible.
When creating the UI element, the following code is used.
DATA lr_input_field TYPE REF TO cl_wd_input_field.
            CALL METHOD cl_wd_input_field=>new_input_field
              EXPORTING
                bind_value             = l_context_binding_value
*   bind_visible           =
                id                     = l_id
                 state                  = l_state
* visible                =
              RECEIVING
                control                = lr_input_field.
Keep in mind that I can't use bind_value (I dont want an dedicated context attribute for visibility) and I also can't use visible because it should be context (attribute property) dependent.
Thanks in advance
Oliver

Error when trying to create a Dynamic UI Element(DropDownByKey)

Dear All,
I am trying to create a Dynamic UI element(dropdownbykey) .
I used the following code which i wrote in domodify:
if (firstTime)
IWDTransparentContainer thetransparent =(IWDTransparentContainer)view.getElement("AttributeDynamic_TransparentContainer");
IWDNodeInfo node = wdContext.getNodeInfo().addChild(
"DynamicNode",null,true,true,false,true,false,true,null,null,null);
                          IWDAttributeInfo attr1=node.addAttribute("attrib00","ddic:com.sap.dictionary.string");
IWDAbstractDropDownByKey Sizedropdown=(IWDAbstractDropDownByKey)view.createElement(IWDAbstractDropDownByKey.class,null);
Sizedropdown.bindSelectedKey(attr1);
thetransparent.addChild(Sizedropdown);
When i deployed it i got the following error:
com.sap.tc.webdynpro.services.exceptions.CreationFailedException: Cannot create view element implementation com.sap.tc.webdynpro.clientserver.uielib.standard.api.IWDAbstractDropDownByKey
Can anyone please help me in this regard.
Thanks and Regards
Nishita Salver

Dear All,
Thanks for ur quick reply below is the entire error chain:
com.sap.tc.webdynpro.services.exceptions.CreationFailedException: Cannot create view element implementation com.sap.tc.webdynpro.clientserver.uielib.standard.api.IWDAbstractDropDownByIndex
     at com.sap.tc.webdynpro.progmodel.view.ViewElementFactory.createElement(ViewElementFactory.java:161)
     at com.sap.tc.webdynpro.progmodel.view.View.createElement(View.java:177)
     at com.sap.satyam.dynamic_attrapp.Dynamic_attrAppView.wdDoModifyView(Dynamic_attrAppView.java:184)
     at com.sap.satyam.dynamic_attrapp.wdp.InternalDynamic_attrAppView.wdDoModifyView(InternalDynamic_attrAppView.java:364)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doModifyView(DelegatingView.java:78)
     at com.sap.tc.webdynpro.progmodel.view.View.modifyView(View.java:337)
     at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:481)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doModifyView(WindowPhaseModel.java:551)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:148)
     at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
     at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:321)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(AccessController.java:207)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Caused by: java.lang.NoSuchMethodException
     at java.lang.Class.getConstructorImpl(Native Method)
     at java.lang.Class.getConstructor(Class.java:554)
     at com.sap.tc.webdynpro.progmodel.view.ViewElementFactory.createElement(ViewElementFactory.java:150)
     at com.sap.tc.webdynpro.progmodel.view.View.createElement(View.java:177)
     at com.sap.satyam.dynamic_attrapp.Dynamic_attrAppView.wdDoModifyView(Dynamic_attrAppView.java:184)
Thanks and Regards,
Nishita

Error in context binding for text property

Hello experts,
I receive this error in my WD4A application:
The following error text was processed in the system XXX : Context binding for property TEXT of "T_MONTHTO"
cannot be resolved: Node MAINVIEW.1.TEMPVAL2 does not contain any elements
The error occurred on the application server sapxxxxx_XXX_00 and in the work process 0 .
The termination type was: RABAX_STATE
The ABAP call stack was:
Method: RAISE_FOR of program CX_WDR_ADAPTER_EXCEPTION======CP
Method: RAISE_BINDING_EXCEPTION of program CL_WDR_VIEW_ELEMENT_ADAPTER===CP
Method: GET_BOUND_ELEMENT of program CL_WDR_VIEW_ELEMENT_ADAPTER===CP
TEMPVAL2 has cardinality 0..1, selection 0..1, Inizialization Lead Selection false and the ST22 dump says:
33
34   if l_adapter->m_view_element is bound.
35     l_component ?= l_adapter->m_view_element->view->if_wd_controller~get_component( ).
36     l_view_name = l_adapter->m_view_element->view->name.
37     l_view_element_id = l_adapter->m_view_element->id.
38     l_component_name = l_component->component_name.
39   endif.
40
41   if l_adapter->m_context_element is bound.
42     l_path = l_adapter->m_context_element->get_path( ).
43   endif.
44
>>   raise exception type cx_wdr_adapter_exception
46     exporting
47         textid          = textid
48         previous        = previous
49         component_name = l_component_name
50         view_name       = l_view_name
51         view_element_id = l_view_element_id
52         adapter_stack   = l_adapter_stack
53         path            = l_path
54         p1              = l_p1
55         p2              = l_p2
56         p3              = l_p3
57         p4              = l_p4
58         reason          = reason.
59 endmethod.
Could anybody please tell me why exactly this error is occuring?
Many regards,
Martin

Hi Martin,
I am getting the same error. can you please help me resolve this error.
Error:
Note
The following error text was processed in the system RS2 : Adapter error in &VIEW_ELEMENT_TYPE& "VBELN" of view "Z_MYFIRST_WEBDYNPRO.MAIN": Context binding of property VALUE cannot be resolved: Node MAIN.1.NODE_VBAK does not contain any elements
My Code is in the Method for the action is created for a button on MAIN VIEW
METHOD onactionaction_find .
wd_this->fire_to_alv_table_plg( ).
DATA: node_node_vbak TYPE REF TO if_wd_context_node,
        elem_node_vbak TYPE REF TO if_wd_context_element,
       stru_node_vbak TYPE if_main=>element_node_vbak .
stru_node_vbak type wd_this->element_node_vbak.
navigate from <CONTEXT> to <NODE_VBAK> via lead selection
break dasarikb.
node_node_vbak = wd_context->get_child_node( name =
wd_this->wdctx_node_vbak ).
get element via lead selection
elem_node_vbak = wd_context->get_element( ).
get all declared attributes
elem_node_vbak->get_attribute(
exporting
name = 'VBELN'
    IMPORTING
      value = stru_node_vbak ).
DATA: ls_where(72) TYPE c,
        lt_where     LIKE TABLE OF ls_where,
        lt_vbak      TYPE STANDARD TABLE OF vbak.
create where condition
IF NOT stru_node_vbak-vbeln EQ ''.
    CONCATENATE 'VBELN = ''' stru_node_vbak-vbeln '''' INTO ls_where.
    APPEND ls_where TO lt_where.
ENDIF.
IF NOT stru_node_vbak-erdat EQ '00000000'.
    CONCATENATE 'ERDAT = ''' stru_node_vbak-erdat '''' INTO ls_where.
    IF stru_node_vbak-vbeln NE ''.
      CONCATENATE 'AND' ls_where INTO ls_where SEPARATED BY space.
    ENDIF.
    APPEND ls_where TO lt_where.
ENDIF.
SELECT *
         FROM vbak
         INTO TABLE lt_vbak
        WHERE (lt_where).
DATA: node_node_alv TYPE REF TO if_wd_context_node,
        stru_node_alv TYPE if_main=>element_node_alv.
navigate from <CONTEXT> to <NODE_ALV> via lead selection
node_node_alv = wd_context->get_child_node( name =
if_main=>wdctx_node_alv ).
get all declared attributes
node_node_alv->bind_table( lt_vbak ).
ENDMETHOD.
Thanks,
Kiran

Error with the context binding

hi friends,
i am binding input_feild with the attribute vkorg
it was giving error
The following error text was processed in the system ECC : Adapter error in &VIEW_ELEMENT_TYPE& "IP" of view "ZZZ_TEST13.MAIN": Context binding of property VALUE cannot be resolved: Node MAIN.1.SALES does not contain any elements
The error occurred on the application server csslecc_ECC_01 and in the work process 0 .
The termination type was: RABAX_STATE
but i am giving the cardinality 1 to 1 for the node it was giving solution..
why we are giving 1to1 here...?
i am in confusion what is cardinality & what is selection..?
can anyone explain me in detail,,,,,
regards,
karunakar

Hi Karunakar,
Collection Cardinality or Node Cardinality is a set of two values that define the minimum and maximum number of elements that a node may hold at run-time and is represented as 0..1, 1..1, 0..n, 1..n.
The value on left denotes the minimum number of elements that a node must have at runtime and the value at right denotes the maximum number of elements that a node may have.
Selection Cardinality is again a set of two values like node cardinality but denotes the number of elements that may be selected at run-time. Selection cardinality must not violate Node collection cardinality i.e. if node cardinality is 0..1 0r 1..1, it is invalid to specify 0..n or 1..n as selection cardinality.
Pleae check this...
http://help.sap.com/saphelp_erp2005/helpdata/en/7a/787e40417c6d1de10000000a1550b0/content.htm
Cheers,
Kris.

Dynamic context binding in web dynpro alv

I use dynamic context binding (see code below to show and edit the ALV table.
'DB_TABLE' is a tranparent table. It works fine.
But now this table should be expanded with additional fields which are only known at runtime and could be different from case to case.
How can I get these fields in the context dynamically?
DATA:
        rootnode_info TYPE REF TO if_wd_context_node_info,
        dyn_node      TYPE REF TO if_wd_context_node,
        tablename   TYPE string.
rootnode_info = wd_context->get_node_info( ).
tablename = 'DB_TABLE'.
cl_wd_dynamic_tool=>create_nodeinfo_from_struct(
    parent_info = rootnode_info
    node_name = tablename
    structure_name = tablename
    is_multiple = abap_true ).
DATA:
        stru_tab TYPE REF TO data.
FIELD-SYMBOLS: <tab> TYPE table.
CREATE DATA stru_tab TYPE TABLE OF (tablename).
ASSIGN stru_tab->* TO <tab>.
SELECT * FROM (tablename) INTO CORRESPONDING FIELDS OF TABLE <tab>.
dyn_node = wd_context->get_child_node( name = tablename ).
dyn_node->bind_table( <tab> ).

You should create a structure dynamically and use this as the context structure. See the coding below, where a structure is created, which contains CARRID and CONNID.
DATA: node_info type ref to if_wd_context_node_info,
      struct_type TYPE REF TO cl_abap_structdescr,
      table_type type ref to cl_abap_tabledescr,
      comp_tab    TYPE cl_abap_structdescr=>component_table,
      comp        LIKE LINE OF comp_tab,
      my_table    type ref to data,
      my_row      type ref to data.
field-symbols: <table> type table,
                 <row> type data,
                 <flight> type sflight.
* build a structure description from the list of single fields
comp-name = 'CARRID'.
comp-type ?= cl_abap_datadescr=>describe_by_name( 'S_CARR_ID' ).
APPEND comp TO comp_tab.
comp-name = 'CONNID'.
comp-type ?= cl_abap_datadescr=>describe_by_name( 'S_CONN_ID' ).
APPEND comp TO comp_tab.
* note this structure contains the fields "CONNID" and "CARRID"
struct_type = cl_abap_structdescr=>create( comp_tab ).
* now the nodeinfo is created
node_info = wd_context->get_node_info( ).
node_info = node_info->add_new_child_node(
    name                         = 'MY_NODE'
    IS_MANDATORY                 = ABAP_true
    IS_MULTIPLE                  = ABAP_true
    STATIC_ELEMENT_RTTI          = struct_type
    IS_STATIC                    = ABAP_false
* fill new node;
data: l_node type ref to if_wd_context_node,
        l_flight type STANDARD TABLE OF sflight.
l_node = wd_context->get_child_node( 'MY_NODE' ).
l_flight = wd_assist->get_flights( ).
* if you could create a local data type, would be fine, but if you have to do it dynamically ...
struct_type = node_info->GET_STATIC_ATTRIBUTES_TYPE( ).
* create tabledescriptor from structdescription (standard table, no keys)
table_type = cl_abap_tabledescr=>create( p_line_type = struct_type ).
create data my_table type handle table_type.
assign my_table->* to <table>.
loop at l_flight assigning <flight>.
    create data my_row type handle struct_type.
    assign my_row->* to <row>.
    move-corresponding <flight> to <row>.
    append <row> to <table>.
endloop.
l_node->bind_table( <table> ).

Error Error oracle.iam.platform.context.ContextManager BEA-000000 IAM-0030007 org.xml.sax.SAXParseException: Line 1, Column 1 : XML-20108: (Fatal Error) Start of root element expected. error in oim logs

Hi ,
I am getting the below error at times in oim logs not able to find the reason please help.
<Error> <oracle.iam.platform.context.ContextManager> <BEA-000000> <IAM-0030007
org.xml.sax.SAXParseException: <Line 1, Column 1>: XML-20108: (Fatal Error) Start of root element expected.
    at oracle.xml.parser.v2.XMLError.flushErrorHandler(XMLError.java:422)
    at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:287)
    at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:414)
    at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:355)
    at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:226)
<XELLERATE.DATABASE> <BEA-000000> <Class/Method: tcDataBaseClient/bindToInstance encounter some problems: java.lang.ClassNotFoundException: weblogic/jndi/WLInitialContextFactory
oracle.iam.platform.utils.ServiceInitializationException: java.lang.ClassNotFoundException: weblogic/jndi/WLInitialContextFactory
    at oracle.iam.platform.Platform.getService(Platform.java:265)
    at oracle.iam.platform.OIMInternalClient.getService(OIMInternalClient.java:188)
    at com.thortech.xl.dataaccess.tcDataBaseClient.bindToInstance(tcDataBaseClient.java:151)
    at com.thortech.xl.client.dataobj.tcDataBaseClient.recoverConnection(tcDataBaseClient.java:401)
    at com.thortech.xl.client.dataobj.tcDataBaseClient.getInterface(tcDataBaseClient.java:385)
    at com.thortech.xl.dataaccess.tcDataBaseClient.close(tcDataBaseClient.java:349)
    at com.thortech.xl.server.tcDataBaseClient.close(tcDataBaseClient.java:62)
    at com.thortech.xl.server.tcDataBaseClient.finalize(tcDataBaseClient.java:43
Caused By: java.lang.ClassNotFoundException: weblogic/jndi/WLInitialContextFactory
    at java.lang.Class.forName0(Native Method)
    at java.lang.Class.forName(Class.java:247)
    at com.sun.naming.internal.VersionHelper12.loadClass(Ve
<Class/Method: tcDataBaseClient/getInterface encounter some problems: RuntimeException encountered. Reconnecting!
java.lang.NullPointerException
    at oracle.iam.platform.context.ContextManager.getCounter(ContextManager.java:697)
    at oracle.iam.platform.context.ContextManager.incrementCounter(ContextManager.java:684)
<Error> <XELLERATE.DATABASE> <BEA-000000> <Class/Method: tcDataBaseClient/close encounter some problems: Bean has been deleted.
javax.ejb.NoSuchEJBException: Bean has been deleted.
Thanks,
Sahana

hi Antara
about "... Though I have imported the following JDK parsers in the code , the Oracle's SAX parser is taking other inside the application server ..."
If you have used the SAXParserFactory.newSAXParser() method to get a parser, the documentation for this method says "Creates a new instance of a SAXParser using the currently configured factory parameters.".
So you might get a different parser in a different environment.
regards
Jan Vervecken

Error in cost element creation

Hello,
I have just checked the result of my batch input for cost element creation.
For asset cost element (category 90) I use the LSMW
Forother cost element (charge, products...) I use the classic CO-CEL settings.
For example:
- if I define the following accounts : 2030000000, 2060000000, 2990000000, 6010000000, 6050000000, 6990000000
then all the cost elements are created but not those with 99 extension : 2990000000, 6990000000.
Is there a reason and a solution to that dump?
Regards
Pascal Cuenin

Hi,
I suggest you to use OAK7 transaction to create cost elements with 90 category. There is no need in LSMW for this.
Regards,
Eli

Error message "ABAP/4 error during dynamic assign" on Contact Log creation.

Hi,
We are getting an error message "ABAP/4 error during dynamic assign beyond program bounds" displayed while creating contact log using transaction "BCT0".
Please suggest what can be the cause of the error message and how we can remove this.
Regards,
Ankur

Dear Andrea,
The problem should be caused by obsolete entry in table TFAWX.
Please use the following report for deleting this entry (test before in your TEST System) :
report ztfawx_delete.
tables tfawx.
select single * from tfawx where prog = 'SAPLBAS0'
                            and bldgr = '0110'
                            and mnum = 23
                            and bfeld = '$GENERAL'.
if sy-subrc = 0.
delete tfawx.
endif.
Buona Giornata
Mauro

Creating Dynamic UI Elements in Web Dynpro ABAP

Hi,
I want to an application in which the context nodes and the UI Elements for the second screen get created dynamically at run time based on the input on the first screen
First i have used this method :
cl_wd_dynamic_tool=>create_nodeinfo_from_struct()
to create the dynamic context nodes.
I have checked in debugger and the dynamic context node is getting creates successfully.
I have saved the reference for the context node in DYN_NODE.
Now for creating the dynamic UI Elements corresponding to the attributes of this context node, i call the method :
cl_wd_dynamic_tool=>create_form_from_node(
ui_parent = group_1
node = dyn_node
inputlength = 20 ).
But this thing is dumping.
This is the dump.
The following error text was processed in the system CG7 : Adapter error in &VIEW_ELEMENT_TYPE& "BP_ICLIENT" of view "ZWD_ONLINE_FORMS.FINAL_VIEW": Context binding of property VALUE cannot be resolved: Node FINAL_VIEW.1.BP does not contain any elements
Where BP_ICLIENT is the first attribute of the dynmaic context node BP created..
Please Help.
Thanks
Shivi

Refer this wiki :
https://wiki.sdn.sap.com/wiki/display/WDABAP/CreatingUIElementsDynamicallyinAbapWebdynpro+Application
More links are available on SDN reg Dynammci UI creations :
Have a look at the documentation for the WDDOMODIFYVIEW section of the phase model:
http://help.sap.com/saphelp_nw70ehp1/helpdata/en/d2/8acd409cc4dd50e10000000a1550b0/frameset.htm
There is also the class CL_WD_DYNAMIC_TOOL:
http://help.sap.com/saphelp_nw70ehp1/helpdata/en/67/6935425394033be10000000a1550b0/frameset.htm
Also have a look at the example application DEMODYNAMIC.
eLearning on the topic here as well:
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/201ddd3b-b4ce-2b10-8883-880ae8147f89
Edited by: Saurav Mago on Oct 26, 2009 12:23 PM

Context binding of property value cannot be resolved. not contain any eleme

I have a binding of a inputelment to a context element. the context can be empty. when it is empty it throws the error only when i have that binding. I thougt its not interesting for an inputfield to have a value or?
Following error occurs: The following error text was processed in the system DBW : Adapter error in &VIEW_ELEMENT_TYPE& "ZPM_PROJ" of view "ZPM_MD_PMON.STARTVIEW": Context binding of property VALUE cannot be resolved: Node STARTVIEW.1.PROJ does not contain any elements

Hi,
The thing is that you're trying to access node which might be from 0 to 1 or n records (cardinality). And at runtime point you have 0 records with 0 elements. That's why you have problem.
There might be something wrong with logic how you trying to display some data in your text fields.
At runtime there is no context element from which system could take values.
Or you have to change parent node cardinality to 1..1 if that meets logic or review your logic.

Reg:inputfield binding error

hi all
can you please share your knowledge on this error as soon as possible.
Adapter error in INPUT_FIELD "GROUP1_VEHICLENO" of view "ZWEIGHBRIDGE1.MAIN": Context binding of property VALUE cannot be resolved: Node MAIN.1.LECI_EVENT_DATA does not contain any elements
Thanks in advance
Deepika

Hello There ,
Such kind of errors occurs when you have not defined the proper cardinality values .
Possible cardinality Values are 0-n , 1-n , 0-1, 1-1 . Please check at your end your node attributes and then set the cardinality value .
hope this helps , please let me if you have concerns .
Regards,
Abhishek

TREE --Context binding of property TEXT cannot be resolved:

I have the following Error
Adapter error in &VIEW_ELEMENT_TYPE& "OBJID" of view "YFIDOA_YEAR_EVAL.MAIN": Context binding of property TEXT cannot be resolved: Node MAIN.1.TREE_NODE.1.MAIN_ORGEH.1.ORGEH.1.PERNR does not contain any elements
Requirement
I have two group ( TREE section , Detailed Section )
Tree Section have a 4 Top Org Units loaded initially when clicking on each Top org, it expands as a Tree and goes deep strucure. No trouble in populating Tree,
when I bind the Text element in the Detailed section with the PERNR, I get the Above Error.
Configuration & Code
All cardinalities are 0..N, initailization Lead selection is set for all the NODES.
TREE_NODE > MAIN_ORGEH > ORGEH > PERNR > OBJEC
Main_ORGEH has ORGEH, the attribute TOP_ORG and the SUpply function GET_MAIN_ORGEH
ORGEH has PERNR, attribute OBJID and the Supply function GET_ORGEH.
PERNR has OBJEC structure , attributes PERNR, CALC_AMT, ENAME and supply Function GET_PERNR
OBJEC has the structure objec strucutre
Question
I dont understand why PERNR > Pernr is not being read ? why is it telling me it is empty?
Any suggestions ?

The testing Org unit does not have any pernrs , as a result it was not allowing NULL values at the NODE PERNR level ( though NULL VALUE for the PERNR attribute is set).
On passing some dummy values, the Error is cleared.
I was even populating the Chief of the Org values as default to avoid NULL Values.

Unable to find information on WS data binding error on WLS 9.2.03 startup

Frustratingly, when I Google for "WS data binding error" I get 'old' links to BEA forum issues which may help but these are nowhere to be seen on the read-only copies now on Oracle forums here :- http://forums.oracle.com/forums/category.jspa?categoryID=202.
The link I'm looking for is:-
forums.bea.com/thread.jspa?threadID=600017135
Is there anywhere I can get access to this information or should I just post new items on the new WLS forum?
Many thanks.
p.s. the errors I am trying to research are as follows:-
<WS data binding error>could not find schema type '{http://xmlns.oracle.com/apps/otm}Transmission
<WS data binding error>Ignoring element declaration {http://xmlns.oracle.com/apps/otm}Transmission because there is no entry for its type in the JAXRPC mapping file.

Check this..
http://docs.oracle.com/cd/E10291_01/doc.1013/e10538/weblogic.htm
you can ignore those warnings
The following data type binding warnings and errors are displayed during deployment and start of Decision Service (Business Rules) Applications. These errors and warnings can be ignored.
<WS data binding error>could not find schema type '{http://www.w3.org/2001/XMLSchema}NCName
<WS data binding error>could not find schema type
'{http://websphere.ibm.com/webservices/}SOAPElement
java.lang.IllegalStateException
at weblogic.wsee.bind.runtime.internal.AnonymousTypeFinder$GlobalElementNode.
getSchemaProperty(AnonymousTypeFinder.java:253)

Context binding error in Dynamic UI element creation

Similar Messages

Maybe you are looking for