cancel
Showing results for 
Search instead for 
Did you mean: 

DSO activation issue due to Characters that have a hexadecimal display between HEX00 and HEX1F

Former Member
0 Kudos
845

Hello Experts,

I have a problem Activating the DSO where I have upload from DSO 1 to DSO2

DSO 1 is write optimised.

DSO 2 is standard one where I have so many values where I have invalid char thats Characters that have a hexadecimal display between HEX00 and HEX1F.

Brain message BRAIN290.

I have too many records where I cannot edit each record.

I have value like below where the char could be tab, space which is displayed as # in BI.

This value is preventing to activate the DSO.

I tried debuging and changing the values but as there are too many records cannot do it for each record.

Value "MMI® Navigation Мультимедиа интерфейс Au" from characteristic YCDESCR1 contains an error at position 16

Value in Active data table

MMI® Navigation Plus#Мультимедиа интерфе

# is the cause.

Like above I have so many records.

I have ALL_CAPITAL set in RSKC but still it does not work..

Please advise its urgent to activate this DSO.

Thanks,

Santhosh.

Accepted Solutions (1)

Accepted Solutions (1)

Roney_Mathew
Explorer
0 Kudos

'#' may be for any character not interpreted by BW, for eg: it may be a line separator.

Using the below routine would result in replacing all characters not in the list from RSKC to be replaced by 'space'.

Since this works at Field routine level the data loading time will be affected and the should preferably be used for lesser volume of records.

Please do  a test load to make sure it filters out only the characters that are not required.

_______________________

Data: positn type i,
        Field1 type /BIC/fieldname.

Field1 = source package-field name.

IF source package-field name is not initial.

Field1 = source package-field name.


  TRANSLATE Field1 to UPPER CASE.
  sy_pos = 0.
  Do 60 Times.
    IF Field1+positn(1) CN
' ~!@#$%^&*()_-=+{}[]\|;:",<>/?0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ'.---* please copy all letters from RSKC and paste it here. Check if it includes all languages.
      Field1+positn(1) = ' ' .
    ENDIF.
    postin = positn + 1.

  ENDDO.
  Condense Field1.

Answers (3)

Answers (3)

RamanKorrapati
Active Contributor
0 Kudos

Hi Kumar.

After maintaining at RSKC if not solved then, with help of ABAPer you can maintain Field routine. that would be helpful.

regards

Former Member
0 Kudos

Hi Chowdary,

Thanks for the advise,

Can you please provide a sample code if available in the field level.

I have to write the field level code to eliminate these.

Please provide a solid solution all.

Appreciate as my requests on the failed activation requests are getting accumulated and reports does not show data.

Please advise.

Thanks,

Santhosh

RamanKorrapati
Active Contributor
0 Kudos

Hi kumar,

Is this is value in ur info object characteric: (other wise plz. post ur error screen shot)

MMI® Navigation Мультимедиа интерфейс Au,

those letters not allowed in sap. am not good at code,

say your requirement to abaper, he can understand. These errors are normally in bw loads.

This doc explained abt hex character issue. go thru it.

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/e0cdc928-5e2d-2e10-e1bb-ec77bcb5c...

regards

Former Member
0 Kudos

Hi Chowdary,

The charecters are Russian and they are allowed.

The issue is with the # char in the value

MMI® Navigation Plus Мультимедиа интерфе is the one of the value.

If I see them in DSO activate data table I can see

data as MMI® Navigation Plus#Мультимедиа интерфе where # is displayed in between.

This could be any char BI displays char's like this as #.

I have to eliminate these values.

Thanks,
santhosh

RamanKorrapati
Active Contributor
0 Kudos

Hi Kumar,

By time being do the manual correction.

to eliminate permanent.

These are ways to eliminate ur error:

1. Need to maintain ABAP code,

2. Drop mail to user who are entering these values in source(this won't good idea,)

3. Each and every time, need to do manual correction.

regards

Former Member
0 Kudos

Hello Experts,

Please provide me with the sample code to write at field which I have an issue with to eliminate the Hex values in between the data of the Infoobject.

Please advise.

Thanks,

Santhosh.

Former Member
0 Kudos

Hi Santhosh,

I just came across one similar scenario in the forum. Could you check whether this suit you?

http://scn.sap.com/thread/2057883

And btw, if maintaining ALL_CAPITAL_PLUS_HEX didn't helped you, perhaps # is not the usual # as suggested in the thread I've marked.

Br,

H

Former Member
0 Kudos

Hi Harish,

Its not the # which has been entered in the ECC system, as BI show invalid char which cannot be seen as # in general for example my case

"MMI® Navigation Plus Мультимедиа интерфе" 

The above text has # in "MMI® Navigation Plus#Мультимедиа интерфе" at 20 position this is creating problem .

Now how can this be categorised as Invalid char space or tab or I dont know but # is displayed.

How can I solve this issue . I am struggling to take them off.

There is no solution for this??

Please advise.

Thanks,

Santhosh.

Former Member
0 Kudos

Hi Santhosh,

Position is not a matter here. If it's not removed by a routine in your transformation, it probably is not a real #. Then, I'm afraid it's not possible to remove unless correcting at the source.

Br,

H

Former Member
0 Kudos

Hi Santhosh,

What stops you from correcting the records at the source itself?

Br,

H

Former Member
0 Kudos

Hello Harish,

I am worried as this is a LO data and the delta's are extracted to BI

If I ask for the source to correct do I need to re Init the Extractor.

Please let me know.

Thanks,

Santhosh

Former Member
0 Kudos

Hi Santhosh,

Then maintain ALL_CAPITAL_PLUS_HEX in RSKC. This might solve your issue.

Br,

H

arjun_subhash
Active Participant
0 Kudos

http://scn.sap.com/message/2772900#2772900: try global transfer routine in infoobject.

Also correcting at source means the BW source like the write optimised DSO.

Former Member
0 Kudos

Hello Harish,

I tried maintaining the ALL_CAPITAL_PLUS_HEX and and tried activating again.

Did not work.

IF we maintain ALL_CAPITAL_PLUS_HEX is needed that I have delete the Standard DSO bad requests and then reload it from Write optimised one.

I have Write optimised as Source for the standard one.

Thanks,

santhosh

arjun_subhash
Active Participant
0 Kudos

I would delete the records from the new data table of DSO 2 and reload it with a local routine in transformation for removing the problem spaces and tabs.

Former Member
0 Kudos

Hello Arjun,

Thanks for the reply,

I am not sure if these are with the spaces or tabs but it displays # when I check the value if the infoobject in the active data table.

again pls find the value when checked normally

MMI® Navigation Plus Мультимедиа интерфе

But I go to display of the record particularly I find

MMI® Navigation Plus#Мультимедиа интерфе

Please help me with the local routine in order to eliminate the #'s .

Thanks,

Santhosh.