Permitted characters 'ALL_CAPITAL'

We need to accept a large number of unusual characters, and hit the limit on the number of characters we can enter.  Note 173241 explains that you can use ALL_CAPITAL (on its own) to get round the limit.  This seems to work fine, but I'd like to know exactly what ALL_CAPITAL permits.  I beleive that it accepts any characters that are accepted by the installed codes pages except miniscules letters.  I presume it rejects non-displayable characters.
Anybody know how ALL_CAPITAL works?

Hello,
You created this message in 2004. I am wondering you remember it.
Your description is very interesting for me. Now we have plan to implement BW3.5 Unicode version which we will share in Asia/Pacific. So that our user will use it in Japanese, Korea, English and Germany.
We face data load problem between Japanese source system and BW Unicode system. We can solve this problem, as we set 'ALL_CAPITAL'.
My question is this 'ALL_CAPITAL' is varid for all language.
You mentioned the set of allowed characters depended on the codepage.     
I am wondering the codepage means Logon language or system code page which is Unicode. If it is system code page, 'ALL_CAPITAL' may contain all language included in Unicode.

Similar Messages

  • Non permitted characters-data loading

    In our system, we have a data issue where many records present in the entry level tables (Extraction Layer) have non-permitted characters in text fields.
    we introduced a routine to filter these - but already existing ones will bring problems during the init.
    for this we need a very tricky abap.
    we have a FM to replace wrong characters.
    So now I want to loop a whole databasetable and use the FM against a certain table field
    We did something like that  with abap already. But the biggest issue is that the tables consist of several million records - so we run into memory problems.
    can you please provide a suggestion on how to handle this?
    Your help will be appriciated

    hi  USER1249,
    what about to use standard BW functionality - permitted characters - TA RSKC.
    Via this you can maintain a set of permitted characters which will not be rejected by BW while loading.
    BR
    m./

  • Test for Permitted Characters in Transformation Routine

    Hello,
    Background: There is a data quality issue when loading 3rd party data to BW, which cannot be solved at source. Therefore, initial transformation rules when loading to data warehouse level DSO, should identify and deal with error values.
    Possible Solution: Test validity of value within transformation routine via a custom function module.
    Execution: Function module would require to check lowercase character handling of target InfoObject (RSDCHABAS-LOWERCASE) and scan source value against permitted character set (RSKC).
    Questions: How can the permitted list of characters be returned within transformation routine? Is there an available delivered function module to handle accessing permitted character set?
    I would appreciate any answers to the above questions or alternative suggestions to the above strategy.
    Thanks -
    Brendan.

    There is a function module "RSKC_ALLOWED_CHAR_GET". Use SE37 to check it out.

  • Permitted characters |

    Dear Collegues!
    I have an invalid Character in the InfoObject ZKIDNR. The Character givin me problems is |. It comes at the end of the Kind-number, f.ex 5000459372|, and only in one single record, so it is a mistake.
    I get the error in ODS (0FIGL_O02), and because of this I can not activate my data.
    I have added | in RSKC, but I am now wondering if I should add ALL_CAPITAL instead? Can anyone out there tell me if ALL_CAPITAL will take care of |?
    Will sign Points!
    Silje

    Most of the times ALL_CAPITAL takes care of most of the invalid chars. There is a nice blog by Eugene dealing with RSKC.
    check them out:
    Invalid characters in SAP BW 3.x: Myths and Reality. Part 1.
    Invalid characters in SAP BW 3.x: Myths and Reality. Part 1.

  • # not accepted in permitted characters

    Hello Guys,
    I am fetching data from CRM wherein an anonymous user enters certain free text. While entering data, if he presses "enter" key then it is getting converted into #. Whereas I have maintained # in RSKC, still the error occurs while activating the data store object. Can anyone suggest me the solution for this problem? This is a recurring problem due to which I edit the record in PSA and then reload & reactivate it.
    Thanks,
    Utpal

    HI
    U can use ALL_CAPITAL in the RSKC toce and execute remember it will allow all the special characteristics
    Khaja

  • Check on permitted characters

    Hi all,
    In RSMO, when i go to below path
    Menu>Edit>Init Update>>switch on/off character check>
    I find the    Switch On check for permitted character check box
    What does this option mean?can any one explain.
    Can any one help...

    Hello,
    If you are certain the data coming from R/3 is correct, then you can switch off this character check
    But in practise, this is rarely the case, therefore it's recommended to have this character check switched on
    See also SAP note 173241 and in particular the document on sapnet mentioned within.
    Best Regards
    Barry

  • 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

  • Invalid characters erros

    Hi Experts,
    I am loading the master data for 0MATERIAL , i am getting the error
    "Record 42 :Value 'CMF60249R00FKEB ^LF ' for characteristic 0MANU_MATNR contains invalid characters "
    "Record 1835 :0MANU_MATNR : Data record 1835 ('00400067A '): Version 'MR06 1A 103 KAA (BAG@250EA) ' i "
    Tried RSKC ALL_CAPITAL , still struck with the same error.
    Can anyone help me to resovle this...
    Also pls let me know how to execute RSKC ie. do i need to creat a variant onthis regard?/
    Regards
    Ganesh

    Hi,
    Using Tcode RSKC....... it will whow you the permitted characters list....
    Check wheher the special characters are there in the list.., if not add it and then try to load the data,
    Assign points if it helps.....

  • Hexidecimal Non-Allowed Characters in a Unicode System

    We have a function module that we've written to replace non-permitted characters with a space in transfer rules.  We see a lot of invisible hexidecimal characters coming in free form text fields.  This work great for English.  However, we have a Unicode system with other languages installed.  We are also getting the hex characters in other character sets. 
    Has anyone dealt with this issue and if so what was you solution?
    Thanks!
    Al

    Hello aLaN,
    how r u ?
    Hey we have faced the problem with Hexadecimal characters, but not the same issue. In our case the problem was in the Source System. In the DB Tables we had some unwanted characters, that was showing some errors while data loading, particularly ERROR 18.
    So we resolved it by changing the Source System data.
    I have already posted for the hexadecimal issue.... the replies was
    I think this is related to Invalid character issues.. or SPaces setting in RSKC..
    may be you want to look at eh following post..
    Re: invalid characters
    /people/siegfried.szameitat/blog/2005/07/18/text-infoobjects-part-1
    Example:
    let us say..
    1. Check in RSKC for allowed characters..
    2. Add a code in the update rule to restrict the texts contains..
    !"%&''()*+,-./:;<=>?_0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ' are allowed characters in RSKC transaction then other than the above character is 'Invalid' including the smaller case letters and will throw the hex.. error.
    since this is from database system even 'NULL' datatype from there is not visble to the eyes and can cause the failure.
    Hope this helps
    Best Regards....
    Sankar Kumar
    91 98403 47141

  • Error: 'InfoObject ZDATE contains invalid characters in record 1 in value'

    Dear friends,
    When I am uploading data from oracle datasource (in BW 3.5) I am getting an error 'InfoObject ZDATE contains invalid characters in record 1 in value'. There are no illegal characters in the date instead the date field is blank in datasource. There are other date fields technically the same as ZDATE with blank values but they dont throw an error when scheduler runs.
    Though when I manually upload the data, it's loaded successfully.
    Please suggest where can the error be?
    Regards,
    Amit Srivastava

    You have 2 options:
    1. Corect your data for the characteristics that give errors.
    Or
    2. go to SPRO in BW - Netweaver - BW - general settings - maintain permitted characters.
    In this screen, you maain tain any special characteristic that you the system to recognise and accept. In your case, take your characteristics that give error and add to this.
    Ravi Thothadri

  • Special character

    Hi friends..
    Im getting the following error while ods activation.
    Value 'AMISH GANDHI#4604 ' (hex. '41004D004900530048002000470041004E0044004800490009') of characteristic 0POSTXT contains invalid.
    In ODS and PSA,i dont find # value,and instead of # there is a small square in the PSA and ODS and when i try to copy it in word i just get a space.
    What is that box like character?
    Im planning to use the following routine to control the special characters as given in one of the forum discussion with ALL_capital in RSKC.
    Will this solve my problem??
    Global Declaration
    DATA: L_S_ERRORLOG TYPE RSSM_S_ERRORLOG_INT,
    L_TEXT TYPE STRING,
    G_ALLOWED_CHAR(200) TYPE C.
    Routine
    RESULT = TRAN_STRUCTURE-MSEGNAME.
    Hash is not permitted at all
    while RESULT ca '#'.
    RESULT+sy-fdpos(1) = ' '.
    endwhile.
    Exclamation mark is not permitted as a first symbol of the field
    content
    if RESULT (1) = '!'.
    RESULT (1) = ' '.
    endif.
    *for characteristics to be used for navigation – lower case is not
    *permitted
    TRANSLATE RESULT TO upper case.
    *check if the list of permitted characters provided in the start routing
    *global variable
    *if not – derive it from configuration
    IF G_ALLOWED_CHAR IS INITIAL.
    CALL FUNCTION 'RSKC_ALLOWED_CHAR_GET'
    IMPORTING
    E_ALLOWED_CHAR = G_ALLOWED_CHAR.
    ENDIF.
    if allowed_char = ALL_CAPITAL, all capital letters are allowed,
    otherwise remove characters not specified in RSKC transaction
    CHECK G_ALLOWED_CHAR NE 'ALL_CAPITAL'.
    do.
    if not RESULT co g_allowed_char.
    shift RESULT+sy-fdpos left.
    else.
    exit.
    endif.
    enddo.
    returncode <> 0 means skip this record
    RETURNCODE = 0.
    abort <> 0 means skip whole data package!!!
    ABORT = 0.
    Thanks & Regards
    ragu

    Hi Ragu
    You need to use following transfer routine for this Infoobject in transfer rules. Then load the data in ODS and try activating data in ODS.
    You need to replace –XX 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-XX.
    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 it helps.
    Regards
    Pradip

  • Basic settings in BW

    Hi gurus
    I know in MM we need to do lots of settings but do we need this settings in BW ? whats the use of SPRO in BW? pl explain with some example.
    I found lots of material here but all the time its giving OSS note number..so anybody pl tell me what does it mean and where can I find this notes?
    Thanks in advance

    dear Ketul,
    here are some
    (click the icon 'doc' for detail documentation on each customizing)
    ~ 'business info warehouse'
    maintain permitted characters (transaction rskc), fill with ALL_CAPITAL to allow all special characters
    printer setup (trx SPAD)
    parameter for aggregate (trx rscustv8), aggregate change run, this can be done later or adjust if finding any loading problem
    upload mode for master data
    ods setting (trx rscusta2), ods data loading performance impact
    ~ link to other system
    maintain control parameter for data transfer(rscustv6) - data loading
    general connection setting
    define logical setting, assign logical setting to client etc.
    link between bw and flat file (rscustv1)
    setting for flat file upload, override in infopackage
    link between sap system and bw (rscustv3)
    do the first time after bw installation
    ~ transport setting
    change source system after transport (RSLGMP)
    for mapping source system, done in TARGET (qa/prod)
    ~ reporting relevant setting
    activate personalization ... (rs_pers_activate)
    mostly all are used, but can be done later
    ~ web based setting
    igs setting (if you use chart in web reporting)
    ~ bw enhancement
    - can be done later based on requirement, variable exit, virtual char/keyfigures are customized here.
    ~ general setting ..
    important
    also take a look this thread
    Re: BW implementation
    http://help.sap.com/saphelp_nw04s/helpdata/en/7e/c81c2c52c511d182c50000e829fbfe/frameset.htm
    hope this helps.

  • Cube failed with invalid character stics

    Hi,
    My cube failed with invalid charactersticts....data flow is source sytem to ODS and then cube.
    loading in to ODS and activation is also successful . I would like to know the reason why ODS loading & activation is not failed with above said message and why cube is failed...
    Thanks in advance.....CK

    Hi,
    BW accepts just capital letters and certain characters. The permitted characters list can be seen via transaction RSKC.
    There are several ways to solve this problem:
    1)     Removing erroneous character from R/3 (for example required vendor number that need to be changed can be found from PSA from line shown in error message)
    2)     Changing or removing character in update rules (need to done by ABAP)
    3)     Putting character to BW permitted characters, if character is really needed in BW
    4)     If the bad character only happens once then it can be directly change/removed by editing the PSA
    5)     Put ALL_CAPITAL in permitted characters. Needs to be tested first!
    Editing and updating from PSA, first ensure that the load has been loaded in PSA, then delete the request from the data target, edit PSA by double clicking the field you wish to change and save. Do not mark the line and press change this will result in incorrect data. After you have corrected the PSA, right click on the not yet loaded PSA and choose u201Cstart immediately.u201D
    Hope it will help you.
    Regards,

  • BI Production errors

    Hi,
    Can anybody please give me SAP-BI Production Issues pdf,
    i search on google t i got BW Production Isusues pdf. but i want exclusively bi production error pdf.
    Thanks and Regards.
    Asim.
    this is a commonly discussed topic - please search the forums before posting

    . Time Stamp errors:     This can happen when there is some changes done on data source and data source is not replicated.
    Execute T code SE38 in BW give program name as RS_Transtruc_Activate_All and execute the program. Give Info source and Source System and activate. This will replicate the data source and its status is changed to active. Once this is done, delete the request by changing technical status to red and trigger Info package to get delta back from source system.
    2. Error log in PSA- Error occurred while writing to PSA: This is because of corrupt data or data is not in acceptable format to BW.
    Check the cause of the error in Monitor in Detail tabsrip.This gives the record number and Info object having format issue. Compare the data with correct values and determine the cause of failure. Change the QM status of request in data target to red and delete the request. Correct the incorrect data in PSA and then upload data into data target from PSA.
    3. Duplicate data error in Master data uploads: This can happen if there are duplicate records from the source system. BW do not allow duplicate data records.
    If it is a delta update, change the technical status in the monitor to red and delete the request from the data target. If it is full upload delete the request.
    Schedule again with the option in the Info package, u201Cwithout duplicate datau201D for master data upload.
    4. Error occurred in the data selection: This can occur due to either bug in the info package or incorrect data selection in the info package.
    Data selection checked in the info package and job is started again after changing the technical status to red and deleting the error request from the data target.
    5. Processing (data packet) Errors occurred-Update (0 new / 0 changed): This can be because of data not acceptable to data target although data reached PSA.
    Data checked in PSA for correctness and after changing the bad data uploaded back into data target from PSA.
    6. Processing (data packet) Errors occurred-Transfer rules (0 Records): These errors happen when the transfer rules are not active and mapping the data fields is not correct.
    Check for transfer rules, make relevant changes and load data again.
    7. Missing messages - Processing end Missing messages: This can be because of incorrect PSA data, transfer structure, transfer rules, update rules and ODS.
    Check PSA data, Transfer structure, transfer rules, Update rules or data target definition.
    8. Activation of ODS failed: This happens when data is not acceptable to ODS definition. Data need to be corrected in PSA.
    Check for Info object which has caused this problem in the monitor details tab strip. Delete request from data target after changing QM status to red. Correct data in PSA and update data back to data target from PSA.
    9. Source System not available: This can happen when request IDOC is sent source system, but the source system for some reason is not available.
    Ensure that source system is available. Change technical status of request to red and delete request from data target. Trigger Info package again to get data from source system.
    10. Error while opening file from the source system: This happens when either file is open or file is not deposited on server or not available.
    Arrange for file, delete error request from data target and trigger Info package to load data from file.
    11. While load is going on in R/3 table is locked: This happens when some data source is accessing R/3 transparent table and some transaction takes place in R/3.
    Change the technical status of job to red in the monitor and retrigger the job again from R/3.
    12. Object locked by user: This can happen when user or ALEREMOTE is accessing the same table.
    Change the technical status of job to red, delete request from data target and trigger Info package again. If its delta update it will ask for repeat delta, Click on Yes button.
    13. Process Chains Errors occurred in Daily Master Data: This occurs when Transaction data is loaded before Master data.
    Ensure to load Master data before Transaction data. Reload data depending on update mode (Delta/Full Update)
    14. Processing (data packet) No data: This can be because of some bug in Info package, rescheduling with another Info package corrects the problem.
    This type of problem we can solve with copy the Info package and reschedule the data.
    15. Database errors Enable to extend Table, enable to extend the Index: This is due to lack of space available to put further data.
    16. Transaction Job Fails Giving Message: u201CNO SID FOUND FOR CERTAIN DATA RECORDu201D is due to some illegal characters for the Data records.
    17. Error Asking for Initialization: If you want to load data with the delta update you must first initialize the delta process. Afterwards the selection conditions that were used in the initialization can no longer be changed.
    18. Job Failure at Source System: Go to the background processing overview in the source system. You can get to this with the Wizard or the menu path Environment -> Job Overview -> In the source system (This is the alternate path to see the u201CJob Overviewu201D at the Source System.)
        At source system you can see the reason for the Job Failure. Thus we need to take the action accordingly.
    19. Invalid characters in load: BW accepts just capital letters and certain characters. The permitted characters list can be seen via transaction RSKC.
    There are several ways to solve this problem:
    1)     Removing erroneous character from R/3 (for example required vendor number that need to be changed can be found from PSA from line shown in error message)
    2)     Changing or removing character in update rules (need to done by ABAP)
    3)     Putting character to BW permitted characters, if character is really needed in BW
    4)     If the bad character only happens once then it can be directly change/removed by editing the PSA
    5)     Put ALL_CAPITAL in permitted characters. Needs to be tested first!
    Editing and updating from PSA, first ensure that the load has been loaded in PSA, then delete the request from the data target, edit PSA by double clicking the field you wish to change and save. Do not mark the line and press change this will result in incorrect data. After you have corrected the PSA, right click on the not yet loaded PSA and choose u201Cstart immediately.u201D
    20. Update mode R is not supported by the extraction API: This happens for loading of delta loads of MD attributes. Why has not been covered. Replicate the data source. Use SE38 and function module TRANSTRU_ACTIVATE_ALL.
    Subsequently perform an initial load.
    1.     Go to the info package.
    2.     Delete the previous initial load
    3.     Load the initial
    4.     After the initial is successful check the solution by loading a delta
    Thanks & Regards
    Praveenyagnamurthy

  • Reg:Unwanted charcterstic nesesity

    Hi BW Xpertz
        Recently i got a problem Which i never across My requirement is i need to upload the data from a flat file with hex characters which r not in the acceptable formats like "#" my client needs it in his data target how can i up load is there any option? Could any one come across this type of issue if yes could please give me  the clarification.If any docs can u just mail to the follwoing [email protected]
    Thanx In Advance
    Regards
    Krish K

    hi Krish,
    have you maintain RSKC with ALL_CAPITAL ?
    it should accept all special characters,
    in case # appear in middle, you may check Claudio's routine ..
    RSKC and # sign in the middle of a word
    Permitted characters during BW data load
    Load problem.......Special Chars..Urgent..
    oss note 173241 - Allowed characters in the BW System
    hope this helps.

Maybe you are looking for