Invalid characters ?

Hi there,
I've got the following problem: when writing some types of quotation marks into a varchar-field, they somehow get corrupted. When I read the field again, they show upside-down question marks instead.
These types of quotation marks don't pose a problem:
" Â´ `
These do:
â â â â â â
You get the ones that pose a problem f.e. when copying text out of a Word document. If you want to see the differences, copy them to Word and use Arial 20.
I could simply replace them but that would mean a LOT of work on many different pages. Why can't Oracle (8) save them normally ? Why do I get "Â¿" instead ? Is this some sort of codepage-Problem ?
Thanks for your help,
Thomas

The database uses WE8ISO8859P1, whereas I would need WE8MSWIN1252, especially for the â¬-sign. What do you think will happen if I dump the old database into a new one with the right character set ? What will happen with the unmapped characters ?
What would the behaviour be like if I changed the nls_characterset of the database to what I want ? Does anything have to be remapped ? If yes, are there any mechanisms for that ?
And why the hell can MySQL store the â¬-Sign, when it is also set to latin1 ??? Latin1 usually stands for ISO-8859-1 as far as I know, so it shouldn't support the â¬-sign ... Ok, that's not a question for this forum. :-)
Thanks so far !

Similar Messages

Error message if invalid characters entered in PM order oper.short text fld

Hi ALL,
I need to display a error message, when user enters the invalid characters in work order operation short text field. The error message should be displayed during work order u201CSaveu201D (during creation and change mode).
Kindly let me know is there is any user exit / BADI can be used for this.
Note: I have checked some user exit, such as IWO10009 but I am not getting the value of Operation short text (AFVGD-LTXA1) to compare and throw the error message
Regards
Ramu

hi
the exit is correct but don't use structure field,
follow this to get text
get AUFPL(Routing number of operations in the order)from CAUFV and paa it in AFVC -AUFPLyou get the short text
it can be usefull
-ashok

Discoverer Report showing invalid characters in the report data

Hi,
Can you please help me. I have designed a discoverer report in discoverer desktop 4i, when it is running the data showing some invalid characters in the data like below.
kara¿ah L¿MAK HOLD¿NG A.¿
I have executed the same query in sql plus at that time the data shows correctly. Please let me know, is there any settings required.
Best Regards,
Umamaheshwar.

Hi Umamaheshwar
This could be a registry setting. Let me give you some background. In the Windows registy, every Oracle Home has a setting called NLS_LANG. This is the variable that controls, among other things, the numeric characters and the language used. The variable is made up of 3 parts. These are:
language_territory.characterset
Notice how there is an underscore character between the first two variables and a period between the last two. This is very important and must not be changed.
So, for example, most American settings look like this: AMERICAN_AMERICA.WE8MSWIN1252
The second variable, the territory, controls the default date, monetary, and numeric formats and must correspond to the name of a country. So if I wanted to use the Greek settings for numeric formatting, editing the NLS_LANG for Discoverer Desktop to this setting will do the trick:
AMERICAN_GREECE.WE8MSWIN1252
Can you please check your settings? Here's a workflow:
a) Open up your registry by running Regedit
b) Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE
c) Look for the Oracle Home corresponding to where Discoverer Desktop is installed. It's probably called KEY_ORANT
d) Clicking on the Oracle Home will display all of the variables
e) Take a look at the variable called NLS_LANG - if it is correct Exit the registry
f) If its not correct please right-click on it and from the pop-up select Modify
f) Change the variable to the right setting
g) Click the OK button to save your change
h) Exit the registry
Best wishes
Michael

PHP MYSQL and DW Question: Invalid characters and new lines entry/viewing

