🧾 SAP ABAP Adobe Forms

✅ 1. What Are Adobe Forms in SAP?

Adobe Forms are PDF-based forms used in SAP to display, print, or capture data with a professional and interactive design.

• Successor to SAPscript and SmartForms

• Supports static (read-only) and interactive (input-enabled) forms

• Works in both SAP ECC and SAP S/4HANA
  
  

🧩 2. Key Components

Component	Meaning
Interface	Defines the data structure passed to the form
Form Layout	Visual layout created using Adobe LiveCycle Designer
Context	Mapping between interface fields and layout elements

🖌️ 3. Design Tool

Adobe LiveCycle Designer is used to create Adobe Forms:

• Can be embedded in SAP GUI or installed separately

• Drag-and-drop interface

• Supports:

  • Tables and subforms

  • Conditions (show/hide)

  • Texts, barcodes, buttons, checkboxes, etc.
    
    

🔄 4. How It Works (Process Flow)

1. Create an Interface (define the required data)

2. Design the Layout

3. SAP generates a Function Module

4. In ABAP: use FP_JOB_OPEN, call the FM, then FP_JOB_CLOSE

5. Output is rendered as PDF
   
   

🧪 5. Important T-Codes

T-Code	Purpose
SFP	Create/Edit Adobe Forms and Interfaces
SFPTRACE	Trace/debug Adobe form execution
FP_TEST_00	Test Adobe Form output
FP_JOB_OPEN	Start form session
FP_JOB_CLOSE	Close form session

🔃 6. Data Flow Inside Adobe Forms

Step	What Happens
Interface	Inputs/outputs data (e.g., PO number, items)
Context	Links interface fields to form fields
Layout	Visual design in PDF
Scripting	(Optional) JS or FormCalc for calculations

🛠️ 7. Why Use Adobe Forms?

✅ Clean, professional output

✅ PDF-ready and printable

✅ Interactive form capabilities

✅ Excellent support for barcodes, tables, conditions

✅ Ideal for SAP S/4HANA

📄 8. Example Use Cases

• Purchase Orders (PO)

• Invoices / Billing

• Delivery Notes

• HR Documents (e.g., Offer Letter)

• Customer Applications

• Interactive Leave Requests
  
  

🧷 9. Key SAP Objects Involved

Object	Use
SFPDOCPARAMS	Form printing parameters
SFPOUTPUTPARAMS	Output parameters
FP_JOB_OPEN / CLOSE	Start/end form rendering
FP_FUNCTION_MODULE_NAME	Get FM name linked to the Adobe form

💡 10. Advantages Over SmartForms/SAPscript

Feature	SAPscript	SmartForms	Adobe Forms
Layout Design	Complicated	Easier	Highly professional
Output Format	Print only	Print only	PDF, Web, Interactive
Interactivity	❌	❌	✅
PDF Support	❌	Limited	✅ Full
Barcode/Image	Basic	Good	Excellent

⚠️ 11. Licensing Notes

• Static (print) Adobe Forms are FREE under SAP NetWeaver license.

• Interactive Forms may require a special license.

• Always check with your Basis/License team.

🚀 12. Performance Tips

• Use Flowed Subforms for dynamic tables

• Modularize content instead of cramming one large subform

• Avoid excessive scripting — keep rendering fast

🧾 13. Summary

✅ Adobe Forms are the modern standard for professional SAP outputs
✅ Fully integrated with ABAP, Fiori, and S/4HANA
✅ Essential for anyone working with customer-facing documents or forms

🧾 Smartforms in SAP ABAP

Introduction to SmartForms

SmartForms is SAP's powerful tool for designing and creating business documents. When you execute a SmartForm, it generates a function module that provides a layout for creating business documents. These documents can be downloaded in PDF format or sent via email to users outside the SAP system.

Key Characteristics

• Purpose: Create business documents like sales orders, material master data, purchase orders, and invoices 

• Transaction Code: SMARTFORMS

