Sapscript Formatting

Hi everyone.
I am have this piece of code in SAPscript MAIN window editor:
/:   IF &PAGE& = 1
/:   POSITION XORIGIN '0.2' CM
/:   BOX WIDTH '77' CH HEIGHT '190'MM FRAME 10 TW
/:   BOX WIDTH '77' CH HEIGHT '1.2'LN FRAME 20 TW
/:   BOX XPOS '17' CH WIDTH 0 TW HEIGHT '190' MM FRAME 10 TW
/:   ENDIF
/E 610-B
610-B is a text element.
This code works fine, but when I exit the editor the word 'par' is inserted and this distorts my code as in the following;
/E ENDIFpar610-B.
What do I have to do to keep this 'par' word off.
Will award points for useful answers.
Regards,

Change the name of you text element. It should start with character.
Message was edited by:
Pratiksha Parab

Similar Messages

Revert RDI file forms to SAPScript format

Hi Gurus,
We are currently implementing a change on how the forms are to be processed. Currently, the forms are in SAP but being pushed to Streamserve application for layouting and formatting. The way it is triggered is that from SAP, it triggers an RDI file to be sent to the Streamserve application for layouting before it is being sent to output device.
And now we want to change it by getting rid of application and have the SAPScript format the forms. Have read some documentation onf converting SAPScript to RDI file. Is there links/documentation on how to do the reverse side? Any information you can share on how to go about it?
Thanks a lot!
Napoleon

Hi Christian, Sandra,
Thanks for the reply. We understand that any output layouts will be lost, but that's ok. Our intention is now to process the layouting of forms from an external application to push it back to a SAP based solution via SapScript. In this way, we get rid of the external apps and its associated cost, in turn, drive some efficiency in the IT process.
Do you know how to disregard the RDI settings?
Cheers,
Nap

SAPScript: Formating an Address/Endaddress part as bold

Hello,
I want to format an Adrdess/Endaddress part as bold. Don't know how to do this. Thanks.
Regards, Lars.

For the associated paragraph format, just check the radiobutton for "BOLD".
Double click the paragraph format, click the font button, click the radiobutton to the "ON" position next to BOLD.
Regards,
Rich Heilman
Message was edited by: Rich Heilman

PU19 PDF/SAPScript issue in upgrade between 4.7 to ECC6.0

We are upgrading from 4.7 to ECC6.0. ADS is setup for PDF format. When I run Tax reporter, in the log, I see W2 is getting generated under both PDF format and SAPScript format. Actually creates spool for W2 on both formats (Forms generated in PDF and also in SAPScript format). How do I stop the W2 statement NOT to create in SAPScript format. and Create only in PDF format. Any help please.
Thanks, Raj

Config view V_T5UX7 for tax form 'HR_F_W2' . Delimit alternate form HR_F_W2' (having Sapscript radio button selected) and any forms you no longer want Sapscript to create with an early end date (e.g. 12/31/2007).
Rgds.

Problem in formatting long text

Hi Experts,
I am printing quality notification using adobe forms.
The problem is that if there is any <TAB> in the longtext , then it is being printed as ',,'.
Ex. Test 1 is being printed as test,,1.
I am using READ_TEXT to read the text and in that itself I am getting the above format of ',,'.
Please suggest a way it could be printed as Test 1.
Many Thanks!
Parul.

Hi Parul,
In the internal sapscript format the tab is represented as a ',,'. You should use function module CONVERT_ITF_TO_ASCII to convert the data returned by function READ_TEXT.
Reards,
Aidan

Email a Standard SapScript

Dear Friends,
1. There is a standard program (for Form 16 India)
   which has a normal selection screen
   and outputs a sapscript report.
2. The requirement is to EMAIL the report
   to each individual employees.
   (Thru a Y Program)
3. I had investigated & done ::
   we can email a report which outputs in
   LIST FORMAT
   But
   How To EMail a report which is output in SAPSCRIPT !
Regards,
Amit M

Thanks for the reply friends.
But i could not find the exact solution
to my problem.
1. The report is a standard se38 report
   whose output is in sapscript format.
2. I don't have any control over its code
   of 'OPEN_FORM', 'CLOSE_FORM'. (Since
   it is a standard sap report)
3. A new Z Program is required to be developed
   which LOOPS and mails the sapscript report mentioned in point (1),
   one by one to each individual employees email address.
Regards,
Amit M.

Is it possible to print barcodes from LT31 (SAPScript) on a Zebra?

Hi
We have a factory that would like to print their picking lists/transfer orders using transaction LT31 to a Zebra ZM600 printer. The transaction appears to create a spool in the SAPScript format.
We have tried pretty much all of the Zebra drivers (ZEB), a standard HP driver and a ASCII line printer driver (in SPAD) but nothing works - barcodes are not printed. For some drivers the format of the spool looks good in SP01, but then nothing is printed at all at the printer! In other cases the text is okay but barcodes are not, in other cases the text is complete gibberish.
The user has been informed that SmartForms should be used instead of SAPScript but we believe this would involve changes at ABAP level and our ABAP support is by a third party company which we are trying to avoid using.
I have seen SAP Note 179534 - Label printing with Zebra printers (SAPscript) but it seems this would also involve Application Support/ABAP teams etc.
Is there anything we (SAP Basis) or the end user can do to be able to print barcodes from LT31 to the Zebra printer without involving Application/ABAP support?
Thanks
Ross

Tried but get an error:
SAP spool error log
=====================
Print request processing log
The host spool is reporting errors
Unintelligible response received from assumed SAPLPD ("#")
(SAP)LPD cannot accept request (Queue LDSP0092 disabled?)
Unable to connect to output processor
Any ideas?

Address print problem - sapscript

