SAP Interactive Forms by Adobe

Purpose
As of SAP NetWeaver ’04 (in SAP Web Application Server), you can use a new solution to create interactive forms and print forms for the optimization of your form-based business processes. This solution uses Portable Document Format (PDF) and software from Adobe Systems Inc. that has been integrated into the SAP environment. You can create interactive forms in PDF format that allow users to fill out the form on the screen and save their entries in XML format in the form. When the SAP system receives the PDF form, it extracts the data saved in the form, and can process it further. You can also merge a form template with current system data to generate a PDF document that can then be printed or sent by e-mail. SAP Interactive Forms by Adobe offer you the following business advantages: ● Interactive functions automate the creation of data for SAP systems ● Full integration into the SAP development environments for Java and ABAP ● User-friendly tools reduce the time and costs associated with creating form layouts. ● The usage of the PDF format means that forms retain their appearance regardless of the environment they are used in. In certain circumstances, you require a license for interactive forms. For more detailed information, read SAP Note 750784 on SAP Service Marketplace at service.sap.com/notes.

Implementation Considerations
SAP Interactive Forms by Adobe are particularly well suited to business processes in which employees enter data in a form-based solution and then want to transfer this data automatically to the SAP system. In the simplest cases, you only require the free Adobe Reader to display or fill out PDF forms on your front end.

Integration
SAP Interactive Forms by Adobe is included in SAP Web Application Server and can be used by any applications that are based on SAP NetWeaver ’04 or later. The following Adobe software is included in the form solution: ● Adobe LiveCycle Designer A graphical tool for designing form layouts; it is integrated into SAP NetWeaver Developer Studio and ABAP Workbench. ● Adobe Document Services Web services used to generate the PDF forms at runtime; in interactive scenarios, they extract the XML data from the form and send it to the system. Adobe Document Services run on SAP J2EE Engine. This means that you must install the Java Stack of SAP Web Application Server, regardless of the development language of your application (ABAP or Java).

Features
SAP Interactive Forms by Adobe offer the following basic functions: ● Create form templates for the layout that include logos or pictures

● ● ● ● ● ● ●

Generate documents by merging form templates and current system data Edit forms online or offline Forms can be filled in advance automatically with specific data from SAP applications and then sent to the correct recipients using secure methods Automatic consistency checks for forms Activate enhanced functions such as comments Digital signatures and form certification Send completed forms to the SAP application with automatic updates of the business data

There are two basic types of forms: Interactive Forms For business processes that require close cooperation between employees, you can design interactive forms as a part of a Web Dynpro application. You can use the following development environments: ● Interactive Forms in Web Dynpro for Java in SAP NetWeaver Developer Studio ● Interactive Forms in Web Dynpro for ABAP in ABAP Workbench These forms can contain dropdown menus, pushbuttons, text fields, and other elements that enable users to enter data. The form is generated in PDF format, which, for example, can be displayed by the user in a browser. The user uses Adobe Reader or Adobe Acrobat to fill out the form and saves the changes made to the form in XML format. The SAP system extracts the data from the form and saves it to the database, where it can be processed further. You can use these forms in two basic scenarios: ● Online The user is logged on to the SAP system when he or she fills out the form. ● Offline The user is not logged on to the SAP system when he or she fills out the form. Once the form has been filled out, the user sends it to the issuer of the form, for example by e-mail. The SAP system of the issuer then extracts the data from the form. Forms for Printing, E-Mail, or Fax You can use the Form Builder (integrated into ABAP Workbench) to create PDF-based print forms that you can then print or send by e-mail or fax. When you create these print forms, you can rely on the tried and trusted principle of separate data retrieval and form layout processes. This enables you to make changes to either one of the processes, without affecting the other.

PDF-Based Print Forms
Purpose
PDF-based print forms are part of the SAP Interactive Forms by Adobe solution and are used for printing in SAP systems. As well as standard output on printers, and the option of archiving documents, you can also use your application to send a PDF to the Business Communication Services (BCS). Here, you have the option of faxing or e-mailing your documents. The following gives you an overview of how a PDF-based print form is structured, and also tells you how to create a PDF-based print form in the development environment of the ABAP Workbench. The integrated Adobe LiveCycle Designer™ software supports you when you do this. This software must be installed on your front end before you can create a layout. To see a print

preview of your form, you first need to install Adobe Reader or a complete version of Adobe Acrobat. This documentation does not discuss how documents are printed and controlled on printers. Instead, it discusses the whole process up to when a file is sent to output management functions, such as the spool system in SAP systems. Note that, for printing and previewing PDF-based forms, you need to use a PCL, Postscript, or ZPL printer and an appropriate device type (such as POST2, HPLJ4, HP9500, PDF1, AZPL203, or AZPL300). You cannot use a printer with the device type SAPWIN/SWIN. More information is available in the SAP Printing Guide (BC-CCM-PRN), under Printing PDF-Based Forms.

Integration
An activated PDF-based print form corresponds to a callable function module in the SAP system. The complete logic of the form is represented by this function module. When a form is printed, it is called by an application program, which collects the relevant application data. The application program uses the function module interface to send the data. Therefore, the data collection process is split from the logic of the form. This means that you only need to adjust the form when you modify the logic or layout. There are several ways of creating interactive forms. For more information, see Interactive Forms.

Features
To develop a PDF-based print form, you use Form Builder, integrated with ABAP Workbench. This tool enables you to create a complete form description, even if you do not have extensive programming skills. The tool supports you in the following tasks: ● Creating layouts Here, you use the Adobe LiveCycle Designer to design pages or create the layout. ● Specifying the data used in the form In the form context, you specify which data, tables, texts, and graphics are sent to the form. ● Migration of Smart Forms By migrating Smart Forms, you can reuse them as PDF-based print forms. You can find the Smart Form migration tool in transaction SMARTFORMS.

Smart Forms are still supported; you can continue to forms created in Smart Forms without making any changes. ● Importing existing PDF files or forms This tool is integrated into Adobe LiveCycle Designer and enables you to use your own templates for your form. ● Scripting Adobe LiveCycle Designer uses the script languages JavaScript and FormCalc. FormCalc is a simple Adobe script language for typical form calculations, including mathematical and logical functions, and date and character string functions. For more information about FormCalc, and a FormCalc language reference, see the online help of Adobe LiveCycle Designer. To achieve the best level of performance when processing forms, use as little scripting as possible in the form. If possible, perform all calculations and data analysis in the application program, before the form is called. Printing and archiving the PDF-based print form:

its appearance in graphics. A form context that contains the form logic. you control them with function modules that you integrate in your application program. PDF-Based Print Form Definition A PDF-based print form is a form designed for mass printing in SAP systems. it enables variable fields to be displayed. This logic controls the dynamic formatting of the form. These parameters are not viewed in Form Builder. Use PDF-based print forms can be used for the following: • • • • • • • • Order confirmations Invoices Account statements Checks Salary statements Delivery notes Customs forms Industry-specific forms. A layout. such as quality forms in the automotive industry Structure A PDF-base print form has the following attributes: • • A form interface that sends the application data to the form.You can use output parameters to specify print and archive settings. you define how the output data is positioned. . It has the standard Portable Document Format (PDF). and it can specify that invoice items can be processed repeatedly in a table. In the layout. Instead. For example. it specifies that certain texts appear only under certain conditions (one text for a first warning and a different text for a second warning). and so adapt the output to your requirements. and the design of the pages. • Architecture The following graphics show you the architecture that is implemented when you create and print a PDF-based form.

you generally need to insert application data in the form. which consists of the form context and layout. You can assign multiple forms to the same interface. Form Output − Runtime If you use an application to create a form.Creating a Form The form interface is created separately from the form. Form interfaces and forms are stored as separate development objects in the repository. When you create a form. The form description includes the complete form design as a complex description in XML. if they use the same data. you must assign it to a form interface. The architecture of PDF-based forms is designed to separate the collection of the application data from the definition of the actual form: .

table data selected previously in the application program. Texts. Structures Adobe Designer includes two different types of pages that you can use to structure your form layout: . data. PostScript. When the generated function module is called. and determine the order of the pages that have differing structures. the form description and application data is sent to Adobe document services. This can be. it uses its interface (corresponds to the form interface) to send it the application data. Use You can create any number of pages for your form. for example. When the application program calls the function module. These services create the actual form: ● As a PDF to be processed later by the application or for the preview in Adobe Reader ● As a PCL. or ZPL to be sent to the spool A function module is available for more precise control of the output. a function module is generated that encapsulates all properties of the form.When you activate the PDF-based form. and various other types of objects can be displayed in the output range of a form page. tables. Page Concept and Elements of a Form Definition You specify the page layout for a form in Adobe Designer.

3. Designing Forms with the Form Builder Purpose You can use this process to create or edit a PDF-based form. and lines  Dynamic objects.. 1. 1. graphics. In the interface.• • Master pages Body pages You can position various elements on these pages. 1. you define where the data comes from that you want to display in the form. . 2. To access the online help for Adobe Designer. numeric fields.. You create a form object. you use the Form Builder that is integrated with the ABAP Workbench. To do this. These elements are available in a library in Adobe Designer. and password fields  Special date objects Your own user-defined objects Bar codes For more information about the page concept. 2. • Choose Help → Help Topics under Layout. 3. Process Flow To create a form. Adobe Designer is installed with the SAP front end. text fields. rectangles. see the online help in Adobe Designer. you call the interface function in the Form Builder. You can also edit a migrated Smart Form. Prerequisites You have installed Adobe Designer on your front end. circles. such as option and list fields. You activate the interface. date and time fields. call the Form Builder: • • • You are on the screen Form Builder: Change Form <Form Name> or Form Builder: Display Form . and the different types of page elements. • Standard objects • • • • • Static objects such as texts.

Enter your data and save the object. Proceed as described under 5. 5. proceed as follows: 1.4. The Create Object Directory Entry dialog box appears. you drag and drop the required parameters from the interface you have defined. see Interface in the Form Builder. Enter the name of the form in the Create Form dialog box. 3. proceed as follows: 4. 11. 8. and drag and drop data from the form context you have defined. In the Create Interface dialog box.. 7. In the context menu of the package. For more information about the different interface types. 2. you create the layout. You are in the Repository Browser of the ABAP Workbench. 13. 10. You activate form. and addresses. below. You use this graphical tool to design the printed appearance of the form. You have two options here: Creating a Form Object in the Repository Browser 7. To create a form with a context and layout. choose Create ® Form Object ® Interface. . 3. 9. you must create them. 4. In the context in the Form Builder. graphics. 12. You can use an application program that collects the relevant data to call this function module. You then have a PDF-based document for mass printing in SAP systems. c. Before you can start to edit these objects in the Form Builder. 6. In the context menu of the package. Result You have created a function module that encapsulates the form description. 2. Enter the name of the interface that you want the form to use. 5. b. 6. Creating a Form Object Use Form interfaces and form contexts with layouts are known as form objects. 6. a. c. To create a form interface. b. 1. enter the name of the interface and select an interface type. In the layout function in the Form Builder. .. 4. You can also insert texts. 2. Select a package. choose Create →Form Object → Form. 6. 5. 5. Choose Save. a.

24. 4. 4. 5. . follow the procedure show above under 4a. 20. The system calls the SE61 editor and you can create your documentation. 19. This documentation is used as F1 help and contains information for support team members or form developers who need to examine the form. 3. Choose Back. 1. Result The Form Builder starts. Under Form Builder: Entry Point. follow the procedure shown above under 3a. Under Form Builder: Entry Point. 4. that the documentation is ignored by the functions Upload Form Object and Download Form Object. . Choose Create. Prerequisites You require SAP NetWeaver SPS 8 or higher. The documentation is not included in the form output and is only available in Form Builder. If you want to create a form. If you want to create an interface. 14. 5. Creating and Displaying Form Documentation Use You can create documentation for each of your forms or form interfaces (form objects). Choose Goto → Documentation ® Change. and transported automatically with its accompanying form object. 2. 3. Call transaction SFP. however.. . Note. Choose Goto ® Documentation ® Display. 3... Displaying Documentation 23. 1. specify a form or interface. specify a form or interface. 2. Enter the name of the interface or form. 15. 22. renamed.. The creation of form documentation is integrated into the standard documentation environment (transaction SE61).. 16. 17. A form object is assigned to precisely one piece of documentation.Creating a Form Object from a Transaction 3. 2. 21. Save your changes. 25. Creating or Changing Documentation 18. .. You can start to edit the interface or form. 1. deleted. the documentation object is copied. The documentation is displayed.