• Output: Generated function module that can be called from ABAP programs 

• Flexibility: Documents can be exported as PDF or sent via email

SmartForm Structure Overview

SmartForms consist of two main subfolders:

1. Global Settings

Form Attributes

Contains all generic information about the SmartForm, including basic configuration and metadata.

Form Interface

This acts as the interface of the function module that will be generated by the SmartForm.
It enables: • Input: Send data from ABAP programs to the SmartForm
                  • Output: Receive processed data from the SmartForm

Global Definitions

Defines global data objects, types, and values available throughout the SmartForm:

a. Global Data • Define global variables like internal tables, work areas, and normal variables
• Available throughout the entire SmartForm execution

b. Types • Create global table types and structures
 • Reusable data type definitions

c. Field Symbol • Dynamic data referencing capabilities

d. Initialization • Contains logic that executes at the beginning of SmartForm processing
• Used for initial data preparation and calculations

e. Form Routine • Define subroutines for complex business logic
• Modular code organization

f. Currency/Quantity Field • Pass reference fields for currency or quantity columns
• Ensures proper formatting and decimal places

2. Pages and Windows

Contains the visual layout structure with pages and windows. A default Main Window is always available for every SmartForm.

Types of Windows in SmartForms

1. Main Window

• Default: Always available when creating any SmartForm
• Purpose: Display dynamic data that can flow from one page to another
• Auto-pagination: Automatically transfers content to the next page when current page is full
• Best Practice: Use for displaying table data due to automatic page break handling

2. Secondary Window

• Purpose: Display output of fixed length
• Usage: Template-based displays with predefined structure
• Default: Any window you create manually is a secondary window by default

3. Copy Window

• Special Case: Special type of secondary window
• Purpose: Making pages as "copy" or "original"
• Usage: Create duplicate versions of documents with different markers

4. Final Window

• Execution: Processes at the very end of SmartForm execution
• Purpose: Display content that should appear last
• Use Case: Summary information, totals, or final processing results

Data Display Approach in SmartForms

Fixed Data Display

For predetermined, fixed number of records:
• Method: Design templates with defined columns and rows
• Structure: Static layout with known data positions

Dynamic Data Display

For variable-length data with unpredictable size:
• Method: Create tables inside windows
• Automatic Looping: Tables provide built-in iteration over internal table data
• Configuration: Simply pass internal table and work area names
• Recommendation: Always use Main Window for table data to ensure proper pagination

Types of Text in SmartForms

1. Text Element

• Reusability: Non-reusable text
• Scope: Dedicated to only one section of the SmartForm
• Usage: Section-specific content that won't be reused elsewhere

2. Text Module

• Reusability: Fully reusable text
• Creation: Created via SMARTFORMS transaction code
• Scope: Can be reused across multiple SmartForms
• Management: Centralized text management for consistency

3. Include Text

• Creation: Created using SO10 transaction code
• Reusability: Can be reused in SmartForms, ABAP programs, and function modules
• Integration: Use standard function module READ_TEXT to access in ABAP programs
• Flexibility: Highest level of reusability across SAP components

4. Dynamic Text

• Definition: Text passed at runtime during execution
• Standard Type: Uses SAP standard table type TSFTEXT
• Flexibility: Content determined during program execution

Styling and Formatting

SmartStyles (Transaction: SMARTSTYLES)

Configure text appearance including colors and alignment through two main folders:

Paragraph Format

• Purpose: Define font properties and colors for text
• Scope: Overall text block formatting
• Features: Font family, size, color, alignment

Character Format

• Purpose: Create barcodes for text elements
• Usage: Special formatting for specific characters or text segments
• Barcode Creation: Use SE73 transaction for creating or utilizing existing barcodes
• Syntax: <BA>&VARIABLE_NAME&<BA> for barcode implementation

Graphics and Logo Integration

Adding Logos to SmartForms

Using Existing Graphics

• Availability: SAP provides numerous pre-installed logos and graphics
• Access: Browse available graphics during SmartForm design