Hello
I have a problem with print name for example
"Mr &Smith& and &M& company" from field &VBDKR-NAME1&. The output is "Mr and company" sapscript format the name. I use
/: ADDRESS PARAGRAPH AS
/: ADDRESSNUMBER &VBDKR-ADRNR(K)&
/: FROMCOUNTRY &VBDKR-SLAND&
/: ENDADDRESS
and it helps but now i want to output only street from the address or name2 (&VBDKR-NAME2&). I try to use
ADDRESS PARAGRAPH AS PRIORITY 6APHRT7I8LCBS5O LINES 1
but it returns "invalid label".
Any help ?
Regards Bartek

Hi,
Instead of ADDRESSNUMBER can you use the other way like
/: ADDRESS [DELIVERY] [TYPE t] [PARAGRAPH a] [PRIORITY p] [LINES l]
/: TITLE title
/: NAME name1[,name2[,name3[,name4]]]
/: PERSON name of natural person [TITLE form of address]
/: PERSONNUMBER number of the personen
/: DEPARTMENT department
/: STREET street name HOUSE house number
/: LOCATION additional location information
/: POBOX po box [CODE post code / zip code] [CITY city]
/: POSTCODE post code / zip_code
/: CITY city1[,city2]
/: NO_UPPERCASE_FOR_CITY
/: REGION county / state
/: COUNTRY recipient country [LANGUAGE language code]
/: COUNTRY_IN_REC_LANG
/: LANG_FOR_COUNTRY language key
/: FROMCOUNTRY sender country
/: ENDADDRESS
You have the STREET option here. Also find the detail help at,
http://help.sap.com/saphelp_470/helpdata/en/d1/803238454211d189710000e8322d00/frameset.htm
Thanks
Vinod

SAPscript form archiving

dear all,
Have anyone try outgoing document archiving for SAPscript form? please advise.
Thanks,
Jess

Hi
Did you find a solution for SAPscript archiving?
I am trying to archive payment advice notes, without success. 've followed all instructions as per the SAP library, but I'm getting ArchiveLink errors.
I think it is because my payment advice notes are in SAPScript format, while the customizing requires PDF format.
Now I'm not sure whether to find a solution for archiving SAPscript, or whether to convert the docs to PDF before archiving.
Any suggestions?
Thanks
ES--

Tcodes in sapscripts

what r all the necessary tcodes in sapscripts including monitoring tcodes if avl

Hi,
Take this freq. used t codes....I think it wil be very usefull for u.
SE10 Customizing Organizer
SE11 ABAP/4 Dictionary Maintenance
SE12 ABAP/4 Dictionary Display
SE13 Maintain Technical Settings (Tables)
SE14 Utilities for Dictionary Tables
SE15 ABAP/4 Repository Information System
SE16 Data Browser
SE17 General Table Display
SE30 ABAP/4 Runtime Analysis
SE32 ABAP/4 Text Element Maintenance
SE35 ABAP/4 Dialog Modules
SE36 ABAP/4: Logical Databases
SE37 ABAP/4 Function Modules
SE38 ABAP/4 Program Development
SE39 Splitscreen Editor: Program Compare
SE41 Menu Painter
SE43 Maintain Area Menu
SE51 Screen Painter
SE80 ABAP/4 Development Workbench
SE71 SAPscript layout set
SE72 SAPscript styles
SE73 SAPscript font maintenance (revised)
SE74 SAPscript format conversion
SE75 SAPscript Settings
SE76 SAPscript Translation Layout Sets
SE77 SAPscript Translation Styles
SE91 Maintain Messages
SE93 Maintain Transaction Codes
If its going to be helpfull reward points.
Sakthi.

Dump in SAPLSTXD

Here is the short dump that I am getting while generating Z report transaction.
Can anyone please help me out to resolve the issue?
The current ABAP program "SAPLSTXD" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
Error analysis
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_IMPORT_MISMATCH_ERROR', was
not caught in
procedure "READ_TEXTLINES" "(FORM)", nor was it propagated by a RAISING clause.
Since the caller of the procedure could not have anticipated that the
exception would occur, the current program is terminated.
The reason for the exception is:
Missing RAISING Clause in Interface
Program SAPLSTXD
Include LSTXDFDB
Row 75
Module type (FORM)
Module Name READ_TEXTLINES
Trigger Location of Exception
Program SAPLSTXD
Include LSTXDFDB
Row 106
Module type (FORM)
Module Name READ_TEXTLINES
Source Code Extract
85 DATA: l_mod LIKE tcp0c-modifier.
86
87 refresh rt_lines.
88 move-corresponding rt_header to stxl_id.
89 * only for nonunicodesystems:
90 * the import-statment contains a conversion from internal cp
91 * to the codepage of language key.
92 * if the import-process can't assign a codepage it is using
93 * the actual systzem-codepage. So we make a SET LOCALE
94 l_unich = CL_ABAP_CHAR_UTILITIES=>charsize.
95 IF l_unich = 1.
96 GET LOCALE LANGUAGE l_sypr COUNTRY l_count MODIFIER l_mod.
97 CATCH SYSTEM-EXCEPTIONS localization_errors = 1.
98 SET LOCALE LANGUAGE rt_header-tdspras.
99 ENDCATCH.
100 IF sy-subrc 0.
101 SET LOCALE LANGUAGE l_sypr.
102 ENDIF.
103 ENDIF.
104
105 if rt_header-tdtexttype is initial. "SAPscript format
>>>>> import tline to rt_lines
107 from database stxl(tx)
108 client rt_client
109 id stxl_id
110 ACCEPTING TRUNCATION "important for Unicode->Nonunicode
111 IGNORING CONVERSION ERRORS.
112 else. "non-SAPscript text
113 import tline to rt_lines
Someone please help in finding the solution.
Regards,
Vikas

