sapnote_0001009567- adobeforms

17.02.2011 Page 1 of 5

SAP Note 1009567 - Functional differences SAP InteractiveForms/Smart Forms

Note Language: English Version: 32 Validity: Valid Since 15.09.2010

Summary

SymptomAt the moment, several functional differences exist between the solutionsSmart Forms and SAP Interactive Forms by Adobe. This note lists thefunctional limitations of the SAP Interactive Forms by Adobe solution whencompared to Smart Forms.

Other termsAdobe Document Services, Adobe LiveCycle Designer

Reason and Prerequisites

SolutionWhen choosing a forms solution, ensure that you compare your requirementswith the features offered by the respective forms solution.

The following functional differences exist at this time:

1. Page numbering of the print job

There is no page counter for the numbers of pages in a print job, butonly one for the pages of a form.

2. Page numbering mode

Settings such as "Initialize Counter" or "Increase Counter" are set ina different way, scripting may be required.

3. Copy window and copy counter

Not supported.

4. Final window

Final windows as such are not supported. Often, however, the conceptcan be realized using scripting and the different events.

5. Styles

Styles such as the ones in Smart Forms cannot be defined in a centrallocation and used in multiple forms.

6. Large documents

There is currently a limit for the document size: on MicrosoftWindows platforms approx. 1,000 pages, on Unix or Linux systemsapprox. 2,000 pages. SAP and Adobe recommend to generate no more than800 and 1,800 pages, respectively in one document. This depends onthe complexity of the form and the data.

Generating large documents can even cause problems with only a fewhundred pages, because the data stream is transmitted as part of aSOAP message, which can result in memory bottlenecks during the

17.02.2011 Page 2 of 5


parsing of the XML document.

To prevent memory bottlenecks during transfer, you can change the typeof data transfer as of Netweaver 7.0 Support Package 6 for a doublestack installation or as of NetWeaver 7.0 Support Package 12 for aseparate ABAP Java installation. For information about the roles andtable entries to be used, see SAP Note 993612.

In either case, however, the limit of approx. 1,000 pages (up to 2,000pages depending on the platform) per document will remain.

7. Page protection

Among others, page protection can be set for subforms level. Pageprotection based on paragraphs ("Paragraph protected" or "Nextparagraph same page") in Smart Forms text modules or SAPscript Includetexts is not supported.

8. Outline paragraphs

Outline paragraphs in Smart Forms text modules or SAPscript Includetexts are only partially supported. In particular, it is not possibleto define the numbered margin independently of the left margin of thetext. The numbering is always part of the text. It is not possibleto initialize the numbering in the form context.

9. Tabs

It is not possible to set tabs in static texts. There is no supportfor all types of tab orientation. It may make sense to use tables.

The default tab step width is ignored.

10. Using graphics stored in the SAPscript graphic administration(transaction SE78)

Not supported.

11. Background graphics

Background graphics are not supported in the same way as Smart Forms.

12. SAPscript Include texts and Smart Forms text modules

Not all SAPscript or Smart Forms functions are supported. See, forexample, SAP Notes 1008550, 863893, 894389 and the onlinedocumentation. These are some of the limitations: SAPscript styles,control characters, page protection, SAP characters, system symbols,orientation of fields (for decimal separators using tabs, forexample).Fields cannot be used if they originate from tables.Note that the form output terminates during the output of unknownfields.

13. Sorting, automatic calculation

Not supported. If possible, this should be included in the applicationprogram. You must use scripting for calculations that must be made

17.02.2011 Page 3 of 5


based on the page break (page subtotals, for example).

14. Coding nodes in the context

Not supported.

15. Explicit page break in the context

Not supported. It may be possible to realize a solution usingscripting.

16. Paper trays

Not supported in NetWeaver 2004. Adjustment options for NetWeaver 7.0are described in the XDC Scenario Guide. The XDC files must beadjusted for this. Support Package 14 is required (ADS Version >=800.20070708051308.406522).

17. Duplex printing

Supported in NetWeaver 2004 as of Support Package 18. For this and forreleases of NetWeaver 7.0 older than Support Package 14, adjustmentoptions are described in the XDC Scenario Guide. See Note 766410.

As of NetWeaver 7.0 Support Package 14 (ADS Version >=800.20070708051308.406522), the design is more flexible: You canadjust the duplex printing in Adobe LiveCycle Designer for therelevant form. Prerequisite is Adobe LiveCycle Designer as of Version8.0.

18. Print controls

Not supported.

19. Bar codes

You can find a list of supported bar codes in the documentation ofAdobe LiveCycle Designer.

20. Fonts OCR and MICR

Supported. However, the font is required for the design time and atruntime. An XDC adjustment is required.

21. OTF output format

Not supported.

22. ASCII output format

Not directly supported. In particular, dot matrix printers are notdirectly supported.

Printing is possible using PDFPRINT (see Note 1444342).

23. Other print formats: Prescribe, DPL, IGP

Not directly supported. The supported formats are PostScript, PCL and

17.02.2011 Page 4 of 5


ZPL.

Printing is possible using PDFPRINT (see Note 1444342).

24. HTML output

Not supported.

25. XSF or XDF

Not supported. However, there is a similar interface called XFP. Thecertificate is "BC-XFP 6.40".

26. Callbacks to other programs during form output

Not supported.

27. Fixed user values

The decimal and date display in the user defaults is ignored. Tooutput a decimal figure or a date, the technology uses only the localeinformation passed to the form at runtime, e.g. de_DE, en_US etc.

28. Partial printing

It is not possible to print only parts of a form (neither directlywhen calling the template nor later from the spool overview).

29. Output medium (DEVICE) MAIL/TELEFAX

Not supported. Before you execute the application, you must request aPDF. You must call the send interface (BCS) separately.

30. Grouping copies

You cannot group the output of copies, for example, first three timespage 1, then page 2, and so on.

31. Forms in languages in which the text flows from right to left.

The direction of the text flow from right to left is supported forHebrew and Arabic as of NetWeaver 7.0 Support Package 6 (see Note886572). However, the layout is not automatically reflected as it isin Smart Forms.

32. Sending and downloading ADS requests from SP01

Not supported. See Note 1291734.

33. Cover page

Not supported.

Header Data

Release Status: Released for CustomerReleased on: 15.09.2010 07:49:23

17.02.2011 Page 5 of 5


Master Language: GermanPriority: Recommendations/additional infoCategory: ConsultingPrimary Component: BC-SRV-FP Forms Processing

Secondary Components:BC-CCM-PRN Print and Output Management

BC-SRV-SSF Smart Forms

XX-PART-ADB-IFM Adobe Interactive FormsMaintenance

The Note is release-independent

Related Notes

Number Short Text

1444342 Device type-independent printing of interactive forms

1126931 PPF: No grouped output for output requests

1121176 Adobe LiveCycle Designer 8.0 - Installation

1008550 Limitations on floating fields in Adobe forms

894389 Rel. Restr.: SAP NW 2004s - Adobe Document Services

886572 Adobe document services: Central Patch Note for NW 7.0

863893 Interactive forms: Release restrictions (NetWeaver '04)

517673 Flexible Real Estate: Features and release restrictions

Documents

sapnote_0001009567- adobeforms