Comma in long text of routing comma is appearing sepecial character
Hi Experts,
When I am trying to insert comma in long text of routing comma is appearing as sepecial character like <<,>> in long text preview. Please advice how insert comma.
Regards,
Sandy
Edited by: Sandy2 on Apr 20, 2011 10:30 AM
Try to use Line Editor instead of GUI editor ie
from long text screen Goto--> Change Editor and try
a®
Similar Messages
-
Printing long text from Routing instead of Production order for an order.
Hi Gurus,
When a production order prints it is printing the long text from the routing master rather than the long text on the actual production order.
This field is used to provide specific instructions in special circumstances in addition to the standard text.
I need system to be changed so that printing takes long text from production order.
Please help me.
Naveen.AHi,
In the production order long text, the text we are maintaining is only for information. It can't be able to print. In Production order, copies all the masters and the texts which we are maintaining in the masters only will be able to print. Standard SAP will not print the production order long text.
Regards,
V. Suresh -
Display a Long Text in ALV report
Hi,
I want to display the PO header long text in ALV Report that is 255 character width.
Please help me out how to do this.
please it is very urgent
Thanks and regards
KrishnaUse READ_TEXT and concatenate the first lines of the text.
CALL FUNCTION 'READ_TEXT'
EXPORTING
id = 'F01'
language = sy-langu
name = lv_name " purchase order with leading zeroes
object = 'EKKO'
TABLES
lines = t_lines
EXCEPTIONS
OTHERS = 8.
Regards -
Hello Friends,
How can I extract the long text while runing the CADO report?
Regards
Naveenthere is a tab called EXTRAS and select a output line you ll get long text
or make a column appear as TEXT change the layout you ll get to see column which can be made visibke
you should Transaction CATS_DA instead of CADO -
Routing long text editor change
Hi,
When we go to Routing long text and try to open it, it will open one word document.
My requirement is, I want to change that word document as Notepad (text editor) for particular user.
Please tell me is it possible to change that word doc to text doc, If yes then how to make settings?
Regards,
ChetanHi Chetan,
Even I have the same problem ! I had raised a SAP ticket & waiting for the response...
Now can tell me how/what should i do to change to get a particular editor???
Awaiting for your response..
~Guru -
Standard LSMW to load Routing Long text
We are migrating data to sap for Routings. We are using SAP best practices to load the data into sap using idocs. But we dont have idoc structure to load Long Text.
Do you know a LSMW standard direct input to upload the routing long text.
Please help me out.Yes, you can upload long texts to pretty much any application, routings, boms, material masters, etc.
In LSMW select the following direct input method:
Object 0001 Long texts
Method 0001 (No selection)
Program Name /SAPDMC/SAP_LSMW_IMP
Program Type D Direct Input
You can define the following as constants in field mapping and conversion rule.
TDOBJECT C(010) Text: 'ROUTING'
TDID C(004) Text ID : 'PLKO' <<< if you're uploading to header
TDSPRAS C(001) Language : 'EN'
TDFORMAT C(002) Paragraph format for text line : '*'
If you want upload to operations etc look at the following table
ROUTING PLFH Long Text
ROUTING PLFL Long Text
ROUTING PLFT Long text
ROUTING PLFV Long Text
ROUTING PLKO Long Text
ROUTING PLPH Long text
ROUTING PLPO Long Text
internally SAP stores, routing group with zeros padded on the left. For example if your routing group is 200 it will be stored as 00000200 so in your flat file either you have to pad the zeros or in the LSMW you need to use the conversion exit function module.
You can following link below if you want to deeper understanding on this subject.
Re: LSMW : Long text not visible after the import of data -
Hi,
Is there nay table to see routing long text field for the multiple materialDear,
Please refer these threads,
Table for routing operation text?
Re: Long text indicator
Regards,
R.Brahmankar -
Routing Long text not populated using LSMW
I need help with the ROUTING LONG TEXT using LSMW. I'm using the standard LSMW direct input program /SAPDMC/SAP_LSMW_IMP . I'm confused with NAME field while loading the data. I have tried to create the routing long text manually after successful creation i opened the Longtext at header screen and opened GOTO--> HEADER there i have seen TEXT NAME is constructed based on CLIENT || N || GROUP || GROUPCOUNTER || INTERNAL_COUNTER (CLIENT||N||PLNTY||PLNNR||PLNAL||ZAEHL - field names) I used the same logic to construct the test data for another routings which were created and doesn't have the long text. I have run the lsmw program and executed successfully but when i open the routing in CA03 i dont see the long text populated.
Test data used looks like this:
OBJECT NAME TDID SPRAS TEXTFORM TEXTLINE
ROUTING N500000890100000001 PLKO E * THIS IS A TEST1
ROUTING N500000890100000001 PLKO E * THIS IS A TEST2
ROUTING N500000890100000001 PLKO E * THIS IS LINE3
ROUTING N500000910100000001 PLKO E * LONGTEXT1
ROUTING N500000910100000001 PLKO E * LONGTEXT2
My question here is do i need to construct the NAME as i have mentioned above or do i need to just send the Routing Group number into the file for the NAME field. Help me understand what do i need to populate into NAME field.
Please help with the mistake i have done.
Pretty much appriectiated for your replies.You asked the same question in two different forums multiple times:
Standard LSMW to load Routing Long text
Re: LSMW : Long text not visible after the import of data
Please use same one thread for one question.
I gave you most of the needed information assuming you know how to do LSMW in the first thread itself.
You need to have the following fields in your source structure in addition to other fields like long text
MANDT
PLNTY
PLNNR
PLNAL
ZAEHL
In the step Maintain Field Mapping and Conversion Rules assign the source field MANDT to the variable NAME and then again place the cursor on the variable NAME and assign variable PLNTY, (now you have two source field assigned to same variable) similarly assign all the remaining 3 source fields PLNNR, PLNAL, ZAEHL. (now you have 5 source field assigned to same variable).
Now select the variable NAME by placing the cursor click on Rule (Insert Rule) and select the radio button Concatenation .
Make sure that in your input file you have leading zeros for PLNNR PLNAL and ZAEHL etc. like below
50000089, 01, 00000001
Also, you don't need maintain the value of OBJECT, TDID, SPRAS, TEXTFORM as source fields. You can directly maintain them as constants in Maintain Field Mapping and Conversion Rules by click on the push button Rule . -
Hello
We are using SRM7 Extended classic scenario.
We don't use shopping carts, rather create POs directly in SRM which will be transferred to ECC as per the standard.
Error:
I am getting an error "Error while saving Long Texts" during my PO creation. I get this message in a small pop-up screen. As soon as i click ok or close the pop up screen it kicks me out of the PO creation screen back into the main SRM screen.
When:
During the PO Creation
Any specific situation:
Yes, only for Material POs
This is happening when I am creating the PO with a Material code. I can create free text PO without any issues.
This is a standard message and the message number is 022.
Thaks for the help guys.Hi,
To confirm can you check commeting "getOADBTransaction().commit();" gives any error message?
If yes then you can try the following option:
Have you checked whether the "/" is changed to "\" in the dbc file?
In the following two entries the slash has to be made as shown below:
APPS_JDBC_URL=jdbc\:oracle\:thin\:@(DESCRIPTION\=(ADDRESS_LIST\=(LOAD_BALANCE\=YES)(FAILOVER\=YES)(ADDRESS\=(PROTOCOL\=tcp)(HOST\=10.100.503.6)(PORT\=1521)))(CONNECT_DATA\=(SERVICE_NAME\=VIS)))
JDBC\:processEscapes=true
Thanks and Regards,
Lacman -
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,
GuruHi
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
<b>Reward points for useful Answers</b>
Regards
Anji -
Long Text problem in Process order header
Hi All,
I am using SAVE_TEXT FM to update the header long text in process order.
Also, I am updating the field AUFK-LTEXT = 'E'.
But when i display the order and click on long text, it does not display any thing as the text is not saved.
When I update the text directly in the order using COR2, it gets saved.
Does anyone know why the text is not being saved through FM SAVE_TEXT?
Also tried COMMIT WORK but was not successful.
The paramters I am passing to the FM are
TDOBJECT = 'AUFK'
TDID = 'KOPF'
TDSPRAS = SY-LANGU
TDNAME = sy-mandt+order number with leading zeros.
and the text lines in internal table.
Am I missing anything else here?
Thanks,
SandeepHi Sandeep,
First check table STXH for the order which you saved manually, in order to verify that the values you are passing to the FM SAVE_TEXT are correct.
Also check the documentation which is supplied with this function to determine the INSERT and SAVEMODE_DIRECT values.
Also maybe check function COMMIT_TEXT and its documentation.
Regards,
Robert
PS. also test the scenario in which text s/b added to already existing text. The SAVE_TEXT function wipes out everything and therefore you first should read the existing text (READ_TEXT) to retrieve the current text and save this together with the new text using SAVE_TEXT. (check function group STXD for possible related functions to use).
PPS. Thinking about my comments under PS., I recall now that this was the symptom of the long text passed on through BAPI_SALESORDER_CHANGE and therefore maybe this is not the case for SAVE_TEXT.
Edited by: RJ. Schamhart on Feb 3, 2011 4:53 PM -
Problem in long text in SAP script editor
Hi ,
i am maintaining long text in SAP script editor , when i am trying to change the long text in SAP script that changes are not reflected in print preview ,for example when i am giving tabs in the script then in print preview of the PO these tabs are displayed as , , ( comma) , and underlines are not appearing in print preview.please help me on this.
Thanks and regards.
Rajeshwar.hi
you have to install the correct printer which supports the displaying the drawings and objects/ -
Saving/Commiting the Long Text
Hi,
I am trying to save the long text created in a Z Transaction (Table Control). While saving it, I am getting the message as Text Saved". But It is not actually stored in SAP. I am not sure, what is that I am missing. I am using the SAP Standard Routine to Save the Long Text. I am also calling the FM: COMMIT_TEXT explicitly after the long text is saved. Can any one please suggest me, what should I do to commit the long text in SAP?
Appreciate Your Help.
Thanks,
KannanMay be my earlier post was confusing, I was asking you to set the Insert parameter to SPACE and the Savemode_direct to 'X' and see if it works or not. I had the same issue and resolved it using the above parameters. Also try and see if Srinivas's suggestion in the following thread:
Problem with SAVE_TEXT FM
hith
Sunil Achyut -
Hello,
we are working on a process to download longtexts from one system and to upload into another system to add missing long text there for different objects.
We are using SAVE_TEXT and it is working fine for documents in DRAW/DRAT.
Here we got what we expected. Long texts are uploaded and can be edited in the
transaction CV02N.
But then we started with material and with BOMs (bill of material).
Result of upload:
STXH is filled with entries but in MM02 and CS02 we cannot see the added long texts.
Seems that the connection between material and bom and their texts is missing.
For BOM we are not totally wrong. If there is a longtext in the BOM we can add longtext (we READ_TEXT the existing longtext and add our text. Then we do a update) and can see the added longtext in CSxx transactions.
But if there is only a short text, our insert via SAVE_TEXT is not working.
Is there something we are doing wrong or don´t we understand something?
Any help is appreciated.
Best regard
DirkHello Naren,
oh, this answer was bringing light into my confusion.
My problem is that there will be some import files with any long text for any object in R/3 like
material with x textids , bom, equipment etc...
Is there any chance to find out easily which text object combination with textid belongs to a specific long text. The TTXID table is only a listing w/o any explanantion???????
Update longtext in BOM header -> set STZU-LTXSP
Update longtext alternative in BOM header -> set STKO-LTXSP
Update longtext in BOM position -> set STPO-LTXSP
And what is the text ID DPO for?
My other problem now is with Material long text import.
I checked the SDN threats but could not find the answer.
This is my abap that is not running for material.
I can see the long text entries from READ_TEXT, but not in STXH and STXL.
zs_textline_c [ ] = zs_textline_b [ ] .
CALL FUNCTION 'INIT_TEXT'
EXPORTING
id = wa_header-tdid
language = wa_header-tdspras
name = wa_header-tdname
object = wa_header-tdobject
IMPORTING
header = wa_header_b
TABLES
lines = zs_textline_c
EXCEPTIONS
id = 1
language = 2
name = 3
object = 4
OTHERS = 5.
IF sy-subrc <> 0.
ENDIF.
CALL FUNCTION 'SAVE_TEXT'
EXPORTING
client = sy-mandt
header = wa_header_b
insert = 'X'
savemode_direct = 'X'
owner_specified = 'X'
local_cat = ' '
IMPORTING
function = l_result
NEWHEADER =
TABLES
lines = zs_textline_b
EXCEPTIONS
id = 1
language = 2
name = 3
object = 4
OTHERS = 5
IF sy-subrc <> 0.
ENDIF.
CALL FUNCTION 'COMMIT_TEXT'.
COMMIT WORK.
Your help is welcome!
Best regards
Dirk
Edited by: Dirk Meinhard on Mar 31, 2009 4:33 PM -
Populate long text in transaction QM01
Hi,
I'm trying to populate long text in transaction QM01, meaning, when the user creates a new notification, a constant text should appear automatically.
I currently use enhancement QQMA0007 user exit EXIT_SAPMIWO0_001.
I found FM IQS0_ADD_NOTIFICATION_LONGTEXT which works fine when the notification already exists, but when creating a new notification I still have no number to put in the FM parameters.
Does anyone has an idea?
Thank's,
Hagit.Hi Hagit,
First, in the userexit that gets triggered when saving the notification, call a subroutine via PERFORM .... ON COMMIT.
In this subroutine, you will put the code to update the text and access the notification number using field symbols.
When a subroutine is called ON COMMIT, it means that the subroutine waits in memory until the transaction issues a COMMIT WORK. Once the transaction has issued a COMMIT WORK, the subroutine is called.
At this point, the notification number will have been generated.
In this subroutine, put a break point so you can examine all the memory areas to find the notification number. I suggest that the field VIQMEL-QMNUM in program SAPLIQS0 should have it [type (SAPLIQSO)VIQMEL-QMNUM in the watch fields to check its contents].
As an alternative, whilst looking at the transaction, I noticed some BADIs, the BADI CL_EX_NOTIF_CREATE_OBJ looks promising. Have you tried this one? Maybe the notification number is passed to you here.
Cheers,
Brad
Maybe you are looking for
-
In SAP ECC 6.0 - this relates only for Standard NB PO's we create to procure from a Supplier. With new Service Packs we are currently testing, the GRBIV indicator is now required if the Split IV indicator is selected on the PO item screen. I have r
-
Hi, I want to connect swf file running in www.xxx.com via socket to www.xxx.com:25 My crossdomain.xml looks like: <?xml version="1.0"?> <!DOCTYPE cross-domain-policy SYSTEM " http://www.macromedia.com/xml/dtds/cross-domain-policy.dtd"> <cross-domain-
-
Is 7.5 mm ssd FIT for macbook pro ??
hi im using macbook pro early 2011. now i want to upgrade my macbook pro. can i use 7.5 mm SSD harddisk on my macbook ?? is 7.5 mm SSD fit for macbookpro ?? Best Regards. Message was edited by: uzk Message was edited by: uzk
-
I am beginning the daunting process of sorting through all of my photos to make sure the date is correct. I made a change on a couple of photos, they then disappeared, presumably to the correct date. However, when scrolling to the spot it should ha
-
I'm looking for information/instructions on how to integrate a Captivate version 3 movie into FrameMaker version 8. If anyone has suggestions, I'd appreciate your help.