RSKC special characteristics

Hi Guys,
The Maximum number of allowed special characters in RSKC are 72. If it exceeds more then this what can we do?
Thanks and regards
Rajesh.

Hi Rajesh,
You can manually correct the incorrect records through PSA & you can upload from PSA to rextected cube.
OR
You can goto RSKC --> type ALL_CAPITAL --> F8 (Execute)
OR
Run the report RS_ERRORLOG_EXAMPLE,By this report you can display all incorrected records of the data & you can also find whether the error occured in PSA or in TRANSFER RULES.
Regards,
Lakshman Kumar Ghattamaneni

Similar Messages

Special characteristics are not allowed in excel sheet

Hi experts,
                     Pls help me when i m loading one excel sheet containing one record with # symbol , it is loaded to PSA sucessfully
                 but loaded into cube is failed. i have already maintained special characteristics RSKC and putted # and excuteed.
              still i m getting error message. other records are loaded to cube...
Regards
Giri
Edited by: Siddhes on Aug 4, 2011 1:04 PM

Please follow the below steps.
1.First check what you have given in t-code RSKC or check
the table RSALLOWEDCHAR.
Try to give CAPITAL_ALL_PLUS_HEX.Then delete the data and
reload it.
2.If there is some other error,thene
delete the request from data target.
Go to psa search for error record and correct it and reload it.
3.If some space is coming then you
need to write some formula to remove the
space.
4.You can also enabl the Error stack DTP,so that
erreneous record will go to stack and you can manually correct
then and reload them.
Hope this is helpful.
Thanks,
Saveen Kumar

Special characteristics in Master data

Hi All,
I tried to load the data to ODS object, The data is loaded to ODS object, But when i try to activate the data at ODS level, I am running in to error that due to special characteristics in for info object the activation is not possible.
I tried all methods (like Running through RSKC and setting up all_capitals and special characters as well).
But no luck, Is there any easiest way other than deleting the data manually record by record at PSA level.
Any help greatly appreciated.
Cheers,
Reddy.

Hi,
You can try filtering out the special characters using a transfer routine for the info object.
Check the code below for the code :
Regarding Special Characters
Cheers,
Kedar

Analysis Authorization: Special Characteristics

Hi,
SAP recommends that below special characteristics MUST be assigned to a user in at least one authorization:
-InfoProvider
-Validity
-Activity
As per Note- 1000004, the user authorizations are optimized at query run time. This optimizationfollows steps:
1. Filliing Empty Dimensions
2. Merging Authorizations
3. Iterations.Step 1 & 2 are repeated untill no further optimazation is possible.
Now my question, Is the above steps applicable for Special Characteristics viz InfoProvider, Validity & Activity also?
Best Regards,
UR

Hi,
Can you please elaborate 'validity and activity are independent of restrictions´?
We can maintain values for Activites say 01 (create) 03 (display) etc and also maintain values for Validity stating period.
My question: If we have mulitple authorization objects with different values in InfoProvide, will they be optimized as described in Noted 1000004?
Please advise.
Best Regards,
UR

RSKC Special characters

Hi,
Actually in RSKC there is special character like #.But while loading the data will struckup in NEW DATA itself.Field containing the # key record and that data packet will struck up there only.

Hi,
As a long term you can apply some user exit in source system side or change your update rules to ensure that this field is getting blanked out before getting loaded in cube or add that particular char to permitted character list in BW.
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 Allowed characters in the BW System
Also try in dev first entering in RSKC ALL_CAPITAL_PLUS_HEX
Thanks,
JituK

How to manage special,invalid characteristics

Hi,
Whenever we face any invalid characteristics, special characteristics, How can we allow them apart from allowing them in RSKC. Is there any ABAP code to be performed to allow them. What is the maximum limit of chars allowed in RSKC.

Hi,
I would prefer going to RSA1OLD then do the necessary changes to the PSA data and load the data again from PSA to data targets.
Hope this helps.
PV

Special characters errors

Hi,
what should be done if any errors raise due to special characters.what to be done in RSKC? please tell me the steps clearly taking an example..
thanks in advance,
jack

Hi,
1. Pass the Value ' ALL_CAPITAL' in RSKC this should resolve minor issues with special characteristics
2. Copy the Word with special Characteristics and Past it in RSKC and execute
this will resolve the issue when ever this word is appeared while data loading
Further if it does not resolve your issue
you need to write a routine in Rules /Transformations to handle the special characteristics using function Module CALL FUNCTION 'RSKC_ALLOWED_CHAR_GET'.
Links:
Invalid characters in SAP BW 3.x: Myths and Reality. Part 2.
Regards
Hari

Disadvantage of RSKC

Hi,
Can any one tell me what is the disadvantage of RSKC(for special characteristics)

HI GURUS I HAVE A QSN ASKED IN AN INTERVIEW?IF I AM GETTING DATA FROM R/3 AND IF THERE R SOME SPL CHARACTERS LIKE %,# ETC,THEN WHERE SHOULD I CORRECT THEM? SHOULD I CORRECT THEM ON R/3 SIDE OR ON BI SIDE?I TOLD THAT I WILL CORRECT IT ON BI SIDE BY MOVING TO RSKC T-CODE?SO PLS ANS MY QSN?
THANKING YOU,SSHIVA

RSRQ /RSMO/RSKC/SM50

Hello Gurus,
will you please what RSRQ /RSMO/RSKC/SM50 do?
Many thanks,
Frank Zhang