Hi.,
The import parameter passing is mismatched from the dump error.,
check the tline has structure same as rt_lines and same fields are passing and get populating.,
Thanks & Regards,
Kiran

VF03 smartform: Output could not be issued

Hi All,
Ive created a custom invoice print program and associated smartform.
These two run perfectly together when standing alone.
However Ive created a custom output type to call this program from VF03.
This output type appears in the "Issue Output To "options in VF03.
But it returns the message "Output could not be issued" when trying to print.
In debug mode the Print Program and smartform execute perfectly when calling from VF03 in the same way, but the output fails to appear.
In the Header -Output section inside the status of the output type is "Not Processed".
Any ideas guys??

Hi
It seems that the Output determination is not taking place correctly
the link between the Output type and Program and smartform is not established peoperly
You have to assign this in SPRO for the billing documents
And most of the times it won't work we assign our custom program to the custom output type
it is better to use the std output type and the Std program(you copy the std and can change it but the same copied ZPeogram to be attached) and Copied/modified smartform.
check this.
Output is a link between the Driver Program and the Sapscript,
An output type summarizes messages of the same meaning. It contains parameters that are valid for all its assigned messages, for example appropriate partner functions.
Transmission medium is a medium which the layout will be come out, this may be printout, Fax or Mail
Check this link.
http://help.sap.com/saphelp_nw2004s/helpdata/en/c8/19884743b111d1896f0000e8322d00/content.htm
ex-how to config output type.
You will assign output types using Transaction NACE.
Do the follow steps to assign output type
1)Select Application Type V2 which will have description Shipping.
2)Click on Output types button.
3)Go to change mode by pressing Ctrl+F4.
4)Select one output type which already exists
5)Do Copy As(F6)
6)Give your output type against Output Type field.
7)Under General data Tab, Give Program and Form routine and Save the data.
i think it a work of functional guy but at senior level i think it is not a big deal for abaper.
Check the following documentation
In NACE t-codewe have the application for each one. based on the application output type can be defined, based on output type script and print progrma can be defined.
If suppose data can be read from EDI then we should go for condition records.
So whenever we execute the script first composer checks the output type and then execute the program. in program whenever opn form FM will be populate then script will open first. After that again program till another FM will populate if it then script will populate........like it is cycle proces. Composer does all these things and at last it will submit that output to spool.
Go to the Transaction NACE.
choose the related sub module.. like billing or shipping
doubel click on Output Types
Choose the Output Type for which whcih you wanted your script to trigger
Then select the Output Type and double click on Processing Routine
Then go to create new entries--> Select the Medium (1- print output), then enter your Script and Print Program detls --> Save and come out
Now go to the Transaction (for which you have created the output type)... Issue output--> Select the output type --> Print....
Device Types for SAP Output Devices (Detail Information)
Definition
The device type indicates the type of printer to be addressed. When you define an output device, choose the name of the device type that was defined in the SAP System for your printer model, such as Post2 for a PostScript printer. In the case of frontend printing under Microsoft Windows, you can also use the generic (device-independent) device type SWIN.
The system uses the information in the device type to convert a document from the internal SAP character representation (spool request in OTF or in text format) to a device-specific, print-ready data stream (output request). Since a device type specifies attributes that apply to all devices of a certain model, it can be shared among device definitions. For example, all devices in the SAP spool system that are compatible with Hewlett-Packard LaserJet IIID printers would use the HPLJIIID device type.
You should not confuse the device type with the printer driver. The device type is the total of all attributes of an output device that the SAP System must know to control the output device correctly, such as control commands for font selection, page size, character set selection, and so on. These attributes also include the printer driver that SAPscript/Smart Forms (the SAP form processor) should use for this printer. The SAPscript printer driver that is to be used for devices of this type for output formatting is therefore only an attribute that the device type specifies.
How do I choose the correct device type?
In most cases, the SAP System already provides the appropriate device type for the printer type for the printer model that you want to use.
These standard device types are completely defined and need no modification or extension before you use them in device definitions.
You can also download missing device types from the sapserv server. For a current list of the supported device types, see SAP Note 8928 in the SAP Service Marketplace.
Most printers can be controlled using a generic format, such as PostScript. They can be switched to a mode that is compatible with one of the standard printers for which an SAP device type is available. In this case, a supported model is emulated.
Almost all printers are delivered with Microsoft Windows printer drivers. The system can control these printers with the generic (device-independent) device type SWIN. The Microsoft Windows spool system then performs the processing of the print data.
If the specified device types are not available, and generic device types cannot be used, you must create your own device type or edit a copy of an existing device type. We recommend that only those with specialist knowledge of the SAP Spool System and printer driver code do this. For more information, see Defining a New Device Type .
Attributes of a Device Type
A device type is distinguished by the attributes listed below. If you change an existing device type or create a new device type, you must change at least some of these attributes.
Character set: A character set specifies the codes with which characters must be represented in the print-ready output stream (output request). This code replaces the generic SAP characters set that is used internally by the SAP spool system (spool request).
Printer driver: You can specify different printer drivers for printing SAPscript documents and ABAP lists.
Print controls: Print controls represent printer operations, such as boldface or changing the font size. These print control are replaced by printer-specific commands during the creation of the output request from a spool request.
Formats: Formats specify the format supported by the SAP system. The system differentiates between SAPScript formats (DINA4 and LETTER) and ABAP list formats (X_65_132 = 65 rows/132 columns).
Page format: A page format is the interface between a format and SAPscript. It specifies the paper dimensions with which SAPScript can calculate the row and column lengths.
Actions: Actions are output device-specific commands that are required for the implementation of a format. The action printer initialization, for example, can contain a printer command with which the number of rows on a page is defined. There is a set of actions for every format supported by a device type.
Output Determiantion :
You can use output control to automate either messages or subsequent processing of partner-specific messages"
This means, it provides a method for you to perform subsequent processing once a document is saved in the system. This subsequent processing is normally to print the document, but can also include activities such as:
- Faxing the document
- Emailing the document
- Sending an idoc of the document
- Sending an EDI message for the document (via an Idoc)
- and so on.
In general, it uses the condition technique to determine what, if any, output is to be produced. The condition technique works by selecting key fields from the document (document type, plant, etc.) and matching them to master data records you have previously set up. If there is a match, then output is produced.
You can use transaction NACE for the output determination settings for all applications.
1. When you start transaction NACE, a list of all represented applications appears.
2. From this initial screen, you can access all the individual processing screens for output determination from the EDIT menu.
3. Select the relevant application. This transaction does not have a menu path in customizing.
Refer the following links.
http://help.sap.com/saphelp_crm40/helpdata/en/b3/58bf39f7568648e10000000a11402f/content.htm
http://help.sap.com/saphelp_erp2004/helpdata/en/c8/19878343b111d1896f0000e8322d00/frameset.htm
http://help.sap.com/saphelp_erp2004/helpdata/en/c0/4e4746497d11d385ee0000e81ddea0/content.htm
<b>Reward points for useful Answers</b>
Regards
Anji