Uploading Custom Images

• Transaction: SE78 for uploading images from local system
• Format Requirement: Images must be in BMP format
• Process: Upload via SE78, then reference in SmartForm graphics node

Converting SmartForms to PDF

PDF conversion is essential as it's the widely accepted format for business documents. The process involves three main steps:

Step 1: Extract OTF Data

• Format: Get Open Text Format (OTF) data from SmartForm
• Setting: Set GETOTF = 'X' in control parameters
• Output: Raw SmartForm data in OTF format

Step 2: Convert OTF to PDF

• Function Module: CONVERT_OTF_2_PDF
• Input: OTF data from Step 1
• Output: PDF data in TLINE format

Step 3: Download PDF File

• Method: Use GUI_DOWNLOAD function module or CL_GUI_FRONTEND_SERVICES=>GUI_DOWNLOAD
• Important: Specify correct PDF file path to avoid data corruption
• Result: PDF file saved to local system

Sample Implementation Structure

" Step 1: Set control parameters for OTF extraction
DATA: ls_control TYPE ssfctrlop,
      ls_output TYPE ssfcrescl.
ls_control-getotf = 'X'.

" Step 2: Call SmartForm function module
CALL FUNCTION 'YOUR_SMARTFORM_FM'
  EXPORTING
    control_parameters = ls_control
    " other parameters
  IMPORTING
    job_output_info = ls_output.

" Step 3: Convert OTF to PDF
DATA: lt_pdf TYPE TABLE OF tline.
CALL FUNCTION 'CONVERT_OTF_2_PDF'
  TABLES
    otf = ls_output-otfdata
    lines = lt_pdf.

" Step 4: Download PDF
CALL FUNCTION 'GUI_DOWNLOAD'
  EXPORTING
    filename = 'path_to_pdf_file'
    filetype = 'BIN'
  TABLES
    data_tab = lt_pdf.

Email Integration with SmartForms

SmartForms can be automatically sent as PDF attachments via email, useful for scheduled reports and automated document distribution.

Required SAP Classes

1. CL_BCS

• Purpose: Create send requests, add recipients, and send documents
• Core Functions: Email orchestration and delivery management

2. CL_DOCUMENT_BCS

• Purpose: Create documents and manage attachments
• Functions: Document creation, content management, attachment handling

3. CL_CAM_ADDRESS_BCS

• Purpose: Manage email addresses for external recipients
• Usage: Define destination email addresses outside SAP system

Email Integration Steps

1. Extract Binary File

• Process: Get BIN_FILE from SmartForm output
• Format: Extract in binary format for email attachment

2. Convert to Binary Format

• Function: SCMS_XSTRING_TO_BINARY
• Purpose: Convert Xstring format to SOLIX_TAB for email processing

3. Create Send Request

• Class: CL_BCS
• Method: CREATE_PERSISTENT
• Purpose: Initialize email sending framework

4. Define External Email Address

• Class: CL_CAM_ADDRESS_BCS
• Method: CREATE_INTERNET_ADDRESS
• Input: Recipient email address

5. Add Recipient

• Method: ADD_RECIPIENT
• Purpose: Associate email address with send request

6. Create Document

• Class: CL_DOCUMENT_BCS
• Method: CREATE_DOCUMENT
• Content: Email body text and metadata

7. Add PDF Attachment

• Method: ADD_ATTACHMENT
• Type: 'PDF'
• Content: Binary SmartForm data

8. Set Document to BCS

• Method: SET_DOCUMENT
• Purpose: Associate document with send request

9. Configure Sending Options

• Method: SET_SEND_IMMEDIATELY
• Parameter: 'X' for immediate sending

10. Send Email

• Method: SEND
• Error Handling: Include proper exception handling

11. Commit Transaction

• Purpose: Finalize email sending process
• Success Message: Confirm email delivery status

Sample Email Integration Structure

