Re: SAP FX translation

While trying to run the new GL FX translation program FAGL_FC_TRANS, it keeps giving error message FR 588 (No financial statement version assigned to valuation area RI).
Not sure why it shows this error , as we have already assigned a Financial statement version and financial item to the valuation area RI in IMG setting: General Ledger Accounting (New) ® Periodic Processing ® Valuate ® Foreign Currency Valuation ® Define Account Determination for Currency Translation.
Does anyone encounters this error before ?
Regards
SK

Solved.
Took me long to come back to this and update, but my silly problem with the FAGL_FC_TRANS error (below)
No balance sheet/PL structure assigned to valuation area
Message no. FR588
was solved by defining the correct missing FS Version "Define Valuation Area"
IMG -> FI (new) -> GL (New) -> Periodic Processing ->Valuate -> Define Valuation Areas
I had more inconsistencies after this and thanks to Christian, we've applied the latest note you have mentioned. Currency valuation is working how we want to for us.
Best Regards,
AY

Similar Messages

SAP BO Translation Management Tool

Hi,
I am using the SAP BO Translation Management Tool to translate our WEBI reports into French language. Most of the queries are getting translated properly and after the export to the server they are available in French language.
But I am having issues with two of those reports in which even on successfully translating the variables and exporting the same to the server the translation is not available. On opening the WEBI report again in TMT it shows that none of the variables were translated and this problem is only with the variables not with query names or prompts.
Any kind of help would be great.
Regards,
Arminder Singh

Hi,
Follow this
1888952 - Translations not retained for user variables when translating to multiple languages in Translation Management Tool.

SAP Script Translation

Hi All,
Need help in SAP Script translation.
I have to change some hardcoded text from one language to another language.
I went to SE63 and changed the text, but the changes are not added into transport request.
Is there anyway to include the changes into the transport request? Please reply back...

Hi,
Other way would be to create a new request all together for the form. SE03----->Include object in tran req..Write click... execute. Click radiobutton Selected Objects. Add a new line at the bottim. FORM give form name in front of it. Tick the sequare box. F8. Click on Save in req.
Transport this request.
Reagards
Raju Chitale

Transaction SE76 - SAP Script Translations

Hi All!
I'm working with Smart Forms (similar to SAP Script) and I have to make somne translations. Does somebody know how to use transaction SE76?
Thanks!
Ale.

this is for translate script to existing language to required language...
this u can also do in se71
se71-> enter form name & existing language name -> change
->utilities -> conver language...
i think...
Regards,
Ramesh

Foreign Currency Translation at Year End - How SAP Works for P&L items?

Hi All,
I wanted to know "How SAP works on Foreign Currency Translation at year end" from Local Currency to Group Currency for P&L Items.
I know how SAP works for Balance sheet items but am really confused with when the translation was done for P&L Items.
Configuration:
We are on ECC 6.0 . Local Currency is CAD and we have 2nd Local Currency as "USD - Group Curr".
We have set up Valuation Method - 4
We have set up Valuation Area - 40
For Account Determination for Currency Translation, GL accounts (Loss, Gain and B/S Adj) were setup for the combination of Chart of Accounts, Val Area and Fin Stmt Ver.
Sales Account Balance
CAD (LC)        USD (2nd LC)
1000                   920
Using tcode "FAGL_FC_TRANS", we translated our P&L items.
Local Currency is CAD and Group Currency is USD.
CAD 1000 and USD 920 are cumulative balances over a period of time.
Since at the end of year CAD became stronger, exchange rate is 1.11 as an example
Sales Account Balance
CAD (LC)        USD (2nd LC)        Translated Value in USD
1000                   920                        900
System passed the following entry in USD:
Debit Balance Sheet Adj A/c 20
Credit Translation Gain / Loss A/c 20
Here are the questions:
1. How does over all translation work? - Should we get any Gain / Loss and have an effect on P&L when all accounts (P&L, B/S) are translated?
2. How can there be a gain entry when USD value has really fallen from 920 to 900 in the current case.
Thanks for your time.
Vijay

