Defaulting long text in fmbbc

Hi to all experts,
I have requirement of defaulting long text in transaction FMBBC . when the user clicks on long text button some text should be defaulted is it possible. Im thinking of using enhancement points to achieve this .

you are right that the only way to do it.
Atul

Similar Messages

Default Long Text required for KP06

Hello Gurus,
In KP06 for Cost Center / Cost Element planning, Long Text is available at Cost Element level (Overview screen). How can I change this to ONLY allow for Long Text at the next level (Period Screen)..... So that the Planner can create Long Text e.g for Period 1 but not for Period 2.
I am hoping for a functional solution. Please help.
Regards Debra

Naveen Navins,
Define Formula in the Profile Form !!!! cannot see how a formula can help
Can you elaborate, please supply intructions, thanks in advance
Debi

Default values for long text for mic in inspection plan

hi,
Some long text are coming default when i am creating inpection plan for mic.
This is coming for only particular plant. For other plant it is not coming. Is there anywhere we can make it as default for a particualar line item . ie for particular characteristics i.e 10, 20 etc
sathish. R

Hi,
I am not sure , whether you are mentioning about Long text for MIC or Default insp char number (10,20,30..) in the insp plan.
If you are talking about Insp char number in the insp plan . you can specify the same in SPRO , QM->Q planning ->Insp planning -> General -> Maintain profiles for default values.
Regards
K.M.Arun

Default Production Order Component Long Text

Dear guru ,
Whose are the defaults for production order component long text ?
Can I copy this text only from bom ?
Can I copy this text also from material master ?
Thanks

Hi,
The defaults are from the BOM item text 1 & 2. POTX1 & POTX2 fields.
I suppose no option from material master.
Hope this helps
Regards
Raju

Can not see long text description of a characteristics in portal

Hi experts,
I designed two queries via Query designer and published them to portal but I can not see the the long text description of "Name" attribute belongs to 0BPARTNER characteristics.
One of the queries shows only the last name of partner in portal while it is showing full name and last name in Bex Analyzer. The other query shows only the key value in both portal and Bex Analyzer.
I want to see long text description in both queries.
For an additional information, I'm extracting data from CRM 5.00 to BW 7.00
What will be the reason for this and how can I solve it?
Can anyone help me for this issue, it's a kind of emergency situation.

Hi,
we have the same problem.
We want to change only in the screen variable the hierarchy text (from default to long\medium text) but even if there's a possibility to do this, really it doesn't happen anything - it' s possible when you start query, in the selection screen inside every the variable there's a command "User Settings" in which manage what you want to see (I put display custom, as text, medium text).
I try to do this also in query analizer, selecting variable (hierarchy) and enter in this (user setting), changing in display custom as text - medium text, but even if I save this settings, really doesn't happen anything.
It seems the system isn't sensitive to this selection...
By now, if someone has an answer, please write us!
Thanks in advance,
Alessandra Mirone

Long text doesn't fit the window exactly

Hi friends,
in PO smartforms i have included the header text of PO.
the problem is the long text doesn't fit to the window exactly i.e.,
when we enter the text in PO in the header a line can contain only 60 characters approximately where as in my smartforms it can contain more than that.
so in the display of smart form i get lot of space in the right side and i get the remaining part of text in the next line.
regards,
Saravan raj

hi,
what u have told is correct but we can't expect the end user to do it each time when they paste the long text.
is there any option to bring it by default.
regards,
saravan raj

How to get Long text in CJ20n

Hi,
I need to get the long text that we maintained in CJ20n tcode under long text at project level. I need to display the same in Script layout or report. I didnot find any table or functional module to get it. please help me out.
regards,
Chandra