" Create send request
DATA: lo_bcs TYPE REF TO cl_bcs.
lo_bcs = cl_bcs=>create_persistent( ).

" Create external address
DATA: lo_external_user TYPE REF TO cl_cam_address_bcs.
lo_external_user = cl_cam_address_bcs=>create_internet_address( 
  i_address_string = 'recipient@example.com' ).

" Add recipient
lo_bcs->add_recipient( i_recipient = lo_external_user ).

" Create document with body text
DATA: lt_text TYPE TABLE OF soli.
" Populate lt_text with email body content

DATA: lo_document TYPE REF TO cl_document_bcs.
lo_document = cl_document_bcs=>create_document(
  i_type = 'RAW'
  i_subject = 'SmartForm Report'
  i_text = lt_text ).

" Add PDF attachment
lo_document->add_attachment(
  i_attachment_type = 'PDF'
  i_attachment_subject = 'Report Details'
  i_att_content_hex = lt_binary_tab ).

" Set document and send
lo_bcs->set_document( i_document = lo_document ).
lo_bcs->set_send_immediately( i_send_immediately = 'X' ).

DATA: lv_result TYPE os_boolean.
lv_result = lo_bcs->send( ).

IF lv_result IS NOT INITIAL.
  COMMIT WORK.
  MESSAGE 'Email sent successfully' TYPE 'S'.
ENDIF.

Best Practices and Important Notes

SmartForm Development

• Patience Required: SmartForm designing is a lengthy and detailed process
• ABAP Knowledge: Basic ABAP programming knowledge is sufficient
• Logic Placement: Write business logic in ABAP programs rather than directly in SmartForms
• Version Control: Always create copies before making changes to existing SmartForms

Function Module Management

• Dynamic Names: Use SSF_FUNCTION_MODULE_NAME to get generated function module names
• Re-generation: Function modules change when SmartForms are modified
• Testing: Always test function module calls after SmartForm changes

System Configuration

• Email Setup: Basis team must configure system for external email sending
• Email Monitoring: Use SOST transaction code to monitor sent emails
• Error Handling: Implement comprehensive error handling for all operations

Performance Considerations

• Data Preparation: Prepare data in calling programs rather than in SmartForms
• Window Usage: Use appropriate window types for different content types
• Resource Management: Consider storage and processing overhead for large documents

💻 BDC in SAP ABAP – Batch Data Communication

BDC stands for Batch Data Communication. 

It is an old but effective method in SAP ABAP used to transfer large volumes of data from a non-SAP system to an SAP system. The core concept behind BDC is screen recording – we record user interactions (like creating a material) and loop those steps to automate bulk data entries.

🔍 Purpose of BDC

The main goal of BDC is data migration – for example, if you manually create one material using transaction MM01, BDC allows you to automate the creation of 10,000+ materials without manual intervention.

🧩 How Does BDC Work?

✅ Step-by-Step Process:

1. Screen Recording (SHDB)
   Use transaction code SHDB to record the steps of a transaction (e.g., MM01 – Material Creation).

2. Generate Program from Recording
   Transfer the screen recording steps into an ABAP program using SHDB.

3. Read Data from File
   Upload data (e.g., Excel, .txt file) from your local system into SAP.

4. Loop Through Data & Call Recording
   Loop through uploaded data and use the BDC steps inside that loop.

🔧 BDC Methods

1. Call Transaction Method

📌 Program Example: ZBDC_10_12_MORNING_WEEKENDS

CALL TRANSACTION 'MM01' USING bdc_tab
                   MODE    'A/N/E'
                   UPDATE  'A/S/L'
                   MESSAGES INTO bdcmsgcoll.

• Mode Options:

  • A – Show all screens

  • N – No screen (background processing)

  • E – Show only error screens

• Update Options:

  • A – Asynchronous (Commit Work)

  • S – Synchronous (Commit Work and Wait – Recommended)

  • L – Local Update

• Log Storage Structure:
  ➤ BDCMSGCOLL stores the BDC processing messages (success/error log)

