List of activities in SAP requiring printer maintenance

Dear All,
Can anybody help me to gather a list of standard activities/tasks that are performed in SAP and require printer maintenance.
What actually is required is a guide for IT staff to know that in this list of places in system the printer should be populated.
The point is that in one of the departments they removed old printers and installed new ones, but in RFFOEDI1, for example, they did not change old printer to new, which caused the print jobs to fail.
Now, the idea is to have a list of 'places' in SAP the IT has to check, before deleting printer from system.
Thank you for support and any advices or alternative ideas,

Ok, so in case anybody face the same error:
The starting point could be RSPO0040 report. It shows list of tables where printer is maintained.
Those, being brave can go further to developing their own TCode based on above report.
Hope that some day this post would save somebody's time.

Similar Messages

List of standard sap scripts/print programs in SAP MM and SD modules ??

Hi,
I have worked in medruck only. Can anyone give me a list of other standard sap scripts/print program names in SAP MM, FI/CO and SD modules, which often needs to be modified by the client ?
thanks

press f4 in SE71
then press application heirarchy, expand the modules which ever u want.
regards.
santhosh reddy
Reward if useful

SAP REx 3.2 Predefined list of activities for visit type while creating visit on iPad

Colleagues, our customer wants to have a different predefined list of activities for different visit types while creating a visit on iPad. I have seen such functionality in SAP Demo for REx 3.2 on iPad. Could you tell me what I should do to have such functionality?

Hello Viktor,
There are no REx customisation available to mainatin the set of activities that can be assigned to a visit.
In the REx iPAD & iPhone solution, all the surveys, journals and activities are shown together as activities.
For example in the first screenshot provided by you, for the newly created visit the activities shown plannogram check, trade assets, store sales performance and promotion compliance are the surveys and journals assigned to the CRM transaction type of the REx visit Business Review. We can assign activities which are customised in the SPRO path mentioned by me in the previous post. In the device when we go to the details of the visits and activities then we can see that the surveys and journals assigned to these activities are grouped seperatly.
So if want only specific activities (in iPAD & iPhone surveys and journals are activities) to be available for a visit then we should set the CRM customisation for surveys and journals accordingly.
Regards
Pramod

Print Maintenance Order Bulk/ List - Shop paper

Hi all,
As we can print maintenance Order in IW32 wrt the Shop Paper assigned to it, can we print list of Order as per the shop paper assigned to it .
This can be done through IW32 but in that we have do it one by one, can anyone suggest something from where list print of Order wrt shop paper can be done?
Thanks
DM

Have a look at IW38
PeteA

Sap scripts print modes

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

List of Tcodes in SAP(Technical)

Hi Gurus,
Send me a list of Tcodes in SAP.
Thanks in Advance,
Sakthi