Is it possible to configure a smartform in QGA3 instead of the standard script QM_INSP_RESULT.

Is it possible to configure a smartform in QGA3 instead of the standard script QM_INSP_RESULT.

Hello ,
I'm afraid not , the program for the transaction is admitting only Sapscript format , even the BADI
QG_INSP_RESULT_PRINT allow to switch to a SAPscript form
Regards

NOTE TO PAYEE

Hi
The requirement is as below
EBS is loaded into SAP and when it is processed, the open item gets cleared automatically and a clearing document is being generated.
Client requires that the NOTE TO PAYEE info to be captured in the TEXT field of the clearing document.
Is there any standard functionality or customized user exit is required?
This is very urgent please. Points will be assinged.
Thanks
Ashok

Hi,
A note to payee is a field on a data medium containing information on paid line items relevant for the business partner.
Number and length of the note to payee fields are defined in the payment medium format, whilst the content itself is defined in the note to payee.
SAP provides predefined notes to payee that you can adapt for your own formats. Notes to payee are structured according to the following methods:
With Customizing in SAPScript format
With a function module
With a combination of Customizing and function module
U can make the settings for Notes to Payees in Customizing
Financial Accounting > Accounts Receivable and Accounts Payable > Business Transactions > Outgoing Payments > Automatic Outgoing Payments > Payment Media > Make Settings for Payment Medium Formats from Payment Medium Workbench > Adjust Note to Payee
The note to payee consists of a maximum of 6 different line types:
1. Main note to payee for description of the payment, for example with the payment of invoices in the lines there is the invoice number, the invoice date, and/or the invoice amount.
2. Internal short reference for your company for identification of the transaction in case of failed payment. This could be the number of the payment document, for example.
3. External short reference for your business partner, a contract/customer number, for example.
4. Payment advice note that replaces the lines of type 1 where there is not sufficient space available.
How it is integrated?
The note to payee is independent of format, a separate entity that exists alongside the formats. You can assign the note to payee to a format via the payment method and the origin. You can assign a note to payee to several formats, thus minimizing the effort involved.
I hope you understood and found useful
Regards,
Jigar

General questions

hi,
i have some doubts in reports.pls tell the answers.
which contain the details of all name of the programs and forms?
difference between pooled and cluster tables?
what are output types and tcodes?
what are the main events that are used in alv reports?
thanx and regrads
priya

