Invalid Characteristic

Hi,
I come cross invalid characterisitc error while activating ODS. I got several replies that we have to change the data in PSA / allow that invalid char in RSKC. I would like to know what exactly happening while activating ODS and how SID's will be generated.
In the current DSO, I have material and 0Vendor is an attribute for 0Materail. Obvisouly I cannot modify 0Vendor in PSA as it was defiend as attribute for 0materail. As per details tab it is saying datapacket 117 failed with "invalid char' for 0Vendor. But how how PSA will get data for master data.
And even if 0Vendor has invalid char, it should throw an error while loading data for 0material.
Pls clarify all the above questions.
Regards,
Venkat

Hi Venkat.
The invalid char concept has been explained in detail in 3 parts in these below web blogs
Invalid characters in SAP BW 3.x: Myths and Reality. Part 2.
Invalid characters in SAP BW 3.x: Myths and Reality. Part 1.
Steps of Including one special characters into permitted ones in BI
U can follow these steps for any master data that shows invalid chars error
1) edit the records in psa
2) if the records are more, then while scheduling in info pak, in Tab Update, goto error handling,
select the 3rd radio button, so all the records will be extracted then later u can edit them, and schedule error package.
3)Load all the invalid char in a flat file and then load.
4) write up a code , which is mentioned in the blog
5) for material master, goto tcode OMSL and check on the box lexicographical, and then reload, it will work, and then load vendor.
6) goto se11 >RSALLOWEDCHAR and give these !"%&'()*+,-/:;<=>?_0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ  and execute, then goto contents, all these should show up
Thanks and regards
Edited by: Noor Ahmed khan on Jul 29, 2008 2:42 PM

