Since this is a text-heavy output with minimal graphics, the customer chooses SAPscript as the form technology.

ABAP Driver Program → Fetch data (VBAK/VBAP)
↓
SAPscript Layout Set (SE71) → Windows + Paragraph Formats
↓
Functions: OPEN_FORM → WRITE_FORM → CLOSE_FORM
↓
Final Output → Printed / Spool / PDF

REPORT zsd_sapscript_driver.

TABLES: vbak, vbap.

DATA: it_vbak TYPE vbak,
it_vbap TYPE TABLE OF vbap,
wa_vbap TYPE vbap.

PARAMETERS: p_vbeln TYPE vbak-vbeln OBLIGATORY.

START-OF-SELECTION.

“Fetch Sales Order Header
SELECT SINGLE * INTO it_vbak
FROM vbak
WHERE vbeln = p_vbeln.

IF sy-subrc <> 0.
MESSAGE ‘Sales Order not found’ TYPE ‘E’.
ENDIF.

“Fetch Sales Order Items
SELECT * INTO TABLE it_vbap
FROM vbap
WHERE vbeln = p_vbeln.

“Open Form
CALL FUNCTION ‘OPEN_FORM’
EXPORTING
form = ‘ZSALES_ORDER’ ” SAPscript layout set
language = sy-langu.

“Print Header Window
CALL FUNCTION ‘WRITE_FORM’
EXPORTING
element = ‘HEADER’ ” SAPscript text element
TABLES
lines = it_vbak.

“Print Items
LOOP AT it_vbap INTO wa_vbap.
CALL FUNCTION ‘WRITE_FORM’
EXPORTING
element = ‘ITEMS’
TABLES
lines = wa_vbap.
ENDLOOP.

“Close Form
CALL FUNCTION ‘CLOSE_FORM’.

Key Notes

• Layout set is created in SE71 (e.g., ZSALES_ORDER).

• Text elements HEADER and ITEMS must be defined inside the layout set.

• Data (from VBAK/VBAP) flows from ABAP → WRITE_FORM → Windows in layout.

🔹 1. Layout Set (SE71)

• The backbone of SAPscript.

• Contains definitions of pages, windows, and formatting.

• Example: A Sales Order form might have one page layout for the confirmation letter.

🔹 2. Windows

• Specific areas on a page where text/data is printed.

  • Main Window → prints dynamic data like sales order items (repeats if data overflows).

  • Header Window → prints customer and document info.

  • Footer Window → prints terms, disclaimers, or totals.

🔹 3. Paragraph & Character Formats

• Define how the text looks (font size, bold, alignment).

• Example: Paragraph “H1” for header text, Character format “B” for bold emphasis.

🔹 4. Standard Texts (SO10)

• Reusable text blocks.

• Example: “Payment Terms” or “Delivery Conditions” maintained once, used in multiple forms.

Flow of SAPscript Document Generation

Example:
In a Delivery Note:

• Header Window → Customer details (name, address).

• Main Window → Item details (material, quantity, description).

• Footer Window → Terms & conditions (from SO10).

 Takeaway: These components work together like a blueprint → SAPscript pulls data, places it into defined windows, formats it using paragraph/character settings, and prints the final structured document.

How it works:

• The main design object in SAPscript is the Layout Set, which contains:

  • Pages – overall structure of the document.

  • Windows – areas for content (main window, header, footer).

  • Paragraph & Character Formats – define text style.

• A driver program (ABAP) fetches data and passes it to the layout set.

• Output is generated using function modules like OPEN_FORM, WRITE_FORM, and CLOSE_FORM.

Important TCodes for SAPscript:

• SE71 – Create/change Layout Set.

• SE78 – Upload graphics (logos, signatures).

• SO10 – Maintain Standard Texts.

• SE38/SA38 – Execute the driver program.

Example: To print a Sales Order Confirmation, you design a layout in SE71, write a driver program that fetches VBAK/VBAP data, and link it via WRITE_FORM.

Difference: Compared to Smart Forms (drag-and-drop UI) and Adobe Forms (interactive PDFs), SAPscript is more technical, harder to maintain, and less flexible for modern business needs.

• The sales team needs a printable Sales Order Form that shows both header details (from VBAK: order number, date, sold-to party, order type) and line item details (from VBAP: material, description, quantity, UoM).

• This form will be sent to customers as an official order confirmation in PDF format.

• Since the form must be interactive and professional, SAP Adobe Forms are chosen over Smart Forms.

REPORT zdemo_adobe_form.

*———————————————————-*
* Data Declarations
*———————————————————-*
TABLES: vbak, vbap.

DATA: lv_vbeln TYPE vbak-vbeln, “Sales Order
lt_vbak TYPE TABLE OF vbak,
lt_vbap TYPE TABLE OF vbap.

* Form interface structures
DATA: gs_output TYPE zstr_output, “Custom structure for Adobe Form
gt_items TYPE STANDARD TABLE OF zstr_items.

*———————————————————-*
* Selection Screen
*———————————————————-*
PARAMETERS: p_vbeln TYPE vbak-vbeln OBLIGATORY.

*———————————————————-*
* Start-of-selection
*———————————————————-*
START-OF-SELECTION.

” Fetch Sales Order Header
SELECT SINGLE *
INTO vbak
FROM vbak
WHERE vbeln = p_vbeln.

