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:

This logic controls the dynamic formatting of the form. and it can specify that invoice items can be processed repeatedly in a table. its appearance in graphics. A layout. For example. and the design of the pages. you define how the output data is positioned. • Architecture The following graphics show you the architecture that is implemented when you create and print a PDF-based form. PDF-Based Print Form Definition A PDF-based print form is a form designed for mass printing in SAP systems. 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. A form context that contains the form logic.You can use output parameters to specify print and archive settings. Instead. 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. it enables variable fields to be displayed. It has the standard Portable Document Format (PDF). In the layout. These parameters are not viewed in Form Builder. 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. you control them with function modules that you integrate in your application program. .

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

for example. Structures Adobe Designer includes two different types of pages that you can use to structure your form layout: . and determine the order of the pages that have differing structures. a function module is generated that encapsulates all properties of the form. 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.When you activate the PDF-based form. or ZPL to be sent to the spool A function module is available for more precise control of the output. tables. When the generated function module is called. When the application program calls the function module. PostScript. Page Concept and Elements of a Form Definition You specify the page layout for a form in Adobe Designer. This can be. and various other types of objects can be displayed in the output range of a form page. data. 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. table data selected previously in the application program. Texts. the form description and application data is sent to Adobe document services.

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

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

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

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

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

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

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

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

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

● ● ● Move and copy nodes Set node as active or inactive Update nodes For an overview of the graphical user interface. 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. see Screen Display in the Context of Form Builder. To edit the layout. choose the Properties tab and double-click the name of the interface. . choose the Layout tab. but cannot be changed here. To edit the interface.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

