SAP POSS_UIREQ_OPT_INIT Function Module for Init POSS options for new spool request
POSS_UIREQ_OPT_INIT is a standard poss uireq opt init SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Init POSS options for new spool request 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 poss uireq opt init FM, simply by entering the name POSS_UIREQ_OPT_INIT into the relevant SAP transaction such as SE37 or SE38.
Function Group: RSPOPOSS
Program Name: SAPLRSPOPOSS
Main Program: SAPLRSPOPOSS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function POSS_UIREQ_OPT_INIT 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 'POSS_UIREQ_OPT_INIT'"Init POSS options for new spool request.
EXPORTING
PRINTER = "Spool: Output Device
DOCTYPE = "Spool: document type
SPOOLRQ = 0 "Spool request number
* ADS_SUPPORTS_PRINT_OPTIONS = "Does the ADS support the extended print options?
IMPORTING
JT_TAB = "Job ticket table for spool request
PRINTER_HAS_OPTIONS = "'X'=printer supports OPT, space=no opt
EXCEPTIONS
INVALID_SPOOLREQUEST = 1
IMPORTING Parameters details for POSS_UIREQ_OPT_INIT
PRINTER - Spool: Output Device
Data type: RSPOPNAMEOptional: No
Call by Reference: Yes
DOCTYPE - Spool: document type
Data type: RSPODOCTYPOptional: No
Call by Reference: Yes
SPOOLRQ - Spool request number
Data type: RSPOIDOptional: No
Call by Reference: Yes
ADS_SUPPORTS_PRINT_OPTIONS - Does the ADS support the extended print options?
Data type: COptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for POSS_UIREQ_OPT_INIT
JT_TAB - Job ticket table for spool request
Data type: POSS_JOBTICKETTABOptional: No
Call by Reference: Yes
PRINTER_HAS_OPTIONS - 'X'=printer supports OPT, space=no opt
Data type: COptional: No
Call by Reference: Yes
EXCEPTIONS details
INVALID_SPOOLREQUEST - Bad spoolrq
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for POSS_UIREQ_OPT_INIT 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: | ||||
| lv_jt_tab | TYPE POSS_JOBTICKETTAB, " | |||
| lv_printer | TYPE RSPOPNAME, " | |||
| lv_invalid_spoolrequest | TYPE RSPOPNAME, " | |||
| lv_doctype | TYPE RSPODOCTYP, " | |||
| lv_printer_has_options | TYPE C, " | |||
| lv_spoolrq | TYPE RSPOID, " 0 | |||
| lv_ads_supports_print_options | TYPE C. " |
|   CALL FUNCTION 'POSS_UIREQ_OPT_INIT' "Init POSS options for new spool request |
| EXPORTING | ||
| PRINTER | = lv_printer | |
| DOCTYPE | = lv_doctype | |
| SPOOLRQ | = lv_spoolrq | |
| ADS_SUPPORTS_PRINT_OPTIONS | = lv_ads_supports_print_options | |
| IMPORTING | ||
| JT_TAB | = lv_jt_tab | |
| PRINTER_HAS_OPTIONS | = lv_printer_has_options | |
| EXCEPTIONS | ||
| INVALID_SPOOLREQUEST = 1 | ||
| . " POSS_UIREQ_OPT_INIT | ||
ABAP code using 7.40 inline data declarations to call FM POSS_UIREQ_OPT_INIT
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