SAP OSS Notes

5312 SAP OSS Note - Variables to be used for printer cover pages








SAP OSS Note 5312 version 0021 contains details of a know issue related to Variables to be used for printer cover pages . This includes any associated symptoms and instructions on how to fix it, see below for full details. Also check out the comments section to view/add related contributions, questions or screen shots, based on real life experience of this oss note and problem.

...For more information about the SAP support system known as OSS please check out the SAP OSS NOTES SECTION, whih includes how to download & implement them onto your SAP system using transaction code SNOTE.

Note 5312 Details:





When does this problem occur



Customer wants to enhance printer cover pages.


List of useable variables.
Customer wants to access values from the user address (like department,
room number) on the title page of a print job.



Cause of the problem and Pre-requisites



No online help, because the list is implemented in the C coding.




Solution instructions



The following is a list of available cover pages text variables:




ANZAHL number of copies. (normal = 1)
AMOUNT


ABTEILUNG department
DEPARTMENT


ANGELEGT date and time of creation of spool request
CREATED


BENUTZER user, who requested the output
USER


DB name and server of database


DRUCKAUFTRAG number of output request (starting with 1
JOBNO for each spool request)


DRUCKER name of output device (from output request)
PRINTER (long device name (30 chars) as of release 4.5B)
DEST


DRUCKERSPRACHE printer language (configured in transaction SPAD)
PRLANG


DRUCKERTYP device type of output device
DEVTYPE


DSN 1st part of name of spool request


ERZEUGT date and time of request for output
LAUNCHED


EIGNER user, who created spool request (and wrote data)
OWNER


EMPFAENGER user, who shall receive the paper
RECEIVER


FORMULAR layout
FORM


GEDRUCKT date and time of output processing
PRINTED
ZEIT
TIME


JOBSEITENZAHL number of pages in the output request
JOBPAGES (correct count)


LAUNCHED_UTC date and time of request for output in UTC


LETZTESEITE last page of output request (correct value
JOBLAST with kernel containing "spool patch collection 14")


MANDANT client of the output request
CLIENT


ORIGDEST name of the output device (from spool request
may be different to DEST if job is redirected)
Only short names supported here.


ORIGPRTYPE device type of ORIGDEST


PJENDPAGE End page of the output request (0=default,
may be larger than PAGES!!!)


PJSTRTPAGE Start page of the output request (0=default)


PJTELENUM Fax number of the output request


PRIO priority


RECHNER computer, which does the output formatting
HOST


RQCLIENT client of the spool request


SAPREL R/3 release number


SEITENZAHL Number of pages of the spool request
PAGES


SHORTNAME Short name for output device (as of release 4.5B)


SPOOLID spool request number


SPRACHE language of the document
SPRAS


STARTSEITE first page of output (1=default)
JOBFIRST


SUFFIX1 2nd part of name of spool request


SUFFIX2 3rd part of name of spool request
SYSTEM system name


TITEL title of spool request.
TITLE


USR Variables of USR03 table (see printing documentation
for details. Please note that as of Release 4.6C, report
RSPOUSR03 has to be executed before these variables can
be used).


These variables can be used on the title page only.


In order to use these variables, copy an existing device type and add
the desired variable in the cover page action of format X_PAPER,

 e.g.


PAGES $(PAGES)\r\n


Description of problem



USR03, titlepage, rspovar


Solution instructions


Please import the corrections attached to this OSS note into your SAP system using SNOTE.

You can also view the full details of this OSS note and download it to your SAP system ready for implementation using transaction code SNOTE. Once it has been downloaded you can read the full details, check out any installation instructions including manual changes and see if there are any pre-requisites.

You can also check if a new version of note 5312 has been released as well as see if the note is valid for your current SAP system landscape.

Check if SAP OSS note 5312 has already been downloaded and is valid


To check if this note has already been download, what status it has and if it is valid for your system first execute t-code SNOTE and click on the SAP Note Browser icon
Icon used to execute SAP Note Browser report within SNOTE

From here you can just enter the note number 5312 and press execute. If the note already exists it's details will be displayed. See here for full step by step instructions on how to check if an SAP note has been downloaded and is valid for your system.



If note 5312 does not exist on your system you will receive the message "Unable to find SAP Note that meets specified criteria"
Icon used to execute SAP Note Browser report within SNOTE

If this is the case you will need to download the note to you SAP system also using transaction SNOTE. For further details see Download note using SNOTE. Even if it does exist you may still want to check if you have downloaded the latest version of the note.

Alternatively you can find full details of this note on the SAP service market place(SNumber / Service market place login will be required)