SAP ADOBE FORMS

PDF-based print forms are a part of the Interactive Forms based on Adobe software package solution and are used for mass printing in SAP systems. as well as normal output on printers, and also the choice of archiving documents, you'll be able to additionally use your application to send a PDF to the Business Communication Services (BCS). Here, you've got the choice of faxing or e-mailing your documents.
The following provides you a summary of how a PDF-based print kind is structured and additionally tells you the way to create a PDF-based print from within the development setting of the ABAP work bench. The integrated Adobe LiveCycle Designer software system supports you after you do that. This software system should be put in on your forepart before you'll be able to produce a layout. to visualize a print preview of your kind, you initially got to install Adobe Reader or an entire version of Adobe athlete.
This documentation doesn't discuss however documents are written and controlled on printers. Instead, it discusses the total method up to once a file is shipped to output management functions, like the spool system in SAP systems (for a lot of info, see SAP Printing Guide (BC-CCM-PRN)).

Objectives

• Create an Adobe Form
• Integrate forms into ABAP programs

How Forms are generated at Runtime

SAP Adobe forms generation process is very simple when the report is run to generate Adobe form following steps are performed before generating the output form. Application program fetches the data from the database and calls the ABAP function module to generate the Form based on the PDF form template and its sent to the output.

SAP Forms at RunTime

Components of an Adobe Form

Form Interface

The Form interface defines which data the program can possibly pass on to a form and Declaration of global data and initialization of variables in the form Interface

Context

Context Define which parts of the interface to be used in a particular form and Add elements like text modules or images into the form.

Layout

The layout is Consists of static elements and dynamic elements

and The layout is defined in Adobe LiveCycle Designer it is the complete template of the form like how it will be displayed on the output.

Advantages of SAP Adobe Forms over SAPScript/SmartForms

SAP Adobe Forms

• Abode forms are Non-Interactive
• Abode forms are Interactive means End user can input data using a PDF and submit it to the SAP server
• Abode forms support Webdynpro Integration
• Provide paper-like User Interface
• Easy for users to fill in the data with minimal user training allows the user to save the data in the desktop
• Can still update the DB once online

SAPScript/SmartForms

• SAP Script/Smart Forms are Non-Interactive
• SAP Script/Smart Forms don't support Interactive behavior
• SAP Script/Smart Forms from don't support Webdynpro integrations

Data sources Supported by SAP Adobe Forms

• SAP Adobe from support Data selected from the SAP database tables like master data and transactional Data

• SAP Adobe from support Data provided by the SAP system or by the PDF-based print forms solution like User input and System variables, for example, sy-datum,sy-uname etc.

• SAP Adobe from support Data that has been coded into the program like Totals and summations and concatenated values

In the form interface, specify the data that is exchanged with the application program (such as tables)

Under Global Definitions, define the needed fields

Interface

Under Code Initialization, create the program code to modify global definition data before the form is processed. Form routines that are predefined in the ABAP Editor may be used.
The system fields contain data with a predefined meaning (such as the date).
You can assign currency and quantity fields.

Code Initialization

Context Define which parts of the interface to be used in a particular form and Add elements like text modules or images into the form. Context is consists of Interface, Properties of interface fields and the properties, Details and conditions of context elements

Context

In Context, we can bind the table so the report loop the table to display results.

Report table context

we can also do the conditions in the context like

Conditions

Sap Adobe Forms also support Including Texts

In a form context, four types of long texts can be included

• Addresses from the Business Address Services
• Text modules (Smart Forms texts)
• Include texts (SAPscript texts)
• Dynamic texts

Layout

The layout is Consists of static elements and dynamic elements

and The layout is defined in Adobe LiveCycle Designer it is the complete template of the form like how it will be displayed on the output.

Layout Style

Data Binding

SAP Adobe form allows the data binding we can Association between form template and data source and Created automatically through drag & drop from Data View and Can be created manually

Data binding

Inserting Static Images

Sap Adobe forms allow adding static images do to so first select the page where you want to add image then drag the image into page like example below

Adding Images

Static Texts with Floating Fields

Static text and floating value

Setup for Tables

The Body Page main subform Content property must be set to Flowed and Table body rows are bound to the data in the table.

Setup for table

Integration of Forms into ABAP Programs

• Data retrieval and processing is normally used to data the data from a database or from the internal table which we want to show to report.
• After getting the data find out name of generated function module and CALL FUNCTION ‘FP_FUNCTION_MODULE_NAME'
• In order to Start form processing, we will CALL FUNCTION ‘FP_JOB_OPEN’
• To End form processing CALL FUNCTION ‘FP_JOB_CLOSE'

Correct Approach to Designing Forms

Create the master page first and Look for data that belongs to the background of the page and Set your content area.

it is recommended to Divide the form information/data into

• Header (master page)
• Form content (body page)
• Leaders / detail lines / trailers
• Footer (master page)

it's good to use subforms because Used to organize different element like text fields, attributes, and tables and Can be laid down only in the content area of a master page and Contents of subform can be protected against a page break.

To Include Subforms Placing objects in a subform makes sense

• If you want to output the element repeatedly (type Flow Content)
• If you want to visually group objects
• If you want to keep objects together (protect them against page break)
• If you want to hide several elements at once (scripting required)