In many support and development projects, we need to modify an existing print layout, debug the print program, or create a custom form. However, it is often difficult to determine which form and print program are being executed.

Please help with the following points:

• How can we identify the Smart Form, Adobe Form, or SAPscript used by a transaction?
• Which transactions can be used to find output types, print programs, and form names?
• How can we use NACE, SPAD, SE93, and the ABAP Debugger to trace the printing process?
• How can we determine whether the application uses Smart Forms, Adobe Forms, or SAPscript?
• How can we identify the print program that calls the form?
• How can we debug the print program and the form logic?
• How can we find the function module generated for a Smart Form?
• What are the most common issues when a form is not printed or prints incorrect data?
• What are the best practices for enhancing SAP standard forms without modifying SAP standard code?
• Can someone share a real project example explaining how they identified and customized the correct form?

A step-by-step explanation with transaction codes, debugging techniques, screenshots, and practical examples would be very helpful.

• 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.

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).