2. Session Method

📌 Program Example: ZBDC_10_12_MORNING_SESSION

This method creates a session that you must process manually via T-Code SM35.

🔁 Key Function Modules:

1. BDC_OPEN_GROUP – Start the session (group)

2. BDC_INSERT – Insert the transaction step

3. BDC_CLOSE_GROUP – Close session after all data is processed

➡ After running the program, go to SM35, select the session, and process it.

❗ Disadvantages of BDC

• ⚠️ Screen-Dependent: Relies on UI layout (screens, field positions)

• ⚠️ Not Upgrade-Proof: Screens may vary across SAP versions (ECC vs S/4 HANA)

• ⚠️ System-Specific: Might not work across different SAP systems

🛑 Conclusion: Due to these limitations, BDC is considered outdated and is generally replaced by BAPIs, which offer a more stable and SAP-supported alternative for data migration.

📘HOW TO CREATE INDEXES IN SAP ABAP

🔹 Types of Indexes

• Primary Index

• Secondary Index

🔸 Primary Index

• The Primary Key will act as a Primary Index.

• When we assign a primary key to a database table and activate the table:

  • SAP automatically creates the primary index.

• Example:

  • When we search order based on order number, we always get high performance.

  • This is because SAP uses the primary index, which is fast and optimized.
    
    

🔸 Why Secondary Index?

• If we want to search order number based on order date, this is a non-primary key field.

• In such cases:

  • If the table has a huge number of records, performance may drop.

  • To improve performance, we create a Secondary Index.

🔹 Secondary Index

• Helps to directly navigate to a particular record.

• Example:

  • Create a secondary index on Order Header Table for field Order Date.

🛠️ Steps to Create a Secondary Index

1. Go to Change Mode of the table.

2. Click on “Indexes”.

3. Click on Create Index.

4. Index Name must be 3 characters long.

   • Example: ODT for Order Date

5. Provide a Short Description for the index.

6. Choose the Field Name you want to index (e.g., Order Date).

7. Initially, the system shows:

   • Index does not exist in database system ORACLE.

8. Click Save, Check, and Activate the index.
   
   
   

📝 Important Notes

• Index will be stored in the format:
  TableName~IndexName
  Example: ZEMPTABLE~ABC
  (ZEMPTABLE = Table Name, ABC = Index Name)
  
  

⚙️ Index Creation Options

• ✅ Index for all database systems
  ➤ Index will be created on all supported databases.

• ✅ Index for selected database systems
  ➤ You can select specific databases where the index is to be created.

• ❌ No database index
  ➤ Index will be removed from the database, but the definition remains.
  
  

⚠️ Disadvantage of Indexes

• Indexes occupy space on the database layer, which can increase storage usage.

🔍Practicals - Interactive ALV Report Using SALV Classes: Hotspot Column with Action Trigger

 Example: ALV Interactive Report using ALV Object Model (SALV classes-Displaying ALV column as hotspot and action related to that)

REPORT ztestalv.

TYPES : BEGIN OF ty_kna1,
          kunnr TYPE kna1-kunnr,
          name1 TYPE kna1-name1,
          ort01 TYPE kna1-ort01,
        END OF ty_kna1.

DATA : t_kna1  TYPE TABLE OF ty_kna1,
       wa_kna1 TYPE ty_kna1.

TYPES : BEGIN OF ty_vbak.
    INCLUDE TYPE zcvbak.
TYPES END OF ty_vbak.

DATA t_vbak TYPE TABLE OF ty_vbak.

DATA o_alv_kna1 TYPE REF TO cl_salv_table.
DATA o_kna1_events TYPE REF TO cl_salv_events_table.

CLASS lcl_eventreceiver DEFINITION.
  PUBLIC SECTION.
    METHODS handle_link_click FOR EVENT
                  if_salv_events_actions_table~link_click OF cl_salv_events_table
      IMPORTING row column.
ENDCLASS.