IF sy-subrc = 0.
” Fetch Sales Order Items
SELECT *
INTO TABLE lt_vbap
FROM vbap
WHERE vbeln = p_vbeln.
ELSE.
MESSAGE ‘Sales Order not found’ TYPE ‘E’.
ENDIF.

*———————————————————-*
* Prepare Data for Adobe Form
*———————————————————-*
CLEAR gs_output.
gs_output-vbeln = vbak-vbeln.
gs_output-erdat = vbak-erdat.
gs_output-auart = vbak-auart.
gs_output-kunnr = vbak-kunnr.

CLEAR gt_items.
LOOP AT lt_vbap INTO DATA(ls_vbap).
DATA(ls_item) = VALUE zstr_items(
posnr = ls_vbap-posnr
matnr = ls_vbap-matnr
arktx = ls_vbap-arktx
kwmeng = ls_vbap-kwmeng
vrkme = ls_vbap-vrkme
).
APPEND ls_item TO gt_items.
ENDLOOP.

gs_output-items = gt_items.

*———————————————————-*
* Call Adobe Form
*———————————————————-*
DATA: lo_fm_name TYPE rs38l_fnam,
lv_fm_name TYPE rs38l_fnam.

” Function module generated automatically when you activate the form
CALL FUNCTION ‘FP_FUNCTION_MODULE_NAME’
EXPORTING
i_name = ‘ZADOBE_FORM’ ” Adobe Form name in SFP
IMPORTING
e_funcname = lv_fm_name.

” Open spool request
CALL FUNCTION ‘FP_JOB_OPEN’
CHANGING
ie_outputparams = gs_outputparams
EXCEPTIONS
cancel = 1
usage_error = 2
system_error = 3
internal_error = 4.

” Call generated FM
CALL FUNCTION lv_fm_name
EXPORTING
/1bcdwb/docparams = gs_docparams
is_header = gs_output
IMPORTING
/1bcdwb/formoutput = gs_formoutput.

” Close spool request
CALL FUNCTION ‘FP_JOB_CLOSE’
EXCEPTIONS
usage_error = 1
system_error = 2
internal_error = 3.

MESSAGE ‘Adobe Form called successfully’ TYPE ‘I’.

🔹 ADS runs on the SAP NetWeaver Java stack and acts as the PDF rendering engine.
🔹 It takes two inputs: the form template (designed in Adobe LiveCycle Designer) and the data (from the ABAP program).
🔹 ADS merges both and delivers a professional, ready-to-use PDF.

But ADS is more than just rendering. It enables interactivity in forms: dropdowns, checkboxes, digital signatures, and workflow approvals. This makes Adobe Forms powerful for business-critical documents.

Example
An Expense Approval Form is generated in SAP → sent to a manager as a PDF → manager approves/rejects inside the PDF → ADS validates and sends the result back to SAP.

 Concept Flow:

ABAP Program → Form Interface → ADS → Final PDF

Takeaway: Without ADS, Adobe Forms cannot run. Always test with SFP → Utilities → Test ADS Connection to ensure system stability.

When it comes to designing business documents in SAP, two main options stand out: Smart Forms and Adobe Forms.

🔹 Smart Forms are static and mainly print-focused. They work well for simple layouts but offer limited customization.
🔹 Adobe Forms, on the other hand, are interactive, dynamic, and PDF-based. They allow enterprises to deliver professional, user-friendly documents.

Key Features of Adobe Forms

• Dropdowns, checkboxes, and digital signatures for interactivity.

• Dynamic content where text boxes expand as data grows.

• Multilingual PDF generation for global business needs.

Example

• A Smart Form Invoice prints static text with little flexibility.

• An Adobe Form Invoice adapts dynamically, supports multiple languages, and includes polished branding.

Takeaway: Choose Smart Forms for simple outputs, but rely on Adobe Forms for enterprise-ready, interactive documents.

Key Uses of Context in Adobe Forms

1. Data Binding
   • Context defines the data model that you can use in the form layout.
   • You bind form fields (like text fields, tables, etc.) to elements in the context so they can display or collect data.
2. Input and Output
   • Context defines which data is input to the form and which is output from the form (especially in interactive forms where users fill in data).
3. Mapping with Interface
   • It links the form interface (where you define import/export parameters and global data) to the form layout.
   • You can map fields from the interface to the context and then use them in the layout.
4. Conditional Rendering & Logic
   • You can use context elements in form logic, such as scripts or visibility conditions (e.g., show a section only if a context field has a certain value).
5. Repeating Structures
   • For tables or line items, context allows you to define repeating nodes, enabling the layout to handle dynamic data (like sales order items).

Key Features:

• Built using graphical editor (no need to write layout code manually).
• Supports tables, loops, conditions, windows, and dynamic content.
• Output in formats like PDF, print preview, email, or XML.
• Separates form logic from application logic (cleaner design).

Example Function Module Usage:

DATA: lv_fm_name TYPE rs38l_fnam,
      lv_control_param TYPE ssfctrlop,
      lv_output_options TYPE ssfcompop,
      lv_job_output_info TYPE ssfcrescl.

CALL FUNCTION 'SSF_FUNCTION_MODULE_NAME'
  EXPORTING
    formname = 'ZSMARTFORM_NAME'
  IMPORTING
    fm_name  = lv_fm_name.

CALL FUNCTION lv_fm_name
  EXPORTING
    control_parameters = lv_control_param
    output_options     = lv_output_options
    user_settings      = 'X'
    <other_parameters>
  IMPORTING
    job_output_info    = lv_job_output_info.