Hi
Double click on the Long text, it will take you to Text editor
from the Menu GOTO-> HEADER
you will find the OBJECT,ID,OBJECTNAME and LANGUAGE parameters for that lang text which are to be passed to the READ_TEXT fun module
for displaying it on report use the above fun module and fetch the text in IT_LINES internal table and write it on report output
You can also see the doc of the read_text
READ_TEXT
READ_TEXT provides a text for the application program in the specified work areas.
The function module reads the desired text from the text file, the text memory, or the archive. You must fully specify the text using OBJECT, NAME, ID, and LANGUAGE. An internal work area can hold only one text; therefore, generic specifications are not allowed with these options.
After successful reading, the system places header information and text lines into the work areas specified with HEADER and LINES.
If a reference text is used, SAPscript automatically processes the reference chain and provides the text lines found in the text at the end of the chain. If an error occurs, the system leaves the function module and triggers the exception REFERENCE_CHECK.
Function call:
CALL FUNCTION 'READ_TEXT'
EXPORTING CLIENT = SY-MANDT
OBJECT = ?...
NAME = ?...
ID = ?...
LANGUAGE = ?...
ARCHIVE_HANDLE = 0
IMPORTING HEADER =
TABLES LINES = ?...
EXCEPTIONS ID =
LANGUAGE =
NAME =
NOT_FOUND =
OBJECT =
REFERENCE_CHECK =
WRONG_ACCESS_TO_ARCHIVE =
Export parameters:
CLIENT
Specify the client under which the text is stored. If you omit this parameter, the system uses the current client as default.
Reference field: SY-MANDT
Default value: SY-MANDT
OBJECT
Enter the name of the text object to which the text is allocated. Table TTXOB contains the valid objects.
Reference field: THEAD-TDOBJECT
NAME
Enter the name of the text module. The name may be up to 70 characters long. Its internal structure depends on the text object used.
Reference field: THEAD-TDNAME
ID
Enter the text ID of the text module. Table TTXID contains the valid text IDs, depending on the text object.
Reference field: THEAD-TDID
LANGUAGE
Enter the language key of the text module. The system accepts only languages that are defined in table T002.
Reference field: THEAD-TDSPRAS
ARCHIVE_HANDLE
If you want to read the text from the archive, you must enter a handle here. The system uses it to access the archive. You can create the handle using the function module ACHIVE_OPEN_FOR_READ.
The value '0' indicates that you do not want to read the text from the archive.
Reference field: SY-TABIX
Default value: 0
Import parameters:
HEADER
If the system finds the desired text, it returns the text header in this parameter.
Structure: THEAD
Table parameters:
LINES
The table contains all text lines that belong to the text read.
Structure: TLINE
Exceptions:
ID
The text ID specified in the parameter ID does not exist in table TTXID. It must be defined there together with the object of the text module.
LANGUAGE
The parameter LANGUAGE contains a language key that does not exist in table T002.
NAME
The parameter NAME contains the name of a text module that does not correspond to the SAPscript conventions.
Possible errors:
The field contains only blanks.
The field contains the invalid characters * or ,.
OBJECT
The parameter OBJECT contains the name of a text object that does not exist in table TTXOB.
NOT_FOUND
The system did not find the specified text module.
REFERENCE_CHECK
The text module to be read has no text lines of its own but refers to the lines of another text module. This reference chain can include several levels. For the current text, the chain is interrupted, that is, one of the text modules referred to in the chain no longer exists.
WRONG_ACCESS_ TO_ARCHIVE
The exception WRONG_ACCESS_TO_ARCHIVE is triggered if an archive is accessed using an incorrect or non-existing archive handle or an incorrect mode (that is, read if the archive is open for writing or vice versa).
IN SCRIPTS you can use the INCLUDE statement to print the Long texts
/: INCLUDE TEXT<name> ID <id> Lang <en> paragraph <za>
Regards
Anji

How to get Long text in report from FBL3N

Hi,
I need to get Long Text from FBL3N (G/L Account Line Item Display) in my report.Can anyone tell me in which table it is stored?