Hello all,
I have followed David Powers' two php/dw/mysql books and I've
set up PHP
pages that insert, edit, delete, etc. listings. Everything
works fine
except for invalid characters being inserted into the
database, and then
displaying with a question mark in firefox.
Is there a trick to cleaning up the data that a user may
paste into a
textbox on a web page for insertion in the database before
the data is
inserted or as it is inserted? Em dashes, en dashes, 'curly
quotes' etc.
are giving me problems.
Also, when I enter new lines into the php page while I'm
typing out
information for a record, these new lines are not being
displayed either
in the database (using phpmyadmin to view) or on the
resulting details
pages, even though I'm using nl2br, etc. Is there a way to
make this
work reliably?
Thank you for any help you may give me!
-John

Hello all,
I have followed David Powers' two php/dw/mysql books and I've
set up PHP
pages that insert, edit, delete, etc. listings. Everything
works fine
except for invalid characters being inserted into the
database, and then
displaying with a question mark in firefox.
Is there a trick to cleaning up the data that a user may
paste into a
textbox on a web page for insertion in the database before
the data is
inserted or as it is inserted? Em dashes, en dashes, 'curly
quotes' etc.
are giving me problems.
Also, when I enter new lines into the php page while I'm
typing out
information for a record, these new lines are not being
displayed either
in the database (using phpmyadmin to view) or on the
resulting details
pages, even though I'm using nl2br, etc. Is there a way to
make this
work reliably?
Thank you for any help you may give me!
-John

Value 'KIRBYu00A0' of characteristic 0SORTL contains invalid characters

hello experts!
i am facing this error while activating 0vendor. data not available either in info object master neither in psa.
Error Message: Value 'KIRBY ' (hex. '004B004900520042005900A0') of characteristic 0SORTL contains invalid characters
Message no. BRAIN060
Diagnosis
Only the following standard characters are valid in characteristic values by default:
!"%&''()*+,-./:;<=>?_0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ.
Furthermore, characteristic values that only consist of the character # or that begin with ! are not valid.
You are trying to load the invalid characteristic value 1. (hexidecimal representation 004B004900520042005900A0).
Procedure for System Administration
Try to change the invalid characters to valid characters.
If you want values that contain invalid characters to be admitted into the system, make the appropriate setting in BW Customizing. Refer to the documentation describing the requirements for special characters and the possible consequences.
For more information on the problems involved with valid and invalid characters, click here.
regards
vijay

Hi Vijay,
after KIRBY is a characteristic value which cannot be interpreted by BW properply / is not in the valid char list.
KRIBY is hex value 004B0049005200420059
the invalid char is hex value 00A0 -> online hex converter didn't found a ASCI match.
To solve the problem you will need to fix the record in the source. Or you go to PSA -> delete all in teh field and re-enter KRIBY.
Best regards,
Axel

Invalid characters error while ODS activation

I have 2 queries regarding Invalid characters
1) I got following error while activating ODS.
Value 'HYDERABAD - IV COMMISSIONERATE ' (hex. '485944455241424144202D204956A020434F4D4D495353494F') of characteristic ZEXCRG contains invalid characters
 I added space (ALT+255) in RSKC as suggested in other threads and activated the ODS.('-' is already there in RSKC).
Above record did not give any error but got the same error for another record.
Value 'SURAT II ' (hex. '53555241542096204949 ') of characteristic ZEXCRG contains invalid characters
 Can anybody tell me why there is difference between in representation(HEX) of same char and which char should I add to RSKC to solve the error?
2) RSKC_ALLOWED_CHAR_GET lists the space as default allowed char, so why do I need to add the same again?

Hi Vikram:
go to RSKC: do a ALL_CAPITAL. then do the permitted charcters in BW(do a F1 and copy all and paste). also, please be advised that add ~ (tilda) and take a closer look at the error you got and insert that there.
hope it should fix the issue.
assign points if helpful
kalyan

Date / / contains invalid characters IN MODULE POOL

Hi,
I have a display field in infotype creation which will take always take current date.I have tried using the screen field as sy-datum and also tried using z-field with data type char or dats.but when ia am inserting values in a editable field on the screen and pressing enter ,it is giving the error: "Date / / contains invalid characters" .And afetr pressing cancel ,it goes back to the PBO and then pressing f8,it shows the infotype screen designed* but the other functionalities which have been coded in PAI of screen like activating checkboxes,radiobuttons etc. are not there .Even i have tried passing sy-datum to the date field in PBO of the screen.Pls help.