Hello Shakthi,
Transactions:
search_sap_menu - Finds the menu path to a transaction - Can either type in TX code in the search criteria or a description- ie. 1st try SE38 and then ABAP.... the returned result is 'bottom to top'.
EDI Specific Transactions
VOE1 Translation between EDI categories and SD item categories
VOE2 Table EDSC view. Customer link to sales area detail
VOE3 Table view EDPVW. Add partner types that will be transferred to the IDoc
VOE4 Table view EDPAR. Link external partner number with our internal number
WEDI EDI Administrator Menu
BALE Idoc Administration
Scheduling agreements
OVA9 Create entries for each sold-to customer for which you will receive EDI schedule releases. At implementation, the only field that needs to be maintained is "Check PO number," which causes SAP to make sure that the PO number sent on the release matches the PO number on the schedule agreement. This transaction updates table T663A. SAP will not post an EDI schedule release, if this record is missing.
OVAI Create entries for each Vendor / Partner description combination. (Vendors must match sold-to Acct. at Cust., and Partner descriptions must match ship-to Partner descriptions.) This transaction updates table T661W. SAP uses this table to determine the schedule agreement sold-to partner.
OVAJ If you would like SAP to post schedule requirements using discrete dates only, instead of weekly and/or monthly buckets, you can indicate the days of the week that you deliver to this customer. SAP will divide the customer's quantity for a week or month evenly into the days of the week specified by the distribution function code. This code must be sent in the DELINS IDoc in field E1EDP16-ETVTF.
IDoc Transactions
WE09 / WE02 IDoc lists according to content. View IDocs via specific IDoc number or business application detail contained within the contents of a segment.
WE05 View IDocs
WE19 EDI test tool. Use to test inbound Function module changes.
WE20 Partner profile configuration. Add partner detail together with inbound and outbound relationships. We also incorporate message control on the outbound IDocs. Utilize the organizational units to trap functional errors for further processing
WE30 Create IDoc extension type
WE31 Segment create
WE57 Assign function module to logical message and IDoc type
WE60 IDoc type documentation tool
WE82 Link Release detail to Extension IDoc Type
BD55 Conversion rule user exit. Link conversion rule user exit to the different system \ partner combinations
BD87 Reprocess IDocs in error or waiting for action. (Both inbound and outbound in 4.6. Use BD88 in prior versions)
BALA ALE Application Distribution
BALM ALE Master Data Distribution
Output determination
856 - ASN
V/36 Maintain output determination for deliveries (Output determination procedures). V10000 (Header output) has condition type LAVA (usually with requirement 1 NB: Use V/84 V7ALLE SHAD for grouped ASNs. I.e. Group deliveries into shipments
VV21,VV22,VV23 Create output condition records for shipping. LAVA WE (Partner function) - We must add each new partner with VV21
VL71 Reissue output for deliveries
810 - Invoice
V/54 Maintain access sequence for billing documents
VV31,VV32,VV33 Create condition records for billing documents. (RD00 RE Billing party)
VF31 Reissue output for billing documents
855 Order Response
V/30 Sales document output types (BA00)
V/48, V/32, V/43 Maintain access sequence for sales documents
VV11,VV12,VV13 Create condition records for sales documents. (BA00 SP Sold to party)
Requirements coding
V/27 Create code to check requirements for output control. Used to check ZBA0 against BA00 output.
Sales & Distribution
Sales order / Quote / Sched Agreement / Contract
VA02 Sales order change
VA05 List of sales orders
VA22 Quotation change
VA32 Scheduling agreement change
VA42 Contract change
Billing
VF02 Change billing document
VF11 Cancel Billing document
VF04 Billing due list
FBL5N Display Customer invoices by line
FBL1N Display Vendor invoices by line
Delivery
VL02N Change delivery document
VL04 Delivery due list
VKM5 List of deliveries
VL06G List of outbound deliveries for goods issue
VL06P List of outbound deliveries for picking
VL09 Cancel goods issue
VT02N Change shipment
VT70 Output for shipments
General
VKM3, VKM4 List of sales documents
VKM1 List of blocked SD documents
VD52 Material Determination
Workflow
SWEAD Event queue administration
SWE2 Event type linkages
SWE3 Event linkages
PPOME Organizational Unit Maintenance
SWE5 Consistency Checks for Event Linkages
SWUD Workflow Diagnostic Tool
General
The following section provides detail on other useful SAP areas.
Create delivery via transfer orders
Once the order is saved proceed through the following steps. The process assumes the item has values in the warehouse bin.
VL04 Delivery due list. Run the delivery due with your order number to create the delivery
LT03 Create Transfer Order. EG. Warehouse: 101 and enter. Picking background. Save
The Transfer order should now be saved. It now needs to be confirmed.
In LT03 go to menu option Transfer Order -> Confirm Transfer Order
Enter
Save
The transfer order is now confirmed.
VL02N Delivery change. EG: Edit the delivery to do the following Pack External customer material number = COO. External delivery number Waybill number. BOL Transport tag. Carrier Header partner SP (E.G. FXP). Tracking number = Packing Unit
Purchase Orders
ME22N PO Change
ME57 Create PO from purchase requisition
ATP
CO09 Availability overview
Goods Movement
MIGO Post goods receipt
MB51 Material document list
MB01 Goods Movement
Other
MD04 Material Requirements. Shows material requirements and releases against materials
SE38 ABAP Editor. Used to modify ABAP programs
SM01 Transaction list. Lock transactions in the system. Also a good tool to see what transactions are available
SHDB Transaction recorder (BDC)
CMOD User exit \ project tool. Coordinates your changes into projects for the purpose of activating all user exits for a particular project. A user exit needs to be modified before it will work
SE16 Table contents display
SOST View mails sent externally from SAP
SU53 Check authorization object
SQVI Table Quickviewer Used to created quick client dependent reports
ST22 ABAP Dump Analysis
ST01 System trace
ST11 Display developer trace
ST05 SQL Trace
SM21 System log
ST22 Display short dumps
SM12 Display locked entries
With Regards,
Vidya
**Please reward with points

SAP ISU Print Workbench

Hi,
Can any one provide me the basics of the SAP ISU Print workbench?
Regards,
Chandan
Moderator message: please search for available information/documentation.
Edited by: Thomas Zloch on Sep 23, 2011 11:39 PM

Hello,
You need to attach application form for each and every Correspondence Type.
Few of the Corr types are
BL44 Outgoing Payment Confirmation
BL45 Account Statement
BL46 Capital Transfer Offer
BL47 Payment Plan
BL48 Rollover Offer
BL49 Repayment
BL50 Borrower Change Without Capital Transfe
BL51 Deferral of Customer Loan
BL52 Capitalization of Overdue Items CL
BL53 Installment Plan Change CL
BL54 Consumer Loan Confirmation
BL55 Notice Given by Bank
BL56 Rescind Credit Life Insurance
BL57 Confirmation of Change
BL58 Interest on Arrears Statement
You can define them in IMG\FICA\Basic Functions\Correspondence\Define Correspondence types.
<SAP provides lot of correspondence types. You have to copy them from client 000>
After that you have to define application form for correspondence types in
IMG\FICA\Basic Functions\Correspondence\Define Application Forms for Correspondence.
You have to attach SAP defined correspondence forms.
To trigger correspondence, you have to run FPCOPARA run mentioning relevant correspondence type.
The data gets updated in table DFKKCOH.
Do remember that apart from above config, there are various areas of correspondence config you need to do for different categories like Payments, Returns, Refunds , Dunning & Collection agency.
For ex, for Returns, you attach application form in Return reason codes, similarly for Dunning, you attach the application form in Dunning activites ...
To view the list of Application forms, use T-Code EFRM
Hope this helps
Rgds
Rajendra

Follow up activities after SAP (CU&UC) upgrade from SAP 4.6c to ECC6 EHP4

Dear Friends
We have completed SAP (CU&UC) upgrade from SAP 4.6c to ECC6 EHP4.
We refereed the upgrade guide for follow activities and we required confirmation before performing the activities.
Could you please help us what needs to be done immediately after upgrade.
Regards,
Bharathi

Dear Nils,
Thanks for the support.
Yes, we are following the same document 'CUUC46C_to_NW701SP07' for unicode conversion after the upgrade from the note 928729.
Please suggest us in that document which are the steps should be carried out after ECC6.0 EHP4 upgrade,
1. Preparation
2. Unicode Preconversion Phase in SAP Basis 4.6C
3. Upgrade Process
4. Unicode Conversion Phase
5. Unicode Conversion Completion Phase
6. SAP Notes
Regards,
Bharathi

BAPI to fetch list of Activities based on Transaction type

Hi All,
I am looking for the BAPIs for the below functionalities:
1.Which takes import parameter as Transaction type and gives all the activities pertaining to that particular transaction type.
2. Which takes input as date paramters (start and end date) and transaction type, and the output is a list of activities which meets the above criteria.
3. Which takes the input as Partner Function code and BP number and it returns all the activities which meets this criteria.
Will appreciate if the details are given to me as soon as possible.
Many thanks in advance...
Regards
Bala

Hi all,
I am currently working in an integration project . I have to get all the table names based upon the functional modules(MM,FI,SDetc). Can anyone tell me the name of the standard BAPI/RFC which can be used for this requirement?
In detail I can say that I have to give input as the functional modules(MM,FI,SDetc)
and I have to get all the table names which is used for this particular functional module in return.
I have already tried to search out for that using several method. If anyone know the exact RFC name then please reply.
Here functional modules refers to Business Modules such as Material Management(MM) etc.
Thanks in advance.
Regards,
Nitin Kumar

List of Tcodes in SAP

Hi Gurus,
Send me a list of Tcodes in SAP.
Thanks in Advance,
Sakthi

Plant Maintenance (PM)
Stephan Nilsson was kind enough to share some PM transactions. Stephan Nilsson was kind enough to share some PM transactions.
IW31     Create Plant Maintenance Order
IW32     Change Plant Maintenance Order
IW33     Display Plant Maintenance Order
IW34     Create Notification Order
IW51     Create Service Notification
IW52     Change Service Notification
IW53     Display Service Notification
IW54     Create Service Notification :Problem notification
IW55     Create Service Notification :Activity Request
IW56     Create Service Notification :Service Request
IW57     Assign deletion Flag to Completed Service Notifications
IW58     Change Service Notifications: Selection of Notification
IW59     Display Service Notifications: Selection of Notification
Production Planning
Tymon Kerste has provided me with these PP tcodes. Tymon Kerste has provided me with these PP tcodes.
C001     Create Production Order
C005N     Collective Release
C011N     Time Ticket
C012     Confirmation - Collective
C013     Confirmation - Cancel
C00IS     Production order information system
C0GI     Reprocess Goods Movements
C223     Maintain production version
General Notes
You can execute the following commands in the transaction code (tcode) field with Enter. You will find some useful transaction codes below to work in tandem with the following commands:
To call a transaction - In the same session (window) Enter: /nxxxx (xxxx = transaction code). - In an additional session, Enter: /oxxxx (xxxx = transaction code).
If you enter this function before any of the tcodes below, you are able to break out of your current screen/business and begin a completely new session. Otherwise, the current business process has to be terminated, and return to the initial user screen (the main menu) has to be initiated before entering tcode spro). /o tcode saves you the effort of having to do this.
To end the current transaction Enter: /n. Caution: Unsaved changes are lost without warning
To delete the current session. Enter: /i.
To generate a session list Enter: /o.
To log off from the system Enter: /nend.
From John O'Meara
OSS Note 0026171 has additional information on OKCodes in SAP, and is a very useful read
BASIS/ABAP
USMM     Pressing F8 will display all hotpacks applied.
SEARCH_SAP_MENU     Show the menu path to use to execute a given tcode. You can search by transaction code or menu text.
DI02     ABAP/4 Repository Information System: Tables.
LSMW     Legacy System Migration Workbench. An addon available from SAP that can make data converstion a lot easier. Thanks to Serge Desland for this one.
OSS1     SAP Online Service System
OY19     Compare Tables
SM13     Update monitor. Will show update tasks status. Very useful to determine why an update failed.
S001     ABAP Development Workbench
S001     ABAP/4 Development Weorkbench. (from [email protected])
S002     System Administration. (from [email protected])
SA38     Execute a program. (from [email protected])
SCAT     Computer Aided Test Tool
SCU0     Compare Tables
SE01     Old Transport & Corrections screen
SE03     Groups together most of the tools that you need for doing transports. In total, more than 20 tools can be reached from this one transaction.
SE09     Workbench Organizer
SE10     New Transport & Correction screen
SE11     ABAP/4 Dictionary Maintenance SE12 ABAP/4 Dictionary Display SE13 Maintain Technical Settings (Tables)
SE12     Dictionary: Initial Screen - enter object name. (from [email protected])
SE13     Access tables in ABAP/4 Dictionary. (from [email protected])
SE14     Utilities for Dictionary Tables
SE15     ABAP/4 Repository Information System
SE16     Data Browser: Initial Screen. (from [email protected])
SE16N     Table Browser (the N stands for New, it replaces SE16). Provided by Smijo Mathew.
SE17     General Table Display
SE24     Class Builder
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 Editor
SE39     Splitscreen Editor: Program Compare
SE41     Menu Painter
SE43     Maintain Area Menu
SE48     Show program call hierarchy. Very useful to see the overall structure of a program. Thanks to Isabelle Arickx for this tcode.
SE49     Table manipulation. Show what tables are behind a transaction code. Thanks to Isabelle Arickx for this tcode.
SE51     Screen Painter: Initial Screen. (from [email protected])
SE54     Generate View Maintenance Module
SE61     R/3 Documentation
SE62     Industry utilities
SE63     Translation
SE64     Terminology
SE65     R/3 document. short text statistics SE66 R/3 Documentation Statistics (Test!)
SE68     Translation Administration
SE71     SAPscript layout set
SE71     SAPScript Layouts Create/Change
SE72     SAPscript styles
SE73     SAPscript font maintenance (revised)
SE74     SAPscript format conversion
SE75     SAPscript Settings
SE76     SAPscript Translation Layout Sets
SE77     SAPscript Translation Styles
SE80     ABAP/4 Development Workbench
SE81     SAP Application Hierarchy
SE82     Customer Application Hierarchy
SE83     Reuse Library. Provided by Smiho Mathew.
SE84     ABAP/4 Repository Information System
SE85     ABAP/4 Dictionary Information System
SE86     ABAP/4 Repository Information System
SE87     Data Modeler Information System
SE88     Development Coordination Info System
SE91     Maintain Messages
SE92     Maintain system log messages
SE93     Maintain Transaction. (from [email protected])
SEARCH_SAP_MENU     From the SAP Easy Access screen, type it in the command field and you will be able to search the standard SAP menu for transaction codes / keywords. It will return the nodes to follow for you.
SEU     Object Browser
SHD0     Transaction variant maintenance
SM04     Overview of Users (cancel/delete sessions)
SM12     Lock table entries (unlock locked tables)
SM21     View the system log, very useful when you get a short dump. Provides much more info than short dump
SM30     Maintain Table Views. (from [email protected])
SM31     Table Maintenance
SM32     Table maintenance
SM35     View Batch Input Sessions
SM37     View background jobs
SM50     Process Overview. (from [email protected])
SM51     Delete jobs from system (BDC)
SM62     Display/Maintain events in SAP, also use function BP_EVENT_RAISE
SMEN     Display the menu path to get to a transaction
SMOD/CMOD     Transactions for processing/editing/activating new customer enhancements.
SNRO     Object browser for number range maintenance. (from [email protected])
SPRO     Start SAP IMG (Implementation Guide). (from [email protected])
SQ00     ABAP/4 Query: Start Queries
SQ01     ABAP/4 Query: Maintain Queries
SQ02     ABAP/4 Query: Maintain Funct. Areas
SQ03     ABAP/4 Query: Maintain User Groups
SQ07     ABAP/4 Query: Language Comparison
ST05     Trace SQL Database Requests. (from [email protected])
ST22     ABAP Dump analysis
SU53     Display Authorization Values for User. (from [email protected])
WEDI     EDI Menu. IDOC and EDI base.
WE02     Display an IDOC
WE07     IDOC Statistics
Human Resources
PA03     Change Payroll control record
PA20     Display PA Infotypes
PA30     Create/Change PA Infotypes
PP02     Quick Entry for PD object creation
PU00     Delete PA infotypes for an employee. Will not be able to delete an infotype if there is cluster data assigned to the employee.
Sales and Distribution (SD)
OLSD     Config for SD. Use Tools-Data Transfer-Conditions to setup SAP supplied BDC to load pricing data
VA01     Create Sales/Returns Order:Initial Screen
VB21     Transaction for Volume Lease Purchases (done as a sales deal)
VK15     Transaction used to enter multiple sales conditions (most will be entered here)
SAP Office
SO00     send a note through SAP, can be sent to internet, X400, etc
FI Financial Management
FGRP     Report Writer screen
FM12     View blocked documents by user
FST2     Insert language specific name for G/L account. (from [email protected])
FST3     Display G/L account name. (from [email protected])
KEA0     Maintain operating concern. (from [email protected])
KEKE     Activate CO-PA. (from [email protected])
KEKK     Assign operating concern. (from [email protected])
KL04     Delete activity type. (from [email protected])
KS04     Delete a cost centre. (from [email protected])
KSH2     Change cost centre group - delete. (from [email protected])
OBR2     Deletion program for customers, vendors, G/L accounts. (from [email protected])
OKC5     Cost element/cost element group deletion. (from [email protected])
OKE1     Delete transaction data. (from [email protected])
OKE2     Delete a profit centre. (from [email protected])
OKI1     Determine Activity Number: Activity Types (Assignment of material number/service to activity type) (from [email protected])
OMZ1     Definition of partner roles. (from [email protected])
OMZ2     Language dependent key reassignment for partner roles. (from [email protected])
Material Management (MM)
MM06     Flag material for deletion. (from [email protected])
OLMS-     materials management configuration menu, most of the stuff under this menu is not under the implementation guide
MM configuration transactions
OLMB-     Inventory management/Physical Inventory
OLMD-     MM Consumption-Based Planning
OLME-     MM Purchasing
OLML-     Warehouse Management
OLMR-     Invoice Verification
OLMS     Material Master data
OLMW-     MM Valuation/Account Assignment
Config Related
OLE     OLE demo transaction
OLI0     C Plant Maintenance Master Data
OLI1     Set Up INVCO for Material Movements
OLI8     Set Up SIS for Deliveries
OLIA     C Maintenance Processing
OLIP     C Plant Maintenance Planning
OLIQ     New set-up of QM info system
OLIX     Set Up Copying/Deleting of Versions
OLIY     Set Up Deletion of SIS/Inter.Storage
OLIZ     Stat Set Up INVCO: Invoice Verif
OLM2     Customizing: Volume-Based Rebates
OLMB     C RM-MAT Inventory Management Menu
OLMD     C RM-MAT MRP Menu
OLME     C MM Menu: Purchasing
OLML     C MM Menu for Warehouse Management
OLMR     C RM-MAT Menu: Invoice Verification
OLMS     C RM-MAT Master Data Menu
OLMW     C RM-MAT Valuation/Acct. Assgt. Menu
OLPA     SOP Configuration
OLPE     Sales order value
OLPK     Customizing for capacity planning
OLPR     Project System Options
OLPS     Customizing Basic Data
OLPV     Customizing: Std. Value Calculation
OLQB     C QM QM in Procurement
OLQI     Analysis
OLQM     Customizing QM Quality Notifications
OLQS     C QM Menu Basic Data
OLQW     C QM Inspection Management
OLQZ     Quality Certificates
OLS1     Customizing for Rebates
OLSD     Customizing: SD
OLVA     C SD Sales Menu
OLVD     C SD Shipping Menu
OLVF     C SD Billing Menu
OLVS     C SD Menu for Master Data
SPRO     Start SAP IMG (Implementation Guide). (from [email protected])
reward points if useful.
thanks,
usha