Hi
These long texts are not stored completely in any tables
where as the parameters of these texts like OBJECT,OBJECTNAME and ID, LANGUAGE are stored in STXH table
You have to pass these 4 parameters to the fun module READ_TEXT and to fetch the text.
Double click on the long text will goes to text editor
from menu GOTO-> HEADER you will see the above 4 paramters
see the doc of READ_TEXT fun module
READ_TEXT
READ_TEXT provides a text for the application program in the specified work areas.
The function module reads the desired text from the text file, the text memory, or the archive. You must fully specify the text using OBJECT, NAME, ID, and LANGUAGE. An internal work area can hold only one text; therefore, generic specifications are not allowed with these options.
After successful reading, the system places header information and text lines into the work areas specified with HEADER and LINES.
If a reference text is used, SAPscript automatically processes the reference chain and provides the text lines found in the text at the end of the chain. If an error occurs, the system leaves the function module and triggers the exception REFERENCE_CHECK.
Function call:
CALL FUNCTION 'READ_TEXT'
EXPORTING CLIENT = SY-MANDT
OBJECT = ?...
NAME = ?...
ID = ?...
LANGUAGE = ?...
ARCHIVE_HANDLE = 0
IMPORTING HEADER =
TABLES LINES = ?...
EXCEPTIONS ID =
LANGUAGE =
NAME =
NOT_FOUND =
OBJECT =
REFERENCE_CHECK =
WRONG_ACCESS_TO_ARCHIVE =
Export parameters:
CLIENT
Specify the client under which the text is stored. If you omit this parameter, the system uses the current client as default.
Reference field: SY-MANDT
Default value: SY-MANDT
OBJECT
Enter the name of the text object to which the text is allocated. Table TTXOB contains the valid objects.
Reference field: THEAD-TDOBJECT
NAME
Enter the name of the text module. The name may be up to 70 characters long. Its internal structure depends on the text object used.
Reference field: THEAD-TDNAME
ID
Enter the text ID of the text module. Table TTXID contains the valid text IDs, depending on the text object.
Reference field: THEAD-TDID
LANGUAGE
Enter the language key of the text module. The system accepts only languages that are defined in table T002.
Reference field: THEAD-TDSPRAS
ARCHIVE_HANDLE
If you want to read the text from the archive, you must enter a handle here. The system uses it to access the archive. You can create the handle using the function module ACHIVE_OPEN_FOR_READ.
The value '0' indicates that you do not want to read the text from the archive.
Reference field: SY-TABIX
Default value: 0
Import parameters:
HEADER
If the system finds the desired text, it returns the text header in this parameter.
Structure: THEAD
Table parameters:
LINES
The table contains all text lines that belong to the text read.
Structure: TLINE
Exceptions:
ID
The text ID specified in the parameter ID does not exist in table TTXID. It must be defined there together with the object of the text module.
LANGUAGE
The parameter LANGUAGE contains a language key that does not exist in table T002.
NAME
The parameter NAME contains the name of a text module that does not correspond to the SAPscript conventions.
Possible errors:
The field contains only blanks.
The field contains the invalid characters * or ,.
OBJECT
The parameter OBJECT contains the name of a text object that does not exist in table TTXOB.
NOT_FOUND
The system did not find the specified text module.
REFERENCE_CHECK
The text module to be read has no text lines of its own but refers to the lines of another text module. This reference chain can include several levels. For the current text, the chain is interrupted, that is, one of the text modules referred to in the chain no longer exists.
WRONG_ACCESS_ TO_ARCHIVE
The exception WRONG_ACCESS_TO_ARCHIVE is triggered if an archive is accessed using an incorrect or non-existing archive handle or an incorrect mode (that is, read if the archive is open for writing or vice versa).
Reward points for useful Answers
Regards
Anji

Box in Long text of sapscript

Hi All,
I have created a script.....in that i have to print only long text in the main window.
Now my problem is...the LONG text is breaking and going to next page...
means a part on 1 page and remaining on subsequent pages..
And the problem is the box which i have put arround the main window is coming only in first page and last page . In between pages the box arround the main window is not coming .
How to get the box around those pages also.
help me out...
Thanks,
Guru

