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.

• Business wants to generate an invoice Smart Form (based on VBAK/VBAP) and send the PDF to an SAPUI5/Fiori frontend via OData.

• The frontend should receive the Smart Form PDF as binary content to display or download.

High level flow

Frontend (Fiori/UI5) → OData Service → ABAP Backend → Call Smart Form → Convert to PDF → Return Binary to Frontend

Step 1: Create Smart Form

• Transaction SMARTFORMS → Create form (e.g., Z_INVOICE_SF)

• Define nodes for header (VBAK) and items (VBAP)

• Activate form

Step 2: Create ABAP Class / Function Module

• This module will call the Smart Form and capture output as PDF

DATA: lv_formname TYPE tdsfname VALUE ‘Z_INVOICE_SF’,
lv_fm_name TYPE rs38l_fnam,
lv_pdf TYPE solix_tab,
lv_pdf_size TYPE so_obj_len.

” Get generated function module for Smart Form
CALL FUNCTION ‘SSF_FUNCTION_MODULE_NAME’
EXPORTING
formname = lv_formname
IMPORTING
fm_name = lv_fm_name
EXCEPTIONS
no_form = 1
no_function_module = 2
OTHERS = 3.

IF sy-subrc = 0.
” Call Smart Form
CALL FUNCTION lv_fm_name
EXPORTING
control_parameters = VALUE ssfctrlop( device = ‘PRINTER’ )
user_settings = space
vbak = ls_vbak
TABLES
vbap = lt_vbap
pdfoutput = lv_pdf
EXCEPTIONS
OTHERS = 1.
ENDIF.

Step 3: Return PDF via OData

• Create an OData Service (Transaction SEGW)

• Define an Entity Type (e.g., InvoicePDF) with a Binary Stream property

• In DPC_EXT class, map the Smart Form PDF to the property:

METHOD invoicepdf_get_entity.
” Call Smart Form as shown above
io_data_provider->read_entry_data( )->* ” fetch data from backend tables

es_entity-pdf_data = lv_pdf. ” SOLIX table converted to xstring
ENDMETHOD.

• The frontend will receive PDF as binary (xstring)

• Fiori/UI5 can display with PDF.js or offer download