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