SAP RSPO_OUTPUT_POSTSCRIPT Function Module for

Search SAP Function Modules

RSPO_OUTPUT_POSTSCRIPT is a standard rspo output postscript SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 rspo output postscript FM, simply by entering the name RSPO_OUTPUT_POSTSCRIPT into the relevant SAP transaction such as SE37 or SE38.

Function Group: SPOD
Program Name: SAPLSPOD
Main Program: SAPLSPOD
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RSPO_OUTPUT_POSTSCRIPT 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 'RSPO_OUTPUT_POSTSCRIPT'"
  EXPORTING
*  PAGES = 1 "No. of output pages (info only)
*  RQTITLE = ' ' "Title of spool request
*  DEVICE = '    ' "Output device ('    ' = ask interactively)
*  LOCATION = 'db' "Storage Location ('db' Database, '&G' File System)

 IMPORTING
   RQID =  "Spool request number used

TABLES
   POSTSCRIPT_DATA =  "PostScript data that is output

EXCEPTIONS
   DEVICE_UNKNOWN = 1    DEVICE_TYPE_UNKNOWN = 2    CANCELED_BY_USER = 3    INTERNAL_ERROR = 4    DEVICE_TYPE_BAD = 5 

.

IMPORTING Parameters details for RSPO_OUTPUT_POSTSCRIPT

PAGES - No. of output pages (info only)

Data type: RSPOTYPE-PAGES
Default: 1
Optional: Yes
Call by Reference: No ( called with pass by value option)

RQTITLE - Title of spool request

Data type:
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

DEVICE - Output device (' ' = ask interactively)

Data type: TSP03-PADEST
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

LOCATION - Storage Location ('db' Database, '&G' File System)

Data type:
Default: 'db'
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for RSPO_OUTPUT_POSTSCRIPT

RQID - Spool request number used

Data type: TSP01-RQIDENT
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for RSPO_OUTPUT_POSTSCRIPT

POSTSCRIPT_DATA - PostScript data that is output

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

DEVICE_UNKNOWN - Unknown output device

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

DEVICE_TYPE_UNKNOWN - Unknown device type

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

CANCELED_BY_USER - Cancelled by user

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

INTERNAL_ERROR - Internal error in FM

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

DEVICE_TYPE_BAD - Type of output device is unsuitable

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for RSPO_OUTPUT_POSTSCRIPT 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.

ABAP code using 7.40 inline data declarations to call FM RSPO_OUTPUT_POSTSCRIPT

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