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