Hello Sir,
Were you able to sort out this issue.
Would appreciate if you can share the solution. One of our users have this issue in the ADOBE form.
Let me know please.
Thanks,
Akshay...

The File name property is not valid. The file name is a device or contains invalid characters

I have an SSIS task that has run successfully for years. They just moved the dtsx to a new server and now it is failing.
Issue:
The task has a data flow that writes a raw file destination. It then has a subsequent data flow that reads the raw file destination.
The path and name of the raw file is passed to each of the data flows via the same variable.
The raw file resides in a folder on the server in the same path that the dtsx resides in.
The task fails with the "The File name property is not valid. The file name is a device or contains invalid characters" error when trying to access the raw file.
What we have done to troubleshoot:
1. I ran the task successfully on my local machine so it is definitely a server issue.
2. The first thing we were seeing was that it failed trying to write to the raw file. The task is set to "Create Always".
3. We saw that the dba's copied over the entire directory structure from the old server which included a previously created raw file, so we deleted the raw file.
4. We reran the task and it successfully wrote a new raw file but then failed on reading the raw file with the same error as above.
5. We reran the task AGAIN and this time it failed trying to write the raw file throwing the same error as above.
6. The dba looked at the directory and the account that performs the task has full control.
7. The dba looked at the raw file that was created and verified that the account that performs the task has full control of the file and that it is the owner of the file.
Summary:
The task fails when trying to access the file EXCEPT when the file does not exist. In that situation it can write the file but subsequently fails in accessing it again.

Hi Whalensdad,
Based on my research, the issue can be caused by the following reasons:
There are some invalid characters in the File name at package runtime. In this scenario, just as Russ said, could you please post the value that is in the File name variable? Also use a Script Task with Messagebox.show to show the variable values at runtime.
May be it changes to others at run time.
The account runs the package not having access to all the folders in the path. Since you are moving the dtsx file from one server to the current server, do you also move the raw file to the same folder in the current server? Does the user runs the package
have access to all the folders in the path? To solve this, please ensure that the user has access to all folders and the raw file in the path on the current server.
Thanks,
Katherine Xiong
If you have any feedback on our support, please click
here.
Katherine Xiong
TechNet Community Support
Please see the response above. I can't use a message box on a server so I logged the values to the database. The resource account has full control to the folder. I haven't been able to get the DBA to check the SQL Agents permissions, but I was always under
the impression that if you use "Run As" on the task, it will not use the SQL Agent but the account you identify it to "Run As". The "Run As" account has full control on the folder and file.

Script to fix invalid characters for SharePoint synced share