Hi,
I had this issue too. The entry was just opposite to what it should be. I just flipped the accounts in table FAGL_T030TR.
Example: 410000 is sales account which normally should have a credit balance. Here are some entries that were posted to sales in 03/2009 and I am running FAGL_FC_TRANS at the end of the month.
March 1, 2009 Cr. Sales CAD 1000- USD 900-
March 2, 2009 Cr. Sales CAD 500- USD 480-
During FC translation transaction, system takes the balance in the account for the period (if you execute it with 'Val. period balance only' checkbox checked) and not the cumulative balance. SAP recommends translating period balance only (and not cumulative balance) for P&L accounts. It sees a balance in LC (this again depends on the config. you have in OB22 - whether the indicator is 1 (TC as source currency) or 2 (LC as source currency for translation)) which is 1500, converts that at month end rate. After conversion, lets say the balance is 1400-.
In this case, we expect a credit entry on sales account
March 31, 2009 Cr. Sales CAD 0 USD 20-
But system was just posting the opposite. I then flipped the accounts in FC translation configuration. I know it is misleading. In that configuration, system says balance sheet adjustment account, but what you should actually give there is your gain/loss account. Our gain/loss a/c. falls in the same GL account range as the main account. For example, for 410000, it is 410999 and for 510000, it is 510999. We report accounts 410000 to 410999 in the same node in the FSV.
Pl. feel free to ask further questions about this. Pl. test in your system and correct me if my above reply is wrong.
Cheers!

How to translate the text dynamically in the program?

Hi All,
I have a requirement where I need to translate the text dynamically in the program based on the Language Key retrieved.
Let's say that the Login language is 'EN' and in the logic has retrieved the language 'IT'(based on some conditions). I have to transate the text(which is maintained using the text elements) to ITALIAN(IT) Language and send the same as an email.
Could you please tell me if any Function Module is available in SAP which translates the text Dynamically in the program. or is there any other way to translate the text dynamically in the program.
Could you please share your valuable inputs? Thank you in advance.
Thanks & regards,
Paddu.

you could use SET LOCALE LANGUAGE myLanguage - so you can switch to the desired language and all texts will selected from that language.

Urgent! How foreign languages are treated in SAP CRM

How are foreign languages' characters treated in SAP CRM?. If a person's name or address is entered in say Japanese or Greek characters, how would it reflect in reporting. Would it have anything to do with the communication language selected for the contact?
Urgent

If the Data is entered in a foreign Language it will show same in the reports too. SAP has translation service too but that wouldn't be affective and suitable to conversion. So if it is entered in Japanese you will see in Japanese only. But one thing is to make sure your language packs are loaded in to your landscape.
Thanks
Raja

How to integrate the portal system with non-sap system

Hi Gurus,
How to integrate Portal system with non-SAP system?
I know few ways .......Using Usermapping UIDPW method.
Using Appintegrator .....and using Business repository objects in JCA?
Is there anyother way to integrate if so please give me the names and steps for integrating it?
Thanks in Advance,
Dharani

Hi Dharani,
You can get information from the following links:
http://help.sap.com/saphelp_nw04s/helpdata/en/43/d08b00d73001b4e10000000a11466f/frameset.htm
https://www.sdn.sap.com/irj/sdn/thread?threadID=744043
SAP CONNECTORS:- Basically Connectors are like middlewares , that we use to connect to the backend system including Non SAP systems also. Will try to explain it to u with some examples of SAP Connectors:-
a) SAP Business Connectors:-
A middleware application based on the B2B integration server from webMethods.
The SAP Business Connector enables both bi-directional synchronous communication and asynchronous communication between SAP applications and SAP and non-SAP applications.
The SAP Business Connector makes all SAP functions that are available via BAPIs or IDocs accessible to business partners over the Internet as an XML-based service.
The SAP Business Connector uses the Internet as a communication platform and XML or HTML as the data format. It integrates non-SAP products by using an open, non-proprietary technology.
b) SAP Java Connector:-
SAP Java Connector (SAP JCo) is a middleware component that enables the development of SAP-compatible components and applications in Java. SAP JCo supports communication with the SAP Server in both directions: inbound calls (Java calls ABAP) and outbound calls (ABAP calls Java).
SAP JCo can be implemented with Desktop applications and with Web server applications.
SAP JCo is used as an integrated component in the following applications:
1) SAP Business Connector, for communication with external Java applications
2) SAP Web Application Server, for connecting the integrated J2EE server with the ABAP environment.
SAP JCo can also be implemented as a standalone component, for example to establish communication with the SAP system for individual online (web) applications.
To Know more go through,
SAP Java Connectors
II) ALE Concept:-
ALE is not restricted to communication between SAP systems, it can also be used for connecting SAP Systems to non-SAP systems.
By using IDocs as universal information containers, ALE can reduce the number of different application interfaces to one single interface that can either send IDocs from an SAP system or receive IDocs in an SAP system.
SAP certified Translator Programs can convert IDoc structures into customer-defined structures.
Alternatively, the RFC interface for sending and receiving IDocs can be used in non-SAP systems.
In both cases you need the RFC Library of the RFC Software Development Kit (RFC-SDK).
This link gives a great insight into landscape for Connectivity to Non-SAP systems:-
SAP to Non-SAP systems
III) Communication Between SAP Systems and External (Non-SAP) Systems using RFC:-
When you use RFC for communication with an external (non-SAP) system, you can also implement the SAP Java Connector or the SAP .Net Connector for the conversion of data. However, there are no specific security requirements for these components, since they only perform internal system conversion functions.
The additional security recommendations for communication with external systems in this section make particular reference to cases where an external system is used as a server (SAP calls the external system). If you use an external system as a client (the external system calls SAP), the appropriate SAP-specific security mechanisms are implemented on the SAP side.
This link explains in detail all the security considerations you need to take for connecting to an External Non SAP system like, User administration, Network Security etc.
Communication Between SAP Systems and External (Non-SAP) Systems using RFC
Hope this helps,
Regards,
Rudradev Devulapalli
Reward the points if helpful

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

