SAP POSS_ADS_GET_OPTIONS Function Module for Get print options for ADS print









POSS_ADS_GET_OPTIONS is a standard poss ads get options SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Get print options for ADS print 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 ads get options FM, simply by entering the name POSS_ADS_GET_OPTIONS 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_ADS_GET_OPTIONS 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_ADS_GET_OPTIONS'"Get print options for ADS print
EXPORTING
PRINTER = "Spool: Output device
* PRINTTICKET = ' ' "Name of a print ticket
REQUESTED_PRINLANGU = "Printer language of XDC file

IMPORTING
OPTIONS_USED = "Are Print Options used?
OPTIONS = "Options as xstring
USRSTRING09 = "User input string for print option
USRSTRING16 = "User input string for print option
USRSTRING17 = "User input string for print option
USRSTRING18 = "User input string for print option
NON_PJL_OPTIONS_TAB = "Table with non-PJL print commands
PJL_OPTIONS_TAB = "Table with PJL print commands

EXCEPTIONS
INVALID_PRINTER = 1
.



IMPORTING Parameters details for POSS_ADS_GET_OPTIONS

PRINTER - Spool: Output device

Data type: RSPOPNAME
Optional: No
Call by Reference: Yes

PRINTTICKET - Name of a print ticket

Data type: POSS_PRINTTICKETNAME
Default: ' '
Optional: Yes
Call by Reference: Yes

REQUESTED_PRINLANGU - Printer language of XDC file

Data type: TSP0A-DRIVER
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for POSS_ADS_GET_OPTIONS

OPTIONS_USED - Are Print Options used?

Data type: C
Optional: No
Call by Reference: Yes

OPTIONS - Options as xstring

Data type: X
Optional: No
Call by Reference: Yes

USRSTRING09 - User input string for print option

Data type: RSPOPOSS_OPTSTRING
Optional: No
Call by Reference: Yes

USRSTRING16 - User input string for print option

Data type: RSPOPOSS_OPTSTRING
Optional: No
Call by Reference: Yes

USRSTRING17 - User input string for print option

Data type: RSPOPOSS_OPTSTRING
Optional: No
Call by Reference: Yes

USRSTRING18 - User input string for print option

Data type: RSPOPOSS_OPTSTRING
Optional: No
Call by Reference: Yes

NON_PJL_OPTIONS_TAB - Table with non-PJL print commands

Data type: TLINE_TAB
Optional: No
Call by Reference: Yes

PJL_OPTIONS_TAB - Table with PJL print commands

Data type: TLINE_TAB
Optional: No
Call by Reference: Yes

EXCEPTIONS details

INVALID_PRINTER - PRINTER does not exist

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for POSS_ADS_GET_OPTIONS 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_printer  TYPE RSPOPNAME, "   
lv_options_used  TYPE C, "   
lv_invalid_printer  TYPE C, "   
lv_options  TYPE X, "   
lv_printticket  TYPE POSS_PRINTTICKETNAME, "   ' '
lv_usrstring09  TYPE RSPOPOSS_OPTSTRING, "   
lv_requested_prinlangu  TYPE TSP0A-DRIVER, "   
lv_usrstring16  TYPE RSPOPOSS_OPTSTRING, "   
lv_usrstring17  TYPE RSPOPOSS_OPTSTRING, "   
lv_usrstring18  TYPE RSPOPOSS_OPTSTRING, "   
lv_non_pjl_options_tab  TYPE TLINE_TAB, "   
lv_pjl_options_tab  TYPE TLINE_TAB. "   

  CALL FUNCTION 'POSS_ADS_GET_OPTIONS'  "Get print options for ADS print
    EXPORTING
         PRINTER = lv_printer
         PRINTTICKET = lv_printticket
         REQUESTED_PRINLANGU = lv_requested_prinlangu
    IMPORTING
         OPTIONS_USED = lv_options_used
         OPTIONS = lv_options
         USRSTRING09 = lv_usrstring09
         USRSTRING16 = lv_usrstring16
         USRSTRING17 = lv_usrstring17
         USRSTRING18 = lv_usrstring18
         NON_PJL_OPTIONS_TAB = lv_non_pjl_options_tab
         PJL_OPTIONS_TAB = lv_pjl_options_tab
    EXCEPTIONS
        INVALID_PRINTER = 1
. " POSS_ADS_GET_OPTIONS




ABAP code using 7.40 inline data declarations to call FM POSS_ADS_GET_OPTIONS

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.

 
 
 
 
DATA(ld_printticket) = ' '.
 
 
"SELECT single DRIVER FROM TSP0A INTO @DATA(ld_requested_prinlangu).
 
 
 
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!