RSRQ : Data load for monitor for single request, gives the status of any load depending on its requset number.
RSMO: it is the whole monitor for all the loads in BI system(from source and also from BI to BI) and gives 3 status's i.e completed , incorrect and running(not yet completed)
RSKC: Special permitted characteristics.(u can maintain any permitted characteristics here that u want to allow into BI)
SM50:Process overview, takes u the application server.(gives u status of all the dialog, backgroung processes).
rgds,
nkr

RSKC Limit

Hello
If suppose the characteristics limit (72 according to the table) allowed to maintain in the RSKC is crossed, how can we maintain the new special characteristics? I understand that there is a standard program behind it but can we maintain more than 72 characteristics using the program?
No hurry, answer in your leisure time
Srikanth.

Here's the blog Sam was talking about:
/people/sap.user72/blog/2006/07/08/invalid-characters-in-sap-bw-3x-myths-and-reality-part-1
/people/sap.user72/blog/2006/07/23/invalid-characters-in-sap-bw-3x-myths-and-reality-part-2

Problem with special extra characters

Hi Experts,
I´m working in SAP BW 7.0 using Data Integrator XI 3.1 with SAP BW as a target and BO DI as a source and we have some problems with the load process
I have problems with the conversion of special characters that exist in DI and in BI arrive as an entirely different character, for example, Ñ is replaced with Å , and so on witn the á, é, í, ó, ú, etc
In SAP BI these characters were included in the T-code RSKC (Maintenance of the permitted extra characters in BW) as special characters. In addition I tried to change the character set settings in order to use the 1100 SAP internal, like ISO 8859-1 in the infopackage but it doesn't works neither.
The character encoding used in DI by default is utf-8.
Can anyone hel me to solve this issue?
Thanks in advanced.

This worked in BW 3.5:
Use function module RSKC_CHAVL_OF_IOBJ_CHECK to covert Special characteristics into Latin ones.
John Hawk

Required Characteristics from 0BI_ALL for new custom object

Hello,
I created a small query with the following characteristics on 0BPARTNER info.provider
with the following characteristics
Rows:
Business Partner (0BPARTNER)
Country(0COUNTRY)
Region(0REGION) With Variable Mandatory
Now I need to secure this query by region.Hence started creating new authorization object ZREGUSCA using RSECADMIN and with the following charactertics / Dimensions limiting to only these characteristics out of 40 characteristics from 0BI_ALL.(I donot want to assign 0BI_ALL to S_RS_AUTH, if i do,i cannot secure this query)
0REGION
0TCAACTVT
0TCAIPROV
0TCAVALID
0APO_LOCNO
0CUSTOMER
0TCAKYFNM
My question is why do i need to have the last three characteristics (0APO_LOCNO,0CUSTOMER,0TCAKYFNM)
included in the object apart from the region and the special Characteristics? I found these three non related objects as required, after a lot of trouble shooting?
How do i know, what are the required characteristics if i want to secure by plant in another query?
I will really appreciate your responses and thoughts
Regards
Sreeni

Hi Sreeni
Because the chars are auth relevant and are in the cube.
0TCAKYFNM is also auth relevant and therefore you need to authorize key figures.
Chars that are not explicitly in the drilldown must be authorized with aggregation auth, that is with the colon-sign :
You can find the information in the authorization protocol. There is a block auth relevant chars.
Record your query via RSUDO for the restricted user and flag the "with protocol" box or go to RSECADMIN->Error logs where you can enter your name to be logged always.
There, you will also find the protocol.
Best Peter

Special characters within MDM

Hi,
I would like to understand if it is possible to insert special characters (Greek characters like lambda, theeta, Mu, trade mark symbol, registered symbol) within the fields in MDM. If so please let me know the methodology.
thanks
Anantharam

Hi Ananth,
Yes. It is possible to store special characteristics by following method.
1) First and foremost,Define the field type as 'Text' .
2) If you are importing these special chars from a text file > set text file encoding as UTF-8. This can be done by using 'Save as' text file > Input file name,type and Encoding. Use this file in import manager to import.
3) If you are importing from excel > Open the txt file from Excel > in Text import wizard, select 1252 :Western European (Windows) as File Origin > Select the required columns to be converted in excel > execute. Use the converted file to perform import.
All special chars will be precisely stored in text field.
Hope this helps.
Regards,
Vinay M.S

# 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

Error While Loading Data from ODS to ODS

Hi Experts,
When i'm loading the data from ods to further ods, i'm facing an error while activating the data saying that 0ref_doc_no consists of invalid characters.Also it is saying that Error when assigning SID.
I'm unable to see the long text for further information.
Regards,
Vijay

Hi vijay bhaskar,
first go to RSA1 -> go to datasource -> search for the data source with name "8<old DSO>". Go to dispaly and click on PSA button on top. Now you can see PSA data request. in the bottom left you select error records and display. now you will see all the error records. go through each and every records and see what is the special characteristic in that record and copy that special character in notepad. After collecting all the special characters in notepad, goto RSKC -> paste all the special characteristics from note pad. execute it.
Now, go back to PSA, delete the request from PSA. Schedure the infopackage to load the data. Now, will not see any error like special characteristics.
I hope you understood and can handle your issue.
Assign points if it is helpful.
Reagds,
S P.

RSKC special characteristics

Similar Messages

Maybe you are looking for