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.