Invalid characters found in PSA

Hi Guru's,
Can any one tell me the procedure how to resolve the invalid chars in the PSA. I tried in RSKC and permitted the all the invalid chars. But even then i got the same error. How to edit the records? This is a Customer Master data. Your help will be appreciated.
Thanks in Advance,
Venkat.

Hi Venkat
try using ALL_CAPITAL in RSKC and load again.
If still this does not work then write the following transfer routine in transfer rules of your customer master datasource. You should create this routine for the field(or fields) which is bringing invalid characters.
Just replace ZZZ with you transfer structure field.
DATA: L_USER_ALLOWED_CHAR TYPE RSALLOWEDCHAR,
L_ALL_ALLOWED_CHAR(140) TYPE C,
L_RESULT_STR_LEN TYPE I,
L_STR_INCREMENT TYPE I.
CONSTANTS C_SAP_ALLOWED_CHAR(58) TYPE C VALUE
' !"%&''()*+,-./:;<=>?_0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ'.
IF L_ALL_ALLOWED_CHAR IS INITIAL.
SELECT SINGLE * FROM RSALLOWEDCHAR
INTO L_USER_ALLOWED_CHAR
WHERE ALLOWKEY = 'S'.
CONCATENATE C_SAP_ALLOWED_CHAR
L_USER_ALLOWED_CHAR-ALLOWCHAR
INTO L_ALL_ALLOWED_CHAR.
ENDIF.
RESULT = TRAN_STRUCTURE-ZZZ.
TRANSLATE RESULT TO UPPER CASE.
L_RESULT_STR_LEN = STRLEN( RESULT ).
L_STR_INCREMENT = 0.
WHILE L_STR_INCREMENT <> L_RESULT_STR_LEN.
IF NOT RESULT+L_STR_INCREMENT(1) CO L_ALL_ALLOWED_CHAR.
RESULT+L_STR_INCREMENT(1) = ' '.
ENDIF.
ADD 1 TO L_STR_INCREMENT.
ENDWHILE.
If you have loaded data in PSA -> locate the button PSA data maintenance on right hand top side and then you can maintain the data in PSA
Hope this helps.
Regards
Pradip

Similar Messages

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.

Invalid Char could not be found in PSA. Why?

I got an error message in the process chain at DSO activation level. The DSO activation level got failed and shows red.
But in the DTP monitor the QM status shows green. The display message shows
1. @5C@     Error when assigning SID: Action VAL_SID_CONVERT, InfoObject 0REVISION     @35@
2. @5C@     Value '#' (hex. '0023') of characteristic 0REVISION contains invalid characters     @35@
3. @5C@     Process 000347 returned with errors     @35@
in PSA the data package has 332 with 20000 records for every package. I couldn't find the invalid chars for info object 0revision. I could see the 0revision in the PSA. But how to get the exact error row with these above information.
any idea?????
Thanks,
Draj S.

Hi,
as you said there are 332 data packages with 20K records each, in which datapackage have you checked for the error record?
check the record no 347 which may be having the error record - try to edit it save the records in PSA and repeat the load and activate the data.
3rd column is the data request number -- check for the data record no 347 and check for the value for 0revision. if there are any special char like # in your case try to edit the record and reload.
Regards
KP

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 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

How to delete trailing spaces or invalid characters

Hi experts,
I am loading data into a DSO. But in the activation it is showin error. Data is coming upto New data table. After that it is showing error as:
=============================================
Value 'Eversafe ' (hex. '204576657273616665 ') of characteristic 0CUSTOMER contains invalid characte .
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 Eversafe &
    (hexidecimal representation 204576657273616665 ).
System Response
Procedure
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.
===========================================
After i edit this in psa it is showing another record as error.
I think we have to delete the trailing spaces. If this is the case anyone please provide me how to write routine in the transfer rules to delete the trailing space.
Full points will be assigned.
Thanks & Regards,
V N.

Hi Venkat,
Thanks for your reply.
How can i know what are the extra invalid characters to be permitted.
And also i am getting a message while activating the DSO as follows:
============================================
Activation of M records from DataStore object ZDSO_OO3 terminated
Process 000033 returned with errors
=============================================
Please help me to solve this issue.
Thanks & Regards,
V N.

Volume Activation Management Tool invalid characters bug.

I have a Multiple Activation Key from my Technet subscription for Windows 8 Enterprise, and wanted to
find out how many activations I am allowed, and how many I have left. I was advised by a colleague to
download and install the Volume Activation Management Tool 2.0 from Microsoft.
Whilst using this tool, I've found what appears to be a rather serious bug. It does not allow entry of the
product key I wish to manage. If I copy/paste the key under Add Product Keys, it deliberately ignores
one of the characters in the second section of the product key, specifically the letter N.
If I attempt to enter the key manually, it says Invalid character in the product key when I come to this
particular letter. On further investigation, VAMT 2.0 sees several other letters as invalid characters.
It wrongly says all of the following letters are invalid characters - A - E - I - L - N - O - U - S - Z .
This bug makes it impossible to add the product key, and almost impossible to add any other key.

