Varo (FLM) System Requirements

Architecture Overview 

Varo (FLM) is installed on the WebAS ABAP Stack using standard SAP tools.

Varo (FLM) software is supplied in two types of component:

The ABAP objects are of type ‘workbench’, no customizing transports are required. 

Production installation should occur after the Varo (FLM) system setup is completed and Form functionality has been validated successfully.

The entire catalogue of non-original ABAP components is delivered into the namespace /FLM/ and is therefore guaranteed by SAP to create no collisions in the customer’s own SAP system.  The /FLM/ namespace is supplied with a ‘repair key’ and the customer’s system set to be a ‘recipient’ system during the installation.

The package /FLM/CUST is supplied to the customer’s system during the installation process, and this should be repaired immediately to attach to the customer’s own transport layer to facilitate the transportation of FLM generated DDIC components through the customer’s SAP landscape [see post install guide for details].

Online Forms (Web)

For the on-line (web) form scenario a SAP UI5 based portal app is provided.

  • The Varo (FLM) Form Manager Portal.  The Form Manager Portal is a SAP UI5 Portal based on HTML5 and provides a richer user experience and is best for iOS/Andriod scenarios. The UI5 Portal support HTML and PDF based form for Desktop/Laptop environments but HMTL only for mobile devices.

The Form Manager Portal requires the installation of an additional ABAP Add-ON but no further configuration.

The Form Manager Portal has following dependencies:

  • SAPUI5 Framework. Depending on NW release the SAP UI5 component may vary.
    • NW 7.0x -  UI_70x
    • NW 7.40 - SAP_UI

All Varo (FLM) Portals can be deployed as stand alone portals or integrated into SAP Enterprise Portal using standard iViews.

Offline Forms (Email)

The off-line form scenario transports Adobe Interactive Forms as attachments on e-mails.  Hence it is required to link the SAP server to a suitable SMTP server which acts as a relay for these e-mails.  In the on-line scenario, reminders are sent via e-mail and therefore the SMTP server may also be required if this functionality is required.

At any Netweaver release of SAP, SMTP connectivity is standard functionality and is configured via transaction SCOT.  Certain system parameters may also be required to be maintained through transaction RZ10 - it is recommended to consult SAP documentation for this exercise, although configuration can be done by the Arch engineer during the Varo (FLM) setup process if required.

The configuration process is described in SAP Note 455140 - Configuration of e-mail using SMTP

There is an Varo (FLM) Functions in Detail Guide available to guide the setup of the SMTP link if required.

Interactive Forms (ADS)

Adobe Credential

When using Varo (FLM) with Adobe Interactive-Forms (PDF) an ADS Credential will need to be installed on the SAP Java Application server where ADS is deployed.

In order for ADS to be able to render PDF forms which are interactive, it is required to install into each Java stack an ‘Adobe Credential for ReaderRights’.  This is a piece of Adobe intellectual property delivered via the SAP OSS system in the form a small file.  It is installed into the WebAS java stack and then configured using the ‘Visual Administrator’.  Only one Credential is required per customer.

The process is described in SA Note 736902 - Adobe Credentials.

It is recommended that this Credential is installed prior to the Varo (FLM) installation, although this can be done by the Arch engineer during the Varo (FLM) setup process if required.

SAP Service Pack Level

For Interactive Form Scenarios (ADS) it is recommended that both ABAP and Java stacks be at the same Support Pack and are patched to the latest available before the installation process is started.  The ABAP components utilized by the FLM core routines are limited to SAP_ABA  and SAP_BASIS.  The Java components utilized by the Varo (FLM) software are limited to the J2EE Core and Adobe Document Services [ADS] components.

End User and Developer Desktop Environments

End user desktop environments must have Adobe Reader for the Offline scenario and Internet Explorer 11 as well as Reader for the Online scenario.

The lowest version of Adobe Reader supported by SAP and Adobe is currently Adobe Reader 11 (DC).  If the customer organization has an older version of Reader deployed, it is strongly recommended to upgrade to this version of Reader before the FLM installation occurs. 

If it is not possible to use the currently supported version of Adobe Reader, the correct functioning of the software cannot be guaranteed by Arch.

SAP Note 834573 - SAP Interactive Forms by Adobe: Acrobat/Reader version

Please see the latest SAP Product Availability Matrix for further details.

Developer Environments must include the above as well as a recent version of Adobe Designer.

PDF Forms - Note 1863816 - Adobe LiveCycle Designer 10.4 - Installation

PreInstallation Questionaire

Please fill out and submit the PreInstallation Questionaire here.