Hi
which contain the details of all name of the programs and forms?
In TNAPR table you will find them.
difference between pooled and cluster tables?
Pooled table
Pooled tables can be used to store control data (e.g. screen sequences,
program parameters or temporary data). Several pooled tables can be
combined to form a table pool. The table pool corresponds to a physical
table on the database in which all the records of the allocated pooled
tables are stored.
Cluster table
Cluster tables contain continuous text, for example documentation.
Several cluster tables can be combined to form a table cluster. Several
logical lines of different tables are combined to form a physical record
in this table category. This permits object-by-object storage or
object-by-object access. In order to combine tables in clusters, at
least part of the keys must agree. Several cluster tables are stored in
one corresponding table on the database.
what are output types and tcodes?
Output is a link between the Driver Program and the Sapscript,
An output type summarizes messages of the same meaning. It contains parameters that are valid for all its assigned messages, for example appropriate partner functions.
Transmission medium is a medium which the layout will be come out, this may be printout, Fax or Mail
Check this link.
http://help.sap.com/saphelp_nw2004s/helpdata/en/c8/19884743b111d1896f0000e8322d00/content.htm
ex-how to config output type.
You will assign output types using Transaction NACE.
Do the follow steps to assign output type
1)Select Application Type V2 which will have description Shipping.
2)Click on Output types button.
3)Go to change mode by pressing Ctrl+F4.
4)Select one output type which already exists
5)Do Copy As(F6)
6)Give your output type against Output Type field.
7)Under General data Tab, Give Program and Form routine and Save the data.
i think it a work of functional guy but at senior level i think it is not a big deal for abaper.
Check the following documentation
In NACE t-codewe have the application for each one. based on the application output type can be defined, based on output type script and print progrma can be defined.
If suppose data can be read from EDI then we should go for condition records.
So whenever we execute the script first composer checks the output type and then execute the program. in program whenever opn form FM will be populate then script will open first. After that again program till another FM will populate if it then script will populate........like it is cycle proces. Composer does all these things and at last it will submit that output to spool.
Go to the Transaction NACE.
choose the related sub module.. like billing or shipping
doubel click on Output Types
Choose the Output Type for which whcih you wanted your script to trigger
Then select the Output Type and double click on Processing Routine
Then go to create new entries--> Select the Medium (1- print output), then enter your Script and Print Program detls --> Save and come out
Now go to the Transaction (for which you have created the output type)... Issue output--> Select the output type --> Print....
Device Types for SAP Output Devices (Detail Information)
Definition
The device type indicates the type of printer to be addressed. When you define an output device, choose the name of the device type that was defined in the SAP System for your printer model, such as Post2 for a PostScript printer. In the case of frontend printing under Microsoft Windows, you can also use the generic (device-independent) device type SWIN.
The system uses the information in the device type to convert a document from the internal SAP character representation (spool request in OTF or in text format) to a device-specific, print-ready data stream (output request). Since a device type specifies attributes that apply to all devices of a certain model, it can be shared among device definitions. For example, all devices in the SAP spool system that are compatible with Hewlett-Packard LaserJet IIID printers would use the HPLJIIID device type.
You should not confuse the device type with the printer driver. The device type is the total of all attributes of an output device that the SAP System must know to control the output device correctly, such as control commands for font selection, page size, character set selection, and so on. These attributes also include the printer driver that SAPscript/Smart Forms (the SAP form processor) should use for this printer. The SAPscript printer driver that is to be used for devices of this type for output formatting is therefore only an attribute that the device type specifies.
How do I choose the correct device type?
In most cases, the SAP System already provides the appropriate device type for the printer type for the printer model that you want to use.
These standard device types are completely defined and need no modification or extension before you use them in device definitions.
You can also download missing device types from the sapserv server. For a current list of the supported device types, see SAP Note 8928 in the SAP Service Marketplace.
Most printers can be controlled using a generic format, such as PostScript. They can be switched to a mode that is compatible with one of the standard printers for which an SAP device type is available. In this case, a supported model is emulated.
Almost all printers are delivered with Microsoft Windows printer drivers. The system can control these printers with the generic (device-independent) device type SWIN. The Microsoft Windows spool system then performs the processing of the print data.
If the specified device types are not available, and generic device types cannot be used, you must create your own device type or edit a copy of an existing device type. We recommend that only those with specialist knowledge of the SAP Spool System and printer driver code do this. For more information, see Defining a New Device Type .
Attributes of a Device Type
A device type is distinguished by the attributes listed below. If you change an existing device type or create a new device type, you must change at least some of these attributes.
Character set: A character set specifies the codes with which characters must be represented in the print-ready output stream (output request). This code replaces the generic SAP characters set that is used internally by the SAP spool system (spool request).
Printer driver: You can specify different printer drivers for printing SAPscript documents and ABAP lists.
Print controls: Print controls represent printer operations, such as boldface or changing the font size. These print control are replaced by printer-specific commands during the creation of the output request from a spool request.
Formats: Formats specify the format supported by the SAP system. The system differentiates between SAPScript formats (DINA4 and LETTER) and ABAP list formats (X_65_132 = 65 rows/132 columns).
Page format: A page format is the interface between a format and SAPscript. It specifies the paper dimensions with which SAPScript can calculate the row and column lengths.
Actions: Actions are output device-specific commands that are required for the implementation of a format. The action printer initialization, for example, can contain a printer command with which the number of rows on a page is defined. There is a set of actions for every format supported by a device type.
OUTPUT EXECUTION TCODES
ME9F - Pur Order Output
ME9A - RFQ Output
ME9K - Contract Output
MB90 - GRN Output
VA02/VA03 - Sales order Output
VF03/VF02 - Invoice output
VL71   - Delivery Output
VT70 - Shipment Output
VL74 - Handling Unit Output
what are the main events that are used in alv reports?
REUSE_ALV_EVENTS_GET
Description
This table tells ALV which events are processed by the caller by CALLBACK.
The table of possible events per list type can be initialized using the module REUSE_ALV_EVENTS_GET.
You can display the names of the constants in the type pools SLIS which represent the individual events using the individual test function in the function module
REUSE_ALV_EVENT_NAMES_GET. Only events with a form routine name are processed.
The table structure contains the fields:
     IT_EVENTS-NAME
Name of the Callback event.
Possible Callback events:
     Action
USER_COMMAND USING R_UCOMM LIKE SY-UCOMM RS_SELFIELD TYPE SLIS_SELFIELD
Process actions on the list
As this is a frequently-used Callback event, the form routine can also be passed directly in the interface in the IMPORTING parameter I_CALLBACK_USER_COMMAND.
PF_STATUS_SET USING RT_EXTAB TYPE SLIS_T_EXTAB
If a user list status is to be set, it must be done in the form routine assigned to this event. The ALV function codes, which must not be active, are in the Parameter RT_EXTAB. This table must be passed with the SET PF-STATUS command (with inactive user function codes as well, if necessary).
The STANDARD status of the function group SALV should be used as a template for a user-specific status.
As this is a frequently-used Callback event, its form routine can also be passed directly in the interface in the IMPORTING parameter I_CALLBACK_PF_STATUS_SET.
ITEM_DATA_EXPAND USING RS_SELFIELD TYPE SLIS_SELFIELD RFLG_ALL TYPE C
Only relevant for hierarchical-sequential lists using the layout parameter IS_LAYOUT-EXPAND_FIELDNAME of the structure IS_LAYOUT.
Exit for passing item entries (ITEM table) for a header record which was expanded interactively by the user.
RS_SELFIELD-TABINDEX contains the header table index for which the item entries are to be put in the global item output table (T_OUTTAB_SLAVE). The Callback is only called if ALV has no items for a header which is to be expanded.
RFLG_ALL is passed with 'X' if the user shows all items. The application must ensure that entries are not repeated in the item table. RS_SELFIELD is initial in this case.
CALLER_EXIT USING RS_DATA Is called at the beginning of the function module to make special settings. It is not usually used.
     List processing events