Hi
The property of MAIN window is like that, If the Data is more than a Page it automatically goes to next pages.
So better decide where I mean in which you wants to print ? In MAin window , then it automatcially goes to other pages. use a new paragraph format and mention PAGE PROTECTION for that such that it prints in the Same page.
For the boxes see the seetings of the main window in all pages, especially in NEXT page.. so that the box is coming properly
see the box related commands
SAPScripts
POSITION WINDOW
SIZE WIDTH '160' MM HEIGHT '140' MM
BOX FRAME 10 TW
Box
BOX HEIGHT '11' MM WIDTH '160' MM FRAME 10 TW INTENSITY 35
linessssssss
BOX XPOS '20' MM WIDTH 0 TW HEIGHT '140' MM FRAME 10 TW
BOX XPOS '45' MM WIDTH 0 TW HEIGHT '140' MM FRAME 10 TW
BOX XPOS '80' MM WIDTH 0 TW HEIGHT '140' MM FRAME 10 TW
BOX XPOS '120' MM WIDTH 0 TW HEIGHT '140' MM FRAME 10 TW
Boxes, Lines, Shading: BOX, POSITION, SIZE
Use the BOX, POSITION, and SIZE commands for drawing boxes, lines, and shading to print particular windows within a form or passages of text within a window in a frame or with shading.
The SAP printer drivers that are based on page-oriented printers (the HP LaserJet driver HPL2, the Postscript driver POST, the Kyocera Prescribe driver PRES) employ these commands when printing. Line printers and page-oriented printers not supported in the standard ignore these commands. You can view the resulting printer output in the SAPscript print preview.
Syntax:
/: BOX [XPOS] [YPOS] [WIDTH] [HEIGHT] [FRAME] [INTENSITY]
/: POSITION [XORIGIN] [YORIGIN] [WINDOW] [PAGE]
/: SIZE [WIDTH] [HEIGHT] [WINDOW] [PAGE]
BOX Command
Syntax
/: BOX [XPOS] [YPOS] [WIDTH] [HEIGHT] [FRAME] [INTENSITY]
Effect: draws a box of the specified size at the specified position.
Parameters: For each of XPOS, YPOS, WIDTH, HEIGHT, and FRAME, you must specify both a measurement and a unit of measurement. Specify the INTENSITY parameter as a percentage between 0 and 100.
XPOS, YPOS
Upper left corner of the box, relative to the values of the POSITION command.
Default: Values specified in the POSITION command.
The following calculation is performed internally to determine the absolute output position of a box on the page:
X(abs) = XORIGIN + XPOS
Y(abs) = YORIGIN + YPOS
WIDTH
Width of the box. Default: WIDTH value of the SIZE command.
HEIGHT
Height of the box. Default: HEIGHT value of the SIZE command.
FRAME
Thickness of frame.
Default: 0 (no frame).
INTENSITY
Grayscale of box contents as %.
Default: 100 (full black)
Measurements: You must specify decimal numbers as literal values (like ABAP numeric constants) by enclosing them in inverted commas. Use the period as the decimal point character. See also the examples listed below.
Units of measurement: The following units of measurement may be used:
TW (twip)
PT (point)
IN (inch)
MM (millimeter)
CM (centimeter)
LN (line)
CH (character).
The following conversion factors apply:
1 TW = 1/20 PT
1 PT = 1/72 IN
1 IN = 2.54 CM
1 CM = 10 MM
1 CH = height of a character relative to the CPI specification in the form header
1 LN = height of a line relative to the LPI specification in the form header
/: BOX FRAME 10 TW
Draws a frame around the current window with a frame thickness of 10 TW (= 0.5 PT).
/: BOX INTENSITY 10
Fills the window background with shading having a gray scale of 10 %.
/: BOX HEIGHT 0 TW FRAME 10 TW
Draws a horizontal line across the complete top edge of the window.
/: BOX WIDTH 0 TW FRAME 10 TW
Draws a vertical line along the complete height of the left hand edge of the window.
/: BOX WIDTH '17.5' CM HEIGHT 1 CM FRAME 10 TW INTENSITY 15
/: BOX WIDTH '17.5' CM HEIGHT '13.5' CM FRAME 10 TW
/: BOX XPOS '10.0' CM WIDTH 0 TW HEIGHT '13.5' CM FRAME 10 TW
/: BOX XPOS '13.5' CM WIDTH 0 TW HEIGHT '13.5' CM FRAME 10 TW
Draws two rectangles and two lines to construct a table of three columns with a highlighted heading section.
POSITION Command
Syntax
/: POSITION [XORIGIN] [YORIGIN] [WINDOW] [PAGE]
Effect: Sets the origin for the coordinate system used by the XPOS and YPOS parameters of the BOX command. When a window is first started, the POSITION value is set to refer to the upper left corner of the window (default setting).
Parameters: If a parameter value does not have a leading sign, then its value is interpreted as an absolute value, in other words, as a value that specifies an offset from the upper left corner of the output page. If a parameter value is specified with a leading sign, then the new value of the parameter is calculated relative to the old value. If one of the parameter specifications is missing, then no change is made to this parameter.
XORIGIN, YORIGIN
Origin of the coordinate system.
WINDOW
Sets the values for the left and upper edges to match those of the current window (default setting).
PAGE
Sets the values for the left and upper edges to match those of the current output page (XORIGIN = 0 cm, YORIGIN = 0 cm).
/: POSITION WINDOW
Sets the origin for the coordinate system to the upper left corner of the window.
/: POSITION XORIGIN 2 CM YORIGIN '2.5 CM'
Sets the origin for the coordinate system to a point 2 cm from the left edge and 2.5 cm from the upper edge of the output page.
/: POSITION XORIGIN '-1.5' CM YORIGIN -1 CM
Shifts the origin for the coordinates 1.5 cm to the left and 1 cm up.
SIZE Command
Syntax
/: SIZE [WIDTH] [HEIGHT] [WINDOW] [PAGE]
Effect: Sets the values of the WIDTH and HEIGHT parameters used in the BOX command. When a window is first started, the SIZE value is set to the same values as the window itself (default setting).
Parameters: If one of the parameter specifications is missing, then no change is made to the current value of this parameter. If a parameter value does not have a leading sign, then its value is interpreted as an absolute value. If a parameter value is specified with a leading sign, then the new value of the parameter is calculated relative to the old value.
WIDTH, HEIGHT
Dimensions of the rectangle or line.
WINDOW
Sets the values for the width and height to the values of the current window (default setting).
PAGE
Sets the values for the width and height to the values of the current output page.
/: SIZE WINDOW
Sets WIDTH and HEIGHT to the current window dimensions.
/: SIZE WIDTH '3.5' CM HEIGHT '7.6' CM
Sets WIDTH to 3.5 cm and HEIGHT to 7.6 cm.
/: POSITION WINDOW
/: POSITION XORIGIN -20 TW YORIGIN -20 TW
/: SIZE WIDTH +40 TW HEIGHT +40 TW
/: BOX FRAME 10 TW
A frame is added to the current window. The edges of the frame extend beyond the edges of the window itself, so as to avoid obscuring the leading and trailing text characters.
http://esnips.com/doc/1ff9f8e8-0a4c-42a7-8819-6e3ff9e7ab44/sapscripts.pdf
http://esnips.com/doc/1e487f0c-8009-4ae1-9f9c-c07bd953dbfa/script-command.pdf
http://esnips.com/doc/64d4eccb-e09b-48e1-9be9-e2818d73f074/faqss.pdf
http://esnips.com/doc/cb7e39b4-3161-437f-bfc6-21e6a50e1b39/sscript.pdf
http://esnips.com/doc/fced4d36-ba52-4df9-ab35-b3d194830bbf/symbols-in-scripts.pdf
http://esnips.com/doc/b57e8989-ccf0-40d0-8992-8183be831030/sapscript-how-to-calculate-totals-and-subtotals.htm
Reward points for useful Answers
Regards
Anji