If the field has a type from the ABAP Dictionary. current time of the application server Logon name for user in the SAP system If single record nodes are used. for example. in conditions) for any fields. icon. you can query system fields (for example. with the text Reload Interface. Reloading an Interface Use You have already started to edit the form context and you have made changes to the interface. Activities To reload the interface.• • You cannot assign a value to a system field. choose the screen above the 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. current date of the application server Date and time. It is displayed below the interface. on the left of the . System Fields Field Name SFPSY-DATE SFPSY-TIME SFPSY-USERNAME SFPSY-SUBRC Meaning Date and time. in another session. 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 general. you can double-click the type name to go to its entry in the ABAP Dictionary. 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.

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

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

05. * FP_DOCPARAMS-COUNTRY = 'DE'. 2004 5/17/04 German Date 17. 2004 May 17.04 For more information. FormCalc Language Reference Your local Adobe Designer installation includes a FormCalc language reference in a PDF file that you can print out. * 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. FP_DOCPARAMS-COUNTRY = 'US'. [. 2004 May 17.05.] * US format FP_DOCPARAMS-LANGU = 'EN'. . * German format * FP_DOCPARAMS-LANGU = 'D'.. 17. 2004 Monday. 2004 May 17. These values are sent to the generated function module that contains the form description. Mai 2004 17. Mai 2004 17. see Example: Calling Forms in the Application Program. Example You want to display the date objects on the form in US format or in German format.05.2004 17.2004 17. The dates are formatted according to the parameter values entered for language and country in the application program. May 17. DATA FP_DOCPARAMS TYPE SFPDOCPARAMS..• • Localized Medium Date Localized Short Date Use You use these date objects to format dates locally when you call the form.05.2004 Montag.

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

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

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

In this example. RS38L_FNAM. FP_FUNCTION_MODULE_NAME gets the form name. Example: Calling Forms in an Application Program The following is a program excerpt showing how the function modules are called. 3. where they must already be defined. 2.generated pages in the form. SFPDOCPARAMS. 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. Generated function module of the form 158. 4. . TYPE TYPE TYPE TYPE TYPE TYPE SCUSTOM. BOOKINGS. For more information.. 157. FP_JOB_CLOSE closes the spool job. FP_JOB_OPEN opens the spool job. TY_BOOKINGS. 32. TY_CONNECTIONS.. 1. the parameters CUSTOMER. 156. 155. SFPOUTPUTPARAMS. see Form Output. 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. and CONNECTIONS are sent to the form interface. .

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

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

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

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

You can choose one of the following options: 35. 2. Trace 34.. ArchiveLink is a communication interface that manages archiving systems in the SAP system.. .sap. To activate the trace output. Call the function module FP_GET_LAST_ADS_TRACE after the generated function module. for example. 2. Call the function module FP_GET_LAST_ADS_ERRSTR after the generated function module. call the function modules in your application program.. . .• • 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. Troubleshooting Texts 1. FP_GET_LAST_ADS_TRACE gives you the trace. 1. This interface allows you to link the form with application data. FP_GET_LAST_ADS_ERRSTR gives you a text that indicates the cause of the error. Read the SAP Note 717568 on the SAP Service Marketplace at service. the form is forwarded to ArchiveLink. ● ● Printer Archiving In this case. Form Output Purpose You can send a PDF-based form to various types of output media..com/notes. 2. 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. 3. This note gives you precise and up-to-date information about how to proceed when troubleshooting.

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

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

by doing the following. 4.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 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. 3. you want to use the character set MS MINCHO instead of Times New Roman. enter the font that you want to replace the source font with. 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. When you call the form. the system forwards the generated PDF forms to the spool processing functions and sends parameters to the spool dialog. See also: . see the ABAP Dictionary (transaction SE11). Under Target Font. Example For the Japanese version of the form FP_name. 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. You can use this spool dialog to control the output. Under Source Font. specify the font in the original form. To do this. you send these parameters (IE_OUTPUTPARAMS) to the function module FP_JOB_OPEN.

you want to adjust the spool dialog to your requirements when printing a PDF-based form. or if it is compatible with Smart Forms.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. the spool dialog is controlled by different parameters. See also: Controlling the Spool Dialog in the Smart Forms documentation Prerequisites The DEVICE parameter of the structure SFPOUTPUTPARAMS must have the value ’PRINTER’. If a form is migrated from a Smart Form. or hide the spool dialog completely. 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: 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. Adobe Document Services require this file to create the print files. HP9500. 4. XDC files are shipped for the following SAP device types: POST2 (generic device type that can be used for every PostScript printer). You do not usually need to make any modifications to these XDC files to use them for successful printing. call the function module FP_JOB_OPEN and specify the required parameters. Result You have placed the selected forms in a print request. 1. When you call the form in the application program. 3. specify the value ’X’ (for example. HPLJ4. The XDC scenarios provide you with examples of how you can make specific settings for your printer. 2. See also: Calling Forms in an Application Program XDC Scenarios for Print Control Use An XDC file is a printer description in XML format.. NODIALOG = ’X’. first call the function module FP_JOB_OPEN. The function module FP_JOB_CLOSE is the last function module to be called. Determine the names of the generated function modules with FP_FUNCTION_MODULE_NAME. AZPL203. and AZPL300. Then call the generated function module(s) that you want to use in the output.Activities In the application program. To set a parameter with the data type CHAR(1). PDF documents can only be printed on printers of SAP device types for which there is an XDC file in the system. to suppress the user dialog). Procedure 38.

this output device is used as a virtual device for connecting to the external application. 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. By default. at least one printer of device type XFP must be set up in the system. Integration XFP output corresponds to XSF output for Smart Forms and RDI output for SAPscript. . For more information.sap.Integration You can edit XDC files in a text editor and manage them in the SAP system. Software partners can receive a certificate from SAP for products that access the XFP interface. see the Software Partner pages at http://www. but does not contain any layout information about the form. Output in XFP Format Use Using the XML interface for PDF-based forms (XFP). For up-to-date information about downloading this documentation.com/spp.com/notes. we recommend that you set up an XFP output device. external applications outside the SAP system can access and process the contents of forms. Prerequisites Since XFP uses spool processing. see SAP Note 766410 on SAP Service Marketplace at service. 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). see SAP Service Marketplace at Adobe → Media Library → Documentation. 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. The XFP output contains all form data in XML format.sap.

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

and print forms. Runtime Errors. display. 002. 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.● Cache forms that you want to process with Adobe document services. . 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. Performance Analysis You can obtain precise details about the performance of Adobe document services. Communication Errors. 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. For more information. it gives you detailed information about the form data and runtime information specified by Adobe document services. When you call the form. see the description under Problem Analysis Scenarios for Adobe Document Services for detailed troubleshooting information. see Adobe Performance Analysis (in English only).

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

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

choose Utilities → Versions → Generate Version. ● To access the version management functions.Version Management Use The PDF-based forms solution is integrated with version management tools. You can save different versions of both forms and interfaces. Manager Self-Services) are developed in ABAP Workbench (transaction SFP) and implemented in the Web Dynpro for Java runtime environment. and you call it there. See also: Migrating Smart Forms in the Smart Forms documentation Interactive Forms There are several ways of creating an interactive form. • ○ For general information about using forms. 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. . You use one of the following development environments. 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. Integration This function is integrated into the Smart Forms transaction. ● To save a version of the form or interface in the version management database. Activities Under Form Builder: Entry Point. Management. enter a form or interface. see the mySAP ERP documentation under HCM Processes and Forms and Internal Service Request (ISR).

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 . For more information. see SAP Note 750784. see Reader Rights Credential in the Adobe Document Services Configuration Guide. see Creating Forms for Integration with Web Dynpro and ZCI. and data bindings. 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. generate a PDF when you call a form. This development environment is intended mainly for creating print forms. the context structure. All of these options require Reader Rights to be granted before you can use interactive forms in Adobe Reader. these steps run automatically in the environments listed above. In certain circumstances. ABAP Workbench. You can. Transaction SFP. Reader Rights are configured as part of the installation and configuration process of Adobe Document Services. including information about constructing the view. 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. and use certain parameters to control which input is allowed. Note that you need to program some steps manually when you use ABAP Workbench. For more information. interactive forms require licenses. however. A user in Adobe Reader cannot enter and save data in an interactive form until these rights are granted.• ● ○ For information about creating forms in Form Builder.

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

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

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

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

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

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