Similar Messages

  • Invalid Characteristic error

    Hi Friends,
    While loading Transaction data from R/3 to BI, the system is givinng error message about Invalid Characteristic......the message is saying that................
    Value ' A.P. Marketing Federation Ltd' (hex. '200041002E0050002E0020004D00610072006B006500740069') of characteristic ZPAYER contains invalid characters
    Value '  Producers Union Ltd.' (hex. '20002000500072006F00640075006300650072007300200055') of characteristic ZPAYER2 contains invalid characters
    I am not able to understand what the error in it.
    It is not giving any error while laoding data to DSO........it is giving error while the request is Activating......when go and see the Activation Log it is saying the above message.
    Please guide me how to resolve the above error.
    Thanks & Regards
    Anand

    Hi,
    This is a case related to invalid characters. Generally we go through RSKC and include the special characters.
    Go to PSA and edit the invalid characters by finding the error recors by datapackage and reload the data to DSO.
    or yu can do by writing a routine before loading the data to DSO from PSA.
    Regards,
    Jack

  • Invalid characteristic combniation in WAD new row not re-read

    We have a really annoying problem entering new rows in an IP WAD.
    If an incorrect Characteristic Value (Gl account for example) is entered in a new row, then the system provides a nice message, and the cell with the characteristic is highlighted - perfect.  The user can change the value and then check again.
    However if the user types in a Characteristic Value which exists, but is not in the filter for the query, then the system again provides an error message, but instead of highlighting the Characteristic Value the system highlights the Key Figure cell. 
    If the user changes the Characteristic Value to a valid value and checks the data again, the new valueis not checked.  The user has to change the key figure amount to trigger the system to check the updated Characteristic Value.
    This behaviour is the same for checking characteristic combinations.
    Executing the same query in a BEx Analyser workbook does not have this problem, but we prefer a web input.
    Has anyone noticed this problem, and found a solution or workaround?
    Michael

    Hello Michael,
    I agree with you. The check should highlight the incorrect cell, not the key figure. Please open a customer message with a reproducible example so SAP support can analyze the issue.
    Regards,
    Marc
    SAP NetWeaver RIG

  • 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

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

  • How to delete the request in Direct Update DSO

    Dear Gurus,
    I have a situation where I have an invalid characteristic loaded into the Direct update DSO.  This is related to Spend Performance Management.  This DSO is loaded through a data source with the option Without Archive.  So, I cant see any request in this DSO.   This DSO will then supply data to another DSO which is standard DSO. 
    The data Activation job in the standard DSO is failing. 
    My question is I have to delete the request from the Direct Update DSO and then load it to Standard DSO.  I have already repaired the data in PSA.
    Your Kind help is greatly appreciated.
    -Mohan Kumar

    You must be using some fill or delete APIs to fill the data in Direct update DSO.You can't create transformation to fill the data in DIrect Update DSO as you do in Standard DSO.You will not see  request number under the manage tab for direct update dso for any load.
    Whenever you will fill the Direct update DSO next time,previous data gets deleted automatcally. For Direct update DSO there can only be a Full Update.So just load the data using API's  and previous data will get deleted automatically
    Edited by: shyam agarwal on Mar 2, 2012 7:48 AM

  • ODS Issue

    Hi,
    I have one load issue today.while activating the ODS Object Iam getting the error like
    Characteristic values are not allowed if they only consist of the     
    character "# " or begin with "!". If the characteristic is compounded,
    this also applies to each partial key.                                                                               
    You are trying to load the invalid characteristic value               
    TCode-I1//Rec.Typ-CO & (hexidecimal representation                    
    54436F64652D49312F2F5265632E5479702D434F ).  
    Please help me how to solve this issue.
    Thanks in advance.

    Hi
    RSKC -- type ALL_CAPITAL -- F8 (Execute)
    OR
    Go to SE38 and execute the program RSKC_ALLOWED_CHAR_MAINTAIN and give ALL_CAPITAL or the char you want to add.
    Check the table RSALLOWEDCHAR. It should contain ALL_CAPITAL or the char you have entered.
    Refer
    /people/sap.user72/blog/2006/07/23/invalid-characters-in-sap-bw-3x-myths-and-reality-part-2
    /people/sap.user72/blog/2006/07/08/invalid-characters-in-sap-bw-3x-myths-and-reality-part-1
    /people/aaron.wang3/blog/2007/09/03/steps-of-including-one-special-characters-into-permitted-ones-in-bi
    http://help.sap.com/saphelp_nw04/helpdata/en/64/e90da7a60f11d2a97100a0c9449261/frameset.htm
    For adding Other characters
    OSS note #173241 u2013 "Allowed characters in the BW System"
    Sample cleansing routine (#)
    Help loading  char EQUIP#1111#TAG#3311  SN#A01040          *     into Cube
    Hope it helps

  • Error loading the data into ODS - Message no. BRAIN060?

    Hi,
    I am getting following error while load the data from flat file, data loaded successfully from flat file to PSA but I got following error while updating the data from PSA to data target:
    Value '010384 javablue' (hex. '30003100300033003800340020006A0061007600610062006C') of characteristic 0PO_NUMBER contains invalid characters
    Message no. BRAIN060
    Diagnosis
    The following standard characters are valid in characteristic values as default:
    !"%&''()*+,-./:;<=>?_0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ
    Characteristic values are not allowed if they only consist of the character "#" or begin with "!". If the characteristic is compounded, this also applies to each partial key.
    You are trying to load the invalid characteristic value 1. (hexidecimal representation 30003100300033003800340020006A0061007600610062006C).
    I am trying to load Value '010384 javablue' to "0PO_NUMBER" info object for ODS with in one row with some other data.
    Any idea or any input to resolve this issue?
    Thanks in advance for any input.
    Steve

    Thanks Soumya, I have maintained the upper case letters, but I am loading upper and lower case mixed to PO number? and it is not working. What is the solution to this? If I set lower case property to the PO number infoobject, it won't accept upper case. If I uncheck the lower case then it won't accept lower case letters. I cannot add upper and lower case letters in RSKC, because it accepts up to 72 characters, I have already have more than 60 characters (special char, numbers and 26 upper case letters).
    I have already tried transfer routine but you can either convert to lower or upper but it doesn't work. we need both uper and lower case for po number, and R/3 is accepting it. why BW doesn't accept both?
    Any idea what can be done?
    Thanks in advance for your help.
    Steve

  • ERROR DURING LOADING DATA FROM PSA TO DSO IN "PRUEFMBKT"

    Respected all
    I am trying to load data through an r/3 field( pruefmbkt, char-40length) to infoobject. the data is coming correctly to psa but when i am loading it in to dso or infocube request is turning red giving following error message--
    Value '010/12.05-112.15/hold on not operate' (hex.
    '3031302F31322E30352D3131322E31352F686F6C64206F6E20') of characteristic
    PRU_LSIL 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 3031302F31322E30352D3131322E31352F686F6C64206F6E20).
    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.
    kindly give me the solution how to deal with this problem.
    thanks
    abhay

    HI Abhay,
    please check if the infoobject corresponding to field PRU_LSIL in BW system has lower case checkbox enabled in the infoobject properties, as the  value '010/12.05-112.15/hold on not operate' coming from R/3 has lower case alphabets.
    Hope this helps.
    Regards,
    Umesh.

  • Problem while runnning query on 0TCT_MC11

    Hi,
    While reading data from 0TCT_MC11 through query I am getting the following message...
    "Error while reading data; navigation is possible
    "Value XY2CLNT400AHPL_ACCT"
    "You are trying to load the invalid characteristic value 1. (hexidecimal representation 0044004200320043004C004E00540036003000300049004F00)."
    Please let me know if you have any suggestions for this.
    Thanks, Jeetu

    Jeetu,
       It seems like there are some data records with speical characters loaded into one the cubes in 0TCT_MC11.
    hope it helps,
    Balaji

  • Multi-Dimensional Sets in a hierarchy

    Hi
    I'm trying to create a set hierarchy which contains multi-dimensional sets.  When adding the multi-dimensional set as a sub-ordinate in the hierarchy I receive the error <Set Name> invalid characteristic  for Input Field HKONT.
    The requirement is that on a report in BI we need to limit rows on a report to specific GL accounts and then specific transaction types (BEWAR) within those GL accounts.  We have around 20 reports that have the same format but the GL accounts and Transaction Types on each row are different - hence we wanted to use sets to maintain the GL accounts and transaction types for each row.
    So I've created several sets which are single sets and it all works fine.  But when I create a multidimensional set (with Account and Transaction Type) it works fine.  But when I attempt to add that as a subordinate set (ie to create the row in the report hierarchy) I get this message. 
    The Set that contains the rows can't be a multidimensional set as I can't add multi-dimensional sets to multi-dimensional sets.  
    Anyone come across this or know of a way around it ?  or perhaps a different approach.
    Thanks

    Hi
    I guess the problem is because, in a multi dimensional set, you have more than one char i.e. HKONT and BEWAR... In your report row, have you included both of these chars or just one?
    Try to include both the chars and then use a multi dimensional set in the row...
    The idea of multi dimensional set is that no char in it should repeat... When you are adding this multi set to a BASIC SET or SINGLE SET, you are bound to get this error in GS01
    Br, Ajay M

  • Errors found by DSO activation

    Hi gurus,
    i got the following errors after checking the logs of  the DSO activation. Any suggestions??
    Thanks. points will be given,
    SD
    Value " " from characteristic ZM_RMTEXT contains an error at position 1
    Message no. BRAIN290
    Diagnosis
    Characters that have a hexadecimal display between HEX00 and HEX1F are not permitted in characteristic values. The character at position 1 is one of these characters. The value is therefore not permitted.
    Note that these characters cannot be displayed and are therefore displayed as '#'. The actual character '#' has the hexadecimal display HEX23.
    Procedure
    Check the origin of the characteristic value. If possible, change the characteristic value in the source.
    Incorrect source text in update routines and transfer routines can also cause this problem.
    ============================================================================
    Value 'B2 1234567  Kabelsatz' (hex. '4232203132333435363720204B6162656C7361747A') of characteristic ZM_MATTAU 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 4232203132333435363720204B6162656C7361747A).
    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.

    Hi,
    You have invalid characters for the field ZM_MATTAU. Due to these your DSO activation is failing.
    The way to resolve this is to write a cleansing routine for that field to strip away the bad characters and only permit the good characters to go through.
    If you search the forum you'll get sample codes for the same.
    Cheers,
    Kedar

  • '-' is in RSKC but activation still fails

    Hi All,
    As subject already explains we have hyphens '-' in our data and activation fails due to invalid character issue. Hyphens are in special character list in RSKC.
    Pemitted extra characters: '~@#$^`{}[]\ $/!"%&()+-./:;<=>?_0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZW'
    Does anyone know how to allow - in data in order to solve the activation issue?
    I appreciate any help.
    Mike
    Edited by: mike curtis on Jun 29, 2010 8:00 PM

    Here is the whole log
    Value '002336a8-36e7-4491-9a7c-0df2439c' (hex. '30303233333661382D333665372D343439312D396137632D30') of characteristic ZPA_SID 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 30303233333661382D333665372D343439312D396137632D30).
    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.
    Also .....
    Error when assigning SID: Action VAL_SID_CONVERT, InfoObject ZPA_SID
    We do have a report on this DSO

  • Error when assigning SID

    Hello Gurus,
    I have created a characteristic infoobject(ZCSHIPTYP) for Shipment type and included the same in the ODS.
    When I load data, during activation it gives the foll error :-
    By default, only the following standard characters are valid in  characteristic values:
    !"%&''()*+,-_0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ               
    ./:;<=>?                                                                        
    Characteristic values that only consist of the character "#  or that    
    begin with "!  are not valid. If the characteristic is compounded, this 
    applies to each partial key.                                                                               
    You are trying to load the invalid characteristic value Air Cargo &     
    (hexidecimal representation 41697220436172676F ). This is not permitted.
    this is not a master data. i have included this text in the 2lis_11_vahdr and written a user exit to populate values. the data is also coming. but during ods activation the above error occurs.
    Pls guide.

    MM,
    No, I don't think so.
    ALL_CAPITAL will allow you to use capital letters of the national codepage.
    For more info look here:
    Permitted characters 'ALL_CAPITAL'
    Re: Special Characters in BW RSKC setting
    And also OSS Notes: 173241 and 194328.
    Best regards,
    Eugene

  • ODS data Activation with error BRAIN060

    Hi guys,
    I have the next situation with the data activation in a ODS.  The ODS have the extraction completed, but when I try to do the manual activation a error BRAIN 060 is caused:
    1st.:
    Error getting SID for ODS object ZPUR_OP
    Message no. RSM1187
    2d:
    Value 'AYD CALPDS' (hex. '415944A043414C504453') of characteristic 0COORDER contains invalid characters
    Message no. BRAIN060
    Diagnosis
    The following standard characters are valid in characteristic values as default:
    !"%&''()*+,-./:;<=>?_0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ
    Characteristic values are not allowed if they only consist of the character "#" or begin with "!". If the characteristic is compounded, this also applies to each partial key.
    You are trying to load the invalid characteristic value 1. (hexidecimal representation 415944A043414C504453).
    3st:
    Error when assigning SID (details in long text)
    Message no. RSDRO303
    System response
    Request: REQU_4C4G67RXIW7C3PV88B1BMB4ZX
    Data package: 000795
    Data record: 12.153
    InfoObject: 0COORDER
    The error is the master data and the assigment SID; but the extraction did without PSA; only datatarget.  With this I can´t modify the data erroneus.
    Is possible force the activation or I can apply other correction that not be repeat the extraction?
    Please,I need your quick collaboration.
    Regards,
    Jeysi

    Hi Jeysi,
    You can make the changes in ODS. If this request is not activated yet, in this case this data is available in your New Table of the ODS. You can make the changes in this data directly in this new Table.
    After doing this changes it will allow to activate this request. Also you can find this New Table in object configuration.
    Or
    Go to Manage of ODS -> Go to Contents TAb-> In this Button at bottom with New Data. Please go through this and make the changes in New Data.
    But prior doing this changes please check / analyse the reason correctly as per business requirement. Suggest them to take care of this in future to end users.
    This will deffinately helps you.
    Regards,
    Mahesh

Maybe you are looking for