Loaded data is not yet visible in Reporting (see long text) Message no. RSM

Hi All,
I have one issue in BI part of Solman. For one of the scenario of Solution Manager uses its own BI component (BI_CONT 7.03 SP08 SAP_BW 700 SP15).
There is one background job which has to update the data in one of the infocube 0SMD_PE2D. This job is getting failed for the past 2 months.
When i check the logs of that background job, it shows the long text as below.
Loaded data is not yet visible in Reporting (see long text)
Message no. RSM1130
Diagnosis
There is an inconsistency between the load status of the data and the option of reporting on this data.
There is data in the InfoProvider that is OK from a quality point of view, but is not yet displayed in reporting.
The problem, for example, is to do with request 0000000494, number APO_R4CEHVODV7XS7MRL741GSMV9UB.
Procedure
Choose Refresh to remove the inconsistency.
I went to RSA1 and selected that cube and choose "Execution changes - Manage". On the right hand side under request tab page it shows all the requests with request status as Green. In Monitor there is No Data Available
I found a similar thread [Loaded data is not yet visible in Reporting for Data Mart destination cub; unfortunately solution is not updated.
Could any one help me
regards
Naveen

Hi Aduri,
In LISTCUBE i am getting the following error
SQL Error 0
Unknown error in SQL interface
System error in program SAPLRS_EXCEPTION and form RS_EXCEPTION_TO_MESSAGE
Source system is Solution Manager only, production client and BI by default its running in 001 client. We dont have any APO system in our landscape.
Kindly advice
Regards
Naveen

Default header texts in purchase order

Hi,
I would like to ask you for help in following case.
I need to set default purchase header text when a new PO is created in me21n.
I found transaction VOTX where can be this done for sales order, but not for PO. Is there anything similar also in MM?
Maybe I could use user exits in MM06E005, but I didn't find the relevant structure which keeps header texts.
Third idea is to add header text fields into personal setting in me21n, where each user can define his own default texts but I have no idea how to do that.
I need to set default texts which are global for all purchase orders, so it has no sense to use Info record in this case.
Has anybody experience with this? I would appreciate any help. Thanks.

Hi,
you can try to solve it using BADI ME_PROCESS_PO_CUST. The method open is suitable for you problem. Here is a quote from a BADI documentation.
The OPEN method enables you to do the following when opening a new
document:
o Import new data if the document was already posted to the database
o Initialize your own data when creating a new document
You get a reference for object with type IF_PURCHASE_ORDER_MM in this method. This class implements interface IF_LONGTEXTS_MM with methods like IF_LONGTEXTS_MMGET_TEXT and IF_LONGTEXTS_MMSET_TEXT. So you should be able to set long text for your new PO in this method. Check BADI documentation for more info.
Cheers

Unable to upload RTF file in the long text

Hi all,
Could you please help me out in this issue. I am trying to upload the RTF file in the long text editor through this menu path Text-> Upload->RTF file.The RTF file is about only 56 KB memory size consists only texts.
I could able to select the file and when i am executing , ABAP dump is showing as follows:
Runtime error : TABLE_INVALID_INDEX
abap program : SAPLSTXK
Whether any SAP notes to be applied for this ?
Please throw you ideas
Regards,
Suresh.

try this.
REPORT YCMTESTE LINE-SIZE 255 MESSAGE-ID TD.
PARAMETERS:
TEXTNAME LIKE THEAD-TDNAME DEFAULT 'SAPSCRIPT-DRUCKERTEST',
FILE LIKE RLGRAP-FILENAME DEFAULT 'C:\temp\'.
DATA: TEXTHEADER LIKE THEAD.
DATA: TEXTLINES LIKE TLINE OCCURS 100 WITH HEADER LINE.
CALL FUNCTION 'READ_TEXT'
EXPORTING NAME = TEXTNAME
LANGUAGE = SY-LANGU
OBJECT = 'TEXT'
ID = 'ST '
IMPORTING HEADER = TEXTHEADER
TABLES LINES = TEXTLINES
EXCEPTIONS OTHERS = 1.
CHECK SY-SUBRC = 0.
CALL FUNCTION 'EXPORT_TEXT'
EXPORTING CODEPAGE = '1133'
FILE = FILE
FORMATWIDTH = 132
FORMAT_TYPE = 'RTF'
HEADER = TEXTHEADER
SSHEET = ' '
WITH_TAB = ' '
TABLES ITF_LINES = TEXTLINES
EXCEPTIONS DOWNLOAD_ERROR = 1
FILE_OPEN_ERROR = 2
FILE_WRITE_ERROR = 3.
CASE SY-SUBRC.
WHEN 0. MESSAGE S807 WITH FILE.
WHEN 1. MESSAGE E815 WITH FILE.
WHEN 2. MESSAGE E811 WITH FILE.
WHEN 3. MESSAGE E814 WITH FILE.
ENDCASE.
Reference::[http://help.sap.com/saphelp_sm32/helpdata/en/d6/0db7f3494511d182b70000e829fbfe/content.htm]
<removed_by_moderator>
Edited by: Juan Reyes on May 16, 2011 12:05 PM

Getting Long Text of a Field Label

Hi Friends,
I have requirement in which , based on the filed I need get the Long text of the data element.by default I am able to access the medium text of the data element. is there any function-module for getting Long text?
Regards,
Xavier.P

Hi Xavier,
check this
Storing long text data
hope it helps you.
Regards!

Special Characters in Long Text Field of FI Documents

Hi,
Users entered the following in the long text field of a FI document:
"Settlement of claims for direct shipment (Refer to XXX/YY-053/2009, XXX/YY-018/2009, XX2120000031 and X2120000033)"
The default editor used is the one which looks like the MS Word.
When we changd to the other editor (Goto > Change Editor), we see the following:
"Settlement of claims for direct shipment to Thailand (Refer to"
"XXX/YY-053/2009<(>,<)> XXX/YY-018/2009, XX2120000031 and X2120000033)"
How did "<(>,<)> " comes about?
Any ideas?

I'd probably use a regex of "allowed" characters rather than a list of "disallowed" characters, but thats just a difference in approach.
I would probably use a regular expression - alphanumeric is fairly easy to check
String value = request.getParameter("enteredField");
boolean alphaNumericOnly = value.matches("\\w+");As a matter of being nice to the user, you can also do this check in javascript on the client side.
ALWAYS validate server side.
Optionally validate client side to give the user a better experience (less round trip requests)
Cheers,
evnafets

Put Fixed guide line in long text of Notification: IW21

Hi,
I have an requirement where I need to put some fixed guide line in the notification long text whenever notification order gets created.
For an example below guidelines need to be incorporated automatically in the long text of notification whenever they get created
Ex:
Long Text Template as follows:
Detailed description of fault:
What caused the fault?
Action taken to date:
Who:
Suggested Repair / resourcec:
Please suggest how can I implement this requirement?
Appreciate your help in advance.
Thanks,
Jay.
Moderator message : Duplicate post locked. Continue with original thread.
Edited by: Vinod Kumar on Sep 14, 2011 11:29 AM

Hi,
Check the user exit :- QQMA0025 PM/SM: Default values when adding a notification
For wiring into longtext i think u can update via WRITE_TEXT
You should also ensure that this information should not be changed
regards
pushpa

Defaulting long text in fmbbc

Similar Messages

Maybe you are looking for