These fields are replaced by the current data at runtime. you do not need to create the form context here. ● ● XML Schema-Based Interface You use this interface type if you create your forms in Form Builder in Web Dynpro for ABAP. the data is not specified or inserted in the form until runtime. You can use form routines that are defined in ABAP Editor. the system shows the available system fields automatically in the interface. When you call the context in Form Builder. You use fields inserted as placeholders in the form to specify the appearance and location of the data in the form.Interface in Form Builder Use You want to include data in your form that was not specified when the form was created. You cannot edit it within Form Builder. you can create program code to modify global definition data before the form is processed. You cannot enter system fields directly. in an appropriate editor on your front end. You can assign currency and quantity fields. The XML schema already contains the form context. You use the form interface to specify this data. You can then drag and drop the required fields to the context. Features You can choose from the following three interface types: ● ● ● ABAP Dictionary-based interface Smart Forms-compatible interface XML-based interface ABAP Dictionary-Based or Smart-Forms-Compatible Interface These two interface types have different standard parameters in the form interface. This can include the following data: ● ● ● Data selected from the database tables of your application. you specify the data that is exchanged with the application program (such as tables). The system fields contain data with a predefined meaning (such as the date). Under Code Initialization. such as dates Data that you have calculated or implemented in a form yourself. You load the finished interface into Form Builder. you define your own fields. Under Global Definitions. Both interface types give you the following options for including data in PDF-based print forms: ● ● ● In the form interface. which is sent directly to the data view in Adobe LiveCycle Designer. such as totals for tables For all three of these data types. This interface is an XML schema. You create the XML schema as a local XSD-type file. Data provided by the SAP system or by the PDF-based print forms solution. The XML schema-based interface consists of the following: . which must be constructed in accordance with the W3C standard. Unlike ABAP Dictionary-based interfaces and Smart Forms-compatible interfaces.

Activities There are two ways of calling Form Builder for the interface: From the ABAP Workbench (Transaction SE80) Choose Form Objects → Interfaces and select an interface. From Transaction SFP 26. form interfaces do not support Changing parameters. However. Choose Interface. The XML schema The loaded XML schema is displayed here. 28. or Display. 3.. . 4. Choose Create. Enter the name of the interface.. 6. 5. 1.● ● The form interface with the parameters that specify the data The runtime data from the application program is specified in the import parameter /1BCDWB/DOCXML (type XSTRING). Defining a Form Interface Use You define a form interface to send data from your application to a form. 29. ● The application program provides the data that you want to insert in the form. See also: Getting Information about Interface Parameters Overview of Function Modules (in ABAP Workbench: Tools) . Change. Call transaction SFP. To select the interface type. You can start to edit the interface. Form Builder starts. Integration The form interface is a part of the Interface form object and is defined in the Form Builder. You cannot make changes if you have chosen Display. 2. The semantics of the valid parameter types match the semantics of a function module. 27. switch to the Properties tab page. 30. you already know the types of the corresponding variables. Prerequisites ● You have created an Interface form object. The form interface of a form is structured in the same way as the interface of a function module in the system. Therefore.

the application program must provide the parameters. All data types are valid. TYPE can be selected under Type Assignment. you see the standard parameter /1BCDWB/FORMOUTPUT of the generated function module. You use this parameter in your application program. 2. choose Insert Line ( ). ABAP-based or Smart-Forms-compatible interface ○ To insert a new line. Activate the interface. You cannot change this parameter. 37. 31. Open the required interface in the Repository Browser of the ABAP Workbench. 1. To display this structure in the ABAP Dictionary.. You see a screen for entering import parameters. 35. the Tables option gives you extra parameters. they can also be specified in a different order from the code of the application program. then the output of the form ends with the program crashing (hex dump).Creating Function Modules (in ABAP Programming (BC-ABA)) Procedure 7. Under Form Interface. You do not need to mention these parameters in the form. 34. it is also possible that the application program provides parameters that the form does not need. 32. 3. When you double-click Export. double-click the SFPDOCPARAMS type. XML schema-based interface • ○ The standard parameter /1BCDWB/DOCXML with the type XSTRING is used for sending data from the application program. This screen also shows the standard parameter /1BCDWB/DOCPARAMS. The Interface tab is displayed. If a parameter has been defined in the form. This has the advantage that an application program can work with several different forms. However. Migrated Smart Forms Interface or New Smart Forms-Compatible Interface When you edit the interface of a migrated Smart Form or a new interface that is compatible with Smart Forms. Enter the parameter names of the data you want to import. 33. 6. 4. You cannot change this parameter. but is not defined when the application program is called. the system also lets you use the standard parameters from the Smart Forms. 7. to specify the value for the language setting. When you set the Import. At runtime. To display the exceptions used by the generated function module. for example. You use this parameter in your application program. double-click the Import node. 5. These names are valid for the whole form and do not have to match the variable names in the data collection program. . and Exceptions parameters. . to make the generated form available as a PDF for further processing. double-click Exceptions. Export. for example.. • 36.

