Tutorial 2 for BAPI WDA - set column settings in Wizard - page 7, step 4.

[Former Member]

To the Pretty Good WDA Programmers, and/or Experts,

I am new at this, so any help is appreciated.

In the tutorial: Dynpro for ABAP: Tutorial 2 - BAPI Usage at: https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/9cb5d345-0801-0010-6a8e-fc57c23f... has in page 7, step 4. Seems a little vague to me:

-

---

The Required Methods and Context Elements

On the two subsequent dialog windows, default values are listed for giving names to the context nodes and attributes required by the service call as well as to the required methods. The proposed names are based on the names of the embedded service, but you can change them as required.

-

---

So the question is, in the wizard for page 7, step 4, what are the column settings set to: Parameter Values / Controller Attribute / Context Node ... to get the BAPI Input/Output and Changing columns looking like they do in the tutorial on the next page (pg 8)?

Step-by-step, or in this case, column-by-column directions would be most helpful!

Thank You...

Edited by: Daniel Perecky on May 4, 2009 10:58 PM

[Former Member]

Hi Daniel,

You have to choose the option Context (Node/Attribute) for the objectType and the wizard will automatically create a Context node and sub node for you.

Regards,

Trikanth Basetty

[Former Member]

To Trikanth,

Yes... Thank You for your quick reply.

What would be the specific settings for the parameters and tables columns in this BAPI to look like the tutorial's nodes (pg 8)? The default settings are not it, and I tried a bunch of combinations... apparently not the right combo yet.

[Former Member]

Daniel,

I have uploaded few screenshots of the those steps, please check and let me know...

[http://lh5.ggpht.com/_E1SpYl0ZbfE/Sf9wng73gAI/AAAAAAAAAd4/IuXyQTlGp44/s912/1.gif]

[http://lh4.ggpht.com/_E1SpYl0ZbfE/Sf9wn3zJAwI/AAAAAAAAAeA/JMd0uC9J4NQ/2.gif]

[http://lh4.ggpht.com/_E1SpYl0ZbfE/Sf90Of_b0WI/AAAAAAAAAfY/xJJshX7KDB8/4.gif]

[http://lh5.ggpht.com/_E1SpYl0ZbfE/Sf9woLsprMI/AAAAAAAAAeY/lC3Efp6yqfc/5.gif]

[http://lh3.ggpht.com/_E1SpYl0ZbfE/Sf9z7r8p1qI/AAAAAAAAAfM/GOPNNxV00Xg/s912/6.gif]

[http://lh6.ggpht.com/_E1SpYl0ZbfE/Sf9wsJsW4iI/AAAAAAAAAeo/KSzqT6-ZpOc/s912/7.gif]

Regards,

Trikanth Basetty

Edited by: Trikanth Basetty on May 4, 2009 3:58 PM

[Former Member]

hi,

To have a similar look as in Page 8, you need to select Destination From and Destination To And Change its Object Type to Context(Node/Attribute).

Similarly, have Choose Flight List and Change its Object Type to Context(Node/Attribute).

Press Continue and Finally End.

Your screen will appear with Context.

Expand the Context to see the same screen as in Page 8 of the tutorial.

Thanx.

[Former Member]

To Trikanth and Saurav,

Thank you for those screen-shots Trikanth. They definitely helped point me in the right direction. The problem was that all of the 'Changing' structure sub-structures would end up in the view node.

When I would try to map 'Changing | Flight_List' with the context, a message would appear: 'Mapping is only possible for Flight_List if Parent is Mapped'. Then when I mapped the entire 'Changing' node, it would map to the Component Controller, but then it would not map correctly to the output display table.

Apparently only one dimension of structures could be mapped. A (deep) structure of structures cannot be.

So in step 4, in the wizard, to make this work, I had to only make visible 'Changing' by what you both kindly confirmed: making it Context.

Settings Summary: Root Node- unchangable.

Parameter Group 'Importing'- Context (Node/Attribute)- Unchangeable

Parameters- Airline - Changed to Context (Node/Attribute)

Dest_From - Changed to Context (Node/Attribute)

Dest_To - Changed to Context (Node/Attribute)

Max_Rows - Changed to Context (Node/Attribute)

Parameter Group 'Changing'- Context (Node/Attribute)- Unchangeable

Date_Range - left as Controller Attribute

Extension_In - left as Controller Attribute

Flight_List - Changed to Context (Node/Attribute) <---

Extension_Out - left as Controller Attribute

Return - left as Controller Attribute

So, when 'Changing' and ONLY 'Flight_List' was made visible in the node, it mapped correctly to both the Context node and to the output table columns.

This is great. Thanks a Lot!