Skip to Content

External Comp. Context - mapping not completed

Dear SDN,

I have been trying ALL the ways to link Interface Contexts between 2 components.

But nothing has worked.

The error is always the same: "The Mapping to Node COMPONENTCONTROLLER.1.CASE_LIST Has Not Been Completed"

Does anyone have any idea about what can be the problem here?

There is some dynamic programming in the components. Is this the problem? (once I heard it could be).

I have already read ALL the threads about

. mapping in the Component Usage,

. Comp. A and Comp. B...

. 'Input-Element (ext.)' checkbox,

. etc.. etc..

I have tried all the proposals.

But nothing worked for me.

Please, can anybody give me any piece of suggestion?

I will be grateful for any attempt of helping!

Thank you all.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Best Answer
    Aug 12, 2008 at 08:32 AM

    Hi..

    WDA aplication which have 'Input Element (Ext.) node' can not be excuted by itself.

    'Input Element (Ext.)' node should be mapped by other webdynpro components.

    That's why the error is occured.

    The step like that...

    Parent component has node A and child component has node B.

    And node A and B should have same sturcture.

    B node is checked in external mapping( checking 'Input Element (Ext.)').

    Register component usage child component in parent component.

    And double click Component usage-><your child component> in your application tree.

    Then, you can see two window, left hands side is child component, the other is parent component.

    ( If you cannot see the right window, click controller usage button and select controller.)

    And map the node from A to B( right -> left).

    Soo.

    Add comment
    10|10000 characters needed characters exceeded

    • Hi Yogesh,

      that´s it, the question has been answered.

      I managed to exchange data without any problems by keeping both components in the same "Internet Explorer" (browser) window. It means that Comp. B view was embedded in Comp. A window, as an interface view.

      The conclusion I got in the end is that, in ABAP WebDynpro, we can´t have two browser windows working in the same application session.

      Please, correct me if I am wrong.

      Thank you.

      Fabio