I'm hoping for some help implementing a script that will rename files with characters that are invalid for SharePoint, in a synced file share that is accessed by everyone at an office.
Some background: I'm working for a small nonprofit that has a SBS 2012 server and a local domain with about 30 users. I'm the sole volunteer IT person here. We have a network file share on the server that everyone stores their documents on. Recently,
we signed up with Office 365 Online and I set up a SharePoint library and synced it with the document share on our server. A few files aren't being uploaded, though, because of invalid characters (For instance, a file like "Outline/Team plan #3.doc"
Expecting everyone to remember not to use any of the invalid characters isn't really a solution, particularly since I'm not here full-time if things go wrong. I'm looking for a script to run on the server every few minutes that will rename any incompatible
files so that they can be uploaded to SharePoint. Personally, I think it's just plain criminal that Microsoft hasn't provided this functionality itself (it's the least they could do) but that's another rant for another time. Unfortunately, while
I do have a couple of years of experience with basic server administration and group policy, I'm not experienced at all when it comes to PowerShell scripting. I can string together some command line commands in a batch file, and that's about it.
I did find this promising post here:
http://community.spiceworks.com/scripts/show/2097-fix-file-names-for-skydrive-pro-syncing
I was hoping for opinions - is this the sort of thing I'm looking for, and what would be the best way to implement it (eg, every few minutes as a scheduled event)? Also, is this a straight-up powershell script, or are there additional languages/resources
involved? (Like I said, I'm sort of a script newbie).
Additional background: I posted a similar question asking if it could be done with GPOs, and they directed me here, suggesting it could be done with scripts.
Thanks!!

That script that Mike linked to is a good one, i've used it myself a fair few times. Just to weigh in with a bit of information on why those characters are forbidden:
The reason that some characters aren't allowed is that those characters are used as special characters in URLs. If you were to allow them to go into the file names (without 'escaping' them) then all the traffic to and from SharePoint would start to
go horribly wrong.
Now it is theoretically possible to build a tool that recognises the characters, escapes them, then uploads them. As well as updating the SharePoint interface to 'unescape' the characters when it renders them. However it's not a trivial bit of engineering,
you'd have to gut SharePoint and re-do some of the core behaviour. You've then got to re-test it and make sure it doesn't break any previous SharePoint behaviour.
The way MS want you to work is to save the files directly to SharePoint, which would pick up that you have protected characters and prompt the user to correct them. That does break down a bit with OneDrive as you can use the characters locally, it's only
the next step that fails...

Renaming files with invalid characters in their names on NTFS partitions, introduced by operating systems other than Windows

Essentially, Linux created some files with colons (:) in the name on a NTFS partition where I have Windows installed. I have since uninstalled Linux, but now I can only view these files in Windows Explorer. I can't open them, I can't even rename them to
correct the problem. It's as if they don't exist, because of the invalid search paths.
If I try to rename them in Windows Explorer I get following message.
The file name you specified is no valid or too long.
Specify a different file name.
Well isnt' that something?... isn't that nice? Windows is able to display these files, but it doesn't allow me to open them and it certainly doesn't like me to rename them. So why is it whining about it then, when I'm trying to help? It says "try a different
file name". Yeah, right! Like I haven't tried that one already! It doesn't matter what file name I input it will never accept it.
So what am I supposed to do now? Ditch Windows and go back to Linux? Surely, Microsoft doesn't like the sound of that. Sure, I could reinstall Linux or run a Linux live system to correct the problem. But what good is Windows then? I might as well switch to
Linux altogether.
After doing some research I now know by fact that it's (kind of) possible to rename files from UNIX and UNIX-like operating systems to those compliant with Windows by using something called file name character translation. To some level this is essential and
necessary for Windows interoperability with other operating systems (Windows is not the only operating system in the world). But this seems to be very complicated and I can't get my head around it. My brain is in overload. I don't know where to start.
Once there was a...
There's the Windows Services for UNIX (SFU) 1.0, 2.0, 3.0, 3.5. The first two versions were based on MKS Toolkit, a package licensed by Microsoft from MKS Inc. The later versions were based on the similar Interix product, after Microsoft purchased the company
that made it.
Then there's the new Subsystem for UNIX-based Applications (SUA). These are services for UNIX components. They are supposed to have Client for NFS v3 included as well. But the server components from the SFU line is missing (e.g. Server for NFS). These are included
in Server editions of Windows.
Then there's the Microsoft Knowledge Base article
289627: "How to Enable File Name Character Translation". This article seems to describe exactly my situation.
Windows and UNIX operating systems have restrictions on valid characters that can be used in a file name. The list of illegal characters for each operating system, however, is different. For example, a UNIX file name can use a colon (:), but a Windows
file name cannot use a colon (:). If a UNIX user attempts to create a file with a Windows illegal character on a Windows Services for UNIX network file system (NFS) share, the attempt is unsuccessful and the UNIX client computer receives an input or output
error.
It goes further than that. At first glance, this KB article also seems to offer a solution to this exact problem, with examples as shown below.
For example, the following maps the UNIX colon (:) to a Windows dash (-):
0x3a : 0x2d ; replace client : with - on server
I checked these values in charmap.exe and they are correct. Except for 2D not being a "dash", it's rather a hyphen ("hyphen minus" to be exact), but these two have pretty much the same appearance and they get interchanged a lot, I'm sure
they are used to it by now. (Yes, the characters! They don't mind.)
Then there's this registry key.
HKEY_LOCAL_MACHINE\Software\Microsoft\Server For NFS\CurrentVersion\Mapping
Well, of course, I don't have Server for NFS. So this is a dead end. Well, actually, it was a dead end from the beginning...
1. First of all, I'm not working with a network share on a NAS or SAN storage. The files are on the local disk drive where Windows is installed, so that's a DAS for you.
2. I don't have SFU! Well obviously, I'm on Windows Vista! So that means SUA!
3. SUA are service components only. No server components. Can you guess what that means? Yeah... no "Server for NFS" since it's a server component.
4. Windows Vista is a client side operating system! Server for NFS is only offered for use with Windows Server systems.
5. Back to square one!
So there you have it. They all lived happy for the rest of their lives...
I'm stuck here. Can someone tell me what to do? I mean beyond the obvious option to use Linux to fixa a Windows problem? The NTFS file system itself supports colons in file names. It's Windows that doesn't, and so by default it proclaims it invalid character.
Surely, even a Windows client operating system like Windows Vista should be able to allow the user to at least rename files with invalid characters to something more sensible (from the system point of view) and valid, if not being able to open them as they
are. Just add some crazy voodoo code to it and it will work. If you can make it possible on Windows Server with UNIX user-mode subsystem on NT kernel, then what's stopping you from giving the Windows client system the same benefit?
So what now? Purchase a Windows Server 2012 R2 license, copy my invalid files to a NAS share with NFS on a UNIX or Linux system, and have a go at the Windows registry and Server for NFS? Yeah... you're right, it's probably a bit over the top...
On a second thought... I might as well install Linux again. There are countless situations where Linux has helped me solve problems related to, and more often than not caused by Windows.

Essentially, Linux created some files with colons (:) in the name on a NTFS partition where I have Windows installed. I have since uninstalled Linux, but now I can only view these files in Windows Explorer. I can't open them, I can't even rename them to
correct the problem. It's as if they don't exist, because of the invalid search paths.
If I try to rename them in Windows Explorer I get following message.
The file name you specified is no valid or too long.
Specify a different file name.
Well isnt' that something?... isn't that nice? Windows is able to display these files, but it doesn't allow me to open them and it certainly doesn't like me to rename them. So why is it whining about it then, when I'm trying to help? It says "try a different
file name". Yeah, right! Like I haven't tried that one already! It doesn't matter what file name I input it will never accept it.
So what am I supposed to do now? Ditch Windows and go back to Linux? Surely, Microsoft doesn't like the sound of that. Sure, I could reinstall Linux or run a Linux live system to correct the problem. But what good is Windows then? I might as well switch to
Linux altogether.
After doing some research I now know by fact that it's (kind of) possible to rename files from UNIX and UNIX-like operating systems to those compliant with Windows by using something called file name character translation. To some level this is essential and
necessary for Windows interoperability with other operating systems (Windows is not the only operating system in the world). But this seems to be very complicated and I can't get my head around it. My brain is in overload. I don't know where to start.
Once there was a...
There's the Windows Services for UNIX (SFU) 1.0, 2.0, 3.0, 3.5. The first two versions were based on MKS Toolkit, a package licensed by Microsoft from MKS Inc. The later versions were based on the similar Interix product, after Microsoft purchased the company
that made it.
Then there's the new Subsystem for UNIX-based Applications (SUA). These are services for UNIX components. They are supposed to have Client for NFS v3 included as well. But the server components from the SFU line is missing (e.g. Server for NFS). These are included
in Server editions of Windows.
Then there's the Microsoft Knowledge Base article
289627: "How to Enable File Name Character Translation". This article seems to describe exactly my situation.
Windows and UNIX operating systems have restrictions on valid characters that can be used in a file name. The list of illegal characters for each operating system, however, is different. For example, a UNIX file name can use a colon (:), but a Windows
file name cannot use a colon (:). If a UNIX user attempts to create a file with a Windows illegal character on a Windows Services for UNIX network file system (NFS) share, the attempt is unsuccessful and the UNIX client computer receives an input or output
error.
It goes further than that. At first glance, this KB article also seems to offer a solution to this exact problem, with examples as shown below.
For example, the following maps the UNIX colon (:) to a Windows dash (-):
0x3a : 0x2d ; replace client : with - on server
I checked these values in charmap.exe and they are correct. Except for 2D not being a "dash", it's rather a hyphen ("hyphen minus" to be exact), but these two have pretty much the same appearance and they get interchanged a lot, I'm sure
they are used to it by now. (Yes, the characters! They don't mind.)
Then there's this registry key.
HKEY_LOCAL_MACHINE\Software\Microsoft\Server For NFS\CurrentVersion\Mapping
Well, of course, I don't have Server for NFS. So this is a dead end. Well, actually, it was a dead end from the beginning...
1. First of all, I'm not working with a network share on a NAS or SAN storage. The files are on the local disk drive where Windows is installed, so that's a DAS for you.
2. I don't have SFU! Well obviously, I'm on Windows Vista! So that means SUA!
3. SUA are service components only. No server components. Can you guess what that means? Yeah... no "Server for NFS" since it's a server component.
4. Windows Vista is a client side operating system! Server for NFS is only offered for use with Windows Server systems.
5. Back to square one!
So there you have it. They all lived happy for the rest of their lives...
I'm stuck here. Can someone tell me what to do? I mean beyond the obvious option to use Linux to fixa a Windows problem? The NTFS file system itself supports colons in file names. It's Windows that doesn't, and so by default it proclaims it invalid character.
Surely, even a Windows client operating system like Windows Vista should be able to allow the user to at least rename files with invalid characters to something more sensible (from the system point of view) and valid, if not being able to open them as they
are. Just add some crazy voodoo code to it and it will work. If you can make it possible on Windows Server with UNIX user-mode subsystem on NT kernel, then what's stopping you from giving the Windows client system the same benefit?
So what now? Purchase a Windows Server 2012 R2 license, copy my invalid files to a NAS share with NFS on a UNIX or Linux system, and have a go at the Windows registry and Server for NFS? Yeah... you're right, it's probably a bit over the top...
On a second thought... I might as well install Linux again. There are countless situations where Linux has helped me solve problems related to, and more often than not caused by Windows.

Invalid Characters shown in UTF-8 character set

There is an XMLP report whose template output character set is ISO-8859-1. The character set ISO-8859-1 is required for this report as per Spanish Authorities. When the report is run, output gets generated in the output directory file of application server. This output file doesn't contain any invalid characters.
But when the output is opened from SRS window, which opens it in a browser, the invalid characters are shown for characters like Ñ , É etc.
Investigation done:
Found that the output generated on the server is having ISO encoding and hence doesn't contain any invalid characters. Whereas the output generated from SRS window, it is in UTF encoding, so it seems the invalid characters are displayed when conversion takes place from ISO to UTF-8 format.
Created the eText output using the data xml and template using BI publisher tool, the output is in ISO encoding. So if i go and change the encoding to UTF-8 by opening it in explorer or Notepad++, invalid charcters are shown for Ñ, É etc.
Is there any limitation, that output from SRS window will show only in UTF-8 encoding? If not then please suggest.
Thanks,
Saket
Edited by: 868054 on Aug 2, 2012 3:05 AM
Edited by: 868054 on Aug 2, 2012 3:05 AM

Hi Srini,
When customer is viewing output from the SRS window, then it contains invalid characters because it is in UTF-8 character set. Customer is on Oracle OnDemand so they cannot take the output generated on the server.Every time they have to raise a request to Oracle for the output file. So the concern here is, why don't the output from SRS window show output with valid characters ?
The reason could be conversion of ISO format to UTF-8. How could this be resolved ? Does SRS window output cannot generate in ISO format ?
A quick reply will be appreciated as customer is chasing for an update.
Thanks,
Saket
Edited by: 868054 on Aug 7, 2012 11:08 PM

Invalid characters found in the generated out put file

hi ,
I had written a report to generate a file using open dataset , And In the generated file there are invalid characters generated for few fields. can any body help me with this.
regards
nelakonda

Hi,
Try below code.
DATA : l_w_file LIKE rlgrap-filename .
FIELD-SYMBOLS : <l_w_record> TYPE string,
 <l_table> TYPE STANDARD TABLE,
 <l_line> TYPE ANY,
 <l_field> TYPE ANY.
DATA : new_table TYPE REF TO data ,
 new_line TYPE REF TO data .
TYPE-POOLS : slis.
DATA : wa_fieldcat TYPE lvc_s_fcat ,
 wa_fieldcat1 TYPE slis_fieldcat_alv ,
 fieldcat TYPE slis_t_fieldcat_alv,
 gt_fieldcat TYPE lvc_t_fcat .
DATA : l_w_length TYPE i.
DATA : wa TYPE string.
CLEAR : p_subrc .
l_w_file = p_file .
OPEN DATASET l_w_file FOR INPUT IN BINARY MODE.
IF sy-subrc NE 0 .
 p_subrc = 1 .
 EXIT.
ENDIF .
ASSIGN wa TO <l_w_record> CASTING.
DO.
 READ DATASET l_w_file INTO <l_w_record>.
 CONDENSE <l_w_record>.
 IF sy-subrc EQ 0.
 ELSE.
 EXIT.
 ENDIF.
 APPEND <l_w_record> TO p_it_itab.
*This method will create a structure required for the
*runtime table generation
 l_w_length = STRLEN( <l_w_record> ).
 CLEAR wa_fieldcat.
 wa_fieldcat-fieldname = wa.
 wa_fieldcat-seltext = wa.
 wa_fieldcat-outputlen = l_w_length .
 APPEND wa_fieldcat TO gt_fieldcat .
 CALL METHOD cl_alv_table_create=>create_dynamic_table
 EXPORTING
 I_STYLE_TABLE =
 it_fieldcatalog = gt_fieldcat
 I_LENGTH_IN_BYTE =
 IMPORTING
 ep_table = new_table
 EXCEPTIONS
 generate_subpool_dir_full = 1
 OTHERS = 2
 IF sy-subrc <> 0.
 MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
 WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
 ENDIF.
*The structure is assigned to the table <l_table>
 ASSIGN new_table->* TO <l_table>.
*Structure of Work Area of the table created.
 CREATE DATA new_line LIKE LINE OF <l_table>.
*The structure of work area is assigned to <l_line>
 ASSIGN new_line->* TO <l_line>.
 MOVE wa TO <l_line>.
 ASSIGN COMPONENT wa OF STRUCTURE <l_line> TO <l_field>.
 INSERT <l_line> INTO TABLE <l_table>.
 CLEAR : <l_w_record>.
ENDDO.
CLOSE DATASET l_w_file .
IF sy-subrc NE 0 .
 p_subrc = 1 .
 EXIT .
ENDIF .
Refere above code as per your requirement.

Error occured while importing xsd.file(Name contains invalid characters: -

Hello,
i muss import xsd.file. while importing this error occured:
İFMEXTDEF CCTS_CCT_SchemaModule-2.0 | http://example.org/XXX/XXX/OUT/NOZ (SC_NOZ V001 of example.org):
Name contains invalid characters: - .
Only a(A)-z(Z), 0-9, and "_" are permitted
This xsdfile name is CCTS_CCT_SchemaModule-2.0 but PI doesn't accept "-". But i muss use this file because this file is standart. What can i do for this?
Thanks
Nurhan
Edited by: Nurhan on Oct 18, 2011 11:22 AM

HI,
PI doestnt support special characters like '-'. first you need to change the file name as you specify '-'. to remove that and you have to give '_'. then uyou have to impot >XSD file into ESR under ExternalDefination.
i hope this will help you.
regards,
ganesh.

Copying filenames with invalid characters in OSX

I'd like to copy some folders for back up to an external hard disk from the internal hard disk on my G4. Problem is that some of the folders contain files were created in OS 9 and their filenames contain "/" symbols which apparently are not acceptable in OS X (10.3.9) which I am now running. After trying to drag the folders containing the files to the external hard disk I get an error message saying that they can't be copied because some of the filenames contain invalid characters. The problem files are scattered among files in many folders all over my G4's internal hard disk, and the task of finding and manually changing each one's filename is daunting. Is there a way to find and replace "/" with "." ? or some other more automated fix of the invalid characters? I'd prefer to keep the original files in their current folders on the G4. thanks
G4 Mac OS X (10.3.9)

Does any of this software do what you want?
(20586)

Dynamic column Name# Contains Invalid Characters. Bind_table() fails

Hi WD experts,
I have tried to use the bind_table() on a dynamically generated table. Now it happens that this dynamic table contains columns like NAME# . This gave rise to a dump :
The Name NAME# Contains Invalid Characters. Valid Characters are A-Z, 0-9, _, and /.
Other tables which do not have such columns are correctly bound.
In my method , I first loop over the field catalog to retrieve some field names from a dynamicallt generated report...
LOOP AT lt_fieldcat_out INTO lwa_fieldcat.
    comp-name = lwa_fieldcat-fieldname.
    comp-type ?= cl_abap_typedescr=>DESCRIBE_BY_DATA( lwa_fieldcat-FIELDNAME ).
    APPEND comp TO comp_tab.
ENDLOOP.
structure which represents the dynamic table
struct_type = cl_abap_structdescr=>get(
                                          p_components = comp_tab
                                          p_strict = abap_FALSE   ).
node_info = wd_context->get_node_info( ).
node_info = node_info->add_new_child_node(
                              name        = 'DYN_TAB_NODE'
                              IS_MANDATORY                 = ABAP_TRUE
                               IS_MANDATORY_SELECTION       = ABAP_FALSE
                               IS_MULTIPLE                  = ABAP_TRUE
                               IS_MULTIPLE_SELECTION        = ABAP_FALSE
                               IS_SINGLETON                 = ABAP_FALSE
                               IS_INITIALIZE_LEAD_SELECTION = ABAP_FALSE
                              static_element_rtti = struct_type
                              is_static = abap_false
struct_type = node_info->GET_STATIC_ATTRIBUTES_TYPE( ).
Afterwards, I bind a dynamic table to the new node...
Do you have an idea how to circumvent this ?
Thank you,
cheers,Zied.

cols have to be changed

The file name is not valid. The file name is a device or contains invalid characters.

Hi ,
I am getting below error in SSIS 2008 package when it is run through control-m
The file name is not valid. The file name is a device or contains invalid characters.
component "FF_SRC_InboundFidelityInputFile" (1) failed the pre-execute phase and returned error code 0xC020207E.
although this package is working fine in dev environment from visual studio.
control-m agent has proper permissions to the folder still it is failing. Please if anyone knows solution for this issue. I am working on this issue since more than a week but reached nowhere. Please help.
Thanks
Paras Gupta

Hi Paras,
Based on your description, it is not the VS IDE issue, if it is related to the SSIS, I suggest you post the issue in this forum here:http://social.msdn.microsoft.com/Forums/sqlserver/en-US/home?forum=sqlintegrationservices
, and there you would get better response.
Best Regards,
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Invalid characters ?

Similar Messages

Maybe you are looking for