Skip to end of metadataGo to start of metadata


In the SAP system, the Adobe Livecycle can be installed by the following step:

Start a Control Panel a Run Advertised Programs a SAP Adobe Livecycle Designer

Adobe LiveCycle Designer ES4 software helps you easily author form and document templates that combine high-fidelity dynamic presentation with. Hi,I'm new to this forum and new to Adobe interactive forms.I went through the SAP Service market by refering to the sapnote 962763 where they mention the path as shown belowInstallation SourceYou can download the Adobe LiveCycle Designer installer from S. I got an issue to create a PDF form with charts. Those charts are not static of course. So, we are to use the Adobe LiveCycle Designer and CL_IGS_CHART_ENGINE. Help reduce costs of form design. Environments through SAP NetWeaver Adobe LiveCycle Designer. Software—which is available as a free download.



Go to IMG -> Regulation Sets & Elements -> Standard Elements -> Define Elements

Select Content & create a new element with Element type=6 (form).

got to Texts and create new entry with Text Type=1 (Full text), Fomat = PDF and enter the name of the form you will be creating in the Form name field.


Go to IMG -> Basic Functions -> Variables -> Information Systems -> Display output as WSDL

Select your content and Form standard element ( created in previous step ).

Select Generate Form XML Schema and execute.

Now the XML schema is displayed. Make sure the first tag <xsd: element name='Form_name'> has the Form name and the next tag <xsd: element name='Form_element_name'> has the form element name.

Download this XML schema and save it with extension .xsd.


Form interfaces may be defined with a previously generated schema. A form interface allows you to map Document Builder variables to form fields. Note that you can only assign one interface to a form, but an interface can be used by more than one form.
The procedure is:

1. Run transaction Form Builder (SFP)
2. Select Interface and choose Create
3. Enter the name of the interface and a description

4. Select the XML Schema-Based Interface type

5. In the File field, specify the path of the XML schema you have created and choose Load
6. Select the _Interface tab to view the newly generated interface.

When working with Document Builder, go to the Document Builder IMG, go to Standard Elements, highlight the form element, go to texts, highlight the full text and click on Edit Form. This will open the transaction Form Builder from the IMG and from there the procedure is the same as above.


Before creating a form, check for the following points:
1. XML schema has been generated

2. Form interface has been created

3. SAP Interactive Forms by Adobe has been installed. It is based on transaction

Form Builder (SFP) enhanced with Adobe Livecycle designer

4. The RFC connection to Adobe Livecycle Designer using transaction RFC

destinations (SM59) are checked.

- Run transaction Form Builder (SFP)

- Select Form and choose Create

- Enter a description and an existing form interface when prompted.

- Choose Save

- Select Layout to view the work area: the Data view on the left pane displays the Document Builder variables, the Body Page on the right pane the form you want to design.

- You can drag and drop the variables from the Data view to the Body page on the empty form

- Save your changes and choose PDF Preview on the right pane to view the form in PDF format.

Livecycle Designer is a point-and-click graphical form design tool that simplifies the creation of XML form designs for distribution as Adobe PDF forms.

Using Livecycle Designer, we can drag-and-drop images and other objects, such as list boxes, drop-down lists, and command buttons, onto their forms.

We can design a form, define its logic, modify it to match paper counterparts or meet strict legislative requirements, and then preview the form before distributing it.


The latest version is Livecycle Designer 7.1 which is additional features like table creation, language support, addition of 2D barcode objects to the form, creation of dynamic forms, etc.

Livecycle Designer when used in ABAP Workbench or SAP Netweaver Developer Studio, the environment creates the new form designs and templates for us.

The Livecycle Designer workspace is arranged to help focus on creating and editing form designs.
The Layout Editor is the main area where you create and maintain the form design. Tabbed palettes are arranged around the Layout Editor to provide easy access to the tools without cluttering our workspace.

Sap Adobe Livecycle Designer 11.0 Download

When building a form, use the tools in the Livecycle Designer workspace. The following tabs represent the canvas on which you assemble and view the components of the form design:
1. Body Pages tab displays the body pages making up the form design.

2. Master Pages tab displays the master pages that can be applied to body pages.

3. XML Source tab displays the XML source code that describes the structure of

the form design and its objects.

4. PDF Preview tab displays a PDF form based on the current form design.

Palettes provide easy access to the tools without cluttering our workspace. Palettes can include one or more tabs, each containing common properties. For example, all objects are stored in the Library palette. As you can see in the following figure, the objects are further grouped into tabs.

You can arrange the palettes in the workspace to suit your work style. For example, you can hide the rarely used palettes and move the frequently used ones into one palette window. There are several ways to organize the palettes:
1. Move the palettes anywhere on the screen.

2. Dock the palettes to the right and left of the window. You can also dock the

Script Editor to the top or bottom of the window.

3. Resize a palette horizontally and vertically.

4. Reset the palettes to their original position.

5. As you work in the Layout Editor, the information that appears in the palettes

Adobe Livecycle Designer Latest Version

changes to reflect the selected object. For example, if you select an object, the

information in the Layout palette changes to display information about the object's size and position.

We can use rulers, guidelines, crosshairs, and the grid to help us position objects precisely.

When visible, rulers appear along the top and left side of the active page. Markers in the ruler display the pointer's position when we move it. Changing the grid origin (the (0, 0) mark on the top and left rulers) lets us measure from a specific point on the form design.

We can also show or hide object boundaries on the form design. Showing boundaries is useful for displaying objects that do not have borders on the form.

We can set these options in the Drawing Aids palette.

The SAP environment saves the form for us automatically.

To be able to merge data with our form, we need to connect to a data source. After we have connected to a data source, we bind the data to a field in our form design.

When we bind the fields in a form design to a data source, we create an association between the form design and the data source that allows us to capture, present, move, process, output, and print information associated with the form design.

After we have connected to a data source, we need to tell the form design where the data should be seen.

To bind single fields, we can use the drag and drop method.

To bind repeating objects, such as the row in a particular table, to repeating items in the schema, we use the Default Binding box in the Binding tab of the Object palette. After the row is bound, we can bind cells in the row to nodes in the schema, which makes these bindings relative to the row binding.

In the previous tutorial, we created a form that users fill electronically and print. Now, we will take this static form and make it dynamic to show the orders that a client of ours has requested.

In this tutorial, the form design presents information from a data source. It is a non-interactive form that we can print or store electronically.

When we have finished working through this tutorial, the form we create will look like the original form merged with data.