for example. you define any data needed by the form. Activities Double-click the node that you want to edit. you have the option of defining your own fields to be used anywhere in the form. Field Symbols You can use field symbols as pointers when you extract data from internal tables. but which has not been provided by the form interface (for example. Here. You can also select additional data without having to make changes in the application program. to display totals).) Result You have defined the form interface and you can use the specified parameter names in the form context. You can initialize the global data. you create data types as free ABAP code. You can initialize global data before you start to process the form. Features Global Data Here. for example. See also: Initialization Initialization Use SAP customers can use this function to execute ABAP program code before a form is processed. Global Definitions Use Global definitions belong to the interface in the Form Builder. We recommend that you use Global Datain the initialization. Types Here. you can use the existing application program of this Smart Form without making any modifications. Functions You use the ABAP Editor to write the program code (Code Initialization) that is executed before the form is processed. . You can include subroutines (Form Routines) when you do this. to convert selected application data. if the ABAP Dictionary does not provide a type. (See also Switching Runtime in Migrating Smart Forms. to convert selected application data.If you have a Smart Forms-compatible interface.

See also: Global Definitions Specifying a Currency or Quantity Reference Use In the ABAP Dictionary. the system cannot recognize this reference automatically. you also decide the form logic by specifying conditions for processing the nodes. Context in Form Builder Use In the context (also known as the form context). . to ensure that the value field is formatted correctly. and formats the value field according to the currency or unit in the assigned field. 39.. Under Data Type. 2. you can assign a currency or quantity field to a table field. CURTAB) to a value field in another table (for example. If the value field is in a different table from the currency or quantity field. the system recognizes the reference automatically. Create the reference to the currency field by entering the following values: 1. you specify which data is copied from the interface to the form. you must indicate this reference to the system in the form. Procedure You want to assign a currency or quantity field in one table (for example.. In this hierarchy. In the second case. the system can then insert the relevant currency or unit: If the value field is in the same table as the corresponding currency or quantity field. which is the currency field of CURTAB. In the output of these fields. Reference Field: CURTAB-CURRENCY. 8. 38. Result In the output of the PDF-based print form. VALTAB). . if this is the value field of VALTAB that you want to display. specify whether the data type is a currency or quantity. the system formats the value field VALTABVALUE according to the assigned value in the currency or quantity field of the global variable CURTAB-CURRENCY. You include this data as a node in a hierarchy structure. Field Name: VALTAB-VALUE.

then the node is skipped. 43. you can hide any items. You cannot edit if you have chosen Display. a properties window is displayed under the context. The system sends the form context to the layout function of Form Builder automatically. Enter the name of the form. From Transaction SFP 40. To do this. 41. you use the Data View nodes to include the data in the form. For each node. You can also specify WHERE conditions for the selection of data from tables. In this way. You can specify conditions. Features You use the form logic of the context to control which rules are used to send the hierarchy nodes to the layout. 44. or Display. 45. Choose Form. Create or edit the context. When you create the layout. 5. addresses. The layout function calls Adobe Designer. If the condition is not met. graphics) are included in the output Whether the data of a node is Active or Inactive Whether a specified node or an alternative node is processed 9. choose the Properties tab page. To do this. 2. Editing the Form Context You can edit the form context in the following ways: ● Create nodes . Form Builder starts. 6. Call transaction SFP. You construct the form context from the existing interface. and the form context itself appears as a hierarchy under Data View. if this is supported by the selected node. that you do not need. To view the entire form logic. Activities There are two ways of calling Form Builder for the context: From ABAP Workbench (Transaction SE80) From the object list. Only active nodes are forwarded to Form Builder to be processed in the layout. and how they are processed. 42. Define the layout type of the form.Prerequisites You have created the form objects Interface and Form. as well as all its subnodes. choose the Context tab page. Change. Integration The context function in Form Builder is the link that binds the interface to the layout. such as table fields. expand all nodes.. 3. . 4. Choose Create. then the node is processed. If the condition is met.. 1. choose Form Objects → Forms and select a form. The form logic determines the following: ● ● ● Whether the content of the node (text.

. The interface on which the form is based is displayed. Screen Display in the Context of the Form Builder The following graphic shows you the structure of the screen that appears when you select the Context tab in the Form Builder. To edit the layout. but cannot be changed here. see Screen Display in the Context of Form Builder. To edit the interface. choose the Properties tab and double-click the name of the interface.● ● ● Move and copy nodes Set node as active or inactive Update nodes For an overview of the graphical user interface. choose the Layout tab.

Folder Condition . depending on conditions Groups subnodes for clarity Not a separate node. data nodes are generated automatically. You can use conditions to specify whether the data in the form is included and displayed at runtime. data nodes are generated automatically. or dynamic text Graphic Address. All nodes. Some nodes represent the data in the form. Displayed directly after the node that is processed depending on this condition. The first node in the context is a folder node and has the name of the form. Node Types Nodes Without Subnodes Symbol Node Type Text Graphic Address Meaning Text module. the address data is extracted directly from database tables and formatted for printing. include text. TRUE and FALSE.Nodes in the Context Definition Nodes in the context are organized in a hierarchy. can have any node as a direct subnode Any nodes None Table/loop Dynamic table Alternative Alternatives. others represent the form logic. Other Nodes Symbol Node Type Data node Structure Meaning Elementary data field Structure Possible Direct Subnodes None All nodes.

Click a node in the context with the secondary mouse button to display the context menu for this node. . 2. you can create nodes for text. Only active nodes are sent to the layout in the Form Builder. 10. To display the context menu of the node. you can do the following: •  Enter and change properties •  Enter and change conditions Result You have created nodes in the context. and paste nodes. 52. drag it as above.. select the node under which you want to insert the new or copied node. Double-click the node to display more details about the node in a screen under the context. choose Paste. graphics. cut. 4. use Drag&Drop to drag it to the required place in the form context. As well as the data defined in the interface. 47. . .. 1. To copy a node. you have the following options: •  You can set the node as Active or Inactive. To create one or more nodes. choose Copy. and addresses. In the context. Moving or Copying Nodes with the Context Menu 11. click the secondary mouse button.Creating Nodes 46. In the context of this node. In the context. 2. 1. select a node that you want to move or copy. 50. 3. Double-click a field in the interface to display a dialog box with detailed information about the properties and type of the field. 51. •  You can create a new node. Moving or Copying Nodes Moving or Copying Nodes with Drag&Drop • • To move a node. drag the required fields from the interface on the left of the screen to the context. 49.. •  You can copy. Now perform the following: •  To move a node. Depending on the data type. delete. choose Cut in the context menu of the node. 3. •  To copy a node. but press the Ctrl key at the same time. Depending on the node type.. 48.

you see the BOOKINGS node with the row node and FLDATE and PASSNAME in the data view of Adobe Designer. you can set them as Active or Inactive in the context menu. CONNID. . Unlike the active or inactive setting. select all the other data nodes in the table and set them as inactive. you only see the data that you actually need for the form. as long as it is active. PASSNAME. Example You have created a BOOKINGS table node in the form context. 2. CARRID. These nodes are flagged as generated ( ). In this way. At runtime. When you expand the table node and its subnodes. Accordingly. when you choose the Layout tab page. only the active nodes are included in the form. conditions are not implemented until runtime. which makes it easier to use. or copy generated nodes (flagged with ) in structures and tables.You cannot delete. Activities 12. The form context shows both generated and non-generated nodes. then you can use this function to update the context. However. A node with a condition always appears in the data view of Adobe Designer. . Updating Nodes Use If you have already started to edit the form context and you have made changes to the field definition of nodes. and so on). Click the secondary mouse button and choose Set to Active or Set to Inactive in the context menu. Select one or more nodes. move. Setting Nodes as Active or Inactive Use To hide one or more nodes in the form context. FLDATE. 54. To copy only the FLDATE and PASSNAME data nodes to the layout. when sending them to the layout in the Form Builder. You can set also set individual nodes as active or inactive in the Properties window. 1. set these nodes as inactive... Only these two data nodes in the table will be included in the form at runtime. 53. you can see all its data nodes (MANDT. Only active nodes are sent to the layout and can be used by Adobe Designer in the data view.

com/notes. see SAP Note 808116 at service. A node can have active or inactive status. Choose the node that you want to update. such as Name. 56. Description. the top nodes of structures or tables that you have inserted in the context from the interface. For more information about converting older PDF-based print forms. . Properties Use Properties describe the content or meaning of a node. you can nest tables inside each other. and Status. 58. or data nodes that have a reference to the ABAP Dictionary. . To update a node together with all of its subnodes (generated and nongenerated nodes). single record nodes. or move generated nodes.sap. In this way.. For an explanation.Generated nodes (flagged with ) are the fields of structures or tables that you have inserted in the context from the interface. as well as the general properties. You cannot delete. Non-generated nodes are. 59. 13. for example. . structure nodes. 2. Depending on the chosen node. on the right of the screen above the context. If you use loop nodes. These nodes are not generated. 2. You can change the appearance of structures and tables by adding more data nodes or tables.. see the description of the node. the system also displays additional nodespecific properties (which you can change). These nodes are not flagged with . Double-click the node to open the properties screen. Activities 55. and used in the form output. 1.. For more information. You can now change general properties of the node. 14. You cannot change this. 3. and reduces the need for translations.. see Setting Nodes as Active or Inactive. with the text Update. copy. You can choose non-generated nodes only. choose the icon. for example. This has the advantage that these texts do not need to be saved in the form. Activities 57. 1. Only active nodes are sent to the layout in the Form Builder. However. the system copies the short text of the type from the ABAP Dictionary under Description. you can set any nodes that you do not need in your form as inactive.

This field can contain. Choose Conditions. 62. 5. You can choose both AND and OR relationships. The operand can be a field (variable) or a value. . is then only processed if the related condition is met. Prerequisites A node exists for which you want to define conditions. A node. 60. 65. for example. The Properties window opens. Choose Relational Operator to display a screen where you can make a selection of relational operators. • ■ A dynamic field is the name of a field. specified in quotation marks. Activities 15.In many cases. 66. 7. 64. This node must allow conditions to be defined. For each line. 61. for some nodes you can also specify conditions for the form output. It is not entered in quotation marks: FIELDFORNAME. the text module name at runtime. 2. To insert a line. Choose Operator to link successive lines with each other. In the first line. To select from two alternative subhierarchies in the form output. Double-click the node for which you want to define a condition. 1. 3. you can enter a condition with two operands. click . use the alternative node. ■ • Conditions Use You can define conditions for individual nodes. or for whole subhierarchies of the context. 6. 4. you can enter static and dynamic values for the node properties: An example of a static value is a text module. As well as the properties. 63. or all its subnodes. It is entered in the format 'TEXTNAME'. the Operator field stays empty. Features You can define conditions using logical relationships.

• • • • For data nodes that reference the ABAP Dictionary. 2. 70. You cannot change this.. 67. Inserting a Data Node Using the Context Menu 16.. However.  The full field name of the node is displayed under Data. 3. Select an existing node in the context. In the layout in the Form Builder. 1. Choose Continue. Result You have created a complete data node. . you can insert this node in the form. the system takes the related short text from the ABAP Dictionary. enter a field name. Use the F4 help to display a list of all data fields used in the interface. In the Create Data dialog box. The text chosen here is used in Adobe LiveCycle Designer to display the label of the data field in the layout.Inserting Data Use You want to insert elementary data fields ( of the screen. You have two options here: Inserting a Data Node with Drag&Drop ) that are specified in the interface on the left Use Drag&Drop to move the required data field from the interface to an existing node in the context. In the context menu of the node. 68.  Under Status. you can select the Field Label. under which you want to create a data node. 69. To display the context menu of the node. 4. enter the prerequisites that need to be met before the data node is processed at runtime and displayed in the form. you can set the data node as active or inactive. The system creates a data node under the selected node. the system displays the properties of the inserted data node. choose Create → Data. .  Under Conditions. click the secondary mouse button. Editing Properties and Conditions • In the window under the context.

under which you want to create a structure node. In the context menu of the node. you can set the structure node as active or inactive. 76. . 6. 3. or switch it to active or inactive. 1. 71. 72. Under Status. click the secondary mouse button. Select an existing node in the context. 74. which means they are flagged with the icon. 2. These have been generated. you can insert the structure node in the form. 4.Inserting a Structure Use You want to insert a structure ( two options: ) from the interface on the left of the screen. choose Create → Structure. 73. You can specify conditions for each data node in the structure. The system creates a structure node under the selected node. 5. In the Create Structure dialog box. You have Inserting a Structure Node with Drag&Drop Use Drag&Drop to move the required structure from the interface to an existing node in the context. The node is fully expanded so that you can see the individual fields of the structure. When you expand the node. the system displays the properties of the node. Inserting a Structure Node Using the Context Menu 17. enter a structure name. enter the prerequisites that need to be met before the structure node is processed at runtime and displayed in the form. Result You have created a complete structure node. Under Conditions. Use the F4 help to display a list of all structures used in the interface. In the window under the context. To display the context menu of the node. you can see the individual fields of the structure. In the layout in the Form Builder. 75. Choose Continue.

4. The node is fully expanded so that you can see the individual fields of the table. choose Create → Loop. 7. 79. To display the context menu of the node. You can use WHERE conditions to select only parts of the data from the table at runtime. below. click the secondary mouse button. see the documentation for Smart Forms. Choose Enter 5. Under Control Levels. the . 82. The system creates a table node under the selected node. restrict the table range that you want to read by setting the input fields From Row and To Row. You have two options here: Inserting a Table Node with Drag&Drop Use Drag&Drop to move the required table from the interface to an existing node in the context. Proceed as described under 5. 1. 80. you can set the table node as active or inactive. specify the assignment type under Output Behavior and also the work area of the table. enter one or more data fields from the table that you want to use to group information in the output. In the context menu of the node. under which you want to create a table/loop node. 2. 78. Under Conditions. 81. Use the F4 help to display a list of all tables used in the interface. In the window under the context. enter a table name. When you choose this option.Inserting a Table or Loop Use You want to include a table ( ) from the interface on the left of the screen and define the loop that selects the table data. 3. Inserting a Table Node Using the Context Menu 18. enter the prerequisites that need to be met before the table is processed at runtime and displayed in the form. . 83. • ○ If you are using a migrated Smart Form as a form. 84. Only active nodes are sent to the layout in the Form Builder. the system displays the properties of this node.. 8. You can also specify conditions for individual data nodes in the table.. • ○ If required. For more information. In the Create Loop dialog box. under Reading Internal Tables. Select an existing node in the context. 77. You can set individual data nodes in the table as Active or Inactive in the context menu. • ○ Under Status. 6.

If multiple records are accessed. 2. Inserting a Single Record Node Use You can use the single record node ( ) to extract single data records from internal tables. . When you specify a search key. Select an existing node in the context. 91. 4.. which means they are flagged with the icon. In this case. you can see the individual fields of the table. Use the F4 help to display a list of all tables used in the interface. the data is selected according to your settings. At runtime. These have been generated. under which you want to create a single record node. For more information about this statement. kn = fn result. In the Create Single Record dialog box. this system field contains the SY-SUBRC value of the last access. 1. you can set the single record node as active or inactive. You can choose between ascending and descending sorting.. 87.. The node is fully expanded so that you can see the individual fields of the table. 90. 86. 89. you can insert the table node in the form. The system creates a single record node under the selected node. However. 2. When you expand the node.. . the system displays the properties of this node. enter a table name. 3.context tree is changed. Data nodes that are defined as part of a structure within the table cannot be specified as a control level.. Result You have created a complete table node. Choose Continue. . choose Create → Single Record. the table row is read by the ABAP statement READ TABLE itab WITH KEY k1 = f1 . Procedure 20. 1. 85. The grouping is indicated by the selected fields being placed before all other fields of the table. You can extract a single row (record) of a table in two ways: 19. In the window under the context. this is only active if you do not set the Already Sorted flag under Properties. You specify a search key. see Reading Rows of Tables. In the layout in the Form Builder. 88. • ○ Under Status. the return code SYSUBRC is inserted in the system field SFPSY-SUBRC. 5. You enter the row number.. In the context menu of the node.

To do this. ○ Under Row. • Result You have created a complete single record node. Only active nodes are sent to the layout in Form Builder. When you expand the node. enter the prerequisites that need to be met before the table row is processed at runtime and displayed in the form. In this way. you can insert the single record node in the form. which means they are flagged with the icon. Under Conditions. At runtime. see Inserting a Table or Loop. 92. Procedure You enter the required information in the table node. Prerequisites You have created a table node or a loop node. • ○ Select the Binary Search option only if you want to use a search key to display the table row. and you want to perform a binary search. These have been generated and cannot be deleted. enter the row number of the internal table that you want to extract. You can choose from various text types: ● Text modules . 7. select a data node. Inserting a Text Use You can use a text node to insert texts in the output of a form. you can see the individual fields of the table. define a nested output for a flat internal table. You can also specify conditions for individual data nodes in the table. 6. 93. For more information.You can set individual data nodes in the table as Active or Inactive in the context menu. In the layout in Form Builder. for example. Grouping Tables by Data Fields Use You can create control levels to group tables by data fields. Note that you cannot enter any information under Row. Enter this key under With-Key Conditions. the data is selected according to your settings. you can. The properties and conditions that are displayed refer to the data node. You can also use a search key to extract rows from the internal table.

Remember the restrictions that apply when processing forms with inserted texts. 98. or Dynamic Text. You can find a list of restrictions under: • • ■ ■ Entering Text Module Properties Entering Include Text Properties Procedure 21. In the context menu of the node. Only active nodes are sent to the layout in Form Builder. 99. They are crossclient texts and are linked to the Change and Transport System and translation tools. click the secondary mouse button. 97. (See: Entering Text Module Properties. 1. 95. Include Text. Save and confirm your changes in the next dialog box. The text name is specified by the content of a variable field. Prerequisites The text module or include text that you want to insert must exist in the system. Entering Include Text Properties) 100. To display the context menu of the node. For dynamic texts. None of these text types are inserted until the form is printed. In the Properties window under the form context. You can set a text node as Active or Inactive in the context menu.● ● Include texts Dynamic texts Include texts are SAPscript texts that already exist in the system. 96. choose Text Module. Under Conditions. 4. 7. choose Create → Text. The text module exists in the system. Under Properties. Select an existing node in the context. under which you want to create a text node. Text modules also exist in the system. 6. 94. enter the required information about the text type. 3. The system creates a text node under the selected node. 2. 5. you create and edit them in transaction SMARTFORMS. Entering Text Module Properties Prerequisites You have created a text node in the context and selected the text type Text Module. enter the prerequisites that need to be met before the text node is processed at runtime and displayed in the form. the text and its name are not known until the output of the form is created. . The system modifies the Properties window according to your selection.

Specify the general properties of the text module. Enter the text language in which you want the text module to be inserted. 5. 104. Under Text Name. The corresponding text is not inserted until the form is processed. but not SAP icons. 3. but not for aligning fields within texts SAP characters. Choose F4 to see a selection of languages. and status. next paragraph on same page Character formats: Superscript and subscript. . 4. 102.. Procedure 101. even if the inserted text module does not exist in the system. you can specify a different style. bar codes Special characters System fields. such as SFSY-DATE Hyperlinks The following are supported with restrictions: 22. see Maintenance of Text Modules in the Smart Forms documentation.. 106. Under Style. description. Result You have created a text node. ● ● Tabulators. Choose F4 to see a selection of all text modules in the system. 103.Restrictions The following components are not supported in text modules and are ignored when the form is processed: ● ● ● ● ● ● Outline paragraphs Paragraph properties: Page protection. 1. 6. enter the name under which the text module is stored in the system. Set the flag No error if text not available if you still want the form to be printed. and an error message appears. for example More information about these restrictions is available in the SAP Notes 894389 and 863893. 2. Set the flag Copy Style from Text Module if you want to keep the style from the text module. such as the name. For more information about creating and changing text modules. 105. the form is not printed. . If you do not set this flag.

They are cross-client texts and are linked to Change and Transport System and the translation tools. 3. for example The following are supported with restrictions: More information about these restrictions is available in the SAP Notes 894389 and 863893. and status. Prerequisites You have created a text node in the context and selected the text type Include Text. Restrictions The following components are not supported in SAPscript texts and are ignored when the form is processed: ● ● ● ● ● ● ● ● ● ● ● SAPscript styles Outline paragraphs Control statements Paragraph properties: Page protection. Under Text Name. Specify the text object. This text type has the same function as the SAPscript command INCLUDE. such as the name. Specify the general properties of the include text. If you do not have to use SAPscript texts. The include text. The TEXT . description. but not for aligning fields within texts SAP characters. next paragraph on same page Character formats: Superscript and subscript. such as ULINE Standard icons Hyperlinks Tabulators. Choose F4 to see a selection of the texts in the system. In this way. but not SAP icons. which has been created with SAPscript Editor. 2. exists in the system.Entering Include Text Properties Use You want to display a SAPscript text in the form. 108. TEXT indicates a standard SAPscript text. Procedure 107. enter the name under which the include text is stored in the system. 1. You use transaction SE75 to define separate text objects with their own text IDs for applications. 109. you can manage application-specific form texts. we recommend that you use text modules. bar codes Special characters System icons.

text object with the text ID ST is used for general standard texts that you create with the standard text editor (transaction SO10). such as a company logo. The corresponding text is not inserted until the form is processed. Specify the text ID. If you do not set this flag. 5. Text ID. 113. you can insert graphics. The style assigned to the text node contains formatting for standard paragraphs (‘*’). all standard paragraphs in the include text are also formatted with this paragraph format. Set the flag No error if text not available if you still want the form to be printed. You use the graphic node to specify where the content of the image comes from at runtime. For more information about creating and editing SAPscript texts. For information about the supported image file formats. 4. you can set a paragraph format for the first paragraph of the include text. 114. Result You have created a text node with the text type Include Text. you bind graphic nodes to an object of the type Image Field. even if the inserted include text does not exist in the system. you either specify the URL address of an image or the name of a field in which the image content is specified in binary code at runtime. 111. . see the online help in Adobe LiveCycle Designer under Defining Object Properties ® Image Fields ® About Image Fields. If you leave the Standard Paragraph field empty. and an error message appears. If specified. 110. The usual ID of a standard SAPscript text is ST. 6. and Text Language already stored for this text in the SAP system. 112. 9. In Adobe LiveCycle Designer. To do this. 7. see the SAPscript Editor documentation. Enter constant values in quotation marks. 8. 115. the system copies the values for Text Object. Specify the style that you want to use for the include text. the form is not printed. Enter the text language in which you want the include text to be inserted. Under First Paragraph. to be used in the form output. If you specify a paragraph format in the Standard Paragraph field. you override the format of all standard paragraphs in the include text with this format. Inserting a Graphic Use Under the graphic node. This overrides the setting in the style.

117. • Result You have created a complete graphic node. choose Graphic Content. For more information. you can choose whether the system gets the graphic at runtime. The entries you need to make depend on whether you chose Graphic Reference or Graphic Content in the last step. such as ’image/bmp’. you must do the following: • ■ In Field. 3. Graphics stored in MIME Repository cannot be accessed through a URL. Select an existing node in the context. 116. The graphics must be in MIME Repository. Under Conditions. 2. You must be able to access the graphic at the specified URL. In the context menu of the node. enter the prerequisites that need to be met before the graphic node is processed at runtime and displayed in the form. The URL can point to a Web server or to a file system. 5. 4. enter a field name from the interface. Procedure 23. In Adobe LiveCycle Designer. Enter the required data about the graphic in the Properties window under the form context. see Migrating BDS Graphics into MIME Repository.. enter the URL of the graphic. You can insert this node in the layout in Form Builder. This field contains all image information at runtime. . To use these graphics. ○ If you have specified Graphic Content as your graphic type. For more information about graphics used in Smart Forms. You can choose from the following graphic types: • ○ Graphic Reference Choose this option if you want to insert a graphic from its address (URL). under which you want to create a graphic node. • ○ If you have chosen Graphic Reference as your graphic type. • ■ Enter a valid MIME type. 1. 120.. or whether the graphic is embedded in the form. see the online help in Adobe Designer. . ○ Graphic Content Choose this option if you want to specify graphic content using a field. The system creates a graphic node under the selected node. choose Create → Graphic. The field must have the type STRING (graphical data is Base64-coded) or XSTRING (for binarycoded graphical data).Prerequisites Any graphics that you want to display with the Graphic Content option must be stored in MIME Repository. • 119. This means that you may have to configure appropriate access rights for Adobe Document Services (ADS). 118.

otherwise. 1. it contains the name of the graphic that you want to load.com/images/logo. the following URL is entered for the graphic object: http://www. 1. under which you want to create an address node. choose Create → Address.Example You want to insert a graphic from the Website of the fictitious company AnyCompany in your form. which is why no URL appears in Adobe LiveCycle Designer. The addresses are stored in a database.com/images/logo. you must insert your addresses using text nodesor insert them directly in the layoutas text. 121. Prerequisites Your application must manage addresses in the BAS.gif’ Delimiter / GRAPHIC_NAME is a field from the interface that is entered as an import parameter.gif 2. where they are identified by numbers. The example shows you two ways of specifying the URL. At runtime. In the context menu of the node. Inserting an Address Use Many applications use the Business Address Services (BAS) to manage addresses.anycompany. 122. The graphic is unknown when the layout is created. Specifying a URL with Fixed Values Graphic URL ’http://www.com/images’ GRAPHIC_NAME ’. .gif’ Delimiter If you have inserted the graphic node in Adobe LiveCycle Designer. Procedure 24.anycompany. You have chosen Graphic Reference as your graphic type.anycompany. Select an existing node in the context. Specifying the URL by Using Fields Graphic URL ‘http://www. 2.

click the secondary mouse button. To display the context menu of the node. . choose Create → … to create nodes for the alternative options. Under Conditions. 126. The system creates an address node under the selected node. 4. This node has two successors. choose Create → Alternative. otherwise. 3. One difference here is that you need to specify the sending country under Additional Specifications. Enter the required data in the Properties window under the form context. the second successor node (FALSE) is processed. 124. In the context menu of the TRUE and FALSE nodes. 3. You want one of two nodes (and its subnodes) to be processed. you use the alternative node. The system creates an alternative node under the selected node. Result You have created an alternative node. 127. Select an existing node in the context. To do this. under which you want to create an alternative node. 128. with the two subnodes TRUE and FALSE. 1.To display the context menu of the node. In the context menu of the node. 4. 2. The information required for the address node is similar to that in Smart Forms. 123. The first successor node (TRUE) is processed only if the condition is met. See also: Inserting Addresses (from the Smart Forms documentation) Inserting an Alternative Use You want to present an alternative option in a form. Procedure 125. click the secondary mouse button. enter the prerequisites that need to be met before the address node is processed at runtime and displayed in the form. Enter the required data about the address in the Properties window under the form context. Under Alternative Conditions. You can use Drag&Drop to assign any existing node as a subnode. specify the conditions for a node to be processed. The window in which you define the alternative conditions is the same as the window used for defining the conditions for nodes. Double-click the subnodes to enter their properties as well.

choose Create → Folder. To do this. 1. You want to begin a reminder with a different text. 132. the more difficult it is to get a clear overview of the hierarchy of nodes. System Fields The interface of a form contains the field string SFPSY. The following general rules apply to system fields: • You can display the value of any system field in the form. to create subnodes. 130. In the Properties window under the form context. Select an existing node in the context. depending on which deadline has been missed. 4. 131. you can enter a name for the folder node. Here. it is a good idea to group these text nodes in a specific folder. You then use conditions to display just one of these nodes at runtime. The system creates a folder node under the selected node. In the context menu of the folder node. . enter the prerequisites that need to be met before the folder node is processed at runtime (together with its subnodes) and displayed in the form. For example. 129. The field content is either taken from the SAP system or is created while the form is being processed.. choose Create → . In the context menu of the node. 2. under which you want to create a folder node. To make the hierarchy easier to understand. Result You have created a folder node. you create a text node with a different reminder text for each level of reminder. Procedure 25. you can organize nodes under folder nodes. This string contains a range of system fields that the system replaces with values when a form is processed. 3. click the secondary mouse button. Under Conditions.Inserting a Folder Use The more detailed a form becomes. You can use Drag&Drop to assign any existing node as a subnode. you can use the system field SFPSY-DATE to display today’s date on your form. 5.. Migrated forms use the system fields from Smart Forms. 133. To display the context menu of the node.

icon. current time of the application server Logon name for user in the SAP system If single record nodes are used. If the field has a type from the ABAP Dictionary. It is displayed below the interface. current date of the application server Date and time.• • You cannot assign a value to a system field. for example. contains content of the SY-SUBRC field in the ABAP statement READ TABLE Field List Use The field list shows you detailed information about the individual fields (such as structure and tables) of the form interface. choose the screen above the interface. System Fields Field Name SFPSY-DATE SFPSY-TIME SFPSY-USERNAME SFPSY-SUBRC Meaning Date and time. in another session. Activities To reload the interface. In general. with the text Reload Interface. See Screen Display in the Context of the Form Builder Activities Double-click a field in the interface to display information on the properties and type of this field in the lower screen area of the interface. Reloading an Interface Use You have already started to edit the form context and you have made changes to the interface. you can query system fields (for example. You can use this function to update the display of the form interface in the context without having to exit the Form Builder for the context. in conditions) for any fields. you can double-click the type name to go to its entry in the ABAP Dictionary. on the left of the .

In the application toolbar. The layout type you define must match the script code in the layout. and define the order of the pages. You can also specify background pictures for the form. Features Under Layout in the Form Builder. This is the case if you are creating a new form or editing a form created with an older version of SAP NetWeaver.Layout in the Form Builder Use When you create a layout in the Form Builder. an integrated graphical software tool for creating forms. you define the graphical design of the PDF form. you use the form context you have created previously or an XML schema displayed as a tree structure under Data View in Adobe LiveCycle Designer. you choose Layout (quick info Fullscreen Layout). . Adobe LiveCycle Designer starts in fullscreen mode. You can use Drag&Drop to insert data fields from the Data View section in the page layout. Layout Type You use the layout type to define the runtime environment where the form is used. you can use a wide range of functions to design your form. Adobe LiveCycle Designer starts on this tab. Activities There are two ways of editing the layout: • • You choose the Layout tab page. choose the Properties tab page in Form Builder: Change Form. Prerequisites You have created a form context or loaded an XML schema-based interface. you first have to close the tool. Integration The Layout function in the Form Builder calls Adobe LiveCycle Designer. This includes the positioning of the data and the design of tables. To do this. For more information about editing layouts. To access the menu bar and application toolbar. Layout Types Layout Type Unknown layout type Meaning The form has not yet been classified. see the online help in Adobe LiveCycle Designer. You still have to classify the form. To select a layout type. Otherwise runtime errors can occur.

see the Designer’s online help under Working with Objects → Using Custom Objects → Custom Objects for the SAP Environment. or for interactive forms used in an offline scenario and not integrated in a Web Dynpro environment at runtime. You specify this setting when you create new forms. These objects contain special functions and can be found in the Designer’s library. Date Objects in Adobe LiveCycle Designer Definition Under Library ® Form Builder. see Creating Forms for Integration with Web Dynpro and ZCI and Check and Update Functions for Zero Client Installation (ZCI). ActiveX must be enabled in the browser. Note that you can make this setting only if the layout type of your form was previously Unknown. For more information. You can still. Objects in Adobe LiveCycle Designer Definition Adobe LiveCycle Designer provides you with objects that you can use to create your form. however. If your form is already set to Standard or ZCI. access your old form using version management. you cannot choose xACF. The system enters this value automatically when you migrate old forms to ZCI. xACF layout ZCI layout Zero Client Installation (ZCI) technology is used to integrate the form at runtime in Web Dynpro applications. For more detailed information.Standard layout Use this layout type for PDF-based print forms. Adobe LiveCycle Designer provides you with the following date objects: • • Localized Full Date Localized Long Date . The Active Components Framework technology is used to integrate the form at runtime in Web Dynpro applications. Also included are some objects developed specially for the SAP development environment.

17.05. May 17.] * US format FP_DOCPARAMS-LANGU = 'EN'. FormCalc Language Reference Your local Adobe Designer installation includes a FormCalc language reference in a PDF file that you can print out. Mai 2004 17. These values are sent to the generated function module that contains the form description. * German format * FP_DOCPARAMS-LANGU = 'D'. * Call the generated function module CALL FUNCTION FM_NAME EXPORTING /1BCDWB/DOCPARAMS = FP_DOCPARAMS Date Display as Specified by Date Objects Date Object Standard Date/Time Field Localized Default Date Localized Full Date Localized Long Date Localized Medium Date Localized Short Date US Date May 17.05.2004 17. DATA FP_DOCPARAMS TYPE SFPDOCPARAMS. 2004 May 17. 2004 Monday. * FP_DOCPARAMS-COUNTRY = 'DE'.04 For more information. Example You want to display the date objects on the form in US format or in German format. .05..2004 17. FP_DOCPARAMS-COUNTRY = 'US'. Mai 2004 17. The dates are formatted according to the parameter values entered for language and country in the application program. 2004 May 17.• • Localized Medium Date Localized Short Date Use You use these date objects to format dates locally when you call the form.05.. [. see Example: Calling Forms in the Application Program. 2004 May 17.2004 Montag. 2004 5/17/04 German Date 17.

pdf You enter EN for <country> if you have an English installation. Check the form The system runs a syntax check in the context. Features The system enables you to check your form in the following ways: ● Check the interface ● ● ● ● ● The system runs a syntax check on the interface. You can run checks on the form and test it in the print preview. Form preview with and without inserted data The form is displayed in PDF format in Adobe Reader or Adobe Acrobat. Check the layout The system checks whether all fields from the context have been inserted in the layout. DE if you have a German installation. These checks also run each time you start to edit the layout. and that its layout meets your requirements. . Links to the interface can be lost when the interface is modified. The system also runs automatic checks when you activate the form. Checking and Testing a PDF-Based Print Form Use To guarantee that your form is free from errors. You can send test data to this function module. and whether all the fields in the context have a link to the interface. for example. the FormCalc language reference is in the following location: C:\Program Files\Adobe\Designer 7. These checks test the data links between the context and the layout.If you have installed Adobe Designer on your C: drive. For example. you must have installed Adobe Reader or Adobe Acrobat (both with Version 7. The system also checks whether the assigned interface is active. which then inserts this data in a print preview of the form. and also whether all fields in the layout have a data link to the context.1\Documentation\<country>\FormCalc. Test the form The system generates a function module that contains the form description. you can use a range of check options. it checks to see whether all necessary field properties have been entered. You can run additional checks in the layout of the Form Builder. Prerequisites To check the layout and display the preview.0 or later) on your front end. Activation checks The system checks the form each time it is activated.

. 137. . Choose Layout in the application toolbar.Activities Checking an Interface 26. You cannot navigate to the fields from this list.. 134. 140. 135. 2. You are in the interface of the Form Builder. Choose Test (F8) in the application toolbar. 3. These messages are just warnings. 5. 146. . 2. 30. see the online help in Adobe LiveCycle Designer. 3. Checking a Layout 29. For more information. 3. 144. activate the function Saving Runtime Information and a Generated PDF Locally and repeat the test.. The screen Test Function Module: Initial Screen appears. you can still activate the layout later. You are in the layout in the Form Builder. 1. Enter your data and choose Print Preview.. or if errors occur. However. 147. Choose Check (Ctrl+F2) in the application toolbar. 1. 4. If the form does not appear how you want it to. 148. 4. Double-click a message to locate the error in the interface.. The system checks the layout and displays any errors in a list. You are in the context in the Form Builder or in the layout in the Form Builder. this function does not insert any data. 28.. 143. .. 139. You are in the context in the Form Builder or in the layout in the Form Builder. Double-click a message to locate the error in the context. 141. The system checks the interface and displays any errors or warnings in a list. 1. 145. The system starts Adobe Acrobat or Adobe Reader and displays the PDF form with your data inserted. 136. Choose Check (Ctrl+F2) in the application toolbar.. 138. 1. 2... 2. . . 142. Print Preview with Inserted Data or Form 31. 149. 6. The system checks the interface and displays any errors or warnings in a list. Checking a Form 27. . Enter the test data for the import parameters and choose Execute. The printer settings dialog box appears. Preview Without Data You use the preview function in Adobe LiveCycle Designer to display the form in PDF format while you are creating the layout.. 3.

Calling Forms in an Application Program
Purpose
To print or archive a form, you use function modules to call it in an application program. An initial function module determines the name of the generated function module that describes the PDF-based form. Two further function modules control the output of the form, and specify whether it is printed or archived. The form is then called in the application program after the necessary data has been selected. If you want to send your form as a fax or e-mail, you must forward the PDF to the Business Communication Services after the form has been called. You use the function module FP_JOB_OPEN to control how the form is sent back to the application program as a PDF. You get the PDF itself from the generated function module. The following process describes how a PDF-based form with a non-Smart Formscompatible interface is called.
If you migrated the PDF-based form from a Smart Form, or if the interface is Smart Forms-compatible, the form is called in the application program in the same way as a Smart Form. For more information, see the following Smart Forms documentation: Integrating the Smart Form into the Application Migrating Smart Forms (under Switching Runtime)

Prerequisites
You have created and activated a PDF-based form. You have experience of programming with ABAP and handling function modules.

Process Flow
150. 1. In the application program, you define a variable of the type RS38L_FNAM for the name of the generated function module: 151. 2. You call the function module FP_JOB_OPEN. You use this function module to specify settings for the form output. You specify whether you want the form to be printed, archived, or sent back to the application program as a PDF. The form output is controlled using the parameters (IE_OUTPUTPARAMS) with the type SFPOUTPUTPARAMS.
For the individual fields of the structure SFPOUTPUTPARAMS and their meaning, see the ABAP Dictionary (transaction SE11).

152. 3. You determine the name of the generated function module by calling FP_FUNCTION_MODULE_NAME.
The name of the generated function module is unique only in one system. This is why you must first call the function module that gets the current name of the generated function module from the name of the form.

153. 4. You call the generated function module and send the parameters to the form interface.
The structure SFPDOCPARAMS exists as an additional import parameter for the generated function module (for example, for setting the language); the structure FPFORMOUTPUT exists as an export parameter. For more information, see Parameters of the Generated Function Module.

154. 5. You call the function module FP_JOB_CLOSE to complete the processing of the form.

Result
The system creates the form with the integrated application data in PDL (Printer Definition Language) form and forwards it to the spool processing tools. A PDF is created only if the appropriate parameters are sent to FP_JOB_OPEN when archiving, returning a PDF, or using print preview. As long as you do not modify the form interface, you can continue to edit the form without modifying the application program. However, if you modify the form interface, you must also modify the interface in the application program accordingly. See also: Example: Calling Forms in an Application Program

Parameters of the Generated Function Module
You can use the parameters of the generated function module to define the way the form is displayed and its properties when it is called by the application program. The following lists these parameters: From the perspective of the function module interface: ● The parameters of the structure SFPDOCPARAMS are import parameters (/1BCDWB/DOCPARAMS). ● The parameters of the structure FPFORMOUTPUT are export parameters (/1BCDWB/FORMOUTPUT). Parameters of the Structure SFPDOCPARAMS Parameter Name LANGU REPLANGU1 REPLANGU2 REPLANGU3 COUNTRY Type LANGU LANGU LANGU LANGU LAND1 Meaning Language in which the form is displayed If the form does not exist in the language specified in LANGU, the system evaluates these fields in the given sequence instead. Country key for date and

number formatting No setting is required if the SET COUNTRY command is used in the application program before the generated function module is called, and the same country is specified there. FILLABLE FPINTERACTIVE
FILLABLE = X generates an

interactive form. This form can be displayed and edited in Adobe Acrobat or Adobe Reader. Usage rights are allocated to the form; these rights enable data to be entered and saved in Adobe Reader. FILLABLE = N generates an interactive form without usage rights. DYNAMIC FPDYNAMIC
DYNAMIC = X generates an

interactive, dynamic form to be displayed and edited in Adobe Acrobat or Adobe Reader versions higher than 7.0. This parameter is valid only if the FILLABLE parameter is also set. DARATAB TFPDARA If you want to archive the generated form, you must make at least one entry in this table (with archiving indexes).

Parameters of the Structure FPFORMOUTPUT Parameter Name PDF Type FPCONTENT Meaning Contains the generated PDF. A PDF is generated only on demand by the GETPDF parameter of the function module FP_JOB_OPEN in the application program, or by the print preview function. PDL PAGES FPCONTENT FPPAGECOUNT Contains the generated PDL. Contains the number of

2. where they must already be defined. SFPOUTPUTPARAMS. and CONNECTIONS are sent to the form interface. . Generated function module of the form 158. SFPDOCPARAMS. TYPE TYPE TYPE TYPE TYPE TYPE SCUSTOM. BOOKINGS. RS38L_FNAM. 4. 3. 155. For more information. Example: Calling Forms in an Application Program The following is a program excerpt showing how the function modules are called. FP_FUNCTION_MODULE_NAME gets the form name. TY_CONNECTIONS.. 157.generated pages in the form. LANGU LANGU Language key The parameters that control the output options are in the structure SFPOUTPUTPARAMS and are specified as import parameters when the function module FP_JOB_OPEN is called. TY_BOOKINGS. FP_JOB_CLOSE closes the spool job. FP_JOB_OPEN opens the spool job. DATA: CUSTOMER BOOKINGS CONNECTIONS FM_NAME FP_DOCPARAMS FP_OUTPUTPARAMS * GETTING THE DATA <data selection> * PRINT: * Sets the output parameters and opens the spool job CALL FUNCTION 'FP_JOB_OPEN' CHANGING IE_OUTPUTPARAMS = FP_OUTPUTPARAMS EXCEPTIONS CANCEL = 1 USAGE_ERROR = 2 SYSTEM_ERROR = 3 INTERNAL_ERROR = 4 OTHERS = 5. the parameters CUSTOMER. In this example.. 156. 1. 32. see Form Output. .

* Close the spool job CALL FUNCTION 'FP_JOB_CLOSE' * IMPORTING * E_RESULT = EXCEPTIONS USAGE_ERROR = 1 SYSTEM_ERROR = 2 INTERNAL_ERROR = 3 OTHERS = 4. * Language and country setting (here US as an example) fp_docparams-langu = 'E'. <error handling> ENDIF. <error handling> ENDIF. IF SY-SUBRC <> 0. IF SY-SUBRC <> 0. * Call the generated function module CALL FUNCTION FM_NAME EXPORTING /1BCDWB/DOCPARAMS CUSTOMER BOOKINGS CONNECTIONS * IMPORTING * /1BCDWB/FORMOUTPUT EXCEPTIONS USAGE_ERROR SYSTEM_ERROR INTERNAL_ERROR IF SY-SUBRC <> 0. = = = = = = 1 = 2 FP_DOCPARAMS CUSTOMER BOOKINGS CONNECTIONS = 3. . <error handling> ENDIF.IF SY-SUBRC <> 0. fp_docparams-country = 'US'. * Get the name of the generated function module CALL FUNCTION 'FP_FUNCTION_MODULE_NAME' EXPORTING I_NAME = ‘<form name>’ IMPORTING E_FUNCNAME = FM_NAME. <error handling> ENDIF.

This enables you to optimize the way the data is collected in the application program. but not all fields of the interface need to be used in every form. you can define a form interface to send this data to a form. Customers who want to change the way the data is collected. and created and activated the form context. and do not want to modify the application program. which you then bundle and send to the form. Result The data is saved to internal tables in the application program. Now that you know all the types of tables that are used. you must separate the selection of the data from the processing of the form. Getting the Used Interface Fields Use You can use the same interface for multiple forms. Prerequisites You have created a PDF-based form with an interface. and then use this data in the form under Global Data. . The performance of the application program improves because it only needs to provide the parameters required by the relevant form. You save the data in internal tables. These routines usually consist of statements that select data from the database. The following questions need to be answered about the collection of the data: • • What application data do you want to appear on the form? Which database tables need to be accessed to get this data? Process Flow You write an ABAP program that collects the data or you include an appropriate routine in your application. structures. or variables.Collecting the Application Data Background To ensure a good level of performance when you print forms. You use the function module FP_FIELD_LIST to get all fields of the interface that are used in the form. can extract data when the interface is initialized.

• • You specify the name of the form as an import parameter. This includes fields referenced by the data node and fields that are used in conditions. You get a table of the used fields (with the type TFPFIELDS) that can then be used for data collection in the application program. if any are defined. the system saves this information for all forms that are generated while the user is logged on. You can also see field names under Where Conditions for table nodes. Features The function module FP_FIELD_LIST provides you with the following information: • All fields from the interface that are used in active nodes in the form context. You can save files that contain the following information to your local client: ● Runtime information (also known as trace information). Prerequisites You have debugging authorization in the system where you want to use this function. created by the system when forms are generated ● PDF with additional information Once a setting is chosen. Integration You can also get the runtime information directly in the application program that calls the form. using a function module. alternatives. You can also see the used field names in the form context by displaying the properties and conditions for each node. see Troubleshooting. address nodes. .Integration The function module is included in the application program that collects the data and calls the form. • All fields from the interface that are used in the ABAP code (initialization) of the interface. For more information. text nodes. and graphic nodes. Activities You include the function module in the application program that collects the data and calls the form. See also: Collecting the Application Data Saving Runtime Information and a Generated PDF Locally Use Form developers and support desk staff can use this function to analyze the causes of any errors that occur when forms are generated.

When you choose F4 for the file name. However. For a detailed description of the information provided by the system.. select the option Very Detailed Trace.trc on the J2EE Engine. choose an option under Trace Level and enter the name of the file. You can use the troubleshooting options to find out the cause of the error. ● Saving runtime information and a PDF with additional information for multiple forms If multiple forms are called in the application program. This information is a subset of the trace information stored by the J2EE Engine used as a host system for Adobe document services. Troubleshooting for Runtime Errors FPRUNX001. in the event of errors. for example. in addition to the existing numbering. The detailed trace information is located in the file defaultTrace. 002. you can navigate to your system to choose a file. ● Saving the PDF with additional information The PDF with additional information consists of the generated PDF form or. ● To activate the function PDF with Additional Information.Features ● Saving runtime information The system saves the trace information returned by Adobe document services to your local client. the system saves the runtime information automatically with the extension TXT. application data (in XML format). and 004 Use You want to display a PDF-based print form. . An extra sequential number is added to each file. FPRUNX002. A dialog box appears.. proceed as follows: • • ○ Under Runtime Information → Trace Level. If you do not specify an extension for the file name. Features You are provided with various function modules for troubleshooting purposes. the system displays the runtime error FPRUNX001. Activities 33. see the section Execution in the problem analysis scenario Adobe Rendering Error (in English only). the information is saved to separate files. You can use these function modules to extract the following information: . or FPRUNX004 when the generated function module is called. an error file. Choose Utilities → Settings. ● To specify how the runtime information is saved locally. Attached to either of these files are various additional files including. and the runtime information mentioned above. ○ Select PDF with Additional Information and specify a file name. sent to the form at runtime.

This interface allows you to link the form with application data. You can choose one of the following options: 35. .. set the ADSTRLEVEL field in the IE_OUT_OUTPARAMS parameter (type SFPOUTPUTPARAMS) of the FP_JOB_OPEN function module to values between 01 and 10. FP_GET_LAST_ADS_ERRSTR gives you a text that indicates the cause of the error. Call the function module FP_GET_LAST_ADS_TRACE after the generated function module.. To activate the trace output. 2.. Call the function module FP_GET_LAST_ADS_ERRSTR after the generated function module. FP_GET_LAST_ADS_TRACE gives you the trace.sap. Read the SAP Note 717568 on the SAP Service Marketplace at service. 2. the form is forwarded to ArchiveLink.. . 2. ● ● Printer Archiving In this case. for example. . 1. 3.• • Texts about the cause of the error (with the FP_GET_LAST_ADS_ERRSTR function module) A trace of the Adobe document services (with the FP_GET_LAST_ADS_TRACE function module) Activities To perform the troubleshooting actions. This note gives you precise and up-to-date information about how to proceed when troubleshooting. call the function modules in your application program.com/notes. ArchiveLink is a communication interface that manages archiving systems in the SAP system. Form Output Purpose You can send a PDF-based form to various types of output media. Trace 34. Troubleshooting Texts 1.

Output to Archive SAP Printing Guide 159. you must configure a PCL-compatible printer. from where it can be sent as a fax or email. see the ABAP Dictionary (transaction SE11). Process Flow To control the output of the form. see the ArchiveLink documentation under Storing Outgoing Documents. the application program can forward it to Business Communication Services. 1. these fields are sent to the function module FP_JOB_OPEN as parameters (IE_OUTPUTPARAMS). The system forwards the form to ArchiveLink. • • ○ ○ Archive only: SFPOUTPUTPARAMS-ARCMODE = ’2’ Print and archive: SFPOUTPUTPARAMS-ARCMODE = ’3’ You use the NODIALOG field to display the output of the dialog. this is what happens when you use the initial values of the structure when you call FP_JOB_OPEN. For the individual fields of the structure SFPOUTPUTPARAMS and their meaning. 2. you specify an archiving mode for the document: • ○ Archive only • ○ Print and archive If you create the form output without a dialog. If you create the form output with a dialog. see Example: Calling Forms in the Application Program. Here. if you want to print your PDF form. see Spool Processing and Controlling the Spool Dialog. For more information.For more information. To see how function modules are called. specify the archiving mode in the ARCMODE field of the structure mentioned above. For more information. You write at least one entry to the table with archive indexes (SFPDOCPARAMS-DARATAB). You can modify the print parameters and the spool dialog parameters by setting the fields accordingly. see Controlling the Spool Dialog. . 3. see (BC-CCM-PRN). you use various fields in a structure with the type SFPOUTPUTPARAMS. Output to Printer Forms are sent to a printer by default. The SAP system must be configured to be compatible with each output medium. When the form is called in the application program. Prerequisites The form is sent to the output media through interfaces. For example. ● Fax and e-mail If you send the form back to the application program as a PDF. For general information about printing and printer setups. you see the spool dialog..

Activities To define replacement fonts. all texts are translated from the interface. The system sends the generated PDF form back to the application program. In your application program.. 37. . and the layout. For more information. . In this case. The fonts you want to use must be installed for Adobe document services. 1. Font Replacement Use PDF-based forms are created in an original language. The settings are cross-client settings. you require administrator authorization.. When you process forms in another language (referred to here as the target language). the context. Under Language. You make the required settings in the table FPFONTREPL. enter the target language in which the form and the replacement font or fonts are displayed. To do this. This function also gives you the option of setting a default font or fonts to be used as a replacement in forms. enter the name of the form. Integration You can specify replacement fonts for forms that have been created and translated in ABAP systems. However. enter the form name. the system replaces these characters automatically with suitable replacement fonts. 2. set the field SFPOUTPUTPARAMS-GETPDF. Prerequisites • • To edit the table FPFONTREPL. you enter a wildcard character * in the table under Name of Form Object. the fonts used in the layout are retained.Output as Fax or E-Mail 36.. 160.. if a font does not support all characters in the target language. . edit the table FPFONTREPL in the Data Browser (transaction SE16). 1. •  You can define replacement fonts for all forms in the system. 2. where it can then be forwarded to the interface of the Business Communication Services. Under Name of Form Object. When you use the appropriate tools to translate forms. see Adobe Document Services − Configuration. You can do this in the following ways: •  You can define replacement fonts for specific forms.

enter the font that you want to replace the source font with. Under Source Font. you make the following settings in FPFONTREPL: Font Replacement in Table FPFONTREPL for Form Processing Name of a Form Object FP_name Language J Source Font Times New Roman Target Font MS Mincho Spool Processing Use As a default setting.Remember that the form is only displayed in the target language if this is specified for form calls in the field LANGU of the import parameter /1BCDWB/DOCPARAMS of the generated function module. for example: • • Opening a new spool job Specifying the retention period of a job in the spool Integration The functions related to these settings are no longer part of the process of creating PDFbased forms. you want to use the character set MS MINCHO instead of Times New Roman. 3. see the ABAP Dictionary (transaction SE11). the system forwards the generated PDF forms to the spool processing functions and sends parameters to the spool dialog. 4. For the individual fields of the structure SFPOUTPUTPARAMS and their meaning. Features You can use parameters in the structure SFPOUTPUTPARAMS to make print and spool dialog settings. you send these parameters (IE_OUTPUTPARAMS) to the function module FP_JOB_OPEN. When you call the form. You can use this spool dialog to control the output. by doing the following. See also: . specify the font in the original form. To do this. Example For the Japanese version of the form FP_name. Under Target Font.

If a form is migrated from a Smart Form. the spool dialog is controlled by different parameters. or if it is compatible with Smart Forms. Features The following Changing parameters (set with the function module FP_JOB_OPEN) are relevant for controlling the spool dialog: Fields from the Structure SFPOUTPUTPARAMS for Controlling the Spool Dialog Field NODIALOG TITLE NOPREVIEW NOPRINT NOARCHIVE IMMEXIT NOPRIBUTT Component Type Data Type (Length FPNODIALOG CHAR(1) FPTITLE CHAR(50) FPNOPREVIEW CHAR(1) FPNOPRINT CHAR(1) FPNOARCHIVE CHAR(1) FPIMMEXIT CHAR(1) FPNOPRIBUTT CHAR(1) Meaning (when set) Suppress user dialog Title of the dialog box Suppress print preview No print from print preview No archiving from print preview Exit preview immediately after printing No pushbuttons . See also: Controlling the Spool Dialog in the Smart Forms documentation Prerequisites The DEVICE parameter of the structure SFPOUTPUTPARAMS must have the value ’PRINTER’. you want to adjust the spool dialog to your requirements when printing a PDF-based form.Controlling the Spool Dialog Printing PDF-Based Forms in the SAP Printing Guide Displaying and Printing PDF-Based Forms in the SAP Printing Guide Controlling the Spool Dialog Use In the application program. or hide the spool dialog completely.

See also: Example: Calling Forms in an Application Program Printing Multiple Forms in a Print Request Use You want to print multiple forms in a single print request. Procedure 38. to suppress the user dialog). The XDC scenarios provide you with examples of how you can make specific settings for your printer.Activities In the application program. 4. . See also: Calling Forms in an Application Program XDC Scenarios for Print Control Use An XDC file is a printer description in XML format. call the function module FP_JOB_OPEN and specify the required parameters. HP9500. When you call the form in the application program. Result You have placed the selected forms in a print request. specify the value ’X’ (for example. XDC files are shipped for the following SAP device types: POST2 (generic device type that can be used for every PostScript printer). first call the function module FP_JOB_OPEN. AZPL203. To set a parameter with the data type CHAR(1). 3. Determine the names of the generated function modules with FP_FUNCTION_MODULE_NAME. The function module FP_JOB_CLOSE is the last function module to be called. 1. Adobe Document Services require this file to create the print files. Then call the generated function module(s) that you want to use in the output. 2. and AZPL300. You do not usually need to make any modifications to these XDC files to use them for successful printing. PDF documents can only be printed on printers of SAP device types for which there is an XDC file in the system. HPLJ4. . NODIALOG = ’X’..

see the Software Partner pages at http://www.Integration You can edit XDC files in a text editor and manage them in the SAP system. at least one printer of device type XFP must be set up in the system. so enabling you to make the following settings: • • • Printer Paper tray (not defined by default) Paper format (such as A3) Activities For documentation about the XDC scenarios. In spool administration. See also: SAP Printing Guide (BC-CCM-PRN). Functions The documentation about the XDC scenarios describes the entries in the XDC file. but does not contain any layout information about the form.com/spp.sap. Output in XFP Format Use Using the XML interface for PDF-based forms (XFP). You can override this default by setting the output parameter IE_OUTPUTPRAMS of the function module FP_JOB_OPEN accordingly (the ABAP Dictionary reference is SFPOUTPUTPARAMS-XFPOUTDEV).com/notes. The XFP output contains all form data in XML format. Prerequisites Since XFP uses spool processing. Integration XFP output corresponds to XSF output for Smart Forms and RDI output for SAPscript. we recommend that you set up an XFP output device. see SAP Service Marketplace at Adobe → Media Library → Documentation. see SAP Note 766410 on SAP Service Marketplace at service. Software partners can receive a certificate from SAP for products that access the XFP interface. this output device is used as a virtual device for connecting to the external application. For up-to-date information about downloading this documentation. external applications outside the SAP system can access and process the contents of forms. . For more information. By default.sap.

Unless specified otherwise. Place the context nodes used at the top of the form at the initial position in the context tree. together with all its conditions. ● Minimize the amount of communication that takes place with the server in interactive forms. ● If possible. Only use those interactive functions (such as dynamic value help that sends queries to the server) that are strictly necessary. under Creating Forms for Optimal Performance. ● Bundle print forms. These character sets do not need to be embedded in the form. Arial. For more information. but the form context has not been evaluated. ● Keep scripting to a minimum. Do not implement the condition-driven output of multiple forms from the same form object. use the function module FP_FIELD_LIST. Times New Roman. design an individual form that uses its own data retrieval methods. ● For a detailed description of how to improve performance. use the Form Caching function in the Designer. design the data retrieval process in the application program and interface in accordance with your individual requirements. To support you in your work. these recommendations apply both to interactive forms in Web Dynpro and to PDF-based print forms. use only the following character sets. who can use it to achieve an optimal level of runtime performance when using Interactive Forms based on Adobe software. Recommendations for Form Builder ● For each business scenario. The XML data can be displayed in two different ways: • XML data stream with context evaluation The data stream describes the structure of the PDF-based form at runtime with the data integrated from the application program. ● Deactivate any context nodes that you do not need. Performance Aspects The following information is targeted mainly at developers. since scripting in a form can have an effect on performance. see the online help for the Designer. This means the form context is already evaluated. even if the Designer supports others: Courier. Recommendations for Calling Forms and Form Output ● When you create forms for mass printing. • XML data stream without context evaluation The data stream contains the data from the application program.Features The XFP output is activated at runtime by the calling application program. see the online help of the Designer. ● Structure the form context in accordance with the logical flow of data. which improves performance. . which determines all fields used in the interface. Recommendations for Adobe LiveCycle Designer ● For interactive forms.

When you call the form. see the description under Problem Analysis Scenarios for Adobe Document Services for detailed troubleshooting information. No Form Output If you encounter any connection errors or configuration errors when you use Adobe document services. Communication Errors. For more information. Runtime Errors. . Utilities in the Application Program that Calls the Form The following function modules provide you with support when you work with PDFbased print forms: ● Getting the Used Interface Fields ● Troubleshooting for Runtime Errors FPRUNX001. and print forms.● Cache forms that you want to process with Adobe document services. display. see Adobe Performance Analysis (in English only). and 004 You use this function module to find out the causes of any errors you encounter when displaying forms. it gives you detailed information about the form data and runtime information specified by Adobe document services. Features Utilities in the Form Builder The Form Builder that you use to create PDF-based print forms and interactive forms in Web Dynpro for ABAP offers you a wide range of functions: ● Checking and Testing a PDF-Based Print Form ● Saving Runtime Information and a Generated PDF Locally You activate this function in the Form Builder. 002. Handling Errors and Problems Use Interactive Forms based on Adobe software provide you with comprehensive support for detecting and resolving errors and problems when you create. Performance Analysis You can obtain precise details about the performance of Adobe document services.

Translating Texts PDF-based forms are integrated in the same translation process as other development objects. The Transport Organizer distributes the interfaces and forms to other systems. this means that the SFPF and SFPI transport objects are recognized by the translation tools (transaction SE63) and are included in the relevant worklists. Standard Forms Different applications in the SAP system use different standard PDF forms.Delivery and Translation Transport Object The interface and form (context and layout) of a PDF-based form are separate development objects. If you want to adapt these forms to your own requirements. . Original Language When you create a PDF-based form. You assign a package to an interface or form when you create it. and then link it to the application. make your changes to this copy only. see the documentation on transaction SE63 under Translating PDF-Based Forms . Cross-Client Objects The interfaces and forms for PDF-based forms are cross-client objects. see Layout in the Form Builder. If you want to translate older forms in this way. The corresponding transport objects are as follows: ● SFPF for the form (R3TR SFPF <name>) ● SFPI for the interface (R3TR SFPI <name>) The system uses the Transport Organizer in the usual way to create the TADIR entries or transport objects and their attributes. For the procedure for editing a form in Adobe LiveCycle Designer. you must first display the layout in edit mode. the system specifies the logon language as the original language. The translation-relevant texts in a PDF-based form are as follows: ● Descriptions of the nodes These are translated in the same way as other system short texts. Local objects are not included in this process. copy the standard form.) In this way. (The system does not log any modifications to the standard form. For more information about translation. your customer-specific changes are not lost when an updated version of the standard form is imported in an upgrade. You create the form and all its language-specific parts (such as texts and meanings) in the original language. ● Texts in the layout of the PDF-based form that you created in the Form Builder with Adobe LiveCycle Designer From SAP NetWeaver ´04 SPS 11. texts are translated in a splitscreen editor that displays the texts in plain text format. and then save it again. An entry is created in the TADIR (object directory) table for each interface and each form.

See also: Creating Text Modules Business Address Services Creating Text Modules Use You can insert text modules in a PDF form as text nodes. This information does not always apply to PDF-based forms. you will also need to make use of functions and components that are not included in the development environment for PDF-based forms. For more information on inserting a text module. see the following: Maintenance of Styles with the Style Builder Smart Styles Header Data of a Smart Style Paragraph Formats Character Formats Note that the documentation linked to here relates to creating forms in Smart Forms. Business Address Services Use You can insert an address node in a PDF-based form. For more information about address management. You use the addresses managed in the Business Address Services (BAS). Business Address . see the Smart Forms documentation under: Maintenance of Text Modules You can assign a format (also known as a style) to a text module. For more information. The following gives you an overview of these tools and links to additional information. see the documentation Services (BC-SRV-ADR). see the following: Inserting a Text You create and edit text modules in Smart Forms (transaction SMARTFORMS). For more information.Tools Associated with Form Development Use When you develop forms.

enter a form or interface. depending on your application scenario: ● ● ● ● Web Dynpro for ABAP in SAP NetWeaver AS ABAP Web Dynpro for Java in SAP NetWeaver AS Java Guided Procedures Forms in SAP Business Workflow for various mySAP ERP business packages (in particular. See also: Migrating Smart Forms in the Smart Forms documentation Interactive Forms There are several ways of creating an interactive form.Version Management Use The PDF-based forms solution is integrated with version management tools. • ○ For general information about using forms. Integration This function is integrated into the Smart Forms transaction. see the mySAP ERP documentation under HCM Processes and Forms and Internal Service Request (ISR). ● To save a version of the form or interface in the version management database. You can save different versions of both forms and interfaces. Management. and you call it there. You use one of the following development environments. choose Utilities → Versions → Generate Version. Activities Under Form Builder: Entry Point. . ● To access the version management functions. choose Utilities → Versions → Version See also: Documentation about Version Management Migration of Smart Forms Use You want to migrate a Smart Form to a PDF-based form. Manager Self-Services) are developed in ABAP Workbench (transaction SFP) and implemented in the Web Dynpro for Java runtime environment.

See also: • • • Concepts of Developer Studio Detailed information about SAP NetWeaver Developer Studio Development of Interactive Adobe Forms for the Web Dynpro UI Explanation of the concepts behind creating forms Example of the Use of an Interactive PDF Form This documentation gives you a short introduction to creating an interface PDF form. You can. Reader Rights are configured as part of the installation and configuration process of Adobe Document Services. and use certain parameters to control which input is allowed. A user in Adobe Reader cannot enter and save data in an interactive form until these rights are granted. In certain circumstances. Transaction SFP.• ● ○ For information about creating forms in Form Builder. and data bindings. interactive forms require licenses. see Creating Forms for Integration with Web Dynpro and ZCI. Note that you need to program some steps manually when you use ABAP Workbench. For more information. the context structure. See also: • • • Web Dynpro for ABAP General information about the solution Adobe Integration Information about creating a PDF form in Web Dynpro for ABAP InteractiveForm Interface element for creating forms in View Designer Interactive Forms in Web Dynpro for Java You develop interactive forms as part of a Web Dynpro application in SAP NetWeaver Developer Studio. ABAP Workbench. these steps run automatically in the environments listed above. All of these options require Reader Rights to be granted before you can use interactive forms in Adobe Reader. however. This development environment is intended mainly for creating print forms. generate a PDF when you call a form. Interactive Forms in Web Dynpro for ABAP You develop interactive forms as part of a Web Dynpro application in ABAP Workbench. • Web Dynpro InteractiveForm API − IWDInteractiveForm . see Reader Rights Credential in the Adobe Document Services Configuration Guide. see SAP Note 750784. including information about constructing the view. For more information.

. You use SAPGUI Release 6.. 5. the forms must contain special scripting. 161. You can see the scripting in the node (Variables)->ContainerFoundation_JS under Hierarchy in Adobe LiveCycle Designer. Procedure 39. If you want to use Web Dynpro-specific objects in the design of your form layout. You can use transaction SFP_ZCI_UPDATE to make any interactive forms you created with an older version of SAP NetWeaver ZCI-compliant. The system inserts scripting into the form layout in Adobe LiveCycle Designer. 3.. Switch to the Layout tab page. 165. 40. Select ZCI Layout in the Layout Type field under Properties. which you insert when you create new forms in Form Builder. Choose Utilities → Insert Web Dynpro Script.40 Support Package Level 20 or higher (see SAP Note 940637). 164.1 (see SAP Note 962763). . such as forms for Business Package Manager Self-Service. Prerequisites ● ● ● You use SAP NetWeaver 2004s SPS 8 or higher. For more information.. . use the Adobe Designer library Web Dynpro Native. see Check and Update Functions for Zero Client Installation (ZCI). on the Web Dynpro tab page Creating Forms for Integration with Web Dynpro and ZCI Use This procedure is only relevant for forms created with Form Builder at design time and that run in a Web Dynpro application at runtime. You use Adobe LiveCycle Designer 7. They can be used (from SAP NetWeaver SPS 8) at runtime in Web Dynpro for Java based on Zero Client Installation (ZCI).. This starts Adobe LiveCycle Designer in SAPGUI. Create a form. These include interactive forms in the ISR Framework.Interface element in View Designer • Adobe Library Documentation about specific objects in Adobe LiveCycle Designer. 1. To enable this. 162. 163. 4. 2.

1. Call transaction SFP_ZCI_UPDATE. You can use this transaction to update only those forms that are not in editing. 167. Prerequisites ● ● To be able to use the update function.. Any forms that you want to check or update have to be active. . The same prerequisites apply as described in Check and Update Functions with the Report FP_CHK_UPDATE. Prerequisites ● ● ● If you want to update forms from ISR Framework to ZCI. Proceed as described in the documentation for the report FP_CHK_UPDATE. see SAP Note 956074. runs the report for them. Integration This transaction calls the report FP_CHK_UPDATE especially for ZCI. and switches the layout type of the migrated forms to ZCI Layout. Activities 166. Note that you do not need to perform step 7 to select the objects. see SAP Authorization Concept. and update it if necessary. you require a role that is assigned to authorization object S_FP_CHK. you must first run the report FP_CHK_UPDATE with the ISR object.Check and Update Functions for Zero Client Installation (ZCI) Use You use transaction SFP_ZCI_UPDATE to check forms and update them to ZCI. 2. This transaction calls this report with the required objects. You created a layout previously with the integrated Adobe LiveCycle Designer tool. For more information.. . Check and Update Functions with the Report FP_CHK_REPORT Use The report FP_CHK_REPORT enables you to check the layout of a form. 41. Various objects can be selected for both the check function and the update function. For more information. It selects the required check and update objects automatically. Features This transaction calls the report FP_CHK_UPDATE especially for checking and updating forms to ZCI. Only those objects used to migrate forms for Zero Client Installation (ZCI) are currently available. We therefore recommend that you use the transaction SFP_ZCI_UPDATE.

● ● ● Since Adobe Document Services (ADS) are called for this function. The check and update objects must be on the ADS server.. 3. The system determines the number of forms on which the function is used and displays it in the status bar. Enter the name or names of the forms under Form(s). Detailed results of the check or update are shown in a log.. The link to Change and Transport System guarantees that updated forms are transported further in your landscape. You can also copy form names from a text file or the buffer. 4. . Activities 42. by inserting scripting. If you want to migrate forms for ZCI. You can determine the scope of the check or update by selecting appropriate objects. 6. the system creates a version of it automatically and saves it to version management. The default shown by the system is ADS. The system also shows you a list of inactive forms that cannot be used with this function (if available). You can choose one of the following options: ● ● Check form layouts This only checks the forms and does not modify them. Changed By. A dialog box tells you if no check or update objects are available. This guarantees that you always have access to a backup copy of the original form. Update form layouts This checks the forms and updates them if necessary. Under Activity. You can select forms by attributes such as Name. You can also select forms in the Multiple Selectiondialog box. Run report FP_CHK_REPORT in transaction SA38. read SAP Note 956074. Select at least one object to be checked or updated from the list of available check and update objects. specify whether you want the system to run a check or an update. Features This function allows you to check and update one or more forms in a batch process. 5. Created By. 1. 7. . 2. Before it changes a form. or Changed On in a dialog box. you must know the name of the appropriate RFC connection to ADS. specify the RFC connection to Adobe Document Services. Under ADS Connection. Choose Execute (F8).

Integration To fully understand how to use the API. Activities You can use all interfaces from the package SAXFT. This enables you to implement the programdriven generation of form templates.adobe. . This API generates an XFA (XML Forms Architecture) document that can be displayed in Adobe LiveCycle Designer. You generate the root node by using CREATE_OBJECT to instantiate an object from the class CL_SXFT_TEMPLATE. These logs are saved in the application log. It offers only a selection of the XML tags and attributes from the XFA specification.2. You create the structure of the XFA document as follows: ● You use “set” methods to set simple attributes and to send the attribute value to the VALUE parameter in quotation marks. you can call the method GET_FACTORY( ) to create a factory object.com/public/developer/xml/index_arch. we recommend that you restrict program-driven generation to simple form templates only. Each interface corresponds to precisely one tag in the XFA specification. For any forms assigned to a package. where you can display and analyze them later. and to send an object to the VALUE parameter that represents the attribute (and the new element). and may take some time depending on the number of forms selected. the system prompts you to enter the appropriate transport request for each transport layer. For this object. You can generate all subsequent XFA elements by using a “create” method of the factory method to instantiate the corresponding object. The API is based on Adobe XFA Version 2. ● You use “set” methods to set attributes that are themselves elements. 8. Adobe Designer itself offers a much wider range of functions. For this reason. The check or update runs. This prompt does not appear for forms or packages created as local objects. go to the following Internet address: http://partners.html. 9. This guarantees that your updates are transported. To access the Adobe XFA specification. without using Adobe Designer.You must read SAP Note 956074 before you select an object if you want to run an update before migrating forms for ZCI. Program-Driven Generation of Form Templates Use SAP provides an API (application programming interface) that you can use to generate a form template. This specification contains explanations of all elements and attributes. you must read this description together with the XFA specification. You can see the results in a log. as well as suggestions for the hierarchical structure of the elements.

see the program RSXFT_XFT_API_DEMOII. Keep scripting to a minimum. and a pushbutton. Recommendations for Form Builder ● For each business scenario. under Creating Forms for Optimal Performance. Arial. ● Structure the form context in accordance with the logical flow of data. If possible. Only use those interactive functions (such as dynamic value help that sends queries to the server) that are strictly necessary. since scripting in a form can have an effect on performance. For a detailed description of how to improve performance. which improves performance. This program generates a template that includes the following: header and footer. option fields. who can use it to achieve an optimal level of runtime performance when using Interactive Forms based on Adobe software. Place the context nodes used at the top of the form at the initial position in the context tree. these attributes do not need to be generated. Performance Aspects The following information is targeted mainly at developers. and Layout.An exception to this are attributes that are themselves elements but only have a few of their own attributes. Since no context is generated. a text input field. W. This interface is included in all interfaces that represent elements with these attributes. design an individual form that uses its own data retrieval methods. The interface IF_SXFT_NODE is included in all interfaces that represent XFA elements. For more information. Recommendations for Adobe LiveCycle Designer ● For interactive forms. Minimize the amount of communication that takes place with the server in interactive forms. ● You use the method IF_SXFT_NODE~APPEND_CHILD( NEW_CHILD ) to set child elements. use only the following character sets. Unless specified otherwise. Grouping interfaces are used for attributes that are used very frequently ● The interface IF_SXFT_ALIGNMENT groups the “set” methods for the attributes VALIGN and HALIGN. The values can be set directly by using the corresponding “set” method (such as <margin> and <color>). H. a static text. a selection list. Do not implement the condition-driven output of multiple forms from the same form object. . These character sets do not need to be embedded in the form. ● The interface IF_SXFT_MEASUREMENT groups the “set” methods for the attributes X. use the Form Caching function in the Designer. Example For an example implementation. see the online help of the Designer. This interface is included in all interfaces that represent elements with these attributes. these recommendations apply both to interactive forms in Web Dynpro and to PDF-based print forms. no data binding is created. Times New Roman. even if the Designer supports others: Courier. ● ● ● ● see the online help for the Designer. Y.

● Deactivate any context nodes that you do not need. In the latter case. use the function module FP_FIELD_LIST. see the documentation Form Caching in the online help of Adobe LiveCycle Designer (mentioned further below). For more information. There are two types of caching in ADS. which determines all fields used in the interface. which are used to define the bundling of forms. As well as caching the form layout. This function enables you to optimize communication with ADS by caching the form layout on the server where ADS is installed. Activities You activate this function by setting the field CACHING in the table FPCONNECT in the Data Browser (transaction SE16). caching activated The table FPCONNECT also contains other fields. design the data retrieval process in the application program and interface in accordance with your individual requirements. . Prerequisites To use this function. ● Cache forms that you want to process with Adobe document services. you can optimize performance on the ADS server since it retains a ready-made PDF that only needs to be filled with application data at runtime. To support you in your work. Recommendations for Calling Forms and Form Output ● When you create forms for mass printing. CACHING in Table FPCONNECT Value x space Meaning Activate caching Deactivate caching Use the system setting. This setting then applies to all forms in your Web AS ABAP. Caching Forms Use Forms are sent to Adobe document services (ADS) for processing. see Adobe Performance Analysis (in English only). Performance Analysis You can obtain precise details about the performance of Adobe document services. For more information. you can also cache the processed PDF (for interactive forms). you require SAP NetWeaver Support Package Stack 6 or higher. ● Bundle print forms.

Prerequisites To use this function. Bundling of PDF-Based Forms Use Forms are sent to Adobe document services (ADS) for processing. you require the following: ● SAP NetWeaver Support Package Stack 6 or higher ● Adobe document services installed in an SAP NetWeaver AS ABAP + Java system (J2EE Add-In). The function described here enables you to optimize communication with ADS by bundling forms in a single call. make the required settings in the table FPCONNECT in the Data Browser (transaction SE16). Table FPCONNECT Field DESTINATION DIR_GLOBAL BATCHING Required Setting Connection to ADS X is a prerequisite for bundling X to activate simple bundling . Activities There are two ways of bundling PDF-based print forms: Using a Table to Define Form Bundling To set this function in your system. ● Complex bundling Forms with different form designs and different languages are bundled together.See also: Form Caching in the online help of Adobe LiveCycle Designer under Creating Forms for Adobe Document Services → Designing Forms for Adobe Document Services → Optimizing and Improving Adobe Document Services. The data in the forms can be different. The data in the forms can be different. requesting PDFs. and output in XFP format). which enables the system to exchange data using the global directory Features Form bundling is supported for the following scenarios: ● Print ● Print and archive ● Archive only In all other cases (such as print previews. bundling is deactivated automatically by the system. You can choose one of two bundling types: ● Simple bundling Any forms with the same form design (layout and context) and the same language are bundled together.

uses them to describe and flag the document structure. Any gains in performance are also system-dependent. To do this. This has the advantage that you can specify which type of form bundling to run depending on your application. set the parameter IE_OUTPUTPARAMS-BUMODE in the function module FP_JOB_OPEN: Parameter IE_OUTPUTPARAMS-BUMODE Value x M space Meaning Simple bundling Complex bundling Setting taken from FPCONNECT No bundling Form bundling is particularly effective at improving performance for small forms. See Caching Forms. Adobe Acrobat or Adobe Reader tells you whether your PDF document has tags. . it may be a good idea to deactivate it occasionally for very large forms. complex bundling is activated. including elements such as headers. especially the applicable legal requirements. If both BATCHING and MBATCHING are set in the table. They are a requirement for the generation of accessible PDFs. specify –. however. Using the Application Program to Define Form Bundling You can also use the application program that calls the form to define form bundling. You cannot use the function described here if you want your PDF forms to be accessible. and tables.MBATCHING CACHING X to activate complex bundling Not required for bundling. Generation of PDF Forms Without Tags Use Applications that do not require accessible forms can improve runtime performance by creating PDF forms without tags. Check your requirements in advance. texts. If bundling has been activated in the system (using the entry in table FPCONNECT). specify space. To deactivate a field. to use the system setting. A PDF file with tags. PDF forms generated in this way need less memory.

● The PDF is always given tags when archived or returned to the application program. Generated PDF form is a PDF without tags.Features You can use the PDFTAGGED field in the IE_OUTPUTPARAMS parameter (type SFPOUTPUTPARAMS. display. The user settings or the scenario decide how to generate the PDF: ● The way the PDF is displayed in the print preview depends on the GUI settings on the front-end PC (accessibility mode). Parameter PDFTAGGED Value x space Meaning Generated PDF form is a PDF with tags. and print forms. Activities Set the PDFTAGGED field to your requirements in your application program and send it to the function module FP_JOB_OPEN. function module FP_JOB_OPEN) to define whether PDF forms are generated with or without tags. . it gives you detailed information about the form data and runtime information specified by Adobe document services. - Handling Errors and Problems Use Interactive Forms based on Adobe software provide you with comprehensive support for detecting and resolving errors and problems when you create. When you call the form. Features Utilities in the Form Builder The Form Builder that you use to create PDF-based print forms and interactive forms in Web Dynpro for ABAP offers you a wide range of functions: ● Checking and Testing a PDF-Based Print Form ● Saving Runtime Information and a Generated PDF Locally You activate this function in the Form Builder.

No Form Output If you encounter any connection errors or configuration errors when you use Adobe document services. Communication Errors. 002. About this Guide This guide is to provide you with an overview of the security aspects and recommendations when using SAP Interactive Forms by Adobe for your applications. Runtime Errors. and certification For notes for form developers and end users. signatures. The technology is implemented in . Note that these documents are available in English only: ● Interactive Forms based on Adobe Software Security Guide Overview of the architecture and required security-relevant settings in user management and SSL connections Adobe Document Services Configuration Guide Detailed description of each configuration step needed to set up the required users and communication paths Installation and configuration of the certificates for SSL connections. Settings and procedures that are the responsibility of the administrator are described in the following two documents. Security Aspects of SAP Interactive Forms by Adobe The following documents provide you with information about the security functions available when you develop and exchange SAP Interactive Forms by Adobe. and 004 You use this function module to find out the causes of any errors you encounter when displaying forms.Utilities in the Application Program that Calls the Form The following function modules provide you with support when you work with PDFbased print forms: ● Getting the Used Interface Fields ● Troubleshooting for Runtime Errors FPRUNX001. see the following: ● Digital Signatures and Certification in Forms Overview of the features that guarantee document security in forms plus a description of individual functions such as setting and checking signatures Detailed explanation of the validity of certifications and signatures ● SAP Interactive Forms by Adobe Security Guide This guide does not replace the daily operations handbook that we recommend customers to create for their specific productive operations. see the description under Problem Analysis Scenarios for Adobe Document Services for detailed troubleshooting information.

These functions are: ● Creating and verifying digital signatures and certification For these functions the use of SSL is mandatory. Related Security Guides Application SAP Web Application Server Guide SAP NetWeaver Application Server ABAP Security Guide SAP NetWeaver Application Server Java Security Guide Referenced documentation For detailed information on the procedure of configuring the security-related settings in your system. In addition.Adobe Document Services .sap. In this case we recommend that you activate SSL on all communication links.com/adobe → Media Library → Documentation Why is Security Necessary? The Adobe document services may deal with confidential data. Although running within the J2EE Engine. because high authentication.the Adobe document services. see Adobe Document Services Configuration Guide. also available at: http://service. the Adobe document services offer functions which require keys and certificates associated with your company. Restr. data integrity and confidentiality are required. Important SAP Notes SAP Note Number 682619 752153 736902 853497 894389 Title Adobe document services: Configuration Guide Adobe: PDF Manipulation Module High Encryption Adobe Credentials Adobe Acrobat Reader creates temporary files Rel. there are security requirements in the SAP Web AS ABAP and in the SAP Web AS Java.: SAP NW 2004s . Target Groups ● ● Technical consultants System administrators Important SAP Notes The most important SAP Notes that apply to the security of SAP Interactive Forms by Adobe are shown in the table below.

Thus the Destination Service communicates with the Internet Communication Framework (ICF). You must configure SSL on both communication path 1 and path 2. it is HTTPS. Communication path 1: 43.Technical System Landscape PDF-based Forms in ABAP Environment and Interactive Forms in Web Dynpro for ABAP PDF-based forms created in the ABAP Workbench and forms created in Web Dynpro for ABAP use the Adobe document services in the J2EE Engine for processing. . which is stored in the Form Design Repository of the ABAP Engine. The protocol for both communication paths is HTTP using the default HTTP port. . if your scenarios use digital signatures and certification. The figure below gives you an overview of the communication paths. The Form Processing Runtime sends the application data of the form and a link to the form design (template of the form) to the Adobe document services using SOAP.. In the case of SSL.. respectively HTTPS-Port. Communication path 2: Before processing the form and creating a PDF file. the Adobe document services calls the form design. through the RFC destination (SM59).

This library contains strong encryption. The figure below gives you an overview of the communication paths. . In case of SSL it is the IIOP SSL port of the J2EE Engine. if your scenarios use digital signatures and certification. see SAP Note 752153 and Configuration of the IIOP SSL in the Adobe Document Services Configuration Guide. You only need to configure SSL on this communication path if your scenarios require a high level of security. You have the option of storing the URL of the Adobe document services in the System Landscape Directory (SLD). The communication between these parts uses the IIOP service (IIOP port). You must set the Web Service Client Proxy as an SSL connection. you also have to download and deploy the Binaries SSL2 Library. To configure SSL you have to make settings in the User Management and in Communication Destinations. You may need authorization to receive this library.Communication path 3: The Adobe document services are installed on the J2EE Engine and consist of two parts. Communication path 1: Communication between Web Dynpro and the Adobe document services uses a Web Service. If you configure IIOP SSL. Interactive Forms in Web Dynpro for Java Interactive forms created with Web Dynpro in the SAP NetWeaver Developer Studio communicate with the Adobe document services in the J2EE Engine for processing. For more information.

User Management Tools Tool SAP Web AS Java user management using the Visual Administrator Detailed Description Use the Security Provider node in the Visual Administrator to maintain a service user on the SAP J2EE Engine. For more information. You only need to configure SSL on this communication path if your scenarios require a high level of security. For more information. the recommendations and guidelines for authorizations as described in the SAP Web AS Security Guide ABAP and SAP Web AS Security Guide Java apply here also. User Administration and Authentication The communication links described in the Technical System Landscape need a user in the SAP Web AS ABAP and in the J2EE Engine. Communication Destinations In this section. . This library contains strong encryption. see SAP J2EE Engine User Management Using the Visual Administrator. In case of SSL it is the IIOP SSL port of the J2EE Engine. 1. we provide an overview of the tools for user management and type of users which are necessary. The communication between these parts uses the IIOP service (IIOP port). For maintaining a user. User Management The Adobe document services uses the authorization provided by the SAP Web Application Server. we provide an overview of configuring the Web Service Communication between the ABAP and the J2EE environment. Java and ABAP. see SAP Note 752153 and Configuration of the IIOP SSL in the Adobe Document Services Configuration Guide. you may use tools in both application platforms. you also have to download and deploy the Binaries SSL2 Library. You may need authorization to receive this library. See also: Configuration of the Web Service SSL Connection in the Adobe Document Services Configuration Guide. See following topics: User Management In this section.Communication path 2: The Adobe document services are installed on the J2EE Engine and consist of two parts. See the table below. If you configure IIOP SSL. Therefore.

User System J2EE Engine or ABAP Engine ABAP Engine Grou/Role ADSCallers User ADSuser System user ADS_AGENT Service user SAP_BC_FP_ICF Type Service user ADSCaller Security Role See also: 1.com/instguidesNW2004s. Standard Roles Role ADSCaller (in J2EE Engine) Description Security role that allows the ADSuser to access the Adobe document services. that is described under Technical System Landscape. The service user ADS_AGENT in the SAP Web AS ABAP is required for the communication between the SAP Web AS ABAP and the Adobe document services when you use PDF-based printforms in the ABAP environment. Standard User As of NetWeaver 2004s the standard users that are needed for communication. For more information. This user was created in the J2EE Engine or in the SAP Web AS ABAP depending on the J2EE installation settings for the SAP User Management Engine (UME). Each user has a security role assigned to it. Communication Destinations 2. Created when system was installed. see Users and Roles (BC-SEC-USR). Configuring the User ADSUser for the SSL Connection Authorizations The table below shows the standard roles that are used by the Interactive Forms based on Adobe software. PFCG) Use transaction SU01 to maintain a service user on the ABAP engine for the Adobe document services. which has been predefined in the system. Thus also a role ADSCallers in the SAP Web AS ABAP was created. It is in the SAP Web AS ABAP when the UME is configured against the SAP Web AS ABAP backend. . For more information see the Installation Guide on the SAP Service Marketplace at the internet address http://sap. are created during installation of SAP NetWeaver. The ADSCallers role in SAP Web AS ABAP appears automatically as the ADSCallers group in the J2EE Engine. The ADSuser is assigned to this role.service. The ADSuser is required for the communication between the J2EE Engine and the Adobe document services.SAP Web AS ABAP user management and role maintenance (Transactions SU01.

SAP_BC_FP_ICF (in ABAP Engine) ADSCallers (in ABAP Engine) Role that allows the ADS_AGENT to access the ICF service in the SAP Web AS ABAP. See Technical System Landscape. Only if ADSuser is located in the SAP Web AS ABAP (Transaction PFCG). See User Management. The ADSCallers role in SAP Web AS ABAP appears automatically as the ADSCallers group in the J2EE Engine. .

Sign up to vote on this title
UsefulNot useful