Hello,
Which problem are you referring to?
The first issue was with VAMT not recognizing some the characters in the newer product keys, the solution for that is to use VAMT 3.0 or preferably VAMT 3.1 now.
the second issue is the prompt to create a database and all you need to do is enter a name on the database line and it will create one( leave the Server line alone.)
Thanks, Darrell Gorter [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.
Tried that ... it doesn't work. I type my machine name into the Database line and after a few seconds I get this . . .
Running SQL Server Express, the server name is listed as DJGMPC/SQLEXPRESS, so I put that in the Server line
and type the machine name DJGMPC in the Database line, and VAMT finally establishes a connection with
this SQL Server that shouldn't really be needed in the first place, when VAMT2 managed OK without it.

Error with invalid chars found in characteristics

Hi,
I am loading information for this field EKPO-TXZ01 (PO text) into ODS and then into infocube. I have no issue loading this field content into ODS. However from ODS to infocube, I encountered error that says invalid chars found. (This field was defined as chars 40 in the infoobject). At BW customizing, the chars like #, " [] are being maintained. Please advise how to overcome this.

Hi,
From my experience I can say that:
1. Not always assigning permitted characters helps. Especially if chars that you want to pass to the ODS are special chars. And there is too little space in the string with allowable chars.
2. Setting a characteristics as a lower case char helps for its master data. An ODS will not allow to accept data with lower case letters anyway.
3. There are several topics related to your question in this forum with solutions, even with ABAP codes.
Look, for example at this one:
https://www.sdn.sap.com/sdn/collaboration.sdn?contenttype=url&content=https%3A//forums.sdn.sap.com/profile.jspa%3FuserID%3D136828
Best regards,
Eugene

Process Chain Error-Invalid characters

Experts,
Value '30102900 ' (hex. '3330313032393030A0') of characteristic 0MATL_GROUP contains invalid characters.
I tried to remove blank space after 30102900 and repeated.
Still giving the same error .
Any idea?
Thanks
Mano

Hai Manohar,
This is a very common problem and also a bug in SAP BW.The error doesnot really give you the correct information.
It should be one of the two reasons:
1.Go to your transfer rules mapping, scroll all the way to your right and check if under the tab conversion all check boxes are ticked. If these are not checked the alpha conversion fails.
2. There are lower case letter coming iny our data. This could most probably be your reason. Go to PSA and check the records. Use UPPER CASE conversionin your transfer rules.
One of these should solve your problem.

Value '! u2018Hex. '0021characteristic ZORG_INPT contains invalid characters

Dear ALL Expert,
In BI 7 Environment while loading data from psa to Cube I getting error in DTP( Value '! u2018(Hex. '0021 ') of characteristic ZORG_INPT contains invalid characters ). Please guide me regarding is error
regards,
ravi

Hello Ravichendra,
I had a same problem and i have resolved by writing a abap routine in update rules below.
$$ begin of routine - insert your code only below this line        -
CALL FUNCTION 'SCP_REPLACE_STRANGE_CHARS'
EXPORTING
    INTEXT                  = COMM_STRUCTURE-EQUIPMENT
INTEXT_LG               = 0
INTER_CP                = '0000'
INTER_BASE_CP           = '0000'
IN_CP                   = '0000'
   REPLACEMENT             = 32
IMPORTING
   OUTTEXT                 = RESULT
OUTUSED                 =
OUTOVERFLOW             =
EXCEPTIONS
   INVALID_CODEPAGE        = 1
   CODEPAGE_MISMATCH       = 2
   INTERNAL_ERROR          = 3
   CANNOT_CONVERT          = 4
   FIELDS_NOT_TYPE_C       = 5
   OTHERS                  = 6
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
*fill the internal table "MONITOR", to make monitor entries
result value of the routine
RESULT = v_eqp.
if the returncode is not equal zero, the result will not be updated
RETURNCODE = 0.
if abort is not equal zero, the update process will be canceled
ABORT = 0.
$$ end of routine - insert your code only before this line         -
Regards
Sankar

Value '05uFF71uFF7BuFF8B ' for characteristic ZJLEG_PPL contains invalid characters

Hi,
One of our Master data attribute load is failing with the following error message.
Value '05ｱｻﾋ ' for characteristic Z_PPL contains invalid characters
As you see there are some Japanese characters when it is trying to load into Char string?
Can we load such characteristics?
Where can we check which all Languages are installed in the system?
If we want to maintain these to the Special characteristics in RSKC transaction?
Can we enter these characteristics using English keyboard?
Regards
Ajay

Hi Ajay
Some time in the run time environ ment field values are moved to junk chars .
In this case even if u r traying to place the same char in RSKC also it wont
accept..
So in this can just edit that particular error record like in the ordinary process in
the PSA.other wise if its a master data u need to select the option error handling
in the info pak and rerun the info pak..
Hope itz clear a little atleast...!
Thanks & Regards
R M K
***Assigning pointz is the only way of saying thanx in SDN ***
**Winners dont do different things,they do things differently**
> Hi Although,
>
> We do have same Characteristics maintained to QA and
> Production.
>
> But when I load the Same data in QA it is successful
> but it is failing in Production.
>
> Regards
> Ajay

Loading master data : error invalid characters

Hello,
I load master data (example 0PROG_POS) into BW with InfoPackage and loading stops with error "invalid characters". In the logs, the error is due to a special character (in french Ä : a special A).
On BW side, is it possible to solve this problem (I don't understand the message in the help : "If this message appears during a data load, maintain the attribute in the PSA maintenance screens").
My BW is 3.5 patch 7
Thanks in advance for your help.
Daniel.

HI Daniel
all characterstic & special characterstic
goto TCODE: RSKC -> all_capital-> F8
again : rskc-> !"%&'()*+,-./:;<=>?_0123456789ABCDEFGHIJKLMNOPQRSTUVWXY ->F8
GOTO SE11: RSALLOWEDCHAR (maintain special characterstic)
also u can goto-> SE37->RSKC_ALLOWED_CHAR_GET
-> F8
THANKS & BEST REGARDS
SANGRAM KESHARI SUTAR

Need help with Value '# ' of 0REF_DOC_NO contains invalid characters

Hi Experts
We are having load failure due to this Value '# ' of characteristic 0REF_DOC_NO contains invalid characters error. I have managed to find out at PSA level there are few records with contains # value. I have also informed the user about it and user had rectified the record from ECC level.
Our load goes evey night through process chains from PSA to DSO and then to Cube.
We have requests in DSO till today and the problem happened two weeks ago e.g. 7 DEC. In cube the last record came on 6 DEC as after that it was failing everyday.
Now I am just wondering with few questions :-
Should I wait for next delta load to happen so that it can bring all the records from DSO to Cube or Do i need to change the record of that certain date in DSO too.
Please give me your valuable suggestion and steps.
Regards
Sunny

Sorry for posting it in wrong section, i have moved it to right thread now.
Cube is failing with invalid characters error Value # of 0REF_DOC_NO

Invalid Characters during data load

Hi All,
We are in BI7 and its unicode compliant with code page 4102.
My setting in RSKC is ALL_CAPITAL. When i tried loading data from the source system, i got many error records in BW saying that it has invalid characters. On debugging, i found that hexadecimals 00-1F comes as part of the record. Why control characters like 00-1F are not allowed in BW by default? I changed the RSKC setting to ALL_CAPITAL_PLUS_HEX, but its of no use.
when i checked in i18n transaction, i could see that code 4102 can accept all control characters.
Is there any setting that has to be made in order to allow hexadecimals in BW [ without converting it in to space using a routine ]?
Thanks and Regards
Amith

Hi Amith Anand,
Please
check
Program
RSKC_ALLOWED_CHAR_MAINTAIN
Or
RSKCCHECK
Let me know.
Regards
Hari

Value '#' (hex. '') of characteristic 0customer contains invalid characters

Value '#' (hex. '') of characteristic 0customer contains invalid characters
I didn't get the error message when I am loading into ODs.The error occurs only the ODS to Cube load.
RSKC transaction -I have values
ALL_CAPITAL+/=1234567890~`@#$%^&*()_-{}[]\|'";:?.>,<
Other than ABAP routine is their anyway can I handle the invalid characters.
Because I am loading millions of records in the transaction.I can't Manually update in the PSA.
Advance Thanks

Hi
I am surprised why you have not faced this problem while loading to ODS. I guess your ODS is not ON for BEx Reporting. Anyways, You need to write a transfer routine for 0CUSTOMER.
Just replace ZZZ with you transfer structure field.
DATA: L_USER_ALLOWED_CHAR TYPE RSALLOWEDCHAR,
L_ALL_ALLOWED_CHAR(140) TYPE C,
L_RESULT_STR_LEN TYPE I,
L_STR_INCREMENT TYPE I.
CONSTANTS C_SAP_ALLOWED_CHAR(58) TYPE C VALUE
' !"%&''()*+,-./:;<=>?_0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ'.
IF L_ALL_ALLOWED_CHAR IS INITIAL.
SELECT SINGLE * FROM RSALLOWEDCHAR
INTO L_USER_ALLOWED_CHAR
WHERE ALLOWKEY = 'S'.
CONCATENATE C_SAP_ALLOWED_CHAR
L_USER_ALLOWED_CHAR-ALLOWCHAR
INTO L_ALL_ALLOWED_CHAR.
ENDIF.
RESULT = TRAN_STRUCTURE-ZZZ.
TRANSLATE RESULT TO UPPER CASE.
L_RESULT_STR_LEN = STRLEN( RESULT ).
L_STR_INCREMENT = 0.
WHILE L_STR_INCREMENT <> L_RESULT_STR_LEN.
IF NOT RESULT+L_STR_INCREMENT(1) CO L_ALL_ALLOWED_CHAR.
RESULT+L_STR_INCREMENT(1) = ' '.
ENDIF.
ADD 1 TO L_STR_INCREMENT.
ENDWHILE.
Hope this helps
Regards
Pradip

Invalid characters found in PSA

Similar Messages

Maybe you are looking for