The data in the forms can be different. The function described here enables you to optimize communication with ADS by bundling forms in a single call. Table FPCONNECT Field DESTINATION DIR_GLOBAL BATCHING Required Setting Connection to ADS X is a prerequisite for bundling X to activate simple bundling . ● Complex bundling Forms with different form designs and different languages are bundled together. 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). Bundling of PDF-Based Forms Use Forms are sent to Adobe document services (ADS) for processing. bundling is deactivated automatically by the system. make the required settings in the table FPCONNECT in the Data Browser (transaction SE16). 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. The data in the forms can be different. 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. and output in XFP format).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. Prerequisites To use this function. 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. requesting PDFs.

MBATCHING CACHING X to activate complex bundling Not required for bundling. Check your requirements in advance. Adobe Acrobat or Adobe Reader tells you whether your PDF document has tags. Using the Application Program to Define Form Bundling You can also use the application program that calls the form to define form 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. A PDF file with tags. See Caching Forms. and tables. This has the advantage that you can specify which type of form bundling to run depending on your application. to use the system setting. complex bundling is activated. . To deactivate a field. They are a requirement for the generation of accessible PDFs. PDF forms generated in this way need less memory. If both BATCHING and MBATCHING are set in the table. To do this. specify –. however. 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. especially the applicable legal requirements. specify space. If bundling has been activated in the system (using the entry in table FPCONNECT). it may be a good idea to deactivate it occasionally for very large forms. uses them to describe and flag the document structure. including elements such as headers. You cannot use the function described here if you want your PDF forms to be accessible. texts. Any gains in performance are also system-dependent.

function module FP_JOB_OPEN) to define whether PDF forms are generated with or without tags. display.Features You can use the PDFTAGGED field in the IE_OUTPUTPARAMS parameter (type SFPOUTPUTPARAMS. When you call the form. Parameter PDFTAGGED Value x space Meaning Generated PDF form is a PDF with tags. - 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. ● The PDF is always given tags when archived or returned to the application program. . Generated PDF form is a PDF without tags. it gives you detailed information about the form data and runtime information specified by Adobe document services. Activities Set the PDFTAGGED field to your requirements in your application program and send it to the function module FP_JOB_OPEN. 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). 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. and print forms.

Communication Errors. 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. 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. Settings and procedures that are the responsibility of the administrator are described in the following two documents. 002. see the description under Problem Analysis Scenarios for Adobe Document Services for detailed troubleshooting information. 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. and certification For notes for form developers and end users. and 004 You use this function module to find out the causes of any errors you encounter when displaying forms. The technology is implemented in . 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. 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. No Form Output If you encounter any connection errors or configuration errors when you use Adobe document services. signatures.

