SAP PRETTY_PRINTER Function Module for Pretty Printer for ABAP Source Code (No Syntax Check)
PRETTY_PRINTER is a standard pretty printer SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Pretty Printer for ABAP Source Code (No Syntax Check) processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.
See here to view full function module documentation and code listing for pretty printer FM, simply by entering the name PRETTY_PRINTER into the relevant SAP transaction such as SE37 or SE38.
Function Group: SPPR
Program Name: SAPLSPPR
Main Program: SAPLSPPR
Appliation area:
Release date: 27-May-1999
Mode(Normal, Remote etc): Normal Function Module
Update:
Function PRETTY_PRINTER pattern details
In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.CALL FUNCTION 'PRETTY_PRINTER'"Pretty Printer for ABAP Source Code (No Syntax Check).
EXPORTING
INCTOO = "X = Process Include Programs as Well
IMPORTING
INDENTATION_MAYBE_WRONG = "Line Number From Which Indentation May be Wrong
TABLES
NTEXT = "Table of Formatted Source Code
OTEXT = "Table of Source Code Pending Editing
EXCEPTIONS
ENQUEUE_TABLE_FULL = 1 INCLUDE_ENQUEUED = 2 INCLUDE_READERROR = 3 INCLUDE_WRITEERROR = 4
IMPORTING Parameters details for PRETTY_PRINTER
INCTOO - X = Process Include Programs as Well
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for PRETTY_PRINTER
INDENTATION_MAYBE_WRONG - Line Number From Which Indentation May be Wrong
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for PRETTY_PRINTER
NTEXT - Table of Formatted Source Code
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
OTEXT - Table of Source Code Pending Editing
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ENQUEUE_TABLE_FULL - Error in lock management
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
INCLUDE_ENQUEUED - An Include Program is Locked
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
INCLUDE_READERROR - Error Reading an Include Program
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
INCLUDE_WRITEERROR - is no longer used
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for PRETTY_PRINTER Function Module
The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.| DATA: | ||||
| lt_ntext | TYPE STANDARD TABLE OF STRING, " | |||
| lv_inctoo | TYPE STRING, " | |||
| lv_enqueue_table_full | TYPE STRING, " | |||
| lv_indentation_maybe_wrong | TYPE STRING, " | |||
| lt_otext | TYPE STANDARD TABLE OF STRING, " | |||
| lv_include_enqueued | TYPE STRING, " | |||
| lv_include_readerror | TYPE STRING, " | |||
| lv_include_writeerror | TYPE STRING. " |
| CALL FUNCTION 'PRETTY_PRINTER' "Pretty Printer for ABAP Source Code (No Syntax Check) |
| EXPORTING | ||
| INCTOO | = lv_inctoo | |
| IMPORTING | ||
| INDENTATION_MAYBE_WRONG | = lv_indentation_maybe_wrong | |
| TABLES | ||
| NTEXT | = lt_ntext | |
| OTEXT | = lt_otext | |
| EXCEPTIONS | ||
| ENQUEUE_TABLE_FULL = 1 | ||
| INCLUDE_ENQUEUED = 2 | ||
| INCLUDE_READERROR = 3 | ||
| INCLUDE_WRITEERROR = 4 | ||
| . " PRETTY_PRINTER | ||
ABAP code using 7.40 inline data declarations to call FM PRETTY_PRINTER
The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.Search for further information about these or an SAP related objects