ESS - Translations management

Hi everybody,
I have installed ESS into SAP Portal. ESS works fine with any languages (EN IT FR )
The standard interface displays messages like :
"Employee Self-Service applications provide you with
easy access to information and services for employees.
This page gives you an overview of the entire offering."
This is a standard text displayed into the framework page.
I would like to change this kind of text for languages EN IT FR.
I know there is a way to do this under the IMG menu :
Cross-Application Components -> Homepage Framework (Overview) -> Resources -> Define Resources
and
Cross-Application Components -> Homepage Framework (Overview) -> Header and Area Group Pages -> Define Area Group Pages
But It seems that is not the best practice.
I looked at the SE63 but all translations doesn't seems to be there (into table T7XSSSERSTRLAN there are only EN and DE texts)
Where can I change texts translation for any languages according the best practice ?
Thanks in advance

Hi Christopher,
Thanks for your answer.
Actually, my standard translations works fine. By example when my browser's language is set to "English", message is :
"Employee Self-Service applications provide you with
easy access to information and services for employees.
This page gives you an overview of the entire offering."
But when my browser's language is set to "French", the message became :
"Les applications de l'Employee Self-Service vous permettent
d'accéder facilement aux informations et aux services destinés aux salariés.
Cette page présente une synthèse de l'ensemble de l'offre."
My problem is I can't find translations into R/3 (by example the french text) although I'm logged with FR language. And theses translations are existing (because my browser displays the relevant translation according to the language).
I would like to know where are stored theses SAP standard translations for ESS in order to modify them.
Are they stored into the java Package (portal side) ?
Thanks in advance

Non-sap and Sap

Hi ..If we want to communicate non-sap and sap applications which is the best way in ABAP.
regards
khanna

Hi Rajesh,
ALE is not restricted to communication between SAP systems; it can also be used for connecting SAP Systems to non-SAP systems.
By using IDocs as universal information containers, ALE can reduce the number of different application interfaces to one single interface that can either send IDocs from an SAP system or receive IDocs in an SAP system.
SAP certified Translator Programs can convert IDoc structures into customer-defined structures.
Alternatively, the RFC interface for sending and receiving IDocs can be used in non-SAP systems.
In both cases you need the RFC Library of the RFC Software Development Kit (RFC-SDK).
regards
manoj kumar

FM SSF_CLOSE failing and giving error message while printing a smartform

Hi,
for language spanish the smartform is not getting printed for output type SG11 but for english it is getting printed? What could be the reason? I debugged and found that SSF_CLOSE is failing and giving error message.
Thanks and regards,
AP.

Hi Aparajita,
for changing from one languages to another translations in SE63 is to be done, either search on SCN for using SE63 , or atleast see these wiki help .
Transaction SE63 - Translation Tools for Translators (BC-DOC-TTL) - SAP Library
Transaction SE63 (SAP Library - Translation Tools for Translators (BC-DOC-TTL))

