1. General
What does FLM stand for?
FLM stands for Forms Lifecycle Manager.
What does FLM do?
FLM is a tool that facilitates the implementation and management of a SAP Interactive Forms by Adobe form catalogue. More information about SAP Interactive Forms can be found here.
Why should we use FLM?
FLM is the most cost-effective way of implementing SAP Interactive Forms by Adobe. Not only does it reduce the cost and time required to implement the technology approximately fivefold, but it also delivers many more features out-of-the-box to best exploit the potential functionality of Adobe forms technology. This provides efficiency both in the form setup and ongoing upkeep of the form catalogue. In addition you only need basic ABAP and SAP IMG skills to perform the form integration with FLM.
If I already use SAP Interactive forms by Adobe in my landscape, does FLM alter my existing usage?
No, FLM in no way interferes with or precludes the use of any other SAP Interactive forms by Adobe scenario.
Is the product approved by SAP?
FLM was awarded ‘Powered by Netweaver’ application status in mid-2007.
What is Arch’s relationship with SAP?
Arch is an SAP Software Solutions Partner and has ten years’ experience in implementing SAP solutions specialising in Adobe forms technology since 2003. They have worked together on several projects in government, retail and financial services. SAP UK often recommend Arch as the experts in implementing SAP Interactive Forms by Adobe.
2. Suitability
What SAP release is necessary to run FLM?
Any Netweaver 2004s [NW 7.0] release. ABAP and Java stacks are both required.
Which SAP software products support FLM?
FLM is application neutral, and so can be hosted on any SAP system built on the NW2004s platform. Currently this includes, ERP2005, CRM2005, XI, Solution Manager, SEM and SRM.
Does FLM support on-line and off-line scenarios?
Yes. On-line scenario is via FLM Portal; off-line is via SMTP transport. In addition there is a download scenario, where off-line forms are accessed from an on-line Portal and then downloaded to local storage for off-line processing – this is especially useful for people who need to prepare customer-specific forms and then travel to a remote location.
Our location means that bandwidth does not support download of large-size files. What is the smallest size an eForm can realistically be? Is these an alternative way of submitting the data?
If we take the basic FLM Master Template then it takes around 100KB to 200KB, saved for 7.0.5 Adobe Reader/Acrobat Compatibility. Graphics increase the size of a PDF, as do large data connections.
However, for an email form scenario you can enable data-only transport to minimise the file size being transferred by email so large-sized PDFs can be managed relatively easily.
Alternatively, the FLM Mobile Portal available with FLM300 allows secure saving of form data on a laptop, which can then be synchronised via a network from within a firewall.
We have a large forms catalogue but we don’t want to convert them all at once. Is it possible to stagger the implementation of our e-forms?
Yes. Although FLM is most cost-effective for a large form catalogue, it is typically implemented in stages. The initial software cost includes a license for five forms, and future form licences can be purchased in bundles of ten so there are plenty of options for the expansion of a form catalogue after an initial pilot project.
It is also possible to develop a few simple forms using FLM, and integrate the full functionality capability at a later stage.
My form users don’t have SAP skills. Is this a problem?
No, not at all. The front-end presentation of each form is an Adobe PDF, viewable and fillable with free Adobe Reader software. SAP skills are only required for form design and administration.
3. FLM Engagement Model
How long does the basic installation of the product take?
We allow one day for this.
How is FLM licensed?
FLM is licensed via a base charge for the FLM infrastructure which includes a licence to run 5 forms. Additional forms are licensed in groups of 10 and this charge along with that for the base licence builds the gross licence. Discounts are applied for local government contracts, bulk purchase and fair exchange of value. For instance, Arch is happy to reward reference site visits and publicity with a compensating reduction in licence.
What is the maintenance and support charge?
Maintenance & Support at 20% per annum is levied on the gross licence fee.
How is an FLM project managed?
It depends on the customer! An FLM-based project will be designed specifically for each client based on their business needs, which we will gauge from a five-day consultation to decide whether FLM is the best solution for your Interactive Forms. Depending on your location and the nature of the project, one of Arch’s partners may be involved with project management and implementation as well.
Where does FLM training happen and how long does it take?
FLM training takes 3 days and is generally conducted at our west London offices. People with at least a modest background in ABAP would benefit most from the course.
4. Technology
What skills do I need to work with FLM? I don’t have any Java skills in my shop.
FLM needs only ABAP/4 and Adobe Livecycle Designer skills to develop new forms, and is implemented through an extension to the standard IMG.
My team are not familiar with Adobe Designer. Is this a problem?
No. Adobe Designer is a straightforward WYSIWYG tool, and no advanced skills are required for FLM form design. A two or three day training course would teach you everything you need to know. Alternatively, template design can be included in the project implementation.
How does the Designer-created form link to SAP?
FLM links the schema generated by Designer with the field and subform definition created by the FLM Form Wizard in the SAP IMG. The Portal, Routing Engine and Posting Engine conduct the rest of the process of data collection, verification, routing and posting into SAP automatically. This link also allows UserExits to be created and assigned to the form or individual fields, via tools in the FLM IMG menu.
Is the Forms Portal a FLM product? Or is this an SAP Portal?
The Forms Portal is an FLM product, built using the Java WebDynPro. It is a generic form serving product that provides worklist, draft and simple reporting functionality. The SAP Enterprise Portal can contain the FLM Portal if you require, but it is not a mandatory component.
What is different about form design in FLM compared to the bespoke method?
It’s quicker and much less technical. FLM allows the logical design of the form to be separated from the aesthetic design. In the standard scenario the code connecting the PDF to SAP is contained within each individual form and is specific to it. The advantage of separating the logical code from the visual design is that it enables automation of code generation without limiting the possibilities for presentation, saving time and effort while producing more visually consistent forms! In addition, no Java WebDynpro skills are needed because FLM does all the integration for you. ABAP is all that’s required, along with basic Adobe Designer skills.
How does FLM facilitate form catalogue management?
FLM comes with a number of tools to enable anyone familiar with SAP to manage and develop their form catalogue over time:
- The Form Dashboard allows you to view all forms and their statuses in the system at any one time, and make changes if necessary.
- The Cleanup Utility allows you to delete forms from the system, for example if they were initiated in the portal and then abandoned or timed out.
- FLM allows you to generate a form history report which is invaluable for auditing form processes
- Version Control is supported by FLM.
With FLM, I understand that entire forms are saved to the SAP Content Server for later retrieval. Does similar functionality not exist in the standard SAP scenario?
No the standard scenario involves binding form fields to ABAP function module parameters. This means that you can save form data back to SAP (although finding somewhere to put text of unlimited size can be hard), but you don’t get attachments without writing your own code.
Given that Interactive Forms by Adobe are embedded within SAP, how might you go about building forms which involve other applications, or maybe totally non-SAP?
We used FLM at a large utilities company to build a purchase requisition POC form that had a 3 level workflow approval mechanism and posted an actual requisition into SAP in a managed way; when the form is first launched it collects data from 3 systems, 2 SAP systems and 1 SQL-database non-SAP system in order to do the pre-population on the form and to drive the form workflow. With FLM we achieved the whole thing in 3.5 days, including installing the FLM software and training 2 customer staff to use the Adobe designer tool and FLM. So non-SAP systems can be brought into the mix quite easily – any mechanism that SAP itself supports to receive or distribute data from other systems [IDoc, SM59, file, EDI, BAPI, native SQL etc] can be utilised by FLM to make data available to/from forms.
5. Functionality
Is any form of digital security enabled for use with FLM?
Yes. We support the use of https, digital signatures and server-side signing with Adobe forms.
Does FLM support Zero-client-install [ZCI] forms?
Yes.
With FLM, I understand that we would control the forms to which a user has access by assigning Form Groups to the user. Does similar functionality not exist in the standard SAP scenario?
FLM has the concept of form types (an individual form) and Form Categories (a group of forms). We assign authorisations via ABAP transaction SU01 to users via SAP ‘roles’ that themselves allow access to certain or all form types and categories. We also allow or disallow certain activities in these roles, such as ‘change’ or ‘display’. We use a simple SAP User Group also to allow or disallow access to the FLM Portal itself (some users may only participate in the email scenario perhaps).
The standard scenario (by which I mean using an Adobe form embedded in a java WebDynpro application connected via function modules to R/3 ABAP) typically you would have one or more forms embedded in the application and control access via the application URL and/or java roles maintained in the java UME.
What are the main advantages of using FLM over using bespoke development?
Bespoke development of SAP Interactive Forms by Adobe has the following drawbacks that are overcome by FLM:
- Bespoke development produces applications that are form-specific and therefore creates a solution that doesn’t scale easily
- The business logic is distributed between ABAP, the web application and the form itself, and so is tough to support when problems occur
- the bespoke method is a much more expensive solution.
The FLM Business Presentation powerpoint illustrates the differences clearly between the FLM solution and the ‘standard’ solution. FLM tackles many of the more complicated aspects of bespoke development, e.g. attachment handling, concurrent versions, form auditability, solution supportability, decoupling the form posting, multi-languages, workflow etc with ease.
Does FLM support digital signatures?
Yes. FLM provides unrivalled security features for SAP Interactive Forms.
What is the FLM Mobile Portal?
The Mobile Portal enables disconnected use of eforms in a managed environment. The user synchronises their PC, updates forms and documents before disconnecting from the corporate network. Away from the office data can be collected and documents referred to without the need for connectivity. When network connectivity can be established FLM MP uses SAP Mobile Infrastructure to synchronise with the host with, if required, a secure HTTPS session.
The FLM MP is an optional extra module that requires FLM 300 as a pre-requisite.
6. Support
What is included in the annual M&S charge? When do I pay it?
The annual charge covers all new versions, releases and modifications to FLM. It also gives access to Arch FLM technical support for bugs fixes and a support line for high priority support issues.
The charge is levied on a calendar year basis, invoiced on the 1st of January. In the first year a pro rated charge is made.
How is support managed?
The product is supported directly by Arch in the UK who are the creators of the software. For form-related problems, FLM forms can be exported from a customer’s FLM system and sent directly to Arch for analysis.
If you have any questions unanswered on this page, please email them to FAQ@arch.co.uk