I need the list of Topics in SAP XI

Hi To All,
I Need the list of topics in SAP XI will you please send the list of topics...
Thanks & Regards
Satish Patnaik

Hi Sateesh,
I think you are new to Integration.I would suggest you to go thru all the topics in SAP XI and then you will get a good idea whether every topic is important or not
Anyways ,In the present market
1)proxy.
2)Message monitoring
3)BPM
4)Java Mapping
5)Context change
These topics are important for interview point of view.
Also,
They may ask you like
1) What the business systems used ? (Note this is SLD related)
2) They will give you scenario and aks you howmany BS,TS and logical names
you will create
3) Some more things on SWC versions, SAP R/3 Settings like pushing IDOC
receive IDOC ...etc
4) Naming conventions you used ? for BS, LS,TS.....
5) Why sender IDOC,HTTP adpter not required? explain in detail ?
6) What adapters you used ? Tell all the parameters?
7) Any java mapping written? how to write? Packages? UDF....
8) Mapping functions details...like node functions etc....
Scenario's what they asked me ...:::))))
1) SOAP to RFC to SOAP explain in details what you will do
2) Multiple files to Single IDOC using BPM
3) RDBMS to SAP R/3
4) Can you built Sysn-Async Bridge in BPM ? How ?
5) How to write ABAP/Java proxies ? Write all the steps?
6) How will you alert Configuration ? give T.Codes?
7) Given one exp...asked create multi mapping ?
kindly reward if found helpful.
cheers,
Hema.

