SAP script version history
Hello form experts,
is there a possibility to get a version history of SAP script forms?
I have to know who changed when and what exactly in a form window.
Thanks for any help!
Christian
Hi,
To display the versions of a form, choose Utilities -> Versions.
The version list includes the following information:
* Version and status:
* New
No active version, not available for use as yet.
* Active
The current form is the active version, in effect in the System.
* Revised
The current form is being changed. There are active and edit versions of the form.
* Translated
The current form must be translated.
* Current language key
* Original language of the form.
* Description of the form.
To display detailed information on a version of the form, put the cursor on the version and choose Form info.
Regards
Rajesh Kumar
Similar Messages
-
Hi,
We have moved some changes for a SAP Script from development to test system. Now we have realized that the version of the SAP Script on which we have made the changes is not the same as the version in production. My questions are:
1) How can I synchronize the version in development and production, so that I can start doing the changes again on the same version of the SAP Scriipt as production?
2) Is there anyway to download the production version of SAP Script and upload it to development?
Thanks in advance.
Mick
Edited by: Rob Burbank on Jan 27, 2010 3:22 PMThis is not critical for me, but the 16 step-by-step procedure is:
1) Find the person who changed the SAPscript.
2) Take their *** to the basis team and explain the situation to them.
3) Publish their *** in a BSP for the development department to see on the Enterprize Portal.
4) Make them use emergency repairs using their own ID and not DDIC.
5) Transport the clean changes through.
6) Deactivate DDIC's password in SU01...
7) Remove DDIC from all batch jobs and job steps, except during upgrades.
8) etc
9) ...
If you read help.sap.com before making a mess then it helps to a large extent.
Cheers,
Julius -
Version Management on SAP Script Forms
Hello,
Is there a version management for SAP Script forms
like what we have in ABAP programs?
I need to revert back the old version of my SAP scrip form like what I used to do in an ordinary ABAP program.
Is this possible?
Need your views on this.
Thank you very much,
Jeffrey A. PradoHello Jeffrey,
as far as I know there are just two versions stored in the system, the active one and the one you work on. As long as you do not activate your work, you should be able to track your changes. The other way (which I use) is to save the original version with another name and simply load it back when needed. Since we are working with an old Release I do not how it looks in the "new world".
Greetings,
Sebastian -
Hi,
How can we know the version of Sap script like Reports?????
Edited by: subas Bose on Jun 26, 2008 4:52 PMHi,
Sorry, Version management is not there for SAP Scripts.
Below is What u can get is released versions in the script
Use Tcode SE03 ---> select SEARCH FOR OBJECTS IN REQUESTS/TASKS.
and execute in the object selection u have many selections like PROG,FUGR, CLASS etc.. in the blank space give FORM and press enter, enable the check box and give the form name and execute.
it displays all the released requests and tasks .
Thanks
Vikranth -
What are the print modes available in the sap scripts?
Hi
Parent Topic: SAPScript
HOWTO:Sap script
Edit this entry - Discuss - Rename - Watch - History -
Major contributors: gopang, cmurphy262 | All Contributors
Your votes have been tallied! See which wiki entry took top honors and find out who is this year's Wiki Ironman. View the winners.
White Papers
Do You Need a Fax Server? A Special Guide on Fax Servers and SAP Electronic Document Delivery
Achieving Real-Time Supply Chain Integration
E-Invoicing for Business Process Efficiency with SAP(R) Systems
Jobs
SAP Consultants (Any City) - SD, MM, PP, FI/CO, CS, ABAP (Dice)
SAP ABAP LEAD (Dice)
SAP ABAP Workflow Developer -Contract (Dice)
Community Content
3 days until GO-LIVE!!! (Blogs)
RE: RE: RE: RE: RE: Lost connection when using tcode FS00 (Groups)
SAP SCRIPT
Table of contents Show TOCHide TOC
1. 1 Concepts
1.1. 1.1 Modifying SAP Forms
1.2. 1.2 Forms: Concepts
1.3. 1.3 Client and Language Versioning: Concepts
2. 2 Componentes
2.1. 2.1 Header Data
2.2. 2.2 Paragraph Formats and Attributes
2.2.1. 2.2.1 Standard Paragraph Attributes
2.2.2. 2.2.2 Font Attributes for Paragraphs
2.2.3. 2.2.3 Tabs in Paragraph Formats
2.2.4. 2.2.4 Paragraph and Heading Numbering
2.3. 2.3 Character Formats and Attributes
2.3.1. 2.3.1 Standard Attributes for Character Formats
2.3.2. 2.3.2 Font Attributes for Character Formats
2.4. 2.4 Windows
2.4.1. 2.4.1 Default Paragraph
2.5. 2.5 Pages
2.5.1. 2.5.1 Defining Follow-On Pages in Duplex Print Modes
2.5.2. 2.5.2 Testing Tray Selection and Print Mode Selection
2.6. 2.6 Page Windows
2.7. 2.7 Text Elements
2.7.1. 2.7.1 Default Text Element
2.8. 2.8 Main Window
3. 3 Técnicas
3.1. 3.1 Displaying Versions of Forms
3.2. 3.2 Including Graphics
3.2.1. 3.2.1 Using Boxes, Lines, and Shading
3.2.2. 3.2.2 Supported Printers
3.2.3. 3.2.3 Boxes, Lines, Shading: BOX, POSITION, SIZE
3.2.3.1. 3.2.3.1 BOX Command
3.2.3.2. 3.2.3.2 POSITION Command
3.2.3.3. 3.2.3.3 SIZE Command
3.2.4. 3.2.4 Pre-Setting BOX Position Arguments
3.2.5. 3.2.5 Using the Commands in Texts and Forms
3.2.6. 3.2.6 Tips and Guidelines
4. 4 Design Tools
4.1. 4.1 Form Components
4.2. 4.2 Processing in Overview
4.2.1. 4.2.1 Defining Header Data
4.2.1.1. 4.2.1.1 Completing the Header Data After Defining the Attributes
4.2.1.2. 4.2.1.2 Passing Data to an External Program
4.2.2. 4.2.2 Defining Paragraph Formats
4.2.3. 4.2.3 Defining Character Formats
4.2.4. 4.2.4 Defining Pages
4.2.5. 4.2.5 Defining Windows
4.2.6. 4.2.6 Using Text Elements in Page Windows
4.2.7. 4.2.7 Defining Page Windows
4.2.7.1. 4.2.7.1 Filling Page Windows with Text
4.2.8. 4.2.8 Using Text Elements in Page Windows
4.2.9. 4.2.9 Defining Main Windows in Page Windows
4.3. 4.3 Test-Printing a Form
5. 5 Releasing Forms
6. 6 SAPscript Control Commands
6.1. 6.1 Syntax of Control Commands
6.2. 6.2 Explicit Page Break: NEW-PAGE
6.3. 6.3 Preventing Page Breaks: PROTECT
6.4. 6.4 Next Main Window: NEW-WINDOW
6.5. 6.5 Assigning a Value to a Text Symbol: DEFINE
6.6. 6.6 Formatting Date Fields: SET DATE MASK
6.7. 6.7 Formatting Time Fields: SET TIME MASK
6.8. 6.8 Country-Dependent Formatting: SET COUNTRY
6.9. 6.9 Position of the Leading Sign: SET SIGN
6.10. 6.10 Initializing Numbered Paragraphs: RESET
6.11. 6.11 Including Other Texts: INCLUDE
6.12. 6.12 Changing the Style: STYLE
6.13. 6.13 Formatting Addresses: ADDRESS
6.13.1. 6.13.1 Parameters
6.14. 6.14 Setting a Footer Text in the Main Window: BOTTOM
6.15. 6.15 Conditional Text: IF
6.16. 6.16 Finding a Match: CASE
6.17. 6.17 Calling ABAP Subroutines: PERFORM
6.18. 6.18 Inserting Print Controls: PRINT-CONTROL
6.19. 6.19 Boxes, Lines, Shading: BOX, POSITION, SIZE
6.20. 6.20 Hexadecimal Data: HEX, ENDHEX
6.21. 6.21 Summing a Program Symbol: SUMMING
6.21.1. 6.21.1 Summing and Carrying Forward is Incorrect
7. 7 SAPscript Symbols
7.1. 7.1 Syntax of Symbols
7.2. 7.2 System Symbols
7.2.1. 7.2.1 Current Date
7.2.2. 7.2.2 Current Day Number
7.2.3. 7.2.3 Current Month Number
7.2.4. 7.2.4 Current Year Number
7.2.5. 7.2.5 Current Day Name (Long Form)
7.2.6. 7.2.6 Current Month Name (Long Form)
7.2.7. 7.2.7 Current Time
7.2.8. 7.2.8 Hours Component of Current Time
7.2.9. 7.2.9 Minutes Component of Current Time
7.2.10. 7.2.10 Seconds Component of Current Time
7.2.11. 7.2.11 Current Page Number
7.2.12. 7.2.12 Page Number of the Next Page
7.2.13. 7.2.13 Selected Device Type
7.2.14. 7.2.14 Spaces
7.2.15. 7.2.15 Underline
7.2.16. 7.2.16 Vertical Line
7.3. 7.3 Program Symbols
7.3.1. 7.3.1 SYST: System Fields in the ABAP Programming Environment
7.3.2. 7.3.2 USR03: User Address Data
7.3.3. 7.3.3 SAPSCRIPT: General SAPscript Fields
7.4. 7.4 Standard Symbols
7.5. 7.5 Text Symbols
7.6. 7.6 Formatting Options
7.6.1. 7.6.1 Offset
7.6.2. 7.6.2 Output Length
7.6.3. 7.6.3 Omitting the Leading Sign
7.6.4. 7.6.4 Leading Sign to the Left
7.6.5. 7.6.5 Leading Sign to the Right
7.6.6. 7.6.6 Omitting Leading Zeros
7.6.7. 7.6.7 Space Compression
7.6.8. 7.6.8 Number of Decimal Places
7.6.9. 7.6.9 Omitting the Separator for Thousands
7.6.10. 7.6.10 Specifying an Exponent for Floating Point Numbers
7.6.11. 7.6.11 Right-Justified Output
7.6.12. 7.6.12 Fill Characters
7.6.13. 7.6.13 Suppressing Output of Initial Values
7.6.14. 7.6.14 Ignoring Conversion Routines
7.6.15. 7.6.15 Changing the Value of a Counter
7.6.16. 7.6.16 Preceding and Subsequent Texts (Pre-Text / Post-Text)
7.7. 7.7 Country-Dependent Formatting
7.7.1. 7.7.1 Date Mask
7.7.2. 7.7.2 Time Mask
7.8. 7.8 Formatting Conventions
7.8.1. 7.8.1 Primary Formatting of System Symbols
7.8.2. 7.8.2 Primary Formatting of Standard Symbols
7.8.3. 7.8.3 Primary Formatting of Program Symbols
7.8.4. 7.8.4 Primary Formatting of Text Symbols
7.8.5. 7.8.5 End Formatting
1 Concepts Edit section
1.1 Modifying SAP Forms Edit section
If you want to modify SAP forms, set up your development environment as follows:
1. Make sure that no SAP-standard forms are stored as client-specific copies in your development client. Such forms should be held only in client 000, the SAP development and installation client. If you access an SAP-standard form from another client, then the central copy in client 000 is used.
If you need to remove SAP-standard objects from your development client, see Notes 10388 and 3355 in the SAP Online Service System (OSS). These notes explain the procedure for saving modified forms and then deleting all forms.
2. To modify SAP standard forms,
Copy the forms you need from client 000 to your development client.
Rename the forms using a name from the customer name reserve (names starting with Y or Z).
Copy the forms to one of your own Y or Z development classes.
Renaming the SAP standard object makes it possible to manage and transport your changes with the SAP workbench organizer. The organizer is not activated for SAP-standard objects that are modified in clients other than 000.
3. To put your modifications into effect, you must also modify the ABAP print program used to print documents that use this form. You should rename such print programs and store them in your own Y or Z development classes.
You can use the SAP Customizing System to replace the SAP print program with your modified print program in the affected applications
1.2 Forms: Concepts Edit section
Forms are used to control the page layout and also the text formatting in your documents. Before formatting a document for output to the screen or to a printer, you must assign a form to it. If you do not specify a form for a document, then the SYSTEM form is assigned to the document by default.
Application-specific forms are used in SAP applications to specify the page layout for such special documents as invoice or checks. These forms specify the structure of the information on the page(s) of such a document. They define, for example, the address header, item lines, the footer, and so on. There are two ways to format texts with forms:
In the standard SAPscript text processing (Tools  Word processing  Standard text), you can select a form for a document. You can then type text into the main window of the form and output the document in the format defined in the form.
For example, you can select a form for a letter. You can then type the body text of the letter in the main window. When you print the letter, the default text elements in the other windows of the form (heading, footer, and so on) are printed with the body text.
A document can be generated by a print program in one of the SAP applications. The print program uses a form to generate the document. Most correspondence and document generation in the SAP System are handled by way of print programs.
A print program selects the text elements that are to be printed in the windows of a form. It may also collect information from the user or ask the user to input text directly, as in some correspondence functions. The print program may also provide data for variables defined in the form.
Finally, the print program uses the form to format the document for display or printing.
1.3 Client and Language Versioning: Concepts Edit section
Forms and styles are client-specific. That is, a form or style other than the SAP standard in client 000 is available only in the client in which it was created.
Forms and styles are also language-specific. That is, the definitions and texts in a form or style are defined for a particular language. Forms and styles can be translated using the standard SAP translation tools.
Client 000 Defaulting: SAPscript accords forms and styles in client 000 a special status.
If a form or style that is used in a document is not available in the client in which the document is being printed, then SAPscript checks for the form or style in client 000. If it is found there, then the client 000 version is used to print the document.
SAP standard forms and styles are always held in client 000. You can take advantage of the client 000 defaulting as well by storing your Yxxx and Zxxx forms and styles there. That way, if a local version of a form or style is not present in a client, the client 000 version is used instead.
Language rules: SAPscript uses the following rules to manage versions of forms and styles in different languages:
The language in which a form or style is created is its "original language." You can translate a form or style into other languages using SAPs translation tools.
If a form or style is needed only in its original language and need not be translated, then you can indicate this in the language attributes in the header data. The form or style then does not appear in work lists in the translation tools.
In versions other than the original language version, changes to a form or style are limited only to translation of texts. No changes to definitions and attributes are permitted.
2 Componentes Edit section
2.1 Header Data Edit section
You can find header data in both form and style maintenance. In style maintenance, it is used primarily to present important information information designed to make it easier for the end user to select a style. The header data in form maintenance, on the other hand, is used for information and control purposes. For this reason, the header data of a form will be described in more detail.
Below, the header data is described as it appears in the alphanumeric Form Painter.
Like the header data of a style, the header data of a form comprises two parts: the data set by the system and the data you are expected to enter. The latter is dealt with separately.
Device-independent entries.
Description
A short explanatory description of the form (also applies to the style), designed to make selection easier for the end user.
Form class
You can assign a form to a class to help you organize and search for forms. The default set of classes is the set of program classes in your system.
Start page
Tells the print program which page format in a form to use first for printing.
Default paragraph
Paragraph set to * in standard text maintenance.
Tab stop
A grid set at specified intervals in all windows defined in the form. However, you should note that the tab stops are only valid in paragraphs where you have not defined your own tabs.
Language, Original language, Translation applic
Use these fields to record the master language and language of the current version of a form. Marking Translation applic makes the form accessible for translation from the SAP Systems translation tools (transaction SE63).
Device-dependent entries.
You can only enter values here that are supported in the R/3 printer definition. If you make other entries, this leads to errors in the check routine.
Page format
Determined from the spool administration table with transaction SPAD. Make sure there is a printer assignment there must be an additional spool format for the printer with the same page format.
Orientation
Depends on the page format selected. This can also be determined from the spool administration table. Please note that the formats landscape and portrait are not supported by all printers.
Lines per inch (LPI)
Basis for converting the unit of measurement LN in style and form maintenance. The value 6.00 is set by the system, as this value is supported by all printers.
Characters per inch (CPI)
Basis for converting the unit of measurement CH in style and form maintenance. The value 10.00 is set by the system, as this value is supported by all printers.
Font attributes
With these fields, you can set the default font for a form. The default font applies if other objects do not specify a font. SAPscript suggests a default font, which you can change.
2.2 Paragraph Formats and Attributes Edit section
In SAPscript, paragraphs are formatted using formats and their corresponding attributes. Text processing is simplified by the use of different paragraph attribute groups:
Standard
Font
Tabs
Outline
There are naming conventions for paragraph tags:
The paragraph tag can have one or two characters.
The first character in the paragraph tag must be a letter, the second a letter, number, or blank; special characters are not valid.
The paragraph format must be identified in the Description field.
2.2.1 Standard Paragraph Attributes Edit section
In the Standard attribute group, you find the general attributes that can be defined in paragraph formats:
Description
Precise explanation of your paragraph tag, so that the user can immediately identify it.
Left or right margin
Amount of space between the paragraph and the left or right border of the form window.
Indent first line
Indent of the first line of a paragraph. If the value is positive, it is indented to the right, if it is negative, it is indented to the left.
If you specify a negative value, then you must place the minus sign after the number: 1- .
Space before and space after
Space before and space after control the amount of space between paragraphs. The actual space between paragraphs results from the space after the preceding paragraph and the space before the following paragraph.
Alignment
Alignment of a paragraph.
Left-aligned
LEFT
Right-aligned RIGHT
Centered CENTER
Justified BLOCK
Line spacing
Spacing between the lines. The default value is 1 line; the LPI value (lines per inch) in the header data is used to calculate the line spacing.
No blank lines
Suppression of blank lines. You can control whether the blank lines of a paragraph should be suppressed in the printout or not:
No entry
blank lines not suppressed
X blank lines suppressed
Page protection
Cohesion of a paragraph. It is possible to determine whether or not a paragraph can be divided by a page break.
No entry
no page protection (default)
X all lines of the paragraph are on one page
Next paragraph same page
Cohesion of two adjacent paragraphs. Here you can define whether the subsequent paragraph should begin on the same page (that is, at least the first line of the subsequent paragraph must be on the same page).
No entry
subsequent paragraph is output on the same page or the next page, depending on the amount of space (default)
X subsequent paragraph begins on the same page
2.2.2 Font Attributes for Paragraphs Edit section
You can specify font attributes for paragraph formats. They control the font used in the text. You can specify these attributes both for the default font in the header and for particular paragraph formats:
Font family
Enter a font supported in the SAPscript font maintenance.
Font size
Enter the size of a character font. It is measured in 1/10 point.
Bold/Italic
Specify whether to use bold-face printing or italics.
Underlined
Mark this attribute to underline entire blocks of text.
When defining a paragraph format, use More to specify these underline attributes:
Spacing between the base line and the underline
Thickness
Intensity
Intensity is expressed in percent: 0 % is a black underline; 100 % is no underline.
If you defined default underlining in the header, then the fields for underline attributes are already displayed on the screen.
The following selection criteria apply to the font attributes bold, italics, and underlined:
Off attribute is not set
Retain inherited
On attribute is set
The combination of font family, font size, bold type attribute and italics attribute is referred to as a system font or SAP font. To use the SAPscript font maintenance, choose Tools  Word processing  Font.
2.2.3 Tabs in Paragraph Formats Edit section
You can define as many tab positions as you require for each paragraph format. The text can be aligned in different ways:
Left-aligned with LEFT
Right-aligned with RIGHT
Centered with CENTER
At the sign with SIGN
At the comma or decimal point with DECIMAL
You can control the tab feed in a paragraph with tab positions. The tab stops you define in the paragraph format replace the tab spacing you defined in the header data of the form. However, this depends on the extent to which you have defined tab stops in the paragraph format. If there are fewer tabs in the paragraph formats than in the header data, the tab stops of the header data are used for the rest of the line. The tab stops are represented as, , in the text editor.
You can use different units of measurement to define a tab position:
CH Characters
CM Centimeters
MM Millimeters
PT Points
TW Twips (1/20 point)
The unit of measurement CH is converted to an absolute unit of measurement using the CPI value (characters per inch) from the header data of the form.
2.2.4 Paragraph and Heading Numbering Edit section
The paragraph numbering and marking attributes are used to structure texts into chapters, subchapters, and sections. Numbering is carried out automatically by SAPscript.
You can create an outline with the entry options available:
Outline
Enter the name of the highest-level paragraph in an outline hierarchy here. The outline hierarchy is created by assigning this paragraph to all outline paragraphs.
Outline level
Enter the level in the outline hierarchy. The outline levels of the paragraphs are numbered upwards from 1; the highest outline level therefore has the outline number 1.
Number margin
Specify the space between numbering and window border. Note that your numbering may extend into the text area of the paragraph if the difference between the left margin and the number margin is not great enough to hold the numbering characters.
Left/right delimiter
Specify the character that precedes or follows the numbering.
Number chaining
Specify whether you want the paragraph numbering of the paragraph to be preceded by the numbering of all higher paragraphs in the hierarchy.
Example for number chaining
with without
3. 3.
3.1 1.
3.2 2.
3.2.1 1.
Character string
Specify the numbering format. The numbering can be assigned a different font or character format to the rest of the paragraph.
Numbering type
ARABIC
Arabic numerals: 1, 2, 3.
CHAR Fixed character: letter or numeral, entered in the field
LETTER Letters: A-Z
ROMAN Roman numerals: I, II, III, IV
Depending upon the numbering type that you select, the following attributes may also apply:
Fixed character
Define the fixed character to be used for numbering. You should only make an entry in the field Fixed character if you have specified CHAR as the numbering type. Fixed characters include + - and o .
Output length
Enter the number of characters for Arabic numerals.
Upper case
Specify for letters or Roman numerals.
2.3 Character Formats and Attributes Edit section
Character formats, as opposed to paragraph attributes, allow you to format entire blocks of text within a paragraph.
Character attribute groups can be:
Standard
Font
When you define character formats, observe the following naming conventions:
The character format can have one or two characters.
The first character must be a letter, the second a letter, number, or blank; special characters are not valid.
Enter a simple explanation in the field Description. It is intended to help the user make a selection.
2.3.1 Standard Attributes for Character Formats Edit section
Marker
Links a search key to the selected character string when the end user uses this character format. Examples include glossary, hypertext, and data element links. Here, selected character strings are assigned the appropriate key.
Bar code
Bar code that is required for certain variables and is known to the printer, for example EAN8. The character string is printed as a bar code if the character string concerned is selected.
Bar code names, such as EAN8, refer to system bar codes. These are defined in the SAPscript font maintenance (Tools  Word processing  Font).
Protected
The character string is not split by a line break, but printed together on the next line.
Hidden
The character string is not printed. The text is only visible in the text editor.
Superscript/subscript
The character string is printed half a line higher or lower.
The following options are available for defining these attribute types:
Off
Attribute is not set
Retain Attribute is inherited
On Attribute is set
2.3.2 Font Attributes for Character Formats Edit section
Font attributes can be specified for character formats as well as for paragraph formats. You have the same options as for defining font attributes for paragraph formats.
2.4 Windows Edit section
Windows are defined in form maintenance. They represent areas that are positioned on pages as page windows and in which at a later time text is printed. You must define at least one window for each form. Otherwise, SAPscript cannot format the text.
You can assign window names and window types. However, note that you can define only one main window per form.
Use one of these window types:
MAIN
Main window in which continuous text is printed. This is the window used by dialog users of a print program and form. For example, the body text of a letter would be entered in MAIN.
The text in the main window can extend over several pages. If the text fills one page, output continues in the window of the next and subsequent pages, as long as MAIN has been defined for these pages.
VAR
Window with variable contents. The text can vary on each page in which the window is positioned. Variable windows are formatted for each page.
To every window you can assign text, which is printed in the corresponding window when the form is formatted. To assign text, use text elements, which are stored with the form.
To create and maintain text elements with the SAPscript Editor, choose Text elements. Should the text selected for the window exceed the window size, then the text is cut off.
CONST
Window with constant contents that is formatted only once.
Currently, CONST windows are processed in the same way as VAR windows. You should only use windows of type VAR.
2.4.1 Default Paragraph Edit section
For a particular window, you can override the default paragraph format that is set in the form header. Enter the default format that should apply in the window in the Default paragraph field in the window definition screen.
2.5 Pages Edit section
You must define at least one page for every form. And you must designate a "first" page in the form header. Otherwise text formatting is not possible. In addition, you should inform the system which page is to be used after reaching the end of the first page. If you do not specify a next page, the output of your text ends at the end of the current page.
To define a page, give it a name and specify attributes for it:
Name of the next page
Page counter mode
INC Increases the counter by 1
HOLD Counter remains unchanged
START Sets the counter to 1
You can display the contents of the page counter with the system symbol&PAGE&.
Numbering type of the page counter
ARABIC Arabic numerals
LETTER Letters
ROMAN Roman numerals
Although CHAR is displayed as an entry option for the numbering type of the page counter, internally CHAR is converted to ARABIC.
Output length for page numbering with numerals
Upper or lower case for numbering with Roman numerals or letters
Resource name
With Resource name, you specify that the paper for this page should be taken from a particular paper tray at the printer.
In Resource name, enter the print control that has been defined for switching to the paper tray you want to use. In printer types pre-defined by SAP, these print controls are generally as follows:
TRY01 Select first paper tray
TRY02 Select second paper tray (if available at the printer)
TRY03 Select third paper tray (if available at the printer)
TRYEN Print envelopes (if available at the printer)
TRYMN Switch the printer to manual paper feed (if available at the printer). The printer pauses until you feed a sheet of paper into it.
TRYME Switch the printer to manual envelope feed (if available at the printer). The printer pauses until you feed an envelope into it.
You can use all tray selection print controls except TRY03 with suitably equipped printers that are defined with the following SAP device types: HPLJSTND, HPLJ_II, HPLJIIID, HPLJ4, LX4039, and SNI20XX8.
You can use TRY01, TRY02, TRY03, and TRYMN on suitably equipped printers that are defined with these device types: KYOF1000, KYOF1200, KYOFS1500.
See the spool system (transaction SPAD) to check on how your printers are defined.
Print mode
With Print mode, you can specify single- or double-sided printing for a page. You can choose from the following values:
' ' Currently active printing mode continues unchanged.
S The page is printed in simplex mode. That is, the printer should print on only one side of the paper. If another mode was previously active, then the printer is switched to simplex mode with the start of the page.
D The page is printed on the first side of a sheet in duplex mode. If another mode was previously active, then the printer is switched to duplex mode with the start of the pageand continues in this mode.
T The page is printed on the first side of a sheet in tumble duplex mode. That is, the printer prints on both sides. The page on the second side is always inverted, so that the footer of the second page is printed opposite the header of the first page.
If another mode was previously active, then the printer is switched to tumble duplex mode with the start of the page and continues printing in this mode.
Print modes are currently supported for printers that use the PCL-5 language. These are printers that are defined with the following SAP device types: HPLJ_II, HPLJIIID, HPLJ4, LX4039, SNI20XX8.
See the spool system (transaction SPAD) to check on how your printers are defined.
The print controls for these functions are SPMSI (begin simplex printing); SPMDU (begin duplex printing); SPMTU (begin tumble duplex printing); SPMFS (print on first side of sheet in duplex or tumble duplex mode); and SPMBS (print on second side of sheet in duplex or tumble duplex mode).
2.5.1 Defining Follow-On Pages in Duplex Print Modes Edit section
You switch to duplex or tumble duplex mode with a form page for which one of these modes is specified. To continue printing in the current mode, for follow-on pages you must define another page in which the Print mode field is empty. Otherwise, the following pages after the mode switch will continue to be printed only on the front sides of new sheets of paper.
The reason: When SAPscript sends a page with Print mode D or T to the printer, it not only sets the print mode accordingly. To ensure that the first page in the new mode is correctly output, SAPscript also instructs the printer to output the page on the front side of a sheet. If SAPscript sends a sequence of D or T pages to the printer, the output is printed only on the front side of each sheet.
You define a first page named FIRST for a form to be printed in duplex mode. You therefore set the Print mode in FIRST to D.
To make the duplex printing work correctly, you must define a second page FOLLOWER in which Print mode is left empty. In the form definition, you specify FOLLOWER as the follow-on page for FIRST and for itself as well.
Your text is then printed in duplex mode. FIRST switches the printer to duplex mode and forces printing of the first page on the front side of a new sheet. FOLLOWER accepts the duplex mode and sends no further mode print controls to the printer. The printer therefore alternately prints FOLLOWER pages on the fronts and backs of sheets.
2.5.2 Testing Tray Selection and Print Mode Selection Edit section
SAP provides predefined SAPscript documents with which you can test whether tray selection and print mode selection are working properly on your printers.
For tray selection, print the SAPscript document SAPSCRIPT-TRAYTEST, ID ST, Language D or E.
For print mode selection, print the SAPscript document SAPSCRIPT-PRINTMODETEST, ID ST, Language D or E.
2.6 Page Windows Edit section
When you define page windows, the window names are linked to page names. You must specify the position and size of the window on the assigned page.
Define the position of a window by specifying the left margin and upper margin and the size of a window by specifying its width and height.
Left margin
Space between the window and left margin of the page
Upper margin Space between the window and upper margin of the page
Window width Width of the window depending on the page format selected
Window height Height of the window depending on the page format selected
Note that the width of the main window must be the same on all pages. All other window types can have different sizes and positions on different pages.
To print multiple columns, define several main windows on a page. As text entry is continuous, once the first main window has been filled, output continues in the second main window.
Rewards if helpfull
Regards
Pavan -
What is the diff b/w Sap Scripts and Smart Forms
Hi,
Whats the diff b/w SAP Scripts and Smart Forms..
I need the internal explanation for both Smart Forms and SAP Scripts mean when we execute what happens whether Print Program r Forms starts execution 1st and SIMILARLY FOR SMARTFORMS WHETHER FM'S R FORMS.
Thanks & Regards,
Gopi.Hi
Difference with SMARTFORMS vs. SapScript(SE71)
The Following are the differences :-
a) Multiple page formats are possible in smartforms which is not the case in SAPScripts
b) It is possible to have a smartform without a main window .
c) Labels cannot be created in smartforms.
d) Routines can be written in smartforms tool.
e) Smartforms generates a function module when activated.
f) Unlike sapscripts (RSTXSCRP), you cannot upload/download Smartform to your local harddisk.
It was said that it was provided in CRM 3.0 version, but not available in R/3. You can download smartforms into Local PC in a XML format. In the same way you can upload this XML format into Smartform. From the smartform editor itself you can call download option, if you are working in CRM 3.0 environment.
In R3 also, you can download into XML format. However, it's not sure about uploading. Refer to the program 'SF_XSF_DEMO'.
In 4.7 Enterprise, other have seen this utlity which is completey missing in 4.6c. There is functionality to downlaod a complete form or only a particular node. (Utilities -> Download form). It will create a XML file and save it in the hard disk.
For others, if you want to download/upload the Smartforms source, you will need the help from the Basis people. What you can do is to create a Transport and then FTP down to your local harddisk. When you need the Smartform source in another system, you have FTP up the Smartforms file back to the SAP server. Finally, the Basis team, will tp it into your system.
g) The protect and endprotect command in sapscript doesn't work with smartforms. For example on a invoice: First data of position no 80. is printed on page one, other data of position no 80 is printed on page 2. And there's nothing you can do about it. Actually, there is something you can do about it. By using a folder node and checking the 'protect' checkbox, everything in that folder will be page protected.
check out this link:
http://www.sap-img.com/smartforms/sap-smart-forms.htm
Reward points if helpful.
Regards,
Swathi. -
SAP Scripting Languages on the SDN Day - Amsterdam
I would like to give a short summary of what happened on the SDN Day in Amsterdam, the 17-th Oct. 2006.
After the breakfast Craig Cmehil gave us a welcome to the event and presented the schedule. We started with a power networking session: Four 20-minute Sessions with Six SDNers per Table. As I was sitting at the Scripting Languages table, I would like to share some impressions of the atmosphere there. We talked much about the emmerging SAP Scripting Tool and how much value it will bring to all scripting projects that plan to utilize SAP backend systems. We discussed Gregor Wolf's contest and he was so kind to inform us that his test system is also available inside the SAP corporate network, so all SAP employees now can participate too. Gregor works for Siteco Beleuchtungstechnik GmbH and the award they offer for the contest is a Siteco Vistosa task light. More information about the contest can be found at https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/4588. [original link is broken] [original link is broken] Another key discussion was held with Björn Schotte, the chief editor of PHP Magazine, Germany, presenting also his company Mayflower Gmbh. He shared some visions on business applications of PHP and stated that PHP is definitely enterprise ready.
Then after a very short pause we started the SDN breakout sessions (3-5 in parallel). I visited the sessions of Gregor Wolf, André Labahn, Björn Schotte and after this I cooperated for the breakout session of Frank Mittag.
Session 1:
Connecting Typo3 to R/3 Enterprise via Web Services with Gregor Wolf from Siteco Beleuchtungstechnik GmbH
Siteco Beleuchtungstechnik GmbH currently implements a customer service centre into it's Typo3 based website. Typo3 is an Open Source Web Content Management system based on the Scripting Language PHP. The application will allow Siteco's customers to directly check price & availability of products from the backend R/3 Enterprise system, quotations, orders and delivery status. The backend connectivity uses Web Services utilise the PEAR SOAP Package.
Session 2:
SAP supports Scripting Languages with Andre Labahn from SAP.
This session will provide you with more insights on how SAP is supporting scripting languages.
Session 3:
Scripting Languages PHP and Enterprise Software with Björn Schotte (Chief Editor from PHP Magazine).
This session showed us a brief history of PHP and PHP in Germany. Some enterprise applications of PHP were discussed. Björn Schotte was the opinion that PHP is definitely enterprise ready and he proved it with an example of a system that his company has created for Siemens.
Session 4:
Scripting Languages Tool with Frank Mittag and Vasil Bachvarov (me) from SAP
SAP will provide a open source tool to the scripting development community that is supporting the access to SAP Backend Systems via RFC/BAPIs and Webservices. See the concept and demo of the tool and discuss this with SAP Development.
There was a pretty interesting discussion about the tool. Since the time for the last session shrinked with some minutes we had to be very quick, but Frank Mittag did a great job and succeeded to explain the basic concept of the SAP Scripting Tool and show it in action for the tough time constraint.
There were a lot of questions from the audience but it was already 18:30 and we stopped at this point. There would be a second chance for questions on thursday when Frank had the opportunity to make a more complete and comprehensive walk-through of the project.
Then we gathered in the meeting hall and Shai Agassi held a speech and made a summary of the event.
The evening finished in the BoomChicago theater where everybody received a delicious meal, drinks and a great amount of fun with the ChicagoBoom comic crew.
I would like to thank all people that made this event come true! See you soon in Bangalore.
Best Regards,
Vasil Bachvarov
SAP AGI'm be there in Amsterdam as well. In fact I am leaving the US on Sunday and arriving early Monday morning in Amsterdam.
I was planning to do a little site seeing on Monday Afternoon. If anyone else is arriving a bit early as well, they are welcome to join me. It is always more fun to site see in groups. My email address is public in my SDN business card (also not too difficult to figure out ) if anyone is interested in meeting up. -
How to get the Version History of a stored document?
Hi,
I am trying to store and retrieve the content using Content Services features of ADEP 10.0.
I am able to store and retrieve content where as I am not able to get the version of the document. I am trying to store same or different document, but I donot get the version history or version label. Please guide me how I can get the version of a stored document.
Also, please advise me if there are simple alternative to do the same in ADEP10.
Please see below my sample code below:
package test.sample;
import java.io.File;
import java.util.*;
import com.adobe.idp.Document;
import com.adobe.idp.dsc.clientsdk.ServiceClientFactory;
import com.adobe.idp.dsc.clientsdk.ServiceClientFactoryProperties;
import com.adobe.livecycle.contentservices.client.CRCResult;
import com.adobe.livecycle.contentservices.client.impl.DocumentManagementServiceClientImpl;
import com.adobe.livecycle.contentservices.client.impl.UpdateVersionType;
public class AddContent {
public static void main(String[] args) {
try{
//Set connection properties required to invoke Document Services in EJB mode
Properties connectionProps = new Properties();
connectionProps.setProperty(ServiceClientFactoryProperties.DSC_DEFAULT_EJB_ENDPOINT, "jnp://localhost:1099");
connectionProps.setProperty(ServiceClientFactoryProperties.DSC_TRANSPORT_PROTOCOL,Service ClientFactoryProperties.DSC_EJB_PROTOCOL);
connectionProps.setProperty(ServiceClientFactoryProperties.DSC_SERVER_TYPE, "JBoss");
connectionProps.setProperty(ServiceClientFactoryProperties.DSC_CREDENTIAL_USERNAME, "administrator");
connectionProps.setProperty(ServiceClientFactoryProperties.DSC_CREDENTIAL_PASSWORD, "password");
//Create a ServiceClientFactory object
ServiceClientFactory myFactory = ServiceClientFactory.createInstance(connectionProps);
//Create a DocumentManagementServiceClientImpl object
DocumentManagementServiceClientImpl docManager = new DocumentManagementServiceClientImpl(myFactory);
//Specify the store and node name
String storeName ="SpacesStore";
String nodeName = "/Company Home/Test Directory";
//Retrieve the document to store in /Company Home/Test Directory
Document contentA = new Document(new File("C://Adobe/New files/Data-A.pdf"), false);
Document contentB = new Document(new File("C://Adobe/New files/Data-B.txt"), false);
Document contentC = new Document(new File("C://Adobe/New files/Data-C.xlsx"), false);
//Create a MAP instance to store attributes
Map<String,Object> inputs = new HashMap<String,Object>();
//Specify attributes that belong to the new content
String creator = "{http://www.alfresco.org/model/content/1.0}creator";
String description = "{http://www.alfresco.org/model/content/1.0}description";
inputs.put(creator,"Veeraganteppa Sajjan");
inputs.put(description,"A sample application form");
//Store MortgageForm.pdf in /Company Home/Test Directory
CRCResult resultA = docManager.storeContent(storeName,
nodeName,
"dataA.pdf",
"{http://www.alfresco.org/model/content/1.0}content",
contentA,
"UTF-8",
UpdateVersionType.INCREMENT_MAJOR_VERSION,
null,
inputs);
CRCResult resultB = docManager.storeContent(storeName,
nodeName,
"dataB.pdf",
"{http://www.alfresco.org/model/content/1.0}content",
contentB,
"UTF-8",
UpdateVersionType.INCREMENT_MAJOR_VERSION,
null,
inputs);
CRCResult resultC = docManager.storeContent(storeName,
nodeName,
"dataC",
"{http://www.alfresco.org/model/content/1.0}content",
contentC,
"UTF-8",
UpdateVersionType.INCREMENT_MAJOR_VERSION,
null,
inputs);
//Get the identifier value of the new resource
String idA = resultA.getNodeUuid();
String idB = resultB.getNodeUuid();
String idC = resultC.getNodeUuid();
System.out.println("A -The identifier value of the new content is "+idA);
System.out.println("B - The identifier value of the new content is "+idB);
System.out.println("C - The identifier value of the new content is "+idC);
System.out.println("A - The Browse Link is "+resultA.getBrowseLink());
System.out.println("B - The Browse Link is "+resultB.getBrowseLink());
System.out.println("C - The Browse Link is "+resultC.getBrowseLink());
System.out.println("A-The Version Label is "+resultA.getVersionLabel());
System.out.println("B-The Version Label is "+resultB.getVersionLabel());
System.out.println("C-The Version Label is "+resultC.getVersionLabel());
System.out.println("The Version History is "+docManager.getVersionHistory(storeName,nodeName, true));
}catch(Exception e)
e.printStackTrace();
Message was edited by: V B SajjanSorry I did not attach the output and errors. Please find the same below.
A -The identifier value of the new content is f5427f5b-c7c1-4c3c-b959-cb84e4e49a13
B - The identifier value of the new content is b237d22c-5ff5-4628-a83a-23f5e49ae48e
C - The identifier value of the new content is 34a9992c-3705-4488-bb55-6dd7ddfa0517
A - The Browse Link is http://localhost:8080/contentspace/wcs/api/node/content/workspace/SpacesStore/f5427f5b-c7c 1-4c3c-b959-cb84e4e49a13/dataA.pdf
B - The Browse Link is http://localhost:8080/contentspace/wcs/api/node/content/workspace/SpacesStore/b237d22c-5ff 5-4628-a83a-23f5e49ae48e/dataB.pdf
C - The Browse Link is http://localhost:8080/contentspace/wcs/api/node/content/workspace/SpacesStore/34a9992c-370 5-4488-bb55-6dd7ddfa0517/dataC
A-The Version Label is null
B-The Version Label is null
C-The Version Label is null
ALC-CSV-30015-000: com.adobe.livecycle.contentservices.client.exceptions.CSInvocationException: ALC-CSV-030-015-The node [/Company Home/Test Directory] is not versioned.
at com.adobe.contentservices.webscripts.impl.AbstractContentManager.doGetVersionHistory(Abst ractContentManager.java:1362)
at com.adobe.contentservices.webscripts.impl.ContentManagerImpl.executeParams(ContentManager Impl.java:198)
at com.adobe.contentservices.webscripts.impl.CSRetryingTransactionCallback.execute(CSRetryin gTransactionCallback.java:45)
at org.alfresco.repo.transaction.RetryingTransactionHelper.doInTransaction(RetryingTransacti onHelper.java:326)
at com.adobe.contentservices.webscripts.impl.ContentManagerImpl.execute(ContentManagerImpl.j ava:114)
at org.alfresco.repo.web.scripts.RepositoryContainer$2.execute(RepositoryContainer.java:333)
at org.alfresco.repo.transaction.RetryingTransactionHelper.doInTransaction(RetryingTransacti onHelper.java:326)
at org.alfresco.repo.web.scripts.RepositoryContainer.transactionedExecute(RepositoryContaine r.java:386)
at org.alfresco.repo.web.scripts.RepositoryContainer.transactionedExecuteAs(RepositoryContai ner.java:404)
at org.alfresco.repo.web.scripts.RepositoryContainer.executeScript(RepositoryContainer.java: 246)
at org.alfresco.web.scripts.AbstractRuntime.executeScript(AbstractRuntime.java:294)
at org.alfresco.web.scripts.AbstractRuntime.executeScript(AbstractRuntime.java:172)
at org.alfresco.web.scripts.servlet.WebScriptServlet.service(WebScriptServlet.java:122)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.j ava:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at com.adobe.idp.um.auth.filter.CSRFFilter.doFilter(CSRFFilter.java:86)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.j ava:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.j ava:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.ja va:183)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:95)
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEs tablishmentValve.java:126)
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEst ablishmentValve.java:70)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java: 158)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.ja va:598)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:451)
at java.lang.Thread.run(Thread.java:662) -
ABAP QUERY PROGRAM OUTPUT SHOULD DISPLAY FROM SAP SCRIPT.
THIS IS MY URGENT REQUIREMENT ...
I DONT KNOW ABAP QUERY PROGRAM ..
PLEASE SUGGEST ME A WAY ON THIS ....
Functional requirements
Introduction
The wish of the customer is a printable customer overview. All desired fields will be shown in a new query called ZZADDRSS_CO. Double entries are taken for granted because of the data taken from the sales area and because of multiple contact persons. The customer accepts this. It should be made possible that the user creates and saves its own variant.
A second overview is needed, another ABAP will be developed for this requirement. This ABAP will show all the customer data and this list will have the possibility to be printed.
Solution
New Query ZZADDRESS_CO
The desired fields of attachment 1 need to be shown in the query.
The selection criteria are shown in attachment 2.
The column names of the additional data have to changed in the query.
Customer Overview.
Functional specification.
On behalf of this customer overview a standard SAP transaction will be used (transaction VC/2).This transaction will be extended.
The fields are shown on screen with the described headers. Printing of the overview will be done via SAP script. The script makes use of a fixed layout of the data.
The selection criteria are specified in attachment 2.
The layout of the customer overview and the SAP Script are specified in attachment 3.
Specification.
The next steps need to be performed.
1. A routine per infoblock need to be created in Include RV77UNNN. In this routine the data is retrieved and written down to the screen and script,
Example LST1_901 . In include RV77SNNN you can find the standard infoblocks.
2. Adapt via transaction SE16 table TFRM.
3. Create a new view in the customizing (sales and distribution- Sales support-sales summary-Assign Reporting Views).Assign the new view to the infoblocks.(Example view 001 is assigned to block 901).
4. In customizing it is not possible to assign the correct window and element to the infoblock .so this is done via SE16 in table T182A.
5. Adapt script. Copy script SD-SALES-SUMMARY to a Z-SALES_SUMM.
Assign this new version to the new view in customizing. Create in the main window the element who writes the data on behalf of the print.
Attachment 1 Desired fields
Header: Address
~ Customer number KNA1-KUNNR
~ Title KAN1-ANRED
~ Name1 ADRC-NAME1
~ Name2 ADRC-NAME2
~ Name3 ADRC-NAME3
~ Name4 ADRC-NAME4
~ PO Box ADRC-PO_BOX
~ PO Box POSTAL CODE ADRC-POST_CODE2
~ PO Box city ADRC-PO_BOX_LOC
~ Telephone no1 ADR2-TEL_NUMBER 1ST RECORD
~ Telephone no2 ADR2-TEL_NUMBER 2ND RECORD
~ Fax number1 ADR3-FAX_NUMBER 1ST RECORD
~ Fax number2 ADR3-FAX_NUMBER 2ND RECORD
~ E-mail ADR6-SMTP_ADDR
~ Search item ADRC-SORT1
~ Notes ADRT-REMARK
Header: control data
~ VAT registration number KAN1-STCEG
Header: Payment transactions
~Bank country key KNBK-BANKS
~Bank key KNBK-BANKL
~Bank Account number KNBK-BANKN
Header: Marketing
~ Industry key KNA1-BRSCH
~ Industry code 1 KNA1-BRAN1
~ Industry code 2 KNA1-BRAN2
~ Industry code 3 KNA1-BRAN3
~ Industry code 4 KNA1-BRAN4
~ Industry code 5 KNA1-BRAN5
~Annual sales, currency, year KNA1-UMSA1, KNA1-UWAER, KNA1-UMAH
~ Yearly no of employees, year KAN1-JMZAH, KNA1-JMJAH
~ Fiscal year variant KNA1-PERIV
~Legal status KNA1-GFORM
Header: Correspondence
~ Our account number at customer KNB1-EIKTO
Header: sales
~ Sales office KNVV-VKBUR
~ Customer group KNVV-KDGRP
~ ABC-classification KNVV-KLABC
Header: Invoice
~Tax classification KNVI-TAXKD
~Terms of payment key KNVV-ZTERM
~
Header: Contact Persons
~Title KNVK-ANRED
~Name KNVK-NAME1
~Advertising material KNVK-NMAIL
~Martial Status KNVK-FAMST
~Notes KNVK-PARAU
~Function KNVK-PAFKT
~Department KNVK-ABTNR
Header: Partnerroles
~Personnel Number KNVP-PERNR
~Name of employee PA0001-ENAME
Header: Additional Data
~Attribute 1 KNA1-KATR1
~Creation date KNA1-ERDAT
~Attribute 2 KNA1-KATR2
~Change date of field KNA1-KATR2 CDHDR-UDATE
~Attribute 3 KNA1-KATR3
~Attribute 4 KNA1-KATR4
~Attribute 5 KNA1-KATR5
~Attribute 6 KNA1-KATR6
Attachment 2 Selection fields
~Customer number
~Sales office
~Personnel Number
~Sales Organization (default NL01)
~Industry key
~Industry codes (1 till 5)
~ABC- classification
~Creation date
~Attribute 1
~Attribute 2
~Attribute 3
~Attribute 4
~Attribute 5
Attachment 3 Customer overview + SAP Script
Customer master data sheet: 11490 Page1
Requested by karen Dunnewold Date: 25.08.2004
Address
(Default SAP script ADDRESS statement)
Title
Name1
Street + number
PO Box city
Country
Search term: ADRC-SORT1
Telephone 1: ADR2-TEL_NUMBER 2: ADR2-TEL_NUMBER
Fax 1: ADR3-FAX_NUMBER 2: ADR3-FAX_NUMBER
E-mail: ADR6-SMTP_ADDR
Notes: ADRT-REMARK
PO BOX
ADRC-PO_BOX
ADRC-POST_CODE2 ADRC-PO_BOX_LOC
T005T-LANDX (T005T-LAND1 = ADRC-COUNTRY)
Control data
VAT registration number: KNA1-STCEG
Payment transactions
Country: KNBK-BANKS Bank-key: KNBK u2013 BANKL Bank account: KNBK-BANKN
Marketing
Industry KNA1-BRSCH Industry Description
Industry code1 KNA1-BRAN1 Industry Description
Industry code2 KNA1-BRAN2 Industry Description
Industry code3 KNA1-BRAN3 Industry Description
Industry code4 KNA1-BRAN4 Industry Description
Industry code5 KNA1-BRAN5 Industry Description
Figures
Annual Sales KNA1-UMSA1, KNA1-UWAER in KNA1-UMAH
Employees KNA1-JMZAH in KNA1-JMJAH
Legal status KNA1-GFORM description
Customer master data sheet 11490 Page 2
Requested by karen Dunnewold Date: 25.08.2004
Contact Persons
KNVK-ANRED
Mailings: KNVK-NMAIL Notes: KNVK-PARAU
KNVK-ANRED
Mailings: KNVK-NMAIL Notes: KNVK-PARAU
Correspondence
Our account number at customer KNB1-EIKTO
Sales
Sales office KNVV-VKBUR Description
Customer group KNVV-KDGRP Description
ABC-classify KNVV-KLABC
Currency KNVV-WAERS
Invoice
Terms of payment key KNVV-ZTERM Tax classification KNV1-TAXKD
Description
Partner (Leave SAP default)
Partnerrole Number Name
KNVP-PARVW KNVP-KUNNR NAME1
KNVP-PARVW KNVP-KUNNR NAME1
Additional data
Attribute1 kna1-katr1 Description
Attribute2 kna1-katr2 Description
Attribute3 kna1-katr3 Description
Attribute4 kna1-katr4 Description
Attribute5 kna1-katr5 Description
Attribute6 kna1-katr6 Descriptionhi narayana
i think u need to write a driving program and a provided with a smatform u sit along with the SD consultant.
ur further views can be shared.
Rgs,
Venkat. -
SAP Script Check printing Layout, Line Items to display twice in First Page
Hi All,
This requirement is for US check printing Layout.
My Requirement is to display Items twice on the first page.
Eg : Main Window has 10 Items, I need to display all the Items at the bottom in another window at the bottom.
I can't create 2 Main windows in the first page, as the data from the Main window 1 overflows to Main window 2 in the first page.
I copied print program RFFOUS_C into a Z-version and try to implement the logic, however unable to print the line items in the bottom window.
Kindly give your valuable Inputs.
Thanks
VinayakHi
I had the same request for a check form in Canada. I solved it by writing the line item output into variables and print these variables in a second window. It was ~10 hours of effort, not a real nice technical solution but it worked.
If you require I can send you a PDF of the sap script form definition. You can contact me at [email protected] Answers can take 1 week or more.
Best regards
JD -
Sap script - Problem while printing Hungarian characters during Unicode
Hello Friends,
We had done unicode changes ie Version upgrade from 4.6 C to ECC and because of that sap script Hungarian characters are printing as Junk characters ex - #####.
Can any one please help me on this issue. In SO10 Print preview also we are facing same issue.
Thank you,
Regards,
PhaneendraHi Phaneedhra,
the below thread explains the font issue for Hungary..
SAPScript with Hungarian characters on it. Weh we review the output online it looks good, but when we print it we get a u2018#u2019 in place of Hungarian characters. I found the following link in SDN and am wondering if you can help.
Hungarian Character Printing problem
Problem in displaying special chars
Prabhudas -
Sending SAP Script output as a PDF attachment through mail
Dear Guru,
I am using SAP 4.0B version, DATABASE Oracle 8i, OS is sun solaris 7.5.
I want to send SAP script output as a
PDF attachement through mail.Please suggest a solution.
Regards,
RajeshHi Rajesh,
In your print program, while calling OPEN_FORM, pass options-TDGETOTF = 'X'. This is used for returning print output in OTF format.
Then in CLOSE_FORM, get the table OTFDATA returned from the function module. for example
DATA: OTF_DATA LIKE ITCOO OCCURS 0 WITH HEADER LINE.
CALL FUNCTION 'CLOSE_FORM'
IMPORTING
RESULT = RESULT
TABLES
OTFDATA = OTF_DATA.
now you can convert this OTF data to PDF using function module CONVERT_OTF
Then send this data as attachment to a mail using function module SO_NEW_DOCUMENT_ATT_SEND_API1
Regards,
Komal. -
If i got incorrect characters in the output of sap script? HOW TO CORRECT I
If i got incorrect characters in the output of sap script? HOW TO CORRECT IT?
Hi Sunil,
Debug the script and check where exactly those are getting populated. Definately you will get it. Check the conversion parts means character to numeric conversion.
If your version is 4.7E then select unicode check box in the reports attributes. It will display the error message so that we can solve very easily.Hope this helps you, reply for queries, Shall post you the updates.
Regards.
Kumar. . -
Translating for SAP Script in ECC 6.0
Hi All ,
How we can do the transalations for SAP Script in ECC6.0? . I was not able to do as we do in 4.7 version where we follow the following path
Translations -> Long texts -> forms .
Can any ody help me inthis regard ?
Thanks ,
Dharma .Hi Anirban,
I tried that way . When I entered Scripti name in the filed " Object Name" , it is giving warning message "Object not found"( actaully it is existing ) . Even i tried to select by F4, No thing I Could find .Transactional area defaultred to 999999( tried wiht blank also) .
Can any body help for any alternative ?
Thanks ,
Dharma . -
How to use Symbols or icons in SAP script
Hai ,
I am facing one problem in sap script , I want to display one of my field as icon (or )symbol ( tick mark ) in sap script . how to do . Particular transfer order ( check LTAP table ) having 10 line items . In 8 line items are confirmed ( pquit = 'X') others not confirmed . if LTAP-pquit = 'X' then instead of 'X' i need tick mark symbol .Icons and symbols in SAPscript texts
To print these, use output devices whose device type uses one of the following printer drivers:
· HPL2 (PCL-5 printers, such as HPLJ4, HPLJ5, HPLJ5SI, or HPLJ4000)
· POST (PostScript printers, such as POSTSCPT, or POST2)
· PRES (PRESCRIBE printers, such as KYOFS150, or KYOFS170)
· SWIN (device types SAPWIN/SWIN and country-specific versions)
Icons and symbols in ABAP lists
If you also want to print these characters in lists, you must define an output device with one of the following device types:
· HPLJ4000/HPLJ5000/HPLJ1100: Device types for PCL-5-printers
· KYOFS170: Device type for Prescribe II printers
· POST2: Device type for PostScript Level 2 printers
· SAPWIN/SWIN and the country-specific versions: generic, that is, device-independent device type for printing using Microsoft Windows
Maybe you are looking for
-
File Info panel is completely blank
Hello, I'm trying to add copyright information into my file metadata. When I go to File -> File Info, a window frame pops up but is completely blank inside, no text, no forms, no nothing. I have to press escape to get out of it and back to the prog
-
I'm trying to install MacPorts but need Xcode. WEhen I try to install Xcode I get a choose application message. I think it is because I am trying to install an OSX Mountain Lion version but I can't find a version for 10.6.8. Does anyone know where I
-
URGENT: ORA-12154: TNS:could not resolve the connect identifier specified
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 17001] Oracle Error code: 12154, message: ORA-12154: TNS:could not resolve the connect ide
-
Hi, I am trying to run PO Smartform but i am getting an error ' Table %Template 1 does'nt fit into window '. The Smartform is succesfully compiled but when i tried to print preview i am getting this message in result screen. Can i know the possible r
-
Overblown recording level-how to fix?
When recording an audio cassette tape into Soundbooth, how can I lower the audio level if it is too loud??