POSS_PRINTTICKET_TO_JT SAP Function module - Convert PT name into table of selected options

POSS_PRINTTICKET_TO_JT is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name POSS_PRINTTICKET_TO_JT into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: RSPOPOSS
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM POSS_PRINTTICKET_TO_JT - POSS PRINTTICKET TO JT

CALL FUNCTION 'POSS_PRINTTICKET_TO_JT' "Convert PT name into table of selected options
  EXPORTING
    printer =                   " rspopname     Spool: Output device
    devtype =                   " rspoptype     Spool: Device type name
    printticket =               " poss_printticketname  Name of a print ticket
  IMPORTING
    jt =                        " poss_jobtickettab  Job ticket table for spool request
  EXCEPTIONS
    UNKNOWN_PRINTER = 1         "               Unknown printer
    UNKNOWN_PRINTTICKET = 2     "               Unknown print ticket
    DEVTYPE_MISMATCH = 3        "               Devtype of printer has changed
    PRINTER_NO_OPTIONS = 4      "               Device type supports no options
    .  "  POSS_PRINTTICKET_TO_JT

ABAP code example for Function Module POSS_PRINTTICKET_TO_JT

The ABAP code below is a full code listing to execute function module POSS_PRINTTICKET_TO_JT including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_jt  
 
 TYPE POSS_JOBTICKETTAB
.


DATA(ld_printer) = 'Check type of data required'.

DATA(ld_devtype) = 'Check type of data required'.

DATA(ld_printticket) = 'Check type of data required'.
.

CALL FUNCTION 'POSS_PRINTTICKET_TO_JT'
  EXPORTING
    printer =                    ld_printer
    devtype =                    ld_devtype
    printticket =                ld_printticket
  IMPORTING
    jt =                         ld_jt
  EXCEPTIONS
    UNKNOWN_PRINTER =            1
    UNKNOWN_PRINTTICKET =        2
    DEVTYPE_MISMATCH =           3
    PRINTER_NO_OPTIONS =         4
    .  "  POSS_PRINTTICKET_TO_JT

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 3. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 4. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_jt
 
 TYPE POSS_JOBTICKETTAB ,
ld_printer
 
 TYPE RSPOPNAME ,
ld_devtype
 
 TYPE RSPOPTYPE ,
ld_printticket
 
 TYPE POSS_PRINTTICKETNAME .


ld_printer = 'Check type of data required'.
ld_devtype = 'Check type of data required'.
ld_printticket = 'Check type of data required'.