FPM - Trying to get it work on Service Pack 13

Question

I came across the FPM today. Since I had to create a new simple application today I gave FPM a try.
Basically my application would contain two views:
1. A tree illustrating a HR organisation structure
2. A table listing documents based on entry selected in the tree
I probably need the tree soon again for some other application so I wanted to put the tree and the table into 2 different web dynpro components for reusiability. Without FPM I would have created a 3rd WDA component. The main function of this 3rd component would be to pass the lead selection (an OBJID) from the tree to the table view.
If I understood the concept of the FPM framework correctly, the FPM_OIF_COMPONENT could help me with this passing of parameters between both WDA components and would even offer a lot more nice features.
I played around with FPM_DEMO_FLIGHT_OVERVIEW and finally managed to create a configuration that would pass the values. But then things became difficult and maybe someone can help me with my questions (I check already all documents in the library, forums, weblogs and wiki dealing with FPM):
1. Is a good idea to use FPM without having the Enhancement Package 1? The few tutorials and documents I found contained screenshots which look completely different to mine.
2. In the example I could see how a button is being defined, but they wont show up in my application: to be more accurate: once a refresh button showed up but just disappeared again. I guess now, that there is some error in my configuration, but instead of telling me, that there is an error, FPM just ignores my button.
3. Can I never navigate back to the initial screen? In my application that would be a requirement for easy selecting another element of the tree.
4. In the Flight Demo the DELETE_OBJECT button calls the CONFIRMATION view: how is the button linked to the view? In the component controller of the Flight Demo almost all methods of the interface IF_FPM_UI_BUILDING_BLOCK are empty.
Regards
René

Answer 1

> 1. Is a good idea to use FPM without having the Enhancement Package 1? The few tutorials and documents I found contained screenshots which look completely different to mine.
I would be more worried bout SP13. I'm not sure the functionality of FPM is really complete on SP13.  I've done FPM application on SP14 but never SP13.  It is true however that the design tools were significantly enhanced and simplified in 7.0 EnhP1; so SAP really recommends that customers wait until the EnhP before doing a lot of FPM development.
> 2. In the example I could see how a button is being defined, but they wont show up in my application: to be more accurate: once a refresh button showed up but just disappeared again. I guess now, that there is some error in my configuration, but instead of telling me, that there is an error, FPM just ignores my button.
Hard to say without seeing your application and configuration.  I've never had this happen to me. Once I activated one of the standard buttons in the config. they have always appeared for me. 
> 3. Can I never navigate back to the initial screen? In my application that would be a requirement for easy selecting another element of the tree.
Sure - Look at the SDN Mentors' Hands-On Workshop for an example that does this ( SDN Community Day Mentor Hands-On Workshop  and http://code.google.com/p/sdn-mentor-handson-2008/downloads/list ). I use the standard Start Over button.  It fires validation and if passed will return to which ever UIBB you have defined as your Initial Screen.
> 4. In the Flight Demo the DELETE_OBJECT button calls the CONFIRMATION view: how is the button linked to the view? In the component controller of the Flight Demo almost all methods of the interface IF_FPM_UI_BUILDING_BLOCK are empty.
Many of the standard buttons will first fire validation methods and then if they haven't received a flag not to continue they will follow their configuration to the next step.  In the case of the delete that would be to go automatically to whatever UIBB is configured for Confirmation.