This action might not be possible to undo. Are you sure you want to continue?
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.
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.
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).
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
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.
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.
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.
you define how the output data is positioned. and it can specify that invoice items can be processed repeatedly in a table. Instead. 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. and so adapt the output to your requirements. These parameters are not viewed in Form Builder. A layout. and the design of the pages. . PDF-Based Print Form Definition A PDF-based print form is a form designed for mass printing in SAP systems. It has the standard Portable Document Format (PDF). For example. This logic controls the dynamic formatting of the form. it specifies that certain texts appear only under certain conditions (one text for a first warning and a different text for a second warning). • Architecture The following graphics show you the architecture that is implemented when you create and print a PDF-based form. A form context that contains the form logic. In the layout.You can use output parameters to specify print and archive settings. its appearance in graphics. you control them with function modules that you integrate in your application program. it enables variable fields to be displayed. 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.
The architecture of PDF-based forms is designed to separate the collection of the application data from the definition of the actual form: . You can assign multiple forms to the same interface. which consists of the form context and layout. Form interfaces and forms are stored as separate development objects in the repository. Form Output − Runtime If you use an application to create a form. you generally need to insert application data in the form. When you create a form. The form description includes the complete form design as a complex description in XML. you must assign it to a form interface.Creating a Form The form interface is created separately from the form. if they use the same data.
a function module is generated that encapsulates all properties of the form. This can be. table data selected previously in the application program. 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. Use You can create any number of pages for your form. When the generated function module is called. the form description and application data is sent to Adobe document services.When you activate the PDF-based form. PostScript. Page Concept and Elements of a Form Definition You specify the page layout for a form in Adobe Designer. data. it uses its interface (corresponds to the form interface) to send it the application data. Structures Adobe Designer includes two different types of pages that you can use to structure your form layout: . for example. and determine the order of the pages that have differing structures. and various other types of objects can be displayed in the output range of a form page. Texts. tables. or ZPL to be sent to the spool A function module is available for more precise control of the output. When the application program calls the function module.
Designing Forms with the Form Builder Purpose You can use this process to create or edit a PDF-based form. . 1. call the Form Builder: • • • You are on the screen Form Builder: Change Form <Form Name> or Form Builder: Display Form . To access the online help for Adobe Designer. date and time fields. In the interface. text fields. These elements are available in a library in Adobe Designer. and the different types of page elements. you define where the data comes from that you want to display in the form. circles. 3. and lines Dynamic objects.• • Master pages Body pages You can position various elements on these pages. You create a form object. such as option and list fields.. 1. • Standard objects • • • • • Static objects such as texts. 3. 2. Adobe Designer is installed with the SAP front end. Process Flow To create a form. You activate the interface. see the online help in Adobe Designer. you use the Form Builder that is integrated with the ABAP Workbench.. Prerequisites You have installed Adobe Designer on your front end. • Choose Help → Help Topics under Layout. You can also edit a migrated Smart Form. 1. you call the interface function in the Form Builder. and password fields Special date objects Your own user-defined objects Bar codes For more information about the page concept. To do this. graphics. 2. rectangles. numeric fields.
6. choose Create ® Form Object ® Interface. . Proceed as described under 5. 6. In the Create Interface dialog box. 6. You can also insert texts. For more information about the different interface types. Enter the name of the interface that you want the form to use. 5. 4. The Create Object Directory Entry dialog box appears. 2. graphics. 5. Choose Save. 4.. a. Result You have created a function module that encapsulates the form description. You are in the Repository Browser of the ABAP Workbench. 8. . Enter the name of the form in the Create Form dialog box. In the context in the Form Builder. You use this graphical tool to design the printed appearance of the form. Enter your data and save the object. below. In the layout function in the Form Builder.. 3. c. b. proceed as follows: 4. c. and addresses. you create the layout. You then have a PDF-based document for mass printing in SAP systems. 7. 2. 5.4. and drag and drop data from the form context you have defined. You can use an application program that collects the relevant data to call this function module. Select a package. 9. You activate form. You have two options here: Creating a Form Object in the Repository Browser 7. 13. 2. 3. 12. To create a form interface. Creating a Form Object Use Form interfaces and form contexts with layouts are known as form objects. you drag and drop the required parameters from the interface you have defined. 10. a. In the context menu of the package. 5. b. choose Create →Form Object → Form. Before you can start to edit these objects in the Form Builder. proceed as follows: 1. enter the name of the interface and select an interface type. see Interface in the Form Builder. 1. To create a form with a context and layout. 6. In the context menu of the package. you must create them. 11.
5.. 3. If you want to create an interface. 20. specify a form or interface. 21. follow the procedure shown above under 3a. 19. 3.Creating a Form Object from a Transaction 3. 1. the documentation object is copied. Displaying Documentation 23. 15. Under Form Builder: Entry Point. 24.. deleted. 17. This documentation is used as F1 help and contains information for support team members or form developers who need to examine the form. Choose Goto ® Documentation ® Display. A form object is assigned to precisely one piece of documentation. Result The Form Builder starts. 4.. . 2. specify a form or interface.. Under Form Builder: Entry Point. renamed. If you want to create a form. You can start to edit the interface or form. 25. The creation of form documentation is integrated into the standard documentation environment (transaction SE61). 1. Prerequisites You require SAP NetWeaver SPS 8 or higher. Creating and Displaying Form Documentation Use You can create documentation for each of your forms or form interfaces (form objects). 1. . Creating or Changing Documentation 18. Note. The system calls the SE61 editor and you can create your documentation. Call transaction SFP. however. 14. Save your changes. 5. Choose Goto → Documentation ® Change. The documentation is not included in the form output and is only available in Form Builder. 2. follow the procedure show above under 4a. . 4. Choose Back. that the documentation is ignored by the functions Upload Form Object and Download Form Object. 2. Enter the name of the interface or form.. 22.. The documentation is displayed. . Choose Create. and transported automatically with its accompanying form object. 16. 4. 3.
You cannot enter system fields directly. 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. You cannot edit it within Form Builder. such as dates Data that you have calculated or implemented in a form yourself. Unlike ABAP Dictionary-based interfaces and Smart Forms-compatible interfaces. you can create program code to modify global definition data before the form is processed. The system fields contain data with a predefined meaning (such as the date). You load the finished interface into Form Builder. ● ● XML Schema-Based Interface You use this interface type if you create your forms in Form Builder in Web Dynpro for ABAP. which must be constructed in accordance with the W3C standard. Both interface types give you the following options for including data in PDF-based print forms: ● ● ● In the form interface. You use the form interface to specify this data.Interface in Form Builder Use You want to include data in your form that was not specified when the form was created. This interface is an XML schema. in an appropriate editor on your front end. Under Global Definitions. you define your own fields. you specify the data that is exchanged with the application program (such as tables). The XML schema already contains the form context. The XML schema-based interface consists of the following: . Under Code Initialization. Data provided by the SAP system or by the PDF-based print forms solution. You use fields inserted as placeholders in the form to specify the appearance and location of the data in the form. When you call the context in Form Builder. These fields are replaced by the current data at runtime. You can use form routines that are defined in ABAP Editor. This can include the following data: ● ● ● Data selected from the database tables of your application. You can assign currency and quantity fields. such as totals for tables For all three of these data types. the system shows the available system fields automatically in the interface. which is sent directly to the data view in Adobe LiveCycle Designer. You can then drag and drop the required fields to the context. You create the XML schema as a local XSD-type file. you do not need to create the form context here. the data is not specified or inserted in the form until runtime.
However. You can start to edit the interface. The form interface of a form is structured in the same way as the interface of a function module in the system. Prerequisites ● You have created an Interface form object. The semantics of the valid parameter types match the semantics of a function module. The XML schema The loaded XML schema is displayed here. Change. 5. switch to the Properties tab page. Enter the name of the interface. ● The application program provides the data that you want to insert in the form. . or Display. 28. 1. See also: Getting Information about Interface Parameters Overview of Function Modules (in ABAP Workbench: Tools) . 6. You cannot make changes if you have chosen Display. Therefore... you already know the types of the corresponding variables. From Transaction SFP 26. Call transaction SFP. To select the interface type. 27. 3. Choose Create. Defining a Form Interface Use You define a form interface to send data from your application to a form. 30. 29. form interfaces do not support Changing parameters.● ● 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). 2. 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. 4. Choose Interface. Integration The form interface is a part of the Interface form object and is defined in the Form Builder. Form Builder starts.
you see the standard parameter /1BCDWB/FORMOUTPUT of the generated function module.. but is not defined when the application program is called. At runtime. 32. All data types are valid. This screen also shows the standard parameter /1BCDWB/DOCPARAMS. Open the required interface in the Repository Browser of the ABAP Workbench. This has the advantage that an application program can work with several different forms. However. ABAP-based or Smart-Forms-compatible interface ○ To insert a new line. These names are valid for the whole form and do not have to match the variable names in the data collection program. You cannot change this parameter. 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. TYPE can be selected under Type Assignment. 31. When you set the Import. the Tables option gives you extra parameters. for example. • 36. to make the generated form available as a PDF for further processing. then the output of the form ends with the program crashing (hex dump). Enter the parameter names of the data you want to import. 35. . You see a screen for entering import parameters. double-click Exceptions. for example. double-click the SFPDOCPARAMS type. 37. 7. You use this parameter in your application program. To display this structure in the ABAP Dictionary. 33. to specify the value for the language setting. To display the exceptions used by the generated function module. it is also possible that the application program provides parameters that the form does not need. 4. Activate the interface.Creating Function Modules (in ABAP Programming (BC-ABA)) Procedure 7. 6. If a parameter has been defined in the form. You cannot change this parameter. 3. Export.. 5. The Interface tab is displayed. 2. . When you double-click Export. and Exceptions parameters. double-click the Import node. You use this parameter in your application program. the system also lets you use the standard parameters from the Smart Forms. XML schema-based interface • ○ The standard parameter /1BCDWB/DOCXML with the type XSTRING is used for sending data from the application program. Under Form Interface. 1. choose Insert Line ( ). they can also be specified in a different order from the code of the application program. the application program must provide the parameters. 34. You do not need to mention these parameters in the form.
) Result You have defined the form interface and you can use the specified parameter names in the form context. you can use the existing application program of this Smart Form without making any modifications. Functions You use the ABAP Editor to write the program code (Code Initialization) that is executed before the form is processed. You can include subroutines (Form Routines) when you do this. Activities Double-click the node that you want to edit. for example. You can initialize the global data. Here. if the ABAP Dictionary does not provide a type. 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. to convert selected application data. to display totals). (See also Switching Runtime in Migrating Smart Forms. . you have the option of defining your own fields to be used anywhere in the form. Field Symbols You can use field symbols as pointers when you extract data from internal tables. you create data types as free ABAP code. Types Here. to convert selected application data. See also: Initialization Initialization Use SAP customers can use this function to execute ABAP program code before a form is processed. you define any data needed by the form. Features Global Data Here. for example. but which has not been provided by the form interface (for example. We recommend that you use Global Datain the initialization. Global Definitions Use Global definitions belong to the interface in the Form Builder.If you have a Smart Forms-compatible interface.
. 8. you must indicate this reference to the system in the form. the system recognizes the reference automatically. Context in Form Builder Use In the context (also known as the form context). CURTAB) to a value field in another table (for example. you can assign a currency or quantity field to a table field. In the output of these fields. In this hierarchy.. Field Name: VALTAB-VALUE. In the second case. You include this data as a node in a hierarchy structure. you also decide the form logic by specifying conditions for processing the nodes. Create the reference to the currency field by entering the following values: 1. 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. 38. and formats the value field according to the currency or unit in the assigned field. 2. you specify which data is copied from the interface to the form.. the system cannot recognize this reference automatically. to ensure that the value field is formatted correctly. Reference Field: CURTAB-CURRENCY. the system formats the value field VALTABVALUE according to the assigned value in the currency or quantity field of the global variable CURTAB-CURRENCY. Procedure You want to assign a currency or quantity field in one table (for example. VALTAB). Under Data Type. if this is the value field of VALTAB that you want to display. .See also: Global Definitions Specifying a Currency or Quantity Reference Use In the ABAP Dictionary. which is the currency field of CURTAB. Result In the output of the PDF-based print form. 39. If the value field is in a different table from the currency or quantity field. specify whether the data type is a currency or quantity.
You can specify conditions. 45. The system sends the form context to the layout function of Form Builder automatically. and the form context itself appears as a hierarchy under Data View. To view the entire form logic. Call transaction SFP. then the node is skipped. To do this. a properties window is displayed under the context. If the condition is met. Integration The context function in Form Builder is the link that binds the interface to the layout. Choose Form. From Transaction SFP 40. To do this. 6. or Display. choose the Context tab page. choose Form Objects → Forms and select a form. 2. Change.. Create or edit the context.. Activities There are two ways of calling Form Builder for the context: From ABAP Workbench (Transaction SE80) From the object list. you can hide any items. If the condition is not met. For each node. that you do not need. 1. . as well as all its subnodes. if this is supported by the selected node. Editing the Form Context You can edit the form context in the following ways: ● Create nodes . When you create the layout. Define the layout type of the form. 43. 3. Enter the name of the form. you use the Data View nodes to include the data in the form. expand all nodes. and how they are processed. 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. The layout function calls Adobe Designer. 41. Features You use the form logic of the context to control which rules are used to send the hierarchy nodes to the layout. Form Builder starts. The form logic determines the following: ● ● ● Whether the content of the node (text. 4. such as table fields.Prerequisites You have created the form objects Interface and Form. 5. addresses. 42. You construct the form context from the existing interface. Choose Create. Only active nodes are forwarded to Form Builder to be processed in the layout. choose the Properties tab page. You can also specify WHERE conditions for the selection of data from tables. 44. then the node is processed. In this way. You cannot edit if you have chosen Display.
To edit the interface. 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. but cannot be changed here. see Screen Display in the Context of Form Builder. To edit the layout.● ● ● Move and copy nodes Set node as active or inactive Update nodes For an overview of the graphical user interface. . choose the Properties tab and double-click the name of the interface. choose the Layout tab. The interface on which the form is based is displayed.
Displayed directly after the node that is processed depending on this condition. others represent the form logic. All nodes.Nodes in the Context Definition Nodes in the context are organized in a hierarchy. depending on conditions Groups subnodes for clarity Not a separate node. or dynamic text Graphic Address. You can use conditions to specify whether the data in the form is included and displayed at runtime. data nodes are generated automatically. Folder Condition . The first node in the context is a folder node and has the name of the form. TRUE and FALSE. Node Types Nodes Without Subnodes Symbol Node Type Text Graphic Address Meaning Text module. Some nodes represent the data in the form. data nodes are generated automatically. can have any node as a direct subnode Any nodes None Table/loop Dynamic table Alternative Alternatives. the address data is extracted directly from database tables and formatted for printing. include text. Other Nodes Symbol Node Type Data node Structure Meaning Elementary data field Structure Possible Direct Subnodes None All nodes.
10.. Only active nodes are sent to the layout in the Form Builder. you can create nodes for text. 47. . 3. use Drag&Drop to drag it to the required place in the form context. Click a node in the context with the secondary mouse button to display the context menu for this node.. graphics. 3. you can do the following: • Enter and change properties • Enter and change conditions Result You have created nodes in the context.. 51. select the node under which you want to insert the new or copied node.. Double-click the node to display more details about the node in a screen under the context. As well as the data defined in the interface. In the context. Now perform the following: • To move a node. . Depending on the node type. delete. Moving or Copying Nodes Moving or Copying Nodes with Drag&Drop • • To move a node. 52.Creating Nodes 46. choose Paste. Depending on the data type. Moving or Copying Nodes with the Context Menu 11. 2. 1. • To copy a node. 48. drag it as above. In the context. To create one or more nodes. click the secondary mouse button. • You can create a new node. 2. choose Cut in the context menu of the node. you have the following options: • You can set the node as Active or Inactive. and paste nodes. To display the context menu of the node. 4. To copy a node. 50. drag the required fields from the interface on the left of the screen to the context. cut. and addresses. 49. • You can copy. 1. In the context of this node. choose Copy. . Double-click a field in the interface to display a dialog box with detailed information about the properties and type of the field. select a node that you want to move or copy. but press the Ctrl key at the same time.
54. FLDATE. Setting Nodes as Active or Inactive Use To hide one or more nodes in the form context. Click the secondary mouse button and choose Set to Active or Set to Inactive in the context menu. . and so on). You can set also set individual nodes as active or inactive in the Properties window. select all the other data nodes in the table and set them as inactive. At runtime. only the active nodes are included in the form. However. Activities 12. Accordingly. when you choose the Layout tab page. CONNID. Only these two data nodes in the table will be included in the form at runtime. Example You have created a BOOKINGS table node in the form context. Only active nodes are sent to the layout and can be used by Adobe Designer in the data view.. you see the BOOKINGS node with the row node and FLDATE and PASSNAME in the data view of Adobe Designer. 1.You cannot delete. A node with a condition always appears in the data view of Adobe Designer. These nodes are flagged as generated ( ). conditions are not implemented until runtime.. then you can use this function to update the context. Select one or more nodes. 2. To copy only the FLDATE and PASSNAME data nodes to the layout. you can set them as Active or Inactive in the context menu. as long as it is active. The form context shows both generated and non-generated nodes. which makes it easier to use. set these nodes as inactive. you can see all its data nodes (MANDT. CARRID. PASSNAME. When you expand the table node and its subnodes. . you only see the data that you actually need for the form. or copy generated nodes (flagged with ) in structures and tables. when sending them to the layout in the Form Builder. 53. Unlike the active or inactive setting. move. In this way. Updating Nodes Use If you have already started to edit the form context and you have made changes to the field definition of nodes.
. . or data nodes that have a reference to the ABAP Dictionary. for example.com/notes.. and used in the form output. see the description of the node. single record nodes. You cannot delete.Generated nodes (flagged with ) are the fields of structures or tables that you have inserted in the context from the interface. Double-click the node to open the properties screen. the system also displays additional nodespecific properties (which you can change). You can choose non-generated nodes only. .sap. see SAP Note 808116 at service. Activities 55. You cannot change this. 2. Properties Use Properties describe the content or meaning of a node. . You can now change general properties of the node. Depending on the chosen node. with the text Update. the system copies the short text of the type from the ABAP Dictionary under Description. choose the icon. as well as the general properties. 2. 56. If you use loop nodes. see Setting Nodes as Active or Inactive. These nodes are not generated. such as Name. 13. you can nest tables inside each other. Only active nodes are sent to the layout in the Form Builder. structure nodes. 3. on the right of the screen above the context. 1. 58. This has the advantage that these texts do not need to be saved in the form. the top nodes of structures or tables that you have inserted in the context from the interface. 14. 1. For more information.. To update a node together with all of its subnodes (generated and nongenerated nodes). or move generated nodes. Non-generated nodes are. and reduces the need for translations. A node can have active or inactive status. However.. Choose the node that you want to update. For more information about converting older PDF-based print forms. and Status. 59. for example. Description. you can set any nodes that you do not need in your form as inactive. You can change the appearance of structures and tables by adding more data nodes or tables. copy. For an explanation. Activities 57. In this way. These nodes are not flagged with .
for some nodes you can also specify conditions for the form output. 1. Features You can define conditions using logical relationships. Choose Relational Operator to display a screen where you can make a selection of relational operators. It is not entered in quotation marks: FIELDFORNAME. or for whole subhierarchies of the context. you can enter a condition with two operands. You can choose both AND and OR relationships. To insert a line. use the alternative node. 3. 63. 60. 66. A node. Choose Operator to link successive lines with each other. click . This node must allow conditions to be defined. 2. 4. Activities 15. ■ • Conditions Use You can define conditions for individual nodes. This field can contain. the text module name at runtime. 62. is then only processed if the related condition is met. For each line.In many cases. The operand can be a field (variable) or a value. 61. • ■ A dynamic field is the name of a field. you can enter static and dynamic values for the node properties: An example of a static value is a text module. Double-click the node for which you want to define a condition. 65. 6. . It is entered in the format 'TEXTNAME'. the Operator field stays empty. for example. 7. In the first line. The Properties window opens. 64. or all its subnodes. As well as the properties. To select from two alternative subhierarchies in the form output. Prerequisites A node exists for which you want to define conditions. specified in quotation marks. 5. Choose Conditions.
Select an existing node in the context. enter a field name. The system creates a data node under the selected node. . However. • • • • For data nodes that reference the ABAP Dictionary. 1.Inserting Data Use You want to insert elementary data fields ( of the screen. To display the context menu of the node. In the Create Data dialog box. In the context menu of the node. Use the F4 help to display a list of all data fields used in the interface. the system takes the related short text from the ABAP Dictionary. 2. The text chosen here is used in Adobe LiveCycle Designer to display the label of the data field in the layout. you can insert this node in the form. Choose Continue. you can set the data node as active or inactive. The full field name of the node is displayed under Data. 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. click the secondary mouse button. 70. 3. Editing Properties and Conditions • In the window under the context. the system displays the properties of the inserted data node. 67. Result You have created a complete data node. You cannot change this. 68. 4. enter the prerequisites that need to be met before the data node is processed at runtime and displayed in the form. In the layout in the Form Builder. Under Status... Under Conditions. 69. you can select the Field Label. under which you want to create a data node. choose Create → Data. Inserting a Data Node Using the Context Menu 16. .
These have been generated. under which you want to create a structure node. 72. Use the F4 help to display a list of all structures used in the interface. . Choose Continue. 4. In the window under the context. 74. 73. or switch it to active or inactive. 3. enter a structure name. 75. the system displays the properties of the node. 1. click the secondary mouse button.Inserting a Structure Use You want to insert a structure ( two options: ) from the interface on the left of the screen. In the context menu of the node. you can see the individual fields of the structure. 2. You can specify conditions for each data node in the structure. you can insert the structure node in the form. Inserting a Structure Node Using the Context Menu 17. 76. 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. 6. Under Conditions. Result You have created a complete structure node. The node is fully expanded so that you can see the individual fields of the structure. choose Create → Structure. When you expand the node. To display the context menu of the node. enter the prerequisites that need to be met before the structure node is processed at runtime and displayed in the form. Under Status. The system creates a structure node under the selected node. In the Create Structure dialog box. which means they are flagged with the icon. 5. In the layout in the Form Builder. Select an existing node in the context. you can set the structure node as active or inactive. 71.
below.. The system creates a table node under the selected node. To display the context menu of the node. choose Create → Loop. 79. 8. 81. • ○ If required. Inserting a Table Node Using the Context Menu 18. 78. you can set the table node as active or inactive. 2. Under Control Levels. For more information. In the Create Loop dialog box. Under Conditions. When you choose this option. Use the F4 help to display a list of all tables used in the interface. 3. 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. 82. 4. under which you want to create a table/loop node. • ○ Under Status. see the documentation for Smart Forms. specify the assignment type under Output Behavior and also the work area of the table. enter one or more data fields from the table that you want to use to group information in the output. click the secondary mouse button. Choose Enter 5. restrict the table range that you want to read by setting the input fields From Row and To Row. • ○ If you are using a migrated Smart Form as a form. 84. 77.. You can set individual data nodes in the table as Active or Inactive in the context menu. 6. Proceed as described under 5. under Reading Internal Tables. . Only active nodes are sent to the layout in the Form Builder. the . the system displays the properties of this node. 1. 80. In the context menu of the node. In the window under the context. You can also specify conditions for individual data nodes in the table. You can use WHERE conditions to select only parts of the data from the table at runtime. 7.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. The node is fully expanded so that you can see the individual fields of the table. 83. enter the prerequisites that need to be met before the table is processed at runtime and displayed in the form. enter a table name. Select an existing node in the context.
you can set the single record node as active or inactive.. see Reading Rows of Tables. Use the F4 help to display a list of all tables used in the interface. Result You have created a complete table node. 88. 89.. Select an existing node in the context. 2. this system field contains the SY-SUBRC value of the last access. kn = fn result. The system creates a single record node under the selected node. 1. For more information about this statement. When you expand the node... In the context menu of the node. However. • ○ Under Status. 90. the system displays the properties of this node. At runtime. the data is selected according to your settings. Data nodes that are defined as part of a structure within the table cannot be specified as a control level.. In this case. you can insert the table node in the form. you can see the individual fields of the table. .context tree is changed. You can extract a single row (record) of a table in two ways: 19. If multiple records are accessed. 91. The node is fully expanded so that you can see the individual fields of the table. this is only active if you do not set the Already Sorted flag under Properties.. 87. Procedure 20. You enter the row number. In the window under the context. which means they are flagged with the icon. 1. Choose Continue. . 2. choose Create → Single Record. In the Create Single Record dialog box. When you specify a search key. In the layout in the Form Builder. the table row is read by the ABAP statement READ TABLE itab WITH KEY k1 = f1 . the return code SYSUBRC is inserted in the system field SFPSY-SUBRC. . You specify a search key. You can choose between ascending and descending sorting. 5. enter a table name. These have been generated. 86. Inserting a Single Record Node Use You can use the single record node ( ) to extract single data records from internal tables. 85. 3. The grouping is indicated by the selected fields being placed before all other fields of the table. under which you want to create a single record node. 4.
In the layout in Form Builder. For more information. the data is selected according to your settings. enter the row number of the internal table that you want to extract. • Result You have created a complete single record node. To do this. you can see the individual fields of the table. and you want to perform a binary search. 92. You can also use a search key to extract rows from the internal table. Grouping Tables by Data Fields Use You can create control levels to group tables by data fields. You can choose from various text types: ● Text modules . 7.You can set individual data nodes in the table as Active or Inactive in the context menu. The properties and conditions that are displayed refer to the data node. Only active nodes are sent to the layout in Form Builder. select a data node. Procedure You enter the required information in the table node. ○ Under Row. These have been generated and cannot be deleted. define a nested output for a flat internal table. Inserting a Text Use You can use a text node to insert texts in the output of a form. 6. for example. Enter this key under With-Key Conditions. which means they are flagged with the icon. see Inserting a Table or Loop. you can insert the single record node in the form. 93. Note that you cannot enter any information under Row. Under Conditions. When you expand the node. Prerequisites You have created a table node or a loop node. enter the prerequisites that need to be met before the table row is processed at runtime and displayed in the form. In this way. • ○ Select the Binary Search option only if you want to use a search key to display the table row. you can. You can also specify conditions for individual data nodes in the table. At runtime.
(See: Entering Text Module Properties. . 95. the text and its name are not known until the output of the form is created. or Dynamic Text. They are crossclient texts and are linked to the Change and Transport System and translation tools. To display the context menu of the node. enter the required information about the text type. 98. Save and confirm your changes in the next dialog box. choose Create → Text. You can find a list of restrictions under: • • ■ ■ Entering Text Module Properties Entering Include Text Properties Procedure 21. click the secondary mouse button. The system modifies the Properties window according to your selection. 4. Entering Text Module Properties Prerequisites You have created a text node in the context and selected the text type Text Module. 1. under which you want to create a text node.● ● Include texts Dynamic texts Include texts are SAPscript texts that already exist in the system. Under Properties. 3. For dynamic texts. Select an existing node in the context. You can set a text node as Active or Inactive in the context menu. The system creates a text node under the selected node. Prerequisites The text module or include text that you want to insert must exist in the system. In the Properties window under the form context. 6. Entering Include Text Properties) 100. choose Text Module. enter the prerequisites that need to be met before the text node is processed at runtime and displayed in the form. 2. 97. Remember the restrictions that apply when processing forms with inserted texts. Text modules also exist in the system. you create and edit them in transaction SMARTFORMS. Include Text. Only active nodes are sent to the layout in Form Builder. 94. 96. 5. 7. 99. In the context menu of the node. The text module exists in the system. None of these text types are inserted until the form is printed. Under Conditions. The text name is specified by the content of a variable field.
but not SAP icons. 6. 102. 5. enter the name under which the text module is stored in the system. but not for aligning fields within texts SAP characters. description. Choose F4 to see a selection of languages. such as SFSY-DATE Hyperlinks The following are supported with restrictions: 22. ● ● Tabulators. For more information about creating and changing text modules. you can specify a different style. Under Style. 4. 1. Procedure 101. and status.. such as the name. . 3.Restrictions The following components are not supported in text modules and are ignored when the form is processed: ● ● ● ● ● ● Outline paragraphs Paragraph properties: Page protection. Specify the general properties of the text module.. . 106. the form is not printed. Enter the text language in which you want the text module to be inserted. see Maintenance of Text Modules in the Smart Forms documentation. Under Text Name. Set the flag No error if text not available if you still want the form to be printed. 104. next paragraph on same page Character formats: Superscript and subscript. 103. 105. If you do not set this flag. The corresponding text is not inserted until the form is processed. even if the inserted text module does not exist in the system. 2. and an error message appears. Result You have created a text node. Choose F4 to see a selection of all text modules in the system. Set the flag Copy Style from Text Module if you want to keep the style from the text module. bar codes Special characters System fields. for example More information about these restrictions is available in the SAP Notes 894389 and 863893.
Specify the text object. enter the name under which the include text is stored in the system. Under Text Name.Entering Include Text Properties Use You want to display a SAPscript text in the form. 2. If you do not have to use SAPscript texts. next paragraph on same page Character formats: Superscript and subscript. The include text. which has been created with SAPscript Editor. Prerequisites You have created a text node in the context and selected the text type Include Text. Specify the general properties of the include text. but not for aligning fields within texts SAP characters. You use transaction SE75 to define separate text objects with their own text IDs for applications. 3. TEXT indicates a standard SAPscript text. and status. Choose F4 to see a selection of the texts in the system. description. 109. we recommend that you use text modules. bar codes Special characters System icons. but not SAP icons. They are cross-client texts and are linked to Change and Transport System and the translation tools. 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. In this way. such as ULINE Standard icons Hyperlinks Tabulators. The TEXT . exists in the system. you can manage application-specific form texts. Procedure 107. 1. This text type has the same function as the SAPscript command INCLUDE. 108. for example The following are supported with restrictions: More information about these restrictions is available in the SAP Notes 894389 and 863893. such as the name.
This overrides the setting in the style. 111. If you specify a paragraph format in the Standard Paragraph field. If you do not set this flag. Set the flag No error if text not available if you still want the form to be printed. Specify the text ID. In Adobe LiveCycle Designer. For information about the supported image file formats. to be used in the form output. Inserting a Graphic Use Under the graphic node. see the SAPscript Editor documentation. Enter the text language in which you want the include text to be inserted. 7. the system copies the values for Text Object. you bind graphic nodes to an object of the type Image Field. 113. 115. If you leave the Standard Paragraph field empty. The style assigned to the text node contains formatting for standard paragraphs (‘*’). the form is not printed. 6. The usual ID of a standard SAPscript text is ST. see the online help in Adobe LiveCycle Designer under Defining Object Properties ® Image Fields ® About Image Fields. 114. 110. all standard paragraphs in the include text are also formatted with this paragraph format. you can set a paragraph format for the first paragraph of the include text. 9. even if the inserted include text does not exist in the system. you can insert graphics. 4. The corresponding text is not inserted until the form is processed. . Text ID. 8. Specify the style that you want to use for the include text. For more information about creating and editing SAPscript texts. Enter constant values in quotation marks. 112. Result You have created a text node with the text type Include Text. To do this. such as a company logo.text object with the text ID ST is used for general standard texts that you create with the standard text editor (transaction SO10). and an error message appears. and Text Language already stored for this text in the SAP system. you either specify the URL address of an image or the name of a field in which the image content is specified in binary code at runtime. Under First Paragraph. 5. If specified. you override the format of all standard paragraphs in the include text with this format. You use the graphic node to specify where the content of the image comes from at runtime.
under which you want to create a graphic node. You can insert this node in the layout in Form Builder. choose Create → Graphic. You can choose from the following graphic types: • ○ Graphic Reference Choose this option if you want to insert a graphic from its address (URL). The system creates a graphic node under the selected node. 117. The entries you need to make depend on whether you chose Graphic Reference or Graphic Content in the last step. This field contains all image information at runtime. enter the URL of the graphic. You must be able to access the graphic at the specified URL. Under Conditions. • Result You have created a complete graphic node. 2. 1. 5. 118. ○ Graphic Content Choose this option if you want to specify graphic content using a field. enter a field name from the interface. • 119. 4. 120. 116. Enter the required data about the graphic in the Properties window under the form context. Procedure 23. enter the prerequisites that need to be met before the graphic node is processed at runtime and displayed in the form. In the context menu of the node. The field must have the type STRING (graphical data is Base64-coded) or XSTRING (for binarycoded graphical data). . Graphics stored in MIME Repository cannot be accessed through a URL. • ○ If you have chosen Graphic Reference as your graphic type. This means that you may have to configure appropriate access rights for Adobe Document Services (ADS). To use these graphics. The URL can point to a Web server or to a file system. or whether the graphic is embedded in the form. For more information.Prerequisites Any graphics that you want to display with the Graphic Content option must be stored in MIME Repository. 3.. you must do the following: • ■ In Field. The graphics must be in MIME Repository. see Migrating BDS Graphics into MIME Repository. • ■ Enter a valid MIME type. Select an existing node in the context. For more information about graphics used in Smart Forms. see the online help in Adobe Designer. . In Adobe LiveCycle Designer. choose Graphic Content.. you can choose whether the system gets the graphic at runtime. such as ’image/bmp’. ○ If you have specified Graphic Content as your graphic type.
122.gif’ Delimiter If you have inserted the graphic node in Adobe LiveCycle Designer. which is why no URL appears in Adobe LiveCycle Designer.gif 2. Select an existing node in the context. At runtime. Prerequisites Your application must manage addresses in the BAS. under which you want to create an address node.com/images/logo. . In the context menu of the node. you must insert your addresses using text nodesor insert them directly in the layoutas text.anycompany.com/images/logo. Specifying a URL with Fixed Values Graphic URL ’http://www. Procedure 24.anycompany. The addresses are stored in a database.Example You want to insert a graphic from the Website of the fictitious company AnyCompany in your form. it contains the name of the graphic that you want to load.anycompany.gif’ Delimiter / GRAPHIC_NAME is a field from the interface that is entered as an import parameter. 121. You have chosen Graphic Reference as your graphic type. where they are identified by numbers. 1. otherwise. 1. Specifying the URL by Using Fields Graphic URL ‘http://www. the following URL is entered for the graphic object: http://www.com/images’ GRAPHIC_NAME ’. Inserting an Address Use Many applications use the Business Address Services (BAS) to manage addresses. The example shows you two ways of specifying the URL. The graphic is unknown when the layout is created. 2. choose Create → Address.
In the context menu of the TRUE and FALSE nodes. 127. Enter the required data about the address in the Properties window under the form context. 4. The first successor node (TRUE) is processed only if the condition is met. click the secondary mouse button. Procedure 125. enter the prerequisites that need to be met before the address node is processed at runtime and displayed in the form. You can use Drag&Drop to assign any existing node as a subnode. 4. with the two subnodes TRUE and FALSE. 124. 3. 123. . Select an existing node in the context. The system creates an address node under the selected node. the second successor node (FALSE) is processed. To display the context menu of the node. 3. Enter the required data in the Properties window under the form context. Double-click the subnodes to enter their properties as well. choose Create → … to create nodes for the alternative options. The window in which you define the alternative conditions is the same as the window used for defining the conditions for nodes. 128.To display the context menu of the node. you use the alternative node. One difference here is that you need to specify the sending country under Additional Specifications. specify the conditions for a node to be processed. Result You have created an alternative node. choose Create → Alternative. 1. 126. The system creates an alternative node under the selected node. Under Alternative Conditions. otherwise. under which you want to create an alternative node. Under Conditions. The information required for the address node is similar to that in Smart Forms. This node has two successors. You want one of two nodes (and its subnodes) to be processed. See also: Inserting Addresses (from the Smart Forms documentation) Inserting an Alternative Use You want to present an alternative option in a form. In the context menu of the node. To do this. 2. click the secondary mouse button.
In the Properties window under the form context. 131. . The system creates a folder node under the selected node. you can organize nodes under folder nodes. To make the hierarchy easier to understand. Here. You then use conditions to display just one of these nodes at runtime. 130.. You can use Drag&Drop to assign any existing node as a subnode. Select an existing node in the context. 2.Inserting a Folder Use The more detailed a form becomes. 129. Procedure 25. click the secondary mouse button. you create a text node with a different reminder text for each level of reminder. 5. 1. choose Create → Folder. To display the context menu of the node. depending on which deadline has been missed. under which you want to create a folder node. The following general rules apply to system fields: • You can display the value of any system field in the form. you can use the system field SFPSY-DATE to display today’s date on your form. it is a good idea to group these text nodes in a specific folder. choose Create → . Migrated forms use the system fields from Smart Forms. In the context menu of the node. For example. System Fields The interface of a form contains the field string SFPSY. This string contains a range of system fields that the system replaces with values when a form is processed. In the context menu of the folder node. you can enter a name for the folder node. The field content is either taken from the SAP system or is created while the form is being processed. You want to begin a reminder with a different text.. the more difficult it is to get a clear overview of the hierarchy of nodes. 133. 132. Under Conditions. 3. 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. Result You have created a folder node. 4. to create subnodes. To do this.
• • You cannot assign a value to a system field. current date of the application server Date and time. current time of the application server Logon name for user in the SAP system If single record nodes are used. Reloading an Interface Use You have already started to edit the form context and you have made changes to the interface. in another session. If the field has a type from the ABAP Dictionary. with the text Reload Interface. 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. you can double-click the type name to go to its entry in the ABAP Dictionary. in conditions) for any fields. icon. you can query system fields (for example. for example. contains content of the SY-SUBRC field in the ABAP statement READ TABLE Field List Use The field list shows you detailed information about the individual fields (such as structure and tables) of the form interface. Activities To reload 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. System Fields Field Name SFPSY-DATE SFPSY-TIME SFPSY-USERNAME SFPSY-SUBRC Meaning Date and time. In general. choose the screen above the interface. on the left of the . It is displayed below the interface.
Activities There are two ways of editing the layout: • • You choose the Layout tab page.Layout in the Form Builder Use When you create a layout in the Form Builder. Otherwise runtime errors can occur. Layout Type You use the layout type to define the runtime environment where the form is used. you first have to close the tool. and define the order of the pages. Layout Types Layout Type Unknown layout type Meaning The form has not yet been classified. Adobe LiveCycle Designer starts in fullscreen mode. choose the Properties tab page in Form Builder: Change Form. an integrated graphical software tool for creating forms. you can use a wide range of functions to design your form. . Adobe LiveCycle Designer starts on this tab. This includes the positioning of the data and the design of tables. you choose Layout (quick info Fullscreen Layout). For more information about editing layouts. The layout type you define must match the script code in the layout. In the application toolbar. You still have to classify the form. To access the menu bar and application toolbar. Integration The Layout function in the Form Builder calls Adobe LiveCycle Designer. You can also specify background pictures for the form. This is the case if you are creating a new form or editing a form created with an older version of SAP NetWeaver. To do this. see the online help in Adobe LiveCycle Designer. 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. Features Under Layout in the Form Builder. you define the graphical design of the PDF form. Prerequisites You have created a form context or loaded an XML schema-based interface. You can use Drag&Drop to insert data fields from the Data View section in the page layout. To select a layout type.
Also included are some objects developed specially for the SAP development environment.Standard layout Use this layout type for PDF-based print forms. see the Designer’s online help under Working with Objects → Using Custom Objects → Custom Objects for the SAP Environment. Note that you can make this setting only if the layout type of your form was previously Unknown. ActiveX must be enabled in the browser. Date Objects in Adobe LiveCycle Designer Definition Under Library ® Form Builder. The system enters this value automatically when you migrate old forms to ZCI. or for interactive forms used in an offline scenario and not integrated in a Web Dynpro environment at runtime. you cannot choose xACF. however. The Active Components Framework technology is used to integrate the form at runtime in Web Dynpro applications. For more information. see Creating Forms for Integration with Web Dynpro and ZCI and Check and Update Functions for Zero Client Installation (ZCI). You specify this setting when you create new forms. Objects in Adobe LiveCycle Designer Definition Adobe LiveCycle Designer provides you with objects that you can use to create your form. You can still. Adobe LiveCycle Designer provides you with the following date objects: • • Localized Full Date Localized Long Date . If your form is already set to Standard or ZCI. xACF layout ZCI layout Zero Client Installation (ZCI) technology is used to integrate the form at runtime in Web Dynpro applications. For more detailed information. These objects contain special functions and can be found in the Designer’s library. access your old form using version management.
* 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.] * US format FP_DOCPARAMS-LANGU = 'EN'. * German format * FP_DOCPARAMS-LANGU = 'D'. . 2004 Monday.• • Localized Medium Date Localized Short Date Use You use these date objects to format dates locally when you call the form.05. DATA FP_DOCPARAMS TYPE SFPDOCPARAMS.. FP_DOCPARAMS-COUNTRY = 'US'.2004 17.2004 17. The dates are formatted according to the parameter values entered for language and country in the application program. Example You want to display the date objects on the form in US format or in German format.04 For more information. Mai 2004 17. Mai 2004 17.05.05. 2004 May 17. 2004 May 17. May 17.05. 2004 May 17. [. see Example: Calling Forms in the Application Program. 17.2004 Montag. * FP_DOCPARAMS-COUNTRY = 'DE'.. These values are sent to the generated function module that contains the form description. 2004 5/17/04 German Date 17. FormCalc Language Reference Your local Adobe Designer installation includes a FormCalc language reference in a PDF file that you can print out.
you must have installed Adobe Reader or Adobe Acrobat (both with Version 7. The system also checks whether the assigned interface is active. it checks to see whether all necessary field properties have been entered. These checks test the data links between the context and the layout. 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. You can run additional checks in the layout of the Form Builder.pdf You enter EN for <country> if you have an English installation.1\Documentation\<country>\FormCalc. For example. . Form preview with and without inserted data The form is displayed in PDF format in Adobe Reader or Adobe Acrobat. You can run checks on the form and test it in the print preview.0 or later) on your front end. 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. and also whether all fields in the layout have a data link to the context. Links to the interface can be lost when the interface is modified. which then inserts this data in a print preview of the form. Test the form The system generates a function module that contains the form description. the FormCalc language reference is in the following location: C:\Program Files\Adobe\Designer 7. Check the form The system runs a syntax check in the context. You can send test data to this function module. Checking and Testing a PDF-Based Print Form Use To guarantee that your form is free from errors. you can use a range of check options. Activation checks The system checks the form each time it is activated. for example. and that its layout meets your requirements. The system also runs automatic checks when you activate the form. DE if you have a German installation.If you have installed Adobe Designer on your C: drive. Check the layout The system checks whether all fields from the context have been inserted in the layout. Prerequisites To check the layout and display the preview.
.. 4.Activities Checking an Interface 26. . 141.. 135. These messages are just warnings. . 147. You are in the interface of the Form Builder. Choose Test (F8) in the application toolbar. 146. 2. Print Preview with Inserted Data or Form 31. The system starts Adobe Acrobat or Adobe Reader and displays the PDF form with your data inserted.. . 1. Choose Check (Ctrl+F2) in the application toolbar.. Checking a Form 27. The screen Test Function Module: Initial Screen appears. Checking a Layout 29. However. 149. . 137. Enter your data and choose Print Preview. . 2. For more information. 142. 4. 1. You are in the context in the Form Builder or in the layout in the Form Builder. 140. You are in the layout in the Form Builder. 144. 6. 2. activate the function Saving Runtime Information and a Generated PDF Locally and repeat the test. The system checks the interface and displays any errors or warnings in a list. 5. 3.. 28. The printer settings dialog box appears. 148. 136. Choose Layout in the application toolbar. this function does not insert any data. or if errors occur. 3. 3. Choose Check (Ctrl+F2) in the application toolbar. 30. You cannot navigate to the fields from this list. 3. The system checks the interface and displays any errors or warnings in a list. you can still activate the layout later. 2. 145. If the form does not appear how you want it to. Double-click a message to locate the error in the interface. The system checks the layout and displays any errors in a list.. 134. Double-click a message to locate the error in the context. .. Enter the test data for the import parameters and choose Execute. 138. 1.. . You are in the context in the Form Builder or in the layout in the Form Builder. 143. see the online help in Adobe LiveCycle Designer. 1. 139.. 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.
Calling Forms in an Application Program
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)
You have created and activated a PDF-based form. You have experience of programming with ABAP and handling function modules.
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.
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
For more information. see Form Output. TY_BOOKINGS. where they must already be defined. SFPDOCPARAMS. TY_CONNECTIONS. 1. 2. TYPE TYPE TYPE TYPE TYPE TYPE SCUSTOM. Example: Calling Forms in an Application Program The following is a program excerpt showing how the function modules are called. FP_JOB_CLOSE closes the spool job. 4. Generated function module of the form 158. SFPOUTPUTPARAMS. the parameters CUSTOMER.generated pages in the form. and CONNECTIONS are sent to the form interface. 3. 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. . . RS38L_FNAM. 32. In this example. 155.. FP_FUNCTION_MODULE_NAME gets the form name. 156. FP_JOB_OPEN opens the spool job. BOOKINGS. 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.. 157.
<error handling> ENDIF. = = = = = = 1 = 2 FP_DOCPARAMS CUSTOMER BOOKINGS CONNECTIONS = 3. <error handling> ENDIF. . IF SY-SUBRC <> 0. <error handling> ENDIF. * 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. fp_docparams-country = 'US'. * Close the spool job CALL FUNCTION 'FP_JOB_CLOSE' * IMPORTING * E_RESULT = EXCEPTIONS USAGE_ERROR = 1 SYSTEM_ERROR = 2 INTERNAL_ERROR = 3 OTHERS = 4. <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. IF SY-SUBRC <> 0. * Language and country setting (here US as an example) fp_docparams-langu = 'E'.
This enables you to optimize the way the data is collected in the application program. or variables. Customers who want to change the way the data is collected. and then use this data in the form under Global Data. structures. These routines usually consist of statements that select data from the database. you can define a form interface to send this data to a form. and created and activated the form context. Result The data is saved to internal tables in the application program. and do not want to modify the application program. which you then bundle and send to the form. You save the data in internal tables. but not all fields of the interface need to be used in every form. 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. . Prerequisites You have created a PDF-based form with an interface. Getting the Used Interface Fields Use You can use the same interface for multiple forms. you must separate the selection of the data from the processing of the form. You use the function module FP_FIELD_LIST to get all fields of the interface that are used in 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. Now that you know all the types of tables that are used.
address nodes. created by the system when forms are generated ● PDF with additional information Once a setting is chosen. using a function module. • • You specify the name of the form as an import parameter. 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. if any are defined. Activities You include the function module in the application program that collects the data and calls the form. You can save files that contain the following information to your local client: ● Runtime information (also known as trace information). You can also see field names under Where Conditions for table nodes. You can also see the used field names in the form context by displaying the properties and conditions for each node. This includes fields referenced by the data node and fields that are used in conditions. • All fields from the interface that are used in the ABAP code (initialization) of the interface. For more information.Integration The function module is included 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. see Troubleshooting. 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 get a table of the used fields (with the type TFPFIELDS) that can then be used for data collection in the application program. and graphic nodes. text nodes. the system saves this information for all forms that are generated while the user is logged on. . Prerequisites You have debugging authorization in the system where you want to use this function. alternatives.
see the section Execution in the problem analysis scenario Adobe Rendering Error (in English only). proceed as follows: • • ○ Under Runtime Information → Trace Level. 002. Choose Utilities → Settings. ○ Select PDF with Additional Information and specify a file name. You can use the troubleshooting options to find out the cause of the error. Attached to either of these files are various additional files including. ● To activate the function PDF with Additional Information. select the option Very Detailed Trace. ● To specify how the runtime information is saved locally. If you do not specify an extension for the file name. Features You are provided with various function modules for troubleshooting purposes. and the runtime information mentioned above. or FPRUNX004 when the generated function module is called. you can navigate to your system to choose a file. A dialog box appears. For a detailed description of the information provided by the system. the system displays the runtime error FPRUNX001. for example. in addition to the existing numbering. FPRUNX002. an error file. However. When you choose F4 for the file name.. sent to the form at runtime. application data (in XML format). ● Saving the PDF with additional information The PDF with additional information consists of the generated PDF form or. This information is a subset of the trace information stored by the J2EE Engine used as a host system for Adobe document services. the information is saved to separate files. Troubleshooting for Runtime Errors FPRUNX001. You can use these function modules to extract the following information: . The detailed trace information is located in the file defaultTrace. . Activities 33. ● Saving runtime information and a PDF with additional information for multiple forms If multiple forms are called in the application program. and 004 Use You want to display a PDF-based print form..Features ● Saving runtime information The system saves the trace information returned by Adobe document services to your local client. in the event of errors. choose an option under Trace Level and enter the name of the file. An extra sequential number is added to each file. the system saves the runtime information automatically with the extension TXT.trc on the J2EE Engine.
• • 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... To activate the trace output. You can choose one of the following options: 35. FP_GET_LAST_ADS_ERRSTR gives you a text that indicates the cause of the error. Troubleshooting Texts 1. ● ● Printer Archiving In this case. the form is forwarded to ArchiveLink. ArchiveLink is a communication interface that manages archiving systems in the SAP system. 2. 2. 3. This note gives you precise and up-to-date information about how to proceed when troubleshooting. 1. 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. Read the SAP Note 717568 on the SAP Service Marketplace at service. ... Form Output Purpose You can send a PDF-based form to various types of output media. . call the function modules in your application program. . Trace 34. for example. Call the function module FP_GET_LAST_ADS_TRACE after the generated function module. FP_GET_LAST_ADS_TRACE gives you the trace.com/notes. Call the function module FP_GET_LAST_ADS_ERRSTR after the generated function module. 2. This interface allows you to link the form with application data.sap.
see the ABAP Dictionary (transaction SE11). these fields are sent to the function module FP_JOB_OPEN as parameters (IE_OUTPUTPARAMS). see Controlling the Spool Dialog. . The SAP system must be configured to be compatible with each output medium. For example. this is what happens when you use the initial values of the structure when you call FP_JOB_OPEN. you see the spool dialog. from where it can be sent as a fax or email. ● Fax and e-mail If you send the form back to the application program as a PDF. For the individual fields of the structure SFPOUTPUTPARAMS and their meaning. Prerequisites The form is sent to the output media through interfaces. specify the archiving mode in the ARCMODE field of the structure mentioned above. When the form is called in the application program. The system forwards the form to ArchiveLink.For more information. see (BC-CCM-PRN). • • ○ ○ Archive only: SFPOUTPUTPARAMS-ARCMODE = ’2’ Print and archive: SFPOUTPUTPARAMS-ARCMODE = ’3’ You use the NODIALOG field to display the output of the dialog. Here. see Spool Processing and Controlling the Spool Dialog. 2. For general information about printing and printer setups. For more information. Output to Archive SAP Printing Guide 159. the application program can forward it to Business Communication Services. you specify an archiving mode for the document: • ○ Archive only • ○ Print and archive If you create the form output without a dialog. see Example: Calling Forms in the Application Program. Process Flow To control the output of the form. For more information.. To see how function modules are called. you use various fields in a structure with the type SFPOUTPUTPARAMS. 1. If you create the form output with a dialog. you must configure a PCL-compatible printer. You can modify the print parameters and the spool dialog parameters by setting the fields accordingly. You write at least one entry to the table with archive indexes (SFPDOCPARAMS-DARATAB). 3. Output to Printer Forms are sent to a printer by default. if you want to print your PDF form. see the ArchiveLink documentation under Storing Outgoing Documents.
. enter the form name. if a font does not support all characters in the target language. the system replaces these characters automatically with suitable replacement fonts. . The system sends the generated PDF form back to the application program.. you require administrator authorization. In this case. The fonts you want to use must be installed for Adobe document services. enter the name of the form. edit the table FPFONTREPL in the Data Browser (transaction SE16). 2. Prerequisites • • To edit the table FPFONTREPL. When you process forms in another language (referred to here as the target language). In your application program. 1. where it can then be forwarded to the interface of the Business Communication Services. set the field SFPOUTPUTPARAMS-GETPDF. all texts are translated from the interface. see Adobe Document Services − Configuration. Under Name of Form Object.. Under Language. When you use the appropriate tools to translate forms.Output as Fax or E-Mail 36. To do this. you enter a wildcard character * in the table under Name of Form Object. the context. . 2. 1. Integration You can specify replacement fonts for forms that have been created and translated in ABAP systems. Font Replacement Use PDF-based forms are created in an original language. This function also gives you the option of setting a default font or fonts to be used as a replacement in forms. and the layout. 160. You make the required settings in the table FPFONTREPL. You can do this in the following ways: • You can define replacement fonts for specific forms. Activities To define replacement fonts.. the fonts used in the layout are retained. enter the target language in which the form and the replacement font or fonts are displayed. 37. For more information. The settings are cross-client settings. However. . • You can define replacement fonts for all forms in the system.
You can use this spool dialog to control the output. Example For the Japanese version of the form FP_name. 3. enter the font that you want to replace the source font with. See also: . Features You can use parameters in the structure SFPOUTPUTPARAMS to make print and spool dialog settings. 4. Under Target Font. To do this. see the ABAP Dictionary (transaction SE11). specify the font in the original form. the system forwards the generated PDF forms to the spool processing functions and sends parameters to the spool dialog. Under Source Font.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. by doing the following. you send these parameters (IE_OUTPUTPARAMS) to the function module FP_JOB_OPEN. 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. When you call the form. for example: • • Opening a new spool job Specifying the retention period of a job in the spool Integration The functions related to these settings are no longer part of the process of creating PDFbased forms. you want to use the character set MS MINCHO instead of Times New Roman.
If a form is migrated from a Smart Form. the spool dialog is controlled by different parameters. you want to adjust the spool dialog to your requirements when printing a PDF-based form. 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 . or hide the spool dialog completely. See also: Controlling the Spool Dialog in the Smart Forms documentation Prerequisites The DEVICE parameter of the structure SFPOUTPUTPARAMS must have the value ’PRINTER’.Controlling the Spool Dialog Printing PDF-Based Forms in the SAP Printing Guide Displaying and Printing PDF-Based Forms in the SAP Printing Guide Controlling the Spool Dialog Use In the application program. or if it is compatible with Smart Forms.
XDC files are shipped for the following SAP device types: POST2 (generic device type that can be used for every PostScript printer). Result You have placed the selected forms in a print request. The function module FP_JOB_CLOSE is the last function module to be called. To set a parameter with the data type CHAR(1). 2. 4. Adobe Document Services require this file to create the print files. 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.Activities In the application program. Procedure 38. When you call the form in the application program. Determine the names of the generated function modules with FP_FUNCTION_MODULE_NAME. The XDC scenarios provide you with examples of how you can make specific settings for your printer. specify the value ’X’ (for example. . AZPL203. first call the function module FP_JOB_OPEN. NODIALOG = ’X’. and AZPL300. You do not usually need to make any modifications to these XDC files to use them for successful printing. HPLJ4. PDF documents can only be printed on printers of SAP device types for which there is an XDC file in the system. call the function module FP_JOB_OPEN and specify the required parameters. 1. Then call the generated function module(s) that you want to use in the output. to suppress the user dialog). 3. .. See also: Calling Forms in an Application Program XDC Scenarios for Print Control Use An XDC file is a printer description in XML format. HP9500.
See also: SAP Printing Guide (BC-CCM-PRN). Functions The documentation about the XDC scenarios describes the entries in the XDC file. By default. external applications outside the SAP system can access and process the contents of forms. see SAP Note 766410 on SAP Service Marketplace at service. The XFP output contains all form data in XML format. we recommend that you set up an XFP output device. . For up-to-date information about downloading this documentation. at least one printer of device type XFP must be set up in the system.sap.Integration You can edit XDC files in a text editor and manage them in the SAP system. but does not contain any layout information about the form. In spool administration. For more information. Software partners can receive a certificate from SAP for products that access the XFP interface. see the Software Partner pages at http://www. this output device is used as a virtual device for connecting to the external application.com/spp. 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). Prerequisites Since XFP uses spool processing.sap. see SAP Service Marketplace at Adobe → Media Library → Documentation. 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. Integration XFP output corresponds to XSF output for Smart Forms and RDI output for SAPscript. Output in XFP Format Use Using the XML interface for PDF-based forms (XFP).com/notes.
Recommendations for Calling Forms and Form Output ● When you create forms for mass printing. This means the form context is already evaluated. under Creating Forms for Optimal Performance. which determines all fields used in the interface. Arial. To support you in your work. but the form context has not been evaluated. together with all its conditions. design the data retrieval process in the application program and interface in accordance with your individual requirements. ● If possible. 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. use the function module FP_FIELD_LIST. ● Bundle print forms. ● Deactivate any context nodes that you do not need. use the Form Caching function in the Designer. Unless specified otherwise. even if the Designer supports others: Courier. ● Minimize the amount of communication that takes place with the server in interactive forms. . see the online help for the Designer. • XML data stream without context evaluation The data stream contains the data from the application program. These character sets do not need to be embedded in the form. ● Keep scripting to a minimum. Performance Aspects The following information is targeted mainly at developers. ● For a detailed description of how to improve performance. ● Structure the form context in accordance with the logical flow of data. Recommendations for Adobe LiveCycle Designer ● For interactive forms. Recommendations for Form Builder ● For each business scenario. which improves performance. For more information. these recommendations apply both to interactive forms in Web Dynpro and to PDF-based print forms. design an individual form that uses its own data retrieval methods. since scripting in a form can have an effect on performance. Do not implement the condition-driven output of multiple forms from the same form object. use only the following character sets. Only use those interactive functions (such as dynamic value help that sends queries to the server) that are strictly necessary.Features The XFP output is activated at runtime by the calling application program. who can use it to achieve an optimal level of runtime performance when using Interactive Forms based on Adobe software. Times New Roman. Place the context nodes used at the top of the form at the initial position in the context tree. see the online help of the Designer.
● Cache forms that you want to process with Adobe document services. Performance Analysis You can obtain precise details about the performance of Adobe document services. it gives you detailed information about the form data and runtime information specified by Adobe document services. . Communication Errors. 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. display. For more information. and print forms. When you call the form. see the description under Problem Analysis Scenarios for Adobe Document Services for detailed troubleshooting information. and 004 You use this function module to find out the causes of any errors you encounter when displaying forms. No Form Output If you encounter any connection errors or configuration errors when you use Adobe document services. Handling Errors and Problems Use Interactive Forms based on Adobe software provide you with comprehensive support for detecting and resolving errors and problems when you create. 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. 002. see Adobe Performance Analysis (in English only).
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. You assign a package to an interface or form when you create it. Original Language When you create a PDF-based form. The Transport Organizer distributes the interfaces and forms to other systems. Translating Texts PDF-based forms are integrated in the same translation process as other development objects. copy the standard form. the system specifies the logon language as the original language.Delivery and Translation Transport Object The interface and form (context and layout) of a PDF-based form are separate development objects. 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. see the documentation on transaction SE63 under Translating PDF-Based Forms . and then link it to the application. ● 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. (The system does not log any modifications to the standard form. this means that the SFPF and SFPI transport objects are recognized by the translation tools (transaction SE63) and are included in the relevant worklists. texts are translated in a splitscreen editor that displays the texts in plain text format.) In this way. You create the form and all its language-specific parts (such as texts and meanings) in the original language. . Local objects are not included in this process. If you want to translate older forms in this way. For more information about translation. An entry is created in the TADIR (object directory) table for each interface and each form. Standard Forms Different applications in the SAP system use different standard PDF forms. make your changes to this copy only. Cross-Client Objects The interfaces and forms for PDF-based forms are cross-client objects. and then save it again. For the procedure for editing a form in Adobe LiveCycle Designer. you must first display the layout in edit mode. see Layout in the Form Builder. your customer-specific changes are not lost when an updated version of the standard form is imported in an upgrade. If you want to adapt these forms to your own requirements.
Business Address . See also: Creating Text Modules Business Address Services Creating Text Modules Use You can insert text modules in a PDF form as text nodes. For more information on inserting a text module. This information does not always apply to PDF-based forms.Tools Associated with Form Development Use When you develop forms. For more information about address management. you will also need to make use of functions and components that are not included in the development environment for PDF-based forms. see the following: Inserting a Text You create and edit text modules in Smart Forms (transaction SMARTFORMS). 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. The following gives you an overview of these tools and links to additional information. 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. For more information. You use the addresses managed in the Business Address Services (BAS). Business Address Services Use You can insert an address node in a PDF-based form. For more information.
see the mySAP ERP documentation under HCM Processes and Forms and Internal Service Request (ISR). ● To access the version management functions. Activities Under Form Builder: Entry Point. See also: Migrating Smart Forms in the Smart Forms documentation Interactive Forms There are several ways of creating an interactive form. Management. • ○ For general information about using forms. and you call it there. ● To save a version of the form or interface in the version management database. . Manager Self-Services) are developed in ABAP Workbench (transaction SFP) and implemented in the Web Dynpro for Java runtime environment.Version Management Use The PDF-based forms solution is integrated with version management tools. enter a form or interface. choose Utilities → Versions → Generate Version. You can save different versions of both forms and interfaces. You use one of the following development environments. Integration This function is integrated into the Smart Forms transaction. 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. 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.
Note that you need to program some steps manually when you use ABAP Workbench. see SAP Note 750784. For more information. 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. the context structure. including information about constructing the view. see Creating Forms for Integration with Web Dynpro and ZCI. For more information.• ● ○ For information about creating forms in Form Builder. however. Transaction SFP. generate a PDF when you call a form. see Reader Rights Credential in the Adobe Document Services Configuration Guide. Interactive Forms in Web Dynpro for ABAP You develop interactive forms as part of a Web Dynpro application in ABAP Workbench. Reader Rights are configured as part of the installation and configuration process of Adobe Document Services. • Web Dynpro InteractiveForm API − IWDInteractiveForm . You can. these steps run automatically in the environments listed above. All of these options require Reader Rights to be granted before you can use interactive forms in Adobe Reader. ABAP Workbench. In certain circumstances. and data bindings. and use certain parameters to control which input is allowed. A user in Adobe Reader cannot enter and save data in an interactive form until these rights are granted. This development environment is intended mainly for creating print forms. interactive forms require licenses. 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.
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. 2. They can be used (from SAP NetWeaver SPS 8) at runtime in Web Dynpro for Java based on Zero Client Installation (ZCI).. which you insert when you create new forms in Form Builder. Choose Utilities → Insert Web Dynpro Script. 5. Select ZCI Layout in the Layout Type field under Properties. To enable this. For more information. . These include interactive forms in the ISR Framework. This starts Adobe LiveCycle Designer in SAPGUI. the forms must contain special scripting. 165... Create a form. You use Adobe LiveCycle Designer 7. You use SAPGUI Release 6. If you want to use Web Dynpro-specific objects in the design of your form layout. see Check and Update Functions for Zero Client Installation (ZCI). 3. 164. use the Adobe Designer library Web Dynpro Native. . such as forms for Business Package Manager Self-Service.40 Support Package Level 20 or higher (see SAP Note 940637). 162. 4. You can use transaction SFP_ZCI_UPDATE to make any interactive forms you created with an older version of SAP NetWeaver ZCI-compliant.1 (see SAP Note 962763). 1. 40.Interface element in View Designer • Adobe Library Documentation about specific objects in Adobe LiveCycle Designer. Procedure 39. The system inserts scripting into the form layout in Adobe LiveCycle Designer. Prerequisites ● ● ● You use SAP NetWeaver 2004s SPS 8 or higher. You can see the scripting in the node (Variables)->ContainerFoundation_JS under Hierarchy in Adobe LiveCycle Designer. 163.. Switch to the Layout tab page. . 161.
. 41. We therefore recommend that you use the transaction SFP_ZCI_UPDATE. . Integration This transaction calls the report FP_CHK_UPDATE especially for ZCI. Activities 166.Check and Update Functions for Zero Client Installation (ZCI) Use You use transaction SFP_ZCI_UPDATE to check forms and update them to ZCI. 1. Any forms that you want to check or update have to be active. 2. and switches the layout type of the migrated forms to ZCI Layout. For more information. This transaction calls this report with the required objects. The same prerequisites apply as described in Check and Update Functions with the Report FP_CHK_UPDATE. see SAP Authorization Concept. For more information. you require a role that is assigned to authorization object S_FP_CHK. Features This transaction calls the report FP_CHK_UPDATE especially for checking and updating forms to ZCI. Proceed as described in the documentation for the report FP_CHK_UPDATE. Only those objects used to migrate forms for Zero Client Installation (ZCI) are currently available. Note that you do not need to perform step 7 to select the objects.. Various objects can be selected for both the check function and the update function. Prerequisites ● ● To be able to use the update function. It selects the required check and update objects automatically. Call transaction SFP_ZCI_UPDATE. Prerequisites ● ● ● If you want to update forms from ISR Framework to ZCI. see SAP Note 956074. 167. You can use this transaction to update only those forms that are not in editing. runs the report for them. you must first run the report FP_CHK_UPDATE with the ISR object.. You created a layout previously with the integrated Adobe LiveCycle Designer tool. 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. and update it if necessary.
. read SAP Note 956074. The default shown by the system is ADS. You can also select forms in the Multiple Selectiondialog box. . You can also copy form names from a text file or the buffer. 4. Choose Execute (F8). Detailed results of the check or update are shown in a log. you must know the name of the appropriate RFC connection to ADS. Enter the name or names of the forms under Form(s). You can choose one of the following options: ● ● Check form layouts This only checks the forms and does not modify them. The system determines the number of forms on which the function is used and displays it in the status bar. Before it changes a form. specify the RFC connection to Adobe Document Services. Activities 42. You can select forms by attributes such as Name. You can determine the scope of the check or update by selecting appropriate objects. 1. by inserting scripting. Under ADS Connection. Created By. If you want to migrate forms for ZCI.● ● ● Since Adobe Document Services (ADS) are called for this function. Select at least one object to be checked or updated from the list of available check and update objects. The link to Change and Transport System guarantees that updated forms are transported further in your landscape. 5.. Changed By. The system also shows you a list of inactive forms that cannot be used with this function (if available). 2. Features This function allows you to check and update one or more forms in a batch process. Run report FP_CHK_REPORT in transaction SA38. or Changed On in a dialog box. . 6. Update form layouts This checks the forms and updates them if necessary. Under Activity. specify whether you want the system to run a check or an update. the system creates a version of it automatically and saves it to version management. A dialog box tells you if no check or update objects are available. 3. This guarantees that you always have access to a backup copy of the original form. The check and update objects must be on the ADS server. 7.
Integration To fully understand how to use the API. you must read this description together with the XFA specification. This specification contains explanations of all elements and attributes. This prompt does not appear for forms or packages created as local objects. You can generate all subsequent XFA elements by using a “create” method of the factory method to instantiate the corresponding object. and to send an object to the VALUE parameter that represents the attribute (and the new element). 9. and may take some time depending on the number of forms selected. you can call the method GET_FACTORY( ) to create a factory object. The API is based on Adobe XFA Version 2.You must read SAP Note 956074 before you select an object if you want to run an update before migrating forms for ZCI. These logs are saved in the application log.2. where you can display and analyze them later. This enables you to implement the programdriven generation of form templates.html. Each interface corresponds to precisely one tag in the XFA specification. For any forms assigned to a package. The check or update runs. You can see the results in a log.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. . Adobe Designer itself offers a much wider range of functions. without using Adobe Designer. This guarantees that your updates are transported. as well as suggestions for the hierarchical structure of the elements. Program-Driven Generation of Form Templates Use SAP provides an API (application programming interface) that you can use to generate a form template. For this object. the system prompts you to enter the appropriate transport request for each transport layer. It offers only a selection of the XML tags and attributes from the XFA specification. This API generates an XFA (XML Forms Architecture) document that can be displayed in Adobe LiveCycle Designer. we recommend that you restrict program-driven generation to simple form templates only. Activities You can use all interfaces from the package SAXFT. 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. 8.adobe. To access the Adobe XFA specification. For this reason. ● You use “set” methods to set attributes that are themselves elements. go to the following Internet address: http://partners.
For a detailed description of how to improve performance. Y. Performance Aspects The following information is targeted mainly at developers. Recommendations for Form Builder ● For each business scenario. Example For an example implementation. This program generates a template that includes the following: header and footer. . and a pushbutton. see the program RSXFT_XFT_API_DEMOII. design an individual form that uses its own data retrieval methods. Do not implement the condition-driven output of multiple forms from the same form object. ● You use the method IF_SXFT_NODE~APPEND_CHILD( NEW_CHILD ) to set child elements. Arial. The values can be set directly by using the corresponding “set” method (such as <margin> and <color>). ● ● ● ● see the online help for the Designer. use the Form Caching function in the Designer. these recommendations apply both to interactive forms in Web Dynpro and to PDF-based print forms. Minimize the amount of communication that takes place with the server in interactive forms. under Creating Forms for Optimal Performance. Place the context nodes used at the top of the form at the initial position in the context tree. 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. W. Keep scripting to a minimum. This interface is included in all interfaces that represent elements with these attributes.An exception to this are attributes that are themselves elements but only have a few of their own attributes. Only use those interactive functions (such as dynamic value help that sends queries to the server) that are strictly necessary. The interface IF_SXFT_NODE is included in all interfaces that represent XFA elements. For more information. Recommendations for Adobe LiveCycle Designer ● For interactive forms. If possible. use only the following character sets. and Layout. Unless specified otherwise. ● The interface IF_SXFT_MEASUREMENT groups the “set” methods for the attributes X. Times New Roman. These character sets do not need to be embedded in the form. a text input field. see the online help of the Designer. no data binding is created. who can use it to achieve an optimal level of runtime performance when using Interactive Forms based on Adobe software. Since no context is generated. which improves performance. since scripting in a form can have an effect on performance. H. even if the Designer supports others: Courier. option fields. these attributes do not need to be generated. ● Structure the form context in accordance with the logical flow of data. a selection list. This interface is included in all interfaces that represent elements with these attributes.
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. you require SAP NetWeaver Support Package Stack 6 or higher. which determines all fields used in the interface. see Adobe Performance Analysis (in English only). Activities You activate this function by setting the field CACHING in the table FPCONNECT in the Data Browser (transaction SE16). Recommendations for Calling Forms and Form Output ● When you create forms for mass printing. . In the latter case. Caching Forms Use Forms are sent to Adobe document services (ADS) for processing. This function enables you to optimize communication with ADS by caching the form layout on the server where ADS is installed. ● Cache forms that you want to process with Adobe document services. Performance Analysis You can obtain precise details about the performance of Adobe document services. Prerequisites To use this function. CACHING in Table FPCONNECT Value x space Meaning Activate caching Deactivate caching Use the system setting. To support you in your work. see the documentation Form Caching in the online help of Adobe LiveCycle Designer (mentioned further below). design the data retrieval process in the application program and interface in accordance with your individual requirements. For more information. There are two types of caching in ADS. For more information. As well as caching the form layout.● Deactivate any context nodes that you do not need. This setting then applies to all forms in your Web AS ABAP. caching activated The table FPCONNECT also contains other fields. ● Bundle print forms. which are used to define the bundling of forms. you can also cache the processed PDF (for interactive forms). use the function module FP_FIELD_LIST.
bundling is deactivated automatically by the system. 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. The data in the forms can be different. 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. 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. make the required settings in the table FPCONNECT in the Data Browser (transaction SE16). you require the following: ● SAP NetWeaver Support Package Stack 6 or higher ● Adobe document services installed in an SAP NetWeaver AS ABAP + Java system (J2EE Add-In). The function described here enables you to optimize communication with ADS by bundling forms in a single call. The data in the forms can be different. 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. requesting PDFs. Table FPCONNECT Field DESTINATION DIR_GLOBAL BATCHING Required Setting Connection to ADS X is a prerequisite for bundling X to activate simple bundling . Prerequisites To use this function. Bundling of PDF-Based Forms Use Forms are sent to Adobe document services (ADS) for processing. ● Complex bundling Forms with different form designs and different languages are bundled together.
They are a requirement for the generation of accessible PDFs. and tables. uses them to describe and flag the document structure. Check your requirements in advance. See Caching Forms. Adobe Acrobat or Adobe Reader tells you whether your PDF document has tags. including elements such as headers. texts. If both BATCHING and MBATCHING are set in the table. To deactivate a field. If bundling has been activated in the system (using the entry in table FPCONNECT). This has the advantage that you can specify which type of form bundling to run depending on your application. complex bundling is activated. Any gains in performance are also system-dependent. 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. it may be a good idea to deactivate it occasionally for very large forms. especially the applicable legal requirements. specify –. 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. You cannot use the function described here if you want your PDF forms to be accessible. To do this. PDF forms generated in this way need less memory.MBATCHING CACHING X to activate complex bundling Not required for bundling. to use the system setting. Using the Application Program to Define Form Bundling You can also use the application program that calls the form to define form bundling. specify space.
● The PDF is always given tags when archived or returned to the application program. Generated PDF form is a PDF without tags. 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). Activities Set the PDFTAGGED field to your requirements in your application program and send it to the function module FP_JOB_OPEN. it gives you detailed information about the form data and runtime information specified by Adobe document services. Features Utilities in the Form Builder The Form Builder that you use to create PDF-based print forms and interactive forms in Web Dynpro for ABAP offers you a wide range of functions: ● Checking and Testing a PDF-Based Print Form ● Saving Runtime Information and a Generated PDF Locally You activate this function in the Form Builder. . When you call the form.Features You can use the PDFTAGGED field in the IE_OUTPUTPARAMS parameter (type SFPOUTPUTPARAMS. function module FP_JOB_OPEN) to define whether PDF forms are generated with or without 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. Parameter PDFTAGGED Value x space Meaning Generated PDF form is a PDF with tags. and print forms. display.
and certification For notes for form developers and end users. 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. 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. 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. 002. Settings and procedures that are the responsibility of the administrator are described in the following two documents. signatures. see the description under Problem Analysis Scenarios for Adobe Document Services for detailed troubleshooting information. The technology is implemented in .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. Communication Errors. 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. and 004 You use this function module to find out the causes of any errors you encounter when displaying forms. No Form Output If you encounter any connection errors or configuration errors when you use Adobe document services. Runtime Errors.
the Adobe document services offer functions which require keys and certificates associated with your company. see Adobe Document Services Configuration Guide. 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.com/adobe → Media Library → Documentation Why is Security Necessary? The Adobe document services may deal with confidential data. 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. Although running within the J2EE Engine. because high authentication. data integrity and confidentiality are required.: SAP NW 2004s .Adobe Document Services . 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. there are security requirements in the SAP Web AS ABAP and in the SAP Web AS Java. also available at: http://service. These functions are: ● Creating and verifying digital signatures and certification For these functions the use of SSL is mandatory. In addition.the Adobe document services.sap. Restr.
The figure below gives you an overview of the communication paths. it is HTTPS. Communication path 2: Before processing the form and creating a PDF file. which is stored in the Form Design Repository of the ABAP Engine. The protocol for both communication paths is HTTP using the default HTTP port. if your scenarios use digital signatures and certification. In the case of SSL. through the RFC destination (SM59).. You must configure SSL on both communication path 1 and path 2.. Thus the Destination Service communicates with the Internet Communication Framework (ICF). the Adobe document services calls the form design. . respectively HTTPS-Port. Communication path 1: 43.Technical System Landscape PDF-based Forms in ABAP Environment and Interactive Forms in Web Dynpro for ABAP PDF-based forms created in the ABAP Workbench and forms created in Web Dynpro for ABAP use the Adobe document services in the J2EE Engine for processing. 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. .
see SAP Note 752153 and Configuration of the IIOP SSL in the Adobe Document Services Configuration Guide. Communication path 1: Communication between Web Dynpro and the Adobe document services uses a Web Service. You may need authorization to receive this library. You only need to configure SSL on this communication path if your scenarios require a high level of security. This library contains strong encryption. To configure SSL you have to make settings in the User Management and in Communication Destinations. You must set the Web Service Client Proxy as an SSL connection.Communication path 3: The Adobe document services are installed on the J2EE Engine and consist of two parts. 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. The figure below gives you an overview of the communication paths. If you configure IIOP SSL. In case of SSL it is the IIOP SSL port of the J2EE Engine. . you also have to download and deploy the Binaries SSL2 Library. For more information. if your scenarios use digital signatures and certification. You have the option of storing the URL of the Adobe document services in the System Landscape Directory (SLD). The communication between these parts uses the IIOP service (IIOP port).
In case of SSL it is the IIOP SSL port of the J2EE Engine. 1. 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. See following topics: User Management In this section. See the table below. 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. This library contains strong encryption. see SAP J2EE Engine User Management Using the Visual Administrator. . Java and ABAP. See also: Configuration of the Web Service SSL Connection in the Adobe Document Services Configuration Guide. 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. You may need authorization to receive this library. we provide an overview of configuring the Web Service Communication between the ABAP and the J2EE environment.Communication path 2: The Adobe document services are installed on the J2EE Engine and consist of two parts. you may use tools in both application platforms. For more information. see SAP Note 752153 and Configuration of the IIOP SSL in the Adobe Document Services Configuration Guide. If you configure IIOP SSL. User Management The Adobe document services uses the authorization provided by the SAP Web Application Server. For more information. You only need to configure SSL on this communication path if your scenarios require a high level of security. Therefore. The communication between these parts uses the IIOP service (IIOP port). Communication Destinations In this section. you also have to download and deploy the Binaries SSL2 Library. For maintaining a user. we provide an overview of the tools for user management and type of users which are necessary.
Thus also a role ADSCallers in the SAP Web AS ABAP was created. Communication Destinations 2. It is in the SAP Web AS ABAP when the UME is configured against the SAP Web AS ABAP backend.SAP Web AS ABAP user management and role maintenance (Transactions SU01. For more information see the Installation Guide on the SAP Service Marketplace at the internet address http://sap. 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 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 ADSuser is required for the communication between the J2EE Engine and the Adobe document services.service. Each user has a security role assigned to it. 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. which has been predefined in the system. Standard User As of NetWeaver 2004s the standard users that are needed for communication. Standard Roles Role ADSCaller (in J2EE Engine) Description Security role that allows the ADSuser to access the Adobe document services. that is described under Technical System Landscape. Created when system was installed. 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). are created during installation of SAP NetWeaver. Configuring the User ADSUser for the SSL Connection Authorizations The table below shows the standard roles that are used by the Interactive Forms based on Adobe software. PFCG) Use transaction SU01 to maintain a service user on the ABAP engine for the Adobe document services.com/instguidesNW2004s. The ADSuser is assigned to this role.
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. . Only if ADSuser is located in the SAP Web AS ABAP (Transaction PFCG). The ADSCallers role in SAP Web AS ABAP appears automatically as the ADSCallers group in the J2EE Engine. See User Management. See Technical System Landscape.