CLASS lcl_eventreceiver IMPLEMENTATION.
  METHOD handle_link_click.
    CASE column.
      WHEN 'KUNNR'.
*        message 'Customer No Selected' type 'I'.
        CLEAR wa_kna1.
        READ TABLE t_kna1 INTO wa_kna1 INDEX row TRANSPORTING kunnr.
        IF sy-subrc EQ 0.
* get the sales orders for the selected customer
          SELECT vbeln erdat erzet ernam
                  FROM vbak
                   INTO TABLE t_vbak
                    WHERE kunnr =  wa_kna1-kunnr.
          IF sy-subrc EQ 0.
* get the reference of alv table object based on sales orders data
            DATA o_alv_vbak TYPE REF TO cl_salv_table.
            TRY.
                CALL METHOD cl_salv_table=>factory
                  IMPORTING
                    r_salv_table = o_alv_vbak
                  CHANGING
                    t_table      = t_vbak.
              CATCH cx_salv_msg .
                MESSAGE 'Exception in getting reference of alv table object for sales orders data' TYPE 'I'.
            ENDTRY.

            IF o_alv_vbak IS BOUND.
* display the sales orders data in alv grid
              CALL METHOD o_alv_vbak->display.
            ENDIF.
          ELSE.
            MESSAGE 'No sales orders for selected customer' TYPE 'I'.
          ENDIF.
        ENDIF.
      WHEN OTHERS.
        MESSAGE 'Please select customer no' TYPE 'I'.
    ENDCASE.
  ENDMETHOD.
ENDCLASS.

DATA ob TYPE REF TO lcl_eventreceiver.

START-OF-SELECTION.
  PERFORM getcustomers.
  IF t_kna1 IS NOT INITIAL.
* get the reference of ALV table object based on customer data
    TRY.
        CALL METHOD cl_salv_table=>factory
          IMPORTING
            r_salv_table = o_alv_kna1
          CHANGING
            t_table      = t_kna1.
      CATCH cx_salv_msg .
        MESSAGE 'Exception in creating alv object for customer data' TYPE 'I'.
    ENDTRY.
  ELSE.
    MESSAGE 'No Customers' TYPE 'I'.
  ENDIF.

  IF o_alv_kna1 IS BOUND.
* get the reference of ALV columns
    DATA o_alv_cols TYPE REF TO cl_salv_columns_table.
    CALL METHOD o_alv_kna1->get_columns
      RECEIVING
        value = o_alv_cols.

    IF o_alv_cols IS BOUND.
* get the reference of specific column (kunnr)
      DATA o_alv_col TYPE REF TO cl_salv_column.
      TRY.
          CALL METHOD o_alv_cols->get_column
            EXPORTING
              columnname = 'KUNNR'
            RECEIVING
              value      = o_alv_col.
        CATCH cx_salv_not_found .
          MESSAGE 'Exception in getting reference of ALV column KUNNR' TYPE 'I'.
      ENDTRY.
    ENDIF.

    IF o_alv_col IS BOUND.
* type cast the object to ALV column table
      DATA o_alv_col_table TYPE REF TO cl_salv_column_table.
      o_alv_col_table ?= o_alv_col. "widening cast
    ENDIF.

    IF o_alv_col_table IS BOUND.
* set the cell type to hotspot
      CALL METHOD o_alv_col_table->set_cell_type
        EXPORTING
          value = if_salv_c_cell_type=>hotspot.
    ENDIF.

* Register the handler for executing event handler method
*get the alv events object
    CALL METHOD o_alv_kna1->get_event
      RECEIVING
        value = o_kna1_events.

    CREATE OBJECT ob.
    SET HANDLER ob->handle_link_click FOR o_kna1_events.

* display the customer data in alv grid
    CALL METHOD o_alv_kna1->display.
  ENDIF.

FORM getcustomers .
  SELECT kunnr name1 ort01
          FROM kna1
           INTO TABLE t_kna1.
ENDFORM.

Output: