Skip to Content

A new approach for best practices!

Reading books at the beach during the  holidays can help to find new perspectives. “Lean brain management” from Gunter Dueck from IBM was such a book for me. Therefore I changed my blog from tips and tricks for a successful SAP Interactive Forms by Adobe project to the new title. I hope you will have fun and hopefully learn from it how to avoid these mistakes:

Make a 1:1 conversion of all paper forms:

Do not try to analyze the paper forms. Insttead make a 1:1 transition of all the paper forms to the Adobe Interactive Forms. In many project teams have successfully reduced the number of paper forms by analyzing them and found the common denominator for all these forms. Moreover they designed master formulas at the design time which combines fields from different forms in one form out of which the forms for the users are created at run-time. Avoid this approach as it can speed up your project.

Do not differentiate between online- and offline-forms

A good way to damage your performance is the use of offline-scenarios for online-use. As the forms for offline-scenarios are much bigger normally (due to the need to avoid any check with the backend-system) they could have a very good effect to damage your online performance.

Avoid any guidelines for the layout

Ongoing and fierce discussions about the layout of the forms can make your projects nearly unmanageable. Great! That’s exactly what you need. Therefore avoid any guidelines and be open for discussions at any time especially in steering committees sessions where you can discuss about buttons and colours in details.

Make your forms as big as possible:

Adobe has given some recommendations how big your forms should be for a good performance. As you strive for a huge damage you should make your forms as big as possible. The minimum requirements are 10-12 pages, just have a look at the guidelines. But the more pages your forms comprises the better in order to damage your performance.

Avoid usability:

Avoid any help on formulas so that the user is confused. Formulas with very large drop down boxes and many scrollbars can also be very helpful to damage user acceptance.  Therefore always use the original paper size format.

Avoid any frameworks, build everything from scratch:

SAP ECC provides you with two frameworks: ISR (Internal Service Request) and HCM Processes&Forms on top of SAP Interactive forms by Adobe. Chris Solomon has written a lot of blogs how to use HCM processes & forms in your project to speed up the implementation of processes. This is exactly what you need to avoid in order to damage your project. Build everything from scratch.

Ensure a low Support level for SAP Netweaver 7.0:

Make sure that you do not use the newest support level for SAP Netweaver 7.0. The Adobe-SAP integration has been enhanced with the support packages. By avoiding the newest one you could gain problems and trouble which helps you to achieve your aim.


And now: Do the opposite and use all the benefits from the SAP Interactive forms by Adobe technology and enjoy your project. Besides if you want to have a very good help for your SAP Interactive forms by Adobe project read the excellent book from SAP Press.

To report this post you need to login first.


You must be Logged on to comment or reply to a post.

      1. Christopher Solomon
        When doing HCM P&F, might I suggest you duplicate as much as possible of PA30 in a form! It looks great, works slow and has half the built-in functionality if your lucky! Yea!!!!
  1. Former Member
    Some users don’t like the look and feel of SAPGUI for Windows. Consider converting all ABAP Dynpros (screens) into Interactive Forms by Adobe. The users will appreciate the effort, even if your infrastructure doesn’t.
    1. Bernhard Escherich Post author
      It seems that I should have really mentioned it as another colleagues already points to that issue.

      Thanks for your feedback and best regards.

  2. Christopher Solomon
    I think you covered them well here (but I do HOPE that folks “get” your blog….sarcasm is often lost over the internetz! haha)

    I will add an extra gem for you…although I could fill a book with you I am sure!(haha)

    Here’s a fun game….Try to have your form translated into as many languages as possible for your go-live. Start with 1 or 2 in blueprinting, but increase this number every week during implementation…compounding numbers are best! Better yet though, as your go-live date approaches, get other groups involved to review the translations and/or add/change them as they see fit.For example, it’s always great fun to have someone from Canada translate French for you, and then the following week, have someone from France to review/approve it….the jokes almost write themselves…hilarity ensues! In any event, yes, the more languages the better!I mean, it’s just translations, right? No big deal.

    Thanks again for the GREAT blog!

    1. Bernhard Escherich Post author
      Thanks for your feedback. I really appreciated it from the Processes and Forms-guru. The style of my blog was inspired by your blogs. (And you are right: Initially I was a bit afraid that someone takes the advices for real).

      Your proposal is really nice. Translation discussions are the equivalent for qualificaton catalogue discussions in PD.

      Thanks and best regards,


      1. Christopher Solomon
        Thanks for the compliments and glad to “inspire” others. haha Hey, I look at it this way, part of our job if we are going to blog this stuff (which isn’t exactly “sexy” or entertaining by it’s very nature) and people are going to take time to read it is that we make it fun. Is that too much to ask? haha

        Skills/Qualifications/Jobs catlogs…..*shudder* =)

        BONUS: another gem we ran into today…
        -Service Packs and OSS Notes
        Try to get another “mystery” team involved who can and will apply (and back out) OSS notes and service packs at the most inopportune time. This will really test your team’s “problem solving”/support skills while they should be working on completing other pre-“go-live” tasks. It will also test stress levels and patience as well!

  3. Former Member
    Many of your tips and hints will lead to fast implementation. But the implementation will be slow and hard to maintain. It is much better to analyze first.
    1. Bernhard Escherich Post author

      you are right but that was exactly what I intended. These are fun advices as it reads “Damaging your project”. Analysis first is the fundamental point.

      Best regards,

  4. Former Member
    Enjoyed reading this.  I’m not a forms expert, but through ten years of experience on SAP projects I’m impressed at how well you captured a typical project.  Especially the live stakeholder meeting discussions on button colours!

Leave a Reply