data integrity and confidentiality are required.com/adobe → Media Library → Documentation Why is Security Necessary? The Adobe document services may deal with confidential data.Adobe Document Services . the Adobe document services offer functions which require keys and certificates associated with your company. see Adobe Document Services Configuration Guide. 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. Although running within the J2EE Engine. also available at: http://service.the Adobe document services. In addition.sap. Restr. In this case we recommend that you activate SSL on all communication links. 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. These functions are: ● Creating and verifying digital signatures and certification For these functions the use of SSL is mandatory. there are security requirements in the SAP Web AS ABAP and in the SAP Web AS Java. because high authentication.: SAP NW 2004s . 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.

which is stored in the Form Design Repository of the ABAP Engine. through the RFC destination (SM59). if your scenarios use digital signatures and certification. the Adobe document services calls the form design... 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. Communication path 1: 43. Thus the Destination Service communicates with the Internet Communication Framework (ICF). In the case of SSL. The figure below gives you an overview of the communication paths. . You must configure SSL on both communication path 1 and path 2.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. it is HTTPS. . The protocol for both communication paths is HTTP using the default HTTP port. respectively HTTPS-Port. Communication path 2: Before processing the form and creating a PDF file.

If you configure IIOP SSL. This library contains strong encryption. . For more information. To configure SSL you have to make settings in the User Management and in Communication Destinations.Communication path 3: The Adobe document services are installed on the J2EE Engine and consist of two parts. You have the option of storing the URL of the Adobe document services in the System Landscape Directory (SLD). see SAP Note 752153 and Configuration of the IIOP SSL in the Adobe Document Services Configuration Guide. 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. You must set the Web Service Client Proxy as an SSL connection. You may need authorization to receive this library. The communication between these parts uses the IIOP service (IIOP port). you also have to download and deploy the Binaries SSL2 Library. You only need to configure SSL on this communication path if your scenarios require a high level of security. if your scenarios use digital signatures and certification. 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. Communication path 1: Communication between Web Dynpro and the Adobe document services uses a Web Service.

See also: Configuration of the Web Service SSL Connection in the Adobe Document Services Configuration Guide. In case of SSL it is the IIOP SSL port of the J2EE Engine. we provide an overview of configuring the Web Service Communication between the ABAP and the J2EE environment. you also have to download and deploy the Binaries SSL2 Library. Java and ABAP. For more information. 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. See the table below. 1. . we provide an overview of the tools for user management and type of users which are necessary. See following topics: User Management In this section. see SAP Note 752153 and Configuration of the IIOP SSL in the Adobe Document Services Configuration Guide. The communication between these parts uses the IIOP service (IIOP port). User Management The Adobe document services uses the authorization provided by the SAP Web Application Server. 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. If you configure IIOP SSL.Communication path 2: The Adobe document services are installed on the J2EE Engine and consist of two parts. see SAP J2EE Engine User Management Using the Visual Administrator. This library contains strong encryption. Communication Destinations In this section. You only need to configure SSL on this communication path if your scenarios require a high level of security. you may use tools in both application platforms. Therefore. You may need authorization to receive this library. For maintaining a user. 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.

Created when system was installed. which has been predefined in the system. Thus also a role ADSCallers in the SAP Web AS ABAP was created. Standard User As of NetWeaver 2004s the standard users that are needed for communication. are created during installation of SAP NetWeaver. Each user has a security role assigned to it.com/instguidesNW2004s. 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. The ADSuser is required for the communication between the J2EE Engine and the Adobe document services. Communication Destinations 2. It is in the SAP Web AS ABAP when the UME is configured against the SAP Web AS ABAP backend. Standard Roles Role ADSCaller (in J2EE Engine) Description Security role that allows the ADSuser to access the Adobe document services. . 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. For more information see the Installation Guide on the SAP Service Marketplace at the internet address http://sap. 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. PFCG) Use transaction SU01 to maintain a service user on the ABAP engine for the Adobe document services. 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).service.SAP Web AS ABAP user management and role maintenance (Transactions SU01. The ADSuser is assigned to this role. that is described under Technical System Landscape. The ADSCallers role in SAP Web AS ABAP appears automatically as the ADSCallers group in the J2EE Engine. see Users and Roles (BC-SEC-USR).

The ADSCallers role in SAP Web AS ABAP appears automatically as the ADSCallers group in the J2EE Engine. See User Management. . Only if ADSuser is located in the SAP Web AS ABAP (Transaction PFCG). See Technical System Landscape.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.

Sign up to vote on this title
UsefulNot useful