IMPORTANT: The application Callback routine must not manipulate the internal output table and/or its header record. This restriction applies to all Callbacks which are called in the list output and run under the 'List processing events'.
TOP_OF_LIST no USING parameter. Information output at the start of the list
END_OF_LIST no USING parameter. Information output at the end of the list
TOP_OF_PAGE no USING parameter
Equivalent to the list processing TOP-OF-PAGE event
END_OF_PAGE no USING parameter. Not available for hierarchical-sequential lists.
Information output at the end of a page. This is only called for printing.
TOP_OF_COVERPAGE no USING parameter
The selection information and list status are output together (if they exist) on a separate page by default. See also the documentation of the parameters:
IS_PRINT-NO_COVERPAGE
IS_PRINT-NO_PRINT_SELINFOS
IS_PRINT-NO_PRINT_LISTINFOS
IS_LAYOUT-GET_SELINFOS
The user can format the header area of the 'cover page' himself or herself by specifying a Callback routine for this event.
END_OF_COVERPAGE no USING parameter
Analogously to TOP_OF_COVERPAGE the user can add other information to the information output by ALV (selection information, list status) at this event.
FOREIGN_TOP_OF_PAGE no USING parameter
The Top-of-page event is always processed in ALV and is only passed to the caller via the Callback mechanism. This is still the case if the caller, e.g. by a user action, processes a branch list which was not formatted by ALV (e.g. a popup with additional information about the list record selected and displayed by ALV).
In this case, top-of-page cannot be formatted by ALV analogously to the basic list, it must be handled completely by the caller. The event top-of-page still occurs in ALV. When ALV notices a top-of-page which was not caused by an ALV output, the form routine in FOREIGN_TOP_OF_PAGE is called.
FOREIGN_END_OF_PAGE no USING parameter
The event end-of-page is always processed in ALV and only passed to the caller via callback. This is still the case, e.g. when the caller processes a details list which was not formatted by ALV (e.g. a popup with further information about selected list records which were displayed by ALV).
In this case, end-of-page cannot be formatted by ALV analogously to the basic list, it must be handled completely by the caller. The event end-of-page still occurs in ALV. When ALV notices an end-of-page that was not caused by an ALV output, the form routine in FOREIGN_END_OF_PAGE is called.
BEFORE_LINE_OUTPUT USING RS_LINEINFO TYPE SLIS_LINEINFO
Output information before each output line. Should only be used in justified cases because it costs a lot of performance.
AFTER_LINE_OUTPUT USING RS_LINEINFO TYPE SLIS_LINEINFO
Output information after each output line. Should only be used in justified cases because it costs a lot of performance.
     Internal use only
LIST_MODIFY USING R_TABNAME TYPE SLIS_TABNAME
R_INDEX LIKE SY-TABIX
R_INDEX_ITEM LIKE SY-TABIX
R_INDEX_SUM LIKE SY-TABIX
     IT_EVENTS-FORM
Name of the form routine which should be called in the calling program at the event.
Field_catalog:
Field catalog with field descriptions
2.7.1.     Description
Field catalog containing descriptions of the list output fields (usually a subset of the internal output table fields). A field catalog is required for every ALV list output.
The field catalog for the output table is built-up in the caller's coding. The build-up can be completely or partially automated by calling the REUSE_ALV_FIELDCATALOG_MERGE module
See also the documentation of the function module REUSE_ALV_FIELDCATALOG_MERGE.
The minimal field catalog is documented under 'default'. The caller can use the other optional parameters to assign output attributes to a field which differ from the default.
A field catalog need not be built-up and passed explicitly only under the following conditions:
     The internal table to be output has the same structure as a Data Dictionary structure which is referred to in the internal table declaration using LIKE or INCLUDE STRUCTURE.
     all fields in this structure are to be output
     the structure name is passed to ALV in the parameter I_STRUCTURE_NAME.
See also the documentation of the IMPORTING paramter I_STRUCTURE_NAME.
Positioning
     row_pos (row position)
value set: 0, 1 - 3
Only relevant if the list output is to be multi-line (two or three lines) by default.
A multi-line list can also be defined by the user interactively if the default list is one-line.
The parameter specifies the relative output line of the column in a multi-line list.
     col_pos (column position)
value set: 0, 1 - 60
only relevant when the default relative column positions differ from the field catalog field sequence. The parameter specifies the relative column position of the field in the list output. The column order can be changed interactively by the user. If this parameter is initial for all field catalog entries, columns appear in the field catalog field sequence.
Identification
     fieldname (field name)
value set: internal output table field name (required parameter)
Name of the internal output table field which is described by this field catalog entry
     tabname (internal output table)
value set: SPACE, internal output table name
This parameter is used in 'manual' field catalog build-up only for hierarchical-sequential lists.
Name of the internal output table which contains the field FIELDCAT-FIELDNAME.
Data Dictionary reference
     ref_fieldname (reference field name)
value set: SPACE, Data Dictionary field name
Name of the Data Dictionary field referred to.
This parameter is only used when the internal output table field described by the current field catalog entry has a reference to the Data Dictionary (not a program field), and the field name in the internal output table is different from the name of the field in the Data Dictionary. If the field names are identical, naming the Data Dictionary structure or table in the FIELDCAT-REF_TABNAME parameter is sufficient.
     ref_tabname (reference table/structure field name)
value set: SPACE, name of a Data Dictionary structure or table
Structure or table name of the referred Data Dictionary field.
This parameter is only used when the internal output table field described by the current field catalog entry has a Data Dictionary reference (not a program field).
Reference to fields with currency/measurement unit
Each internal output table sum or quantity field whose decimal places are to be formatted appropriately for the unit in the list must follow the convention:
     the field is of data type QUAN or CURR (internal type P) (the field must really have this physical data type. Overwriting the physical data type with the parameter FIELDCAT-DATATYPE has no effect)
     There is a field in the internal output table which contains the associated unit.
     There is also an entry in the field catalog for the unit field.
(If the unit is not to appear as a column in the list, and cannot be interactively displayed as a column, e.g. because it is always unambiguous and is therefore explicitly output by the caller in the list header, the field catalog units field entry can take the parameter FIELDCAT-TECH = 'X'.
The association of a value field to a unit affects the output as follows:
     appropriate decimal places display for the unit
     an initialized field with a link to a non-initial unit is output as '0' for the unit (if FIELDCAT-NO_ZERO is initial). When this field is summed, this unit affects whether the units are homogeneous.
     an initialized field with a link to an initial unit is output as SPACE. When this field is summed, the unit SPACE does not affect the homogeneity of the units.
     When non-initial fields with an initial unit are summed, the unit SPACE is considered to be a unit.
Link to currency unit
     cfieldname (currency unit field name)
value set: SPACE, output table field name
Only relevant for amount columns with associated unit.
Name of the internal output table field containing the currency unit associated with the amount field FIELDCAT-FIELDNAME. The field in FIELDCAT-CFIELDNAME must have its own field catalog entry.
     ctabname (internal currency unit field output table)
value set: SPACE, output table field name
only relevant for hierarchical-sequential lists
Name of the internal output table containing the FIELDCAT-CFIELDNAME field.
Link to measurement unit
     qfieldname (measurement unit field name)
value set: SPACE, output table field name
only relevant for quantity columns with unit link.
Name of the internal output table field containing the measurement unit associated with the quantity field FIELDCAT-FIELDNAME.
The field in FIELDCAT-QFIELDNAME must have its own field catalog entry.
     qtabname (internal measurement unit field output table)
value set: SPACE, output table field name
only relevant for hierarchical-sequential lists
Name of the internal output table containing the FIELDCAT-QFIELDNAME field.
Column output options
     outputlen (column width)
value set: 0 (initial), n
For fields with a Data Dictionary link this parameter can be left initial.
For fields without a Data Dictionary link (program field) the parameter must be given the value of the desired field list output length (column width).
initial = column width is the output length of the referred Data Dictionary field (domain).
n = column width is n characters
     key (key column)
value set: SPACE, 'X'           'X' = kex field (key field output in color)
Key fields can not be interactively hidden. Parameter FIELDCAT-NO_OUT must be left initial.
For exceptions see the documentation of the FIELDCAT-KEY_SEL parameter.
     key_sel (hideable key column)
value set: SPACE, 'X'
only relevant when FIELDCAT-KEY = 'X'
Key field which can be hidden interactively.
The key column sequence cannot be changed interactively by the user.
The output is controlled by the FIELDCAT-NO_OUT parameter analogously to non-key fields.
     no_out (field in field list)
value set: SPACE, 'X'          'X' = field is not displayed in the current list.
The user can interactively choose the field for output from the field list.
The user can display the contents of these fields at line level using the 'Detail' function.
See also the 'Detail screen' documentation of the parameter IS_LAYOUT.
     tech (technical field)
value set: SPACE, 'X'          'X' = technical field
Field cannot be output in the list and cannot be displayed interactively.
Field can only be used in the field catalog (not in IT_SORT, ...).
     emphasize (highlight columns in color)
value set: SPACE, 'X' or 'Cxyz' (x:'1'-'9'; y,z: '0'=off '1'=on)
'X' = column is colored with the default column highlight color.
'Cxyz' = column is colored with a coded color:
     C: Color (coding must begin with C)
     x: color number
     y: bold
     z: inverse
     hotspot (column as hotspot)
value set: SPACE, 'X'
'X' = column cells are output as hotspots
     fix_column (fix column)
value set: SPACE, 'X'
Not relevant for block lists (output of several lists consecutively)
'X' = column fixed (does not scroll horizontally)
All columns to be fixed must have this flag, starting from the left. If a column without this flag is output, only the columns to the left of this column are fixed. The user can change the column fixing interactively. See also the documentation of the Layout parameter
IS_LAYOUT-NO_KEYFIX of the IMPORTING paramter IS_LAYOUT.
     do_sum (sum over column)
value set: SPACE, 'X'           'X' = a sum is to be calculated over this internal output table field.
This function can also be called by the user interactively.
     no_sum (sums forbidden)
value set: SPACE, 'X'          'X' = no sum can be calculated over this field, although the data type of the field would allow summing.
     input (column ready for input)
Function not available
Format column contents
     icon
value set: SPACE, 'X'           'X' = column contents to be output as an icon.
The caller must consider the printability of icons.
     symbol
value set: SPACE, 'X'          'X' = column contents are to be output as a symbol.
The internal output table column must be a valid symbol character.
The caller must consider the printability of symbols.
Symbols can usually be printed, but may not always be output correctly, depending on the printer configuration.
     just (justification)
value set: SPACE, 'R', 'L', 'C'
Only relevant for fields of data type CHAR or NUMC
' ' = default justification for this data type
'R' = right-justified output
'L' = left-justified output
'C' = centered output
The justification of the column header always follows the justification of the columns. Independent justification of the column neader is not possible.
     lzero (leading zeros)
value set: SPACE, 'X'
Only relevant for fields of data type NUMC
ALV outputs NUMC fields right-justified without leading zeros by default.
'X' = output with leading zeros
Note: If a NUMC field is output left-justified or centered by FIELDCAT-JUST, leading zeros are output. If the output of leading zeros is suppressed by a Data Dictionary reference ALPHA conversion exit, the output is always left-justified.
     no_sign (no +/- sign)           Only relevant for value fields
value set: SPACE, 'X'     'X' = value output without +/ sign
     no_zero (suppress zeros)           Only relevant for value fields
value set: SPACE, 'X'          'X' = suppress zeros
     edit_mask (field formatting)
value set: SPACE, template
template = see documentation of WRITE formatting option USING EDIT MASK template
The output conversion conv can be made by template = '== conv'.
Texts
The following text parameters should be specified for program fields without a Data Dictionary reference. The texts are taken from the Data Dictionary for fields with a Data Dictionary reference. If this is not desired, the text parameters can also be specified. The Data Dictionary texts are then ignored. If the user changes the column width interactively, the column header text with the appropriate length is always used. The interactive function 'Optimize column width' takes account of both the field contents and the column headers: if all field contents are shorter than the shortest column header, the column width depends on the column header.
The 'long field label' is also used in display variant definition, sort, etc. popups.
     seltext_l (long field label)
     seltext_m (medium field label)
     seltext_s (short field label)
     reptext_ddic (header)
analogous to the Data element maintenance 'Header'
The specified text is not necessarily output in the list, an optimum among all texts is sought.
     ddictxt (specify text)
value set: SPACE, 'L', 'M', 'S'
You can specify with values 'L', 'M', and 'S', the keyword that should always be used as column header. If the column width changes, no attempt is made in this case to find an appropriate header for the new output width.
Parameters for program fields without Data Dictionary reference
see also 'Text' parameters
     datatype (data type)
value set: SPACE, Data Dictionary data type (CHAR, NUMC,...)
Only relevant for fields without Data Dictionary reference
Program field data type
     ddic_outputlen (external output length)
value set: 0 (initial), n
Only relevant for fields without Data Dictionary reference whose output is nevertheless to be modified by a conversion exit.
Prerequisites:
     FIELDCAT-EDIT_MASK = '==conv'
see also the documentation of the parameter FIELDCAT-EDIT_MASK
     FIELDCAT-INTLEN = n
see also the documentation of the parameter FIELDCAT-INTLEN
n = external format field output length
The column width FIELDCAT-OUTPUTLEN need not be the same as the external format output length (FIELDCAT-DDIC_OUTPUTLEN).
     intlen (internal output length)
value set: 0 (initial), n
Only relevant for fields without Data Dictionary reference whose output is nevertheless to be modified by a conversion exit.
Prerequisites:
     FIELDCAT-EDIT_MASK = '==conv'
see also the documentation of the parameter FIELDCAT-EDIT_MASK
     FIELDCAT-DDIC_OUTPUTLEN = n
see also the documentation of the parameter FIELDCAT-DDIC_OUTPUTLEN
n = internal format field output length
     rollname (data element)
value set: SPACE, Data Dictionary data element name
F1 help can be provided for a program field without a Data Dictionary reference, or F1 help which differs from the Data Dictionary help can be provided for a field with a Data Dictionary reference, using this parameter.
When F1 help is called for this field, the documentation of the specified data element is displayed.
If the FIELDCAT-ROLLNAME is initial for fields with a Data Dictionary reference, the documentation of the data element of the referred Data Dictionary field is output.
Others
     sp_group (field group key)
value set: SPACE, CHAR(1)
Field group key.
Keys are assigned to group names in the IT_SPECIAL_GROUPS parameter (see also the documentation of the parameter IT_SPECIAL_GROUPS).
When such an assignment is made in the field catalog and in IT_SPECIAL_GROUPS, the fields are grouped correspondingly in the display variant popup.
     reprep (Report/Report interface selection criterion)
value set: SPACE, 'X'
Prerequisites:
     The system contains the Report/Report interface (function group RSTI, table TRSTI)
     Parameter LAYOUT-REPREP = 'X'
(see also the documentation of the parameter LAYOUT-REPREP of the IMPORTING parameter IS_LAYOUT )
'X' = When the Report/Report interface is called, the value of this field is passed in the selected interface start record as a selection criterion.
2.7.2.     Default
     The following entries are usually sufficient for internal table fields with a reference to a field defined in the Data Dictionary :
     fieldname
     ref_tabname
Notes:
ALV gets the remaining information from the Data Dictionary.
If no relative column position (COL_POS) is specified, the fields are output in the list in the order in which they were added to the field catalog.
REF_FIELDNAME need only be specifid when the name of the internal table field differs from the name of the referred Data Dictionary field.
Information which is explicitly entered in the field catalog is not overwritten by information from the Data Dictionary.
Priority rule:
Entries in the field catalog have priority over differing entries in the Data Dictionary.
     The following entries are usually sufficient for internal table fields without a reference to the Data Dictionary (program fields):
     fieldname
     outputlen
     datatype
     seltext_s
     seltext_m
     seltext_l
Notes:
F1 help can be provided for program fields by assigning a data element to the parameter ROLLNAME.
If the parameters SELTEXT_S, SELTEXT_M, SELTEXT_L, and REPTEXT_DDIC contain appropriate field labels, the program field column headers are also adjusted appropriately when the column width changes.
Reward points for useful Answers
Regards
Anji

Sapscript Formatting

Similar Messages

Maybe you are looking for