EHP1 FOR CRM 7.0

Hello,
I am installing in my EHP1 CRM 7.0 (ABAP), but in phase (preprocessing) after he doubled the bank of the following message:
To analyze errors During the start of shadow instance,
       view files 'STARTSFI.LOG' and 'DEVTRACE.LOG'
       in directory 'D: \ medias \ ehpi \ EHPI \ abap \ log'
       After fixing the error, repeat phase until shadow instance is
       Can you started and log on instance number '01 '.
The following are the logs.
'STARTSFI.LOG'
Entering a ETQ201 upgrade-phase "START_SHDI_FIRST" ("20111225104654")
Sep 4 ETQ399 connect standard environment is:
2 ETQ367 Connect variables are set is standard instance access
4 ETQ399 System-nr = '00 ', GwService =' sapgw00 '
4 ETQ399 Environment variables:
4 ETQ399 dbs_mss_schema = crd
ETQ399 auth_shadow_upgrade 4 = 0
Executing a pre-phase ETQ206 DB specific actions.
Executing a pre-phase ETQ206 DB specific actions.
Executing a ETQ200 current phase 'MAIN_SHADOW / START_SHDI_FIRST'.
Phase 1 ETQ399 arguments:
2 ETQ399 Arg [0] = 'DEVTRACE.LOG'
Sep 4 ETQ399 environment for shadow connect:
Sep 4 ETQ399 RFC variables for shadow connect:
4 ETQ399 System-nr = '01 ', GwService =' sapgw01 '
4 ETQ380 computing toolpath for request "TP_SHADOW_CONNECT"
4 ETQ381 request "TP_SHADOW_CONNECT" means "tp needs to connect to shadow system"
4 ETQ382 translate to group "R3UP_TOOL_GROUP_NEW"
4 ETQ383 translate to path "exe"
4 ETQ383 translate to path "exe"
Sep 4 ETQ399 tool parameters for shadow connect:
4 ETQ399 default TPPARAM: SHADOW.TPP
4 ETQ380 computing toolpath for request "TP_ALWAYS_NEW"
4 ETQ381 request "TP_ALWAYS_NEW" means "always DIR_PUT from tp / exe, is phase KX_SWITCH"
4 ETQ382 translate to group "R3UP_TOOL_GROUP_NEW"
4 ETQ383 translate to path "exe"
4 ETQ383 translate to path "exe"
2 ETQ399 Starting shadow instance
4 ETQ359 RFC Login to: System = "CRD", Nr = "01", GwHost = "fhsrv011" GwService = "sapgw01"
2 ETQ231 RFC Login failed
4 ETQ359 RFC Login to: System = "CRD", Nr = "01", GwHost = "fhsrv011" GwService = "sapgw01"
2 ETQ231 RFC Login failed
2 Stopping ETQ399 shadow instance
4 ETQ359 RFC Login to: System = "CRD", Nr = "01", GwHost = "fhsrv011" GwService = "sapgw01"
2 ETQ231 RFC Login failed
4 ETQ359 RFC Login to: System = "CRD", Nr = "01", GwHost = "fhsrv011" GwService = "sapgw01"
2 ETQ231 RFC Login failed
2 Starting system ETQ353
2EETQ399 Starting shadow instance failed
And 'DEVTRACE.LOG'
trc file: "dev_disp", trc level: 1, release: "720"
sysno 01
sid CRD
systemid 562 (PC with Windows NT)
RELN 7200
patchlevel 0
patchno 100
intno 20020600
make multithreaded, Unicode, 64 bit, optimized
profile D: \ medias \ ehpi \ EHPI \ abap \ CRD \ SYS \ profile \ CRD_DVEBMGS01_fhsrv011
pid 3332
kernel runs with dp version 131000 (ext = 118000) (@(#) DPLIB-INT-VERSION-131000-UC)
length of 588 bytes is sys_adm_ext
SWITCH TRC-HIDE on ***
LOG Q00 => DpSapEnvInit, DPStart (01 3332) [dpxxdisp.c 1287]
shared lib "dw_xml.dll" version 100 successfully loaded
shared lib "dw_xtc.dll" version 100 successfully loaded
shared lib "dw_stl.dll" version 100 successfully loaded
shared lib "dw_gui.dll" version 100 successfully loaded
shared lib "dw_mdm.dll" version 100 successfully loaded
shared lib "dw_rndrt.dll" version 100 successfully loaded
shared lib "dw_abp.dll" version 100 successfully loaded
shared lib "dw_sym.dll" version 100 successfully loaded
shared lib "dw_aci.dll" version 100 successfully loaded
rdisp / softcancel_sequence: -> 0.5, -1
rdisp / dynamic_wp_check: 0
rdisp / calculateLoadAverage: 1
Sun Dec 25 11:11:48 2011
WARNING => DpNetCheck: NiAddrToHost (1.0.0.0) took 5 seconds
GZZ *** LOG => 1 Possible network problems detected - check tracefile and adjust the DNS settings [dpxxtool2.c 6404]
MtxInit: 30 000 0 0
DpSysAdmExtInit: ABAP is active
DpSysAdmExtInit: VMC (JAVA VM in WP) is not active
DpIPCInit2: dp-profile-write values into sys_adm_ext
DpIPCInit2: start server> fhsrv011_CRD_01 <
DpShMCreate: sizeof (wp_adm) 31 696 (2264)
DpShMCreate: sizeof (tm_adm) 5,517,056 (27,448)
DpShMCreate: sizeof (wp_ca_adm) 64 000 (64)
DpShMCreate: sizeof (appc_ca_adm) 64 000 (64)
DpCommTableSize: max / headSize / ftSize / tableSize = 500/16/584064/584080
DpShMCreate: sizeof (comm_adm) 584 080 (1144)
DpSlockTableSize: max / headSize / ftSize / fiSize / tableSize = 0/0/0/0/0
DpShMCreate: sizeof (slock_adm) 0 (104)
DpFileTableSize: max / headSize / ftSize / tableSize = 0/0/0/0
DpShMCreate: sizeof (file_adm) 0 (80)
DpShMCreate: sizeof (vmc_adm) 0 (2152)
DpShMCreate: sizeof (wall_adm) (41664/36752/64/192)
DpShMCreate: sizeof (gw_adm) 48
DpShMCreate: sizeof (j2ee_adm) 3952
DpShMCreate: SHM_DP_ADM_KEY (addr: 00000000035B0050, size: 6357408)
DpShMCreate: sys_adm allocated at 00000000035B0060
DpShMCreate: wp_adm_list allocated at 00000000035B3040
DpShMCreate: wp_adm allocated at 00000000035B3230
DpShMCreate: tm_adm_list allocated at 00000000035BAE10
DpShMCreate: tm_adm allocated at 00000000035BAE60
DpShMCreate: wp_ca_adm allocated at 0000000003AFDD70
DpShMCreate: appc_ca_adm allocated at 0000000003B0D780
DpShMCreate: comm_adm allocated at 0000000003B1D190
DpShMCreate: system runs without Slock table
DpShMCreate: system runs without file table
DpShMCreate: vmc_adm_list allocated at 0000000003BABB30
DpShMCreate: system runs without vmc_adm
DpShMCreate: gw_adm allocated at 0000000003BABBE0
DpShMCreate: j2ee_adm allocated at 0000000003BABC20
DpShMCreate: ca_info allocated at 0000000003BACBA0
DpShMCreate: wall_adm allocated at 0000000003BACC30
DpCommAttachTable: comm attached table (header = 0000000003B1D190/ft 0000000003B1D1A0 =)
DpSysAdmIntInit: initialize sys_adm
rdisp / test_roll: roll strategy is DP_NORMAL_ROLL
check day token not active (5 tokens)
MBUF OFF state
DpCommInitTable: init table for 500 entries
DpRqQInit: keep protect_queue / slots_per_queue 0 / 2001 in sys_adm
rdisp / queue_size_check_value: -> on, 50,30,40,500,50,500,80
EmInit: MmSetImplementation (2).
MM global diagnostic options set: 0
<ES> Client 0 initializing ....
<ES> InitFreeList
<ES> Block size is 4096 kByte.
Using Implementation View
Using <EsNT> view memory model.
<EsNT> Memory Reset disabled the default NT
ERROR => <EsNT> CreateFileMapping name = Global \ ES_SEG_01_000, size = 2044 MB, error = 1455 [esnti.c 1276]
Memory diagnostic *
SystemInformation
Processor-Typ: Processor-Count: 4
Operating System: NT 6.0, Build 6002
Service Pack: Service Pack 2
NT Pagefile Informations
Config. minimum size: 0 K
Config. maximum size: 0 K
Avail. maximum size: 0 K
A
Pagefile
Min.Size
Max.Size
Avail.Max
Curr.Size
NT Task Manager Informations
Total Handles: 4096
Total Threads: 0
Total Processes: 10
Commit Charge Total: 0 K
Commit Charge Limit: 1749755472 K
Commit Charge Peak: 0 K
Phys.Memory Total: 1749210804 K
Phys.Memory Available: 0 K
File Cache: 54 K
Kernel Memory Total: 0 K
Kernel Memory Paged: 0 K
Kernel Memory Nonpaged: 0 K
Memory usage of current process
Virt.address Total space: 0000008589934464 K
Avail.virt.address space: 0000008589004628 K
Private Pages: 0 K
Total heap size: 14411 K
Virtual memory regions: 36 K
Uncommitted heap memory: 7792 K
Allocated heap memory: 6390 K
Moveable heap memory: 0 K
DDE shared heap memory: 3125 K
Memory usage of all processes
PID
Image
Instance
Work.Set
WAS Peak
Priv.Pages
PP Peak
Pg Fault
13236
sapstartsrv.exe
94832 K
95576 K
119092 K
176464 K
1101
14464
msg_server.EXE
[MS] CRD_00
13300 K
13320 K
15448 K
15536 K
3
14632
disp + work.EXE
[SD] CRD_00
178976 K
178976 K
100204 K
103312 K
43
14452
igswd.EXE
[**] CRD_00
6008 K
6040 K
4172 K
7212 K
1
11628
igsmux.exe
16012 K
16012 K
19736 K
19736 K
3
14720
igspw.exe
36928 K
36928 K
39976 K
40376 K
11
14532
igspw.exe
36180 K
36180 K
39220 K
39620 K
12
14384
gwrd.EXE
[GW] CRD_00
16580 K
16600 K
15680 K
21676 K
4
11612
icman.EXE
[**] CRD_00
106700 K
106708 K
109724 K
111824 K
26
12220
disp + work.EXE
[WP] CRD_00
172264 K
175308 K
180652 K
180652 K
108
13620
disp + work.EXE
[WP] CRD_00
195132 K
260164 K
138844 K
162816 K
169
12884
disp + work.EXE
[WP] CRD_00
109204 K
169228 K
130508 K
143268 K
90
7976
disp + work.EXE
[WP] CRD_00
118696 K
152260 K
131956 K
163248 K
94
13352
disp + work.EXE
[WP] CRD_00
90176 K
94072 K
123736 K
126148 K
29
14736
disp + work.EXE
[WP] CRD_00
101052 K
183384 K
126848 K
198328 K
98
13984
disp + work.EXE
[WP] CRD_00
78400 K
79660 K
118712 K
122304 K
23
10540
disp + work.EXE
[WP] CRD_00
74176 K
75556 K
117032 K
122304 K
22
9756
disp + work.EXE
[WP] CRD_00
68800 K
70104 K
119116 K
122308 K
20
14664
disp + work.EXE
[WP] CRD_00
67660 K
68504 K
119588 K
122308 K
21
9980
disp + work.EXE
[WP] CRD_00
83952 K
84376 K
117100 K
122268 K
24
13556
disp + work.EXE
[WP] CRD_00
56436 K
56472 K
114772 K
122276 K
17
14672
disp + work.EXE
[WP] CRD_00
129136 K
131320 K
124356 K
129668 K
76
1352
disp + work.EXE
[WP] CRD_00
70916 K
72192 K
120832 K
122264 K
22
13632
disp + work.EXE
[WP] CRD_00
76116 K
77592 K
121300 K
122276 K
23
11784
disp + work.EXE
[WP] CRD_00
52516 K
52536 K
115316 K
122264 K
16
10580
disp + work.EXE
[WP] CRD_00
82100 K
82136 K
115872 K
122268 K
23
12872
disp + work.EXE
[WP] CRD_00
52548 K
52568 K
115380 K
122264 K
16
13732
disp + work.EXE
[WP] CRD_00
62384 K
62824 K
117464 K
122264 K
21
11824
disp + work.EXE
[WP] CRD_00
52460 K
52480 K
115408 K
122264 K
16
4668
msg_server.EXE
[MS] CRD_01
14168 K
14168 K
15048 K
15052 K
3
3332
disp + work.EXE
44684 K
44684 K
74600 K
82528 K
10
Sum
2358492 K 3037692 K
**** Error 11 while initializing OS dependent part.*
**** ERROR => DpEmInit: EmInit (1) [dpxxdisp.c 10428]*
**** ERROR => DpMemInit: DpEmInit (-1) [dpxxdisp.c 10342]*
**** DP_FATAL_ERROR => DpSapEnvInit: DpMemInit*
*DISPATCH EMERGENCY SHUTDOWN *** ****
Increase TraceLevel of WPs
NiWait: sleep (10000ms) ...
NiISelect: timeout 10000ms
NiISelect: maximum fd = 1
NiISelect: read-mask is NULL
NiISelect: write-mask is NULL
Sun Dec 25 11:11:58 2011
NiISelect: occured TIMEOUT (10000ms)
dump system status
Workprocess Table (long) Sun Dec 25 13:11:58 2011
========================
In Type Pid Status Cause Start Err RSTR No Time Program Cl User Action Table
Dispatcher Queue Statistics Sun Dec 25 13:11:58 2011
===========================
--------++++ -
+
Typ
now
high
max
writes
reads
--------++++ -
+
NOWP
0
0
2000
0
0
--------++++ -
+
DAY
0
0
2000
0
0
--------++++ -
+
UPD
0
0
2000
0
0
--------++++ -
+
ENQ
0
0
2000
0
0
--------++++ -
+
BTC
0
0
2000
0
0
--------++++ -
+
SPO
0
0
2000
0
0
--------++++ -
+
UP2
0
0
2000
0
0
--------++++ -
+
max_rq_id 0
wake_evt_udp_now 0
wake events total 0, udp 0 (0%), shm 0 (0%)
since last update total 0, udp 0 (0%), shm 0 (0%)
Dump of tm_adm structure: Sun Dec 25 13:11:58 2011
=========================
Term uid man user term lastop mod wp ta a / i (modes)
Workprocess Comm. Area Blocks Sun Dec 25 13:11:58 2011
=============================
Slots: 1000, Used: 0 Max: 0
--------++--
+
Id
owner
pid
eyecatcher
--------++--
+
NiWait: sleep (5000ms) ...
NiISelect: timeout 5000ms
NiISelect: maximum fd = 1
NiISelect: read-mask is NULL
NiISelect: write-mask is NULL
Sun Dec 25 11:12:03 2011
NiISelect: occured TIMEOUT (5000ms)
DpHalt: shutdown server> fhsrv011_CRD_01 <(normal)
DpJ2eeDisableRestart
DpHalt: Switch off Shared memory profiling
ShmProtect (57, 3)
ShmProtect (SHM_PROFILE, SHM_PROT_RW
ShmProtect (57, 1)
ShmProtect (SHM_PROFILE, SHM_PROT_RD
DpWakeUpWps: wake up all wp's
DpHalt: stop work processes
DpHalt: Terminate gui connections
DpHalt: wait for end of work processes
DpHalt: not attached to the message server
DpHalt: EM cleanup
EsCleanup ()
EsCleanup ....
EmCleanup () -> 0
Es2Cleanup: Cleanup ES2
LOG Q05 => DpHalt, DPStop (3332) [dpxxdisp.c 11252]
DpHalt: Good Bye .....
trc file: "dev_ms", trc level: 1, release: "720"
[Thr 5176] Sun Dec 25 11:11:41 2011
[Thr 5176] ms / http_max_clients = 500 -> 500
[Thr 5176] MsSSetTrcLog: trc logging active, max size = 52428800 bytes
systemid 562 (PC with Windows NT)
RELN 7200
patchlevel 0
patchno 92
intno 20020600
make multithreaded, Unicode, 64 bit, optimized
pid 4668

Hi Michael,
even if the guides are very detailed in the procedure itself they don't show a dependency between components. I was now browsing and reading to roughly 600 pages of SAP documentation, Wikis, Upgrade guides, EHPI guides etc. and I'm still not clear. According to the guides it is necessary to set up SolMan using Landscape Verification to get the system details right and then use MOPZ.
As always when it comes to dependencies it's very confusing from a technical perspective to make a clear statement.
As a German (speaking) company we would have to do several things:
- map the used "Business process" to SAP terminology
- translate that terminology from SAP-German to SAP-English
- use MOPZ to find out a dependency (or none)
And even then - for my understanding this is all way to complex and intransparent to just find out a "dependency". I will certainly not upgrade SolMan, install LV on Solman with some dozen notes to just find out, whether it may be necessary to upgrade to EHP5 or not. There has to be a different/documented way in finding that information, even if that means opening OSS calls and insisting someone to give a clear statement.
I don't consent setting up a tool and invest time (and hence money) to configure that tool to get information (note: we're not talking about the upgrade itself, just about preparation). The complexity and integration of the components is SAP made, not customer made, and therefore SAP has to give that information, not telling customers to mess with yet-another-complex tool (SolMan).
It shouldn't be too difficult to say that component SAP_CRM 702 needs an SAP_APPL 605 or not.
Just my EUR 0.02.
Markus

WAD 7.0 - SET_CURRENCY_TRANSLATION does not work???

hi folks,
I have a query with one keyfigure. In my webtemplate i want to use the command SET_CURRENCY_TRANSLATION. We have an existing currency translation type in rscur. Name of the transalation type is ZST. I made a button group item in my wad to translate the currency with currency translation type ZST
<bi:BUTTON_GROUP_ITEM name="BUTTON_GROUP_ITEM_1" designheight="23" designwidth="300" >
                <bi:BUTTON_LIST type="ORDEREDLIST" >
                    <bi:BUTTON type="COMPOSITE" index="1" >
                        <bi:CAPTION value="SSSS" />
                        <bi:ACTION type="CHOICE" value="INSTRUCTION" >
                            <bi:INSTRUCTION >
                                <bi:SET_CURRENCY_TRANSLATION >
                                    <bi:TARGET_DATA_PROVIDER_REF_LIST type="ORDEREDLIST" >
                                        <bi:TARGET_DATA_PROVIDER_REF index="1" value="DP_1" />
                                    </bi:TARGET_DATA_PROVIDER_REF_LIST>
                                    <bi:TRANSLATION_MODE value="ZST" />
                                </bi:SET_CURRENCY_TRANSLATION>
                            </bi:INSTRUCTION>
                        </bi:ACTION>
                    </bi:BUTTON>
                </bi:BUTTON_LIST>
            </bi:BUTTON_GROUP_ITEM>
unfortunately, nothing happens.. when i define the currency translation directly in the bex query, it works perfect.
I guess there is another problem. When i execute my wad I choose "Calculations and Translations -> Global Currency Translation" on the Pop-Up i can only choose the SAP standard translation type 0HRFIXCUR. Why can't I see my translation type ZST?
Thanks for your help
Pascal

Hi Pascal,
Does it work if the conversion type with fixed time ref but variable currency(0company-currency)?
because my problem is we have to use the conversion with variable time ref and variable currency.
Thanks for the info.
Regards,
Tienus

Resource-Exception while mapping

Hi,
I'm getting an error "com.sap.aii.utilxi.misc.api.ResourceException: Connection is invalid" ...
<Trace level="3" type="T">Creating Java mapping com/sap/vv2/xi/mapping/OutboundMapping.</Trace>
<Trace level="1" type="T">Connection is invalid.</Trace>
<Trace level="1" type="T">com.sap.aii.utilxi.misc.api.ResourceException: Connection is invalid. at com.sap.aii.utilxi.sql.api.ReusableStatement.get(ReusableStatement.java:74) at com.sap.aii.utilxi.sql.api.ReusableStatement.bind(ReusableStatement.java:183) at com.sap.aii.utilxi.sql.api.AbstractStatement.bind(AbstractStatement.java:152) at
and inside the SOAP-Header/ERROR the message is
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="MAPPING">RESOURCE_EXCEPTION</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Fehler beim Datenbankzugriff.</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
(translation: <SAP:Stack>Error data base access </SAP:Stack> )
Is it a database problem (e.g. tablespace full,...) or where can I check the reason?
Thx
Regards
Wolfgang Hummel

Hello,
I think its related to memory problem, check the below thread.
Resource Exception - Message mapping
Best regards,
raj.

Re: SAP FX translation

Similar Messages

Maybe you are looking for