SAP Adobe Print forms - Issue with Chinese characters

Hi All,
We are using SAP Adobe Print forms to create a business document. This is designed using Adobe Life Cycle Designer (ALD). The form is displayed in Chinese language. The requirement is to display captions for few fields in bold.
When designing the form we have put the caption as BOLD but when the actual form is generated only few characters are displayed in bold.
I am not sure if this is problem with Adobe Reader or should there be any specific fonts to be installed in the ADS server?
Please let me know which all font packs needs to be installed in the local machine?

Hi Pat,
Thank you again for your reply.
Now, I changed the font in the designer to "Adobe Song Std L" and made the text as "BOLD". Then I get a message
The following is the Designer screen shot.
Questions:
1. Does "Adobe Song Std L" support characters in BOLD?
2. Do I need to install any of those BOLD fonts? If so, where can I get them?
3. I understand that the BOLD font needs to be installed in the local machine (where the design actually happens so that the font can be specified), the ADS Server (where the actual PDF is rendered) and also in the viewers local machine (where the PDF document is viewed). Is this correct?
4. Is the font a freeware or will there be any licensing issues?
Again, thank you for your responses till now.

Where can find information about cost of SAP support and maintenance?

I would like to get some information of cost of SAP support and maintenance, where I can find it?

SAP software licenses and maintenance vary greatly, the fees for onetime/annual maintenance are based on contracts.
To get a price list contact your local sales rep.
Markus

