on 03-05-2014 8:14 AM
Hi All,
I have chain I am getting data in to DSO and while activating it is failing.
I checked activation logs.. there it is unable to generate SID for a Field and content is "some description#". I have read in some document special characters wont be avail as first character .
so I checked in RSKC all special chars are available and I added "ALL_CAPITAL" for that and manage still I m getting same error. while adding ALL_CAPITAL do I need to provide any space or some thing ...
I am not getting where I have done mistake...
Thanks and regards
vijay
Hi,
if you received only one error record then you can do it by manual.
follow the below steps.
1. Delete loaded request from DSO
2. Edit your error record at PSA and save it.
3. Reload the same request to DSO.
4. Activate dso data and load further if any .
if think that as you may receive daily error for this load then impelement routine as suggested above.
or inform users to maintain correct descrptions while saving data.
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi All,
I have done what raman said, but my customer is maintaining that description as a Master data.
so when ever they update with this record i need to follow the same procedure...
During the procedure i deleted " (this char) and loaded in to dso and activated it worked fine... now my problem is how to allow a special char as a first char..............
please find below link for reference, i feel there is a way to allow special char as a first character.....
thanks
vijay
Hi All,
I asked customer not to maintain any special character in 1st place..
thanks and regards
vijay
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Vijay,
If you have error records please follow the below steps
follow the below steps.
1. Delete loaded request from DSO
2. Edit your error record at PSA and save it.
3. Reload the same request to DSO.
4. Activate dso data and load further if any .
if think that as you may receive daily error for this load then implement routine as suggested above.
or inform users to maintain correct descriptions while saving data.
For this load if you have many error records , select all the error records in PSA & click on change button.
It will open a window with fields not filled , in the error field type the correct description i..e without # values & space . It will change all the records at time .But be carefully while correcting records if you are in production sys. Filters all errors and then select change them .
Please assign points if you are satisfy with solution.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi vijay,
check the DSO activation logs then find the which filed getting error.
you can try below code in filed level routine for specfic field.
this code will resolve the problem.
data: l_d_length like sy-index.
DATA: l_d_offset LIKE sy-index.
DATA: CharAllowedUpper(60) TYPE C.
DATA: CharAllowedLower(60) TYPE C.
DATA: CharAllowedNumbr(60) TYPE C.
DATA: CharAllowedSondr(60) TYPE C.
DATA: CharAllowedAll(240) TYPE C.
CharAllowedUpper = 'ABCDEFGHIJKLMNOPQRSTUVWXYZÄÜÖ'.
CharAllowedLower = 'abcdefghijklmnopqrstuvwxyzäüöß'.
CharAllowedNumbr = '0123456789'.
CharAllowedSondr = '!"§$%&/()=?{[]}\u00B4`*+~;:_,.-><|@'''.
CONCATENATE CharAllowedUpper CharAllowedLower CharAllowedNumbr
CharAllowedSondr INTO CharAllowedAll.
RESULT = SOURCE_FIELDS-XXXXXXXXX.(source field name)
l_d_length = strlen( RESULT ).
IF NOT RESULT CO CharAllowedAll.
DO l_d_length TIMES.
l_d_offset = sy-index - 1.
IF NOT RESULT+l_d_offset(1) CO CharAllowedAll.
RESULT+l_d_offset(1) = ''.
ENDIF.
ENDDO.
endif.
CONDENSE RESULT NO-GAPS.
Thanks,
Phani.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Vijay,
As the system is not able to generate the SID for the relevant data, it might be due to Invalid Characters in the data ( not just only at the first place or as a first character) . Any Invalid character in the data (at any place) will lead to failure of process.
Please check the Erroneous record ( full string ) and try to locate the Invalid character(s).
Hope this helps ..!
Regards
YN
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
83 | |
10 | |
10 | |
9 | |
7 | |
6 | |
6 | |
6 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.