How to get the list of materials from Sap r/3

Hi Experts,
I have one doubt, here iam implementing
HTTP TO RFC scenario.
My doubts are------
1. Should we create DT MT MI and all (OR) not
2.In Request DT how the message structure wil be to get the list of materials from sap r/3 system as Response(Ex: Fields in the source structure).
3.Or the second thing is how to get the list of materials start with some alphabate.
Please reply me for each and every questions mentioned above. Please clarify me.
Helpful answers wil be rewarded.
Reagards
khanna

Hi Khanna,
 1. Should we create DT MT MI and all (OR) not
 Yes U need to create for HTTP site...for RFC U need to import..
2.In Request DT how the message structure wil be to get the list of materials from sap r/3 system as Response(Ex: Fields in the source structure).
 You create your own structres for Request and respoce.. and Map it with RFC..
3.Or the second thing is how to get the list of materials start with some alphabate.
 I think it will come with acending order....
for more help go through this link
/people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit - File to RFC
regards,
Ansar.

What is the difference in SAPS requirement for ECC 6.0 (No EhP) vs ECC 6.7 (EhP 7)?

Hi Team,
Hope you are doing well, Can you please explain the below points.
1)      What is the difference in SAPS requirement for ECC 6.0 (No EhP) vs ECC 6.7 (EhP 7)?
2)     What is the split of SAPS between Core and RAM?
Thanks in advance.

Hi Deepak,
We are not partner/ customer with SAP, so don't have access to tools.
Can you please give theoretical idea about
1)      What is the difference in SAPS requirement for ECC 6.0 (No EhP) vs ECC 6.7 (EhP 7)?
2)     What is the split of SAPS between Core and RAM?
Thank you,
Gopi Reddy

List of activities in SAP requiring printer maintenance

Similar Messages

Maybe you are looking for