Urgent!!Invalid character (Hex.'456461204C616D')!!

[Former Member]

Hi All

I am getting an following error .While loading no error,While activating the request I am getting the following invalid character..

Value 'Eda Lam' (hex. '456461204C616D') of characteristic ZPENAME contains invalid characters

pls help me resolve..

thanx in advance

[former_member184494]

Are you loading texts or transaction data.

It is an issue with Lower Case characters if you are loading Transaction data - if it is texts then it is an issue with invalid characters not maintained in RSKC.

Either convert to Upper as directed in the reply above or look at enabling Lower case for the characteristic ( but this has implications on query performance - do not use this option if you are using this as a main characteristic. )

Arun

[Former Member]

Hi

I tried both as u say,only by selecting lower cas,error is resolved..Also as u say that,I have a query performance...but for my report data will not be that much ..so then it shld be ok ,right???

When I convert it still says the same,not sure wht Culd be the reason??

Can I use Alpha Conversion????

Thnx a lot for ur ideas..

pls give me some more ideas

[Former Member]

How can it give the same error ?

You mean it is not converting LC to UC ?

[Former Member]

Hi Roberto,

Very sorry yaar..I got some ABAP dump error in between..Actually I did the mistake...forgot to load tht object after converting..

So I think Now it shld be ok..Not sure..I am in activation process..

will let u know

Once done..

[Former Member]

Hi Roberto,

It was unsuccessful...It throws the same error...

Value 'Eda Lam' (hex. '456461204C616D') of characteristic ZPENAME contains invalid characters

Pls tell any why is it so??or better I select the lower case option check box in the object??

[Former Member]

Did you activate the Transformation ?

I dont beleive it still errors with Eda Lam instead EDA LAM !!

[Former Member]

Hi Roberto..

I did it in masterdata,I did all & I can see all converted to upper case in masterdata..When I am taking to Info Provider...It throws the error..

Thnx a lot for ur support..is there any other ideas?

[Former Member]

Hi Roberto,

I loaded it again...Atlast I got it again..

Thanks a lot for ur help...

One favour...Can u help me with regard to LONG TEXT??Pls give some ideas...

Cheers

Raji..

[Former Member]

Hi Roberto,

I am now loading thru flat file..still I am getting the same HEX Error.....Following are 3 errors with same diagnosis & procedure.

Value "" or from characteristic ZAPPLICAT contains an error at position 1
Message no. BRAIN290

Value "#" from characteristic ZSUR_ID contains an error at position 1

Value "Àe" from characteristic 0BBP_SC_ID contains an error at position 1

Diagnosis

Characters that have a hexadecimal format between HEX00 and HEX1F are not permitted in characteristic values. The 1th character is one of these characters. The value is therefore not permitted.

Procedure

Check where the characteristic value comes from. If possible, change it in the source. Incorrect source text in update routines and transfer routines can also cause this problem.

[Former Member]

Take a look at this blog...

/people/sap.user72/blog/2006/07/23/invalid-characters-in-sap-bw-3x-myths-and-reality-part-2

[prem_kool]

Hi BI Learner,

Could you please forward me the steps you took in resolving this issue?

Would appreciate your help, I am having the similar issue and it is kind of urgent.

Thanks,

Pramod.

[Former Member]

Pramod,

Paste the error here, so we can help.

[prem_kool]

Jr. Thank you for immeidate response.

The error message is:

=====================

Value 'S.Nikolic ' (hex. '20532E4E696B6F6C6963 ') of characteristic 0BPARTNER contains invalid character.

=======================

I am getting this error during data load into ODS. Using DS 2LIS_02_ITM ( purchasing - doc level).

Thanks,

Pramod.

[Former Member]

Pramod,

'S.Nikolic' - This is hpng because of lower case letters.

Convert LCase to UppCase in transfer rules /transformations.

Or

Edit the record in PSA and load it from there.

Or

Check the Infoobject for Lower Case . ( least preferred )

[prem_kool]

Jr,

Thanks for the solutions.

Unfortunately, I tried the top two methods.

1.

I put in a formula in 0BPARTNER transfer rule like follows:

TOUPPER( L_TRIM( R_TRIM( 0BPARTNER ) ) )

Loaded the MD object 0BPARTNER. Before loading I could not delete ALL the old records in this objects, since these were being used.

Tried to do the data load to ODS. The data load is successful. but cannot activate the ODS.

2. Deleted the last request from ODS.

Went to PSA maintenance through RSA1.

Changed all the records with 'S.Nikolic ' to 'N. RYAN' ( which does not give any errors). So there are no 'S.Nikolic' records in the PSA.

"Saved" the change.

'Right-click -> Start the update immediately.

The data load successful - but getting same errors:

==============

18:41:56 Value 'S.Nikolic ' (hex. '20532E4E696B6F6C6963 ') of characteristic 0BPARTNER contains invalid characte BRAIN

============

18:42:40 Error when assigning SID (details in long text) RSDRO 303

==========

Long Text -->

System response

Request: REQU_2ZHYOFDY6CLWO092FE864LVEZ

Data package: 000015

Data record: 934

InfoObject: 0BBP_REQSTR

Procedure

============================

Would really appreciate your help. This is getting delayed...

Thanks a million..

Pramod.

[prem_kool]

Jr.

When I said "this is getting delayed", I mean to say was - " this is killing me."

Any help is highly appreciated.

thanks

Pramod.

[Former Member]

1. Why were you not able to activate the ODS ?

Error message ?

Formula = TOPUPPER(ECCFIELDNAMEFOR0BPARTNER)

[Former Member]

Hi Pramod,

It will work..I am the same BI Learner where JR helped me..

U see whether ur 0bpartner Infoobject has not CHECKED THE LOWER CASE BOX...

Then,wht is L_TRIM & R_TRIM....is it the formula as well for TRIMMING left & right???if u r using so..

Dont use all those...Just USE TOUPPER(0BPARTNER) IN ur transformation rule for tht INFOOBJECT...

No need Change the records of data in PSA,u can directly load to TARGET Once u activated the transformation....

HOPE THIS HELPS..

TRY...100% it will work..

[Former Member]

hi,

check your characteristics ZPENAME data type and also check the data available in that.

i think that characteristics having hexadecimal values. change data or data type. activate it and load it.

hope this help you

regards

harikrishna N

[Former Member]

Hi Hari

U r telling to change data type,u mean i have to use NUMC??

Thnx a lot. but in source it is created as CHAR...I am not sure I can change in datasource..

pls give me ideas..

[Former Member]

Write a Formula to convert LC to UC.

Change Transformation - RClick on ZPENAME - Rule - Change Direct Ass to Formula - Right handside find & double click " TOUPPER " - In the brackets () - Place cursor inside & double click on ZPENAME - ECC Field - left hand side - save - activate - Rerun the DTP

[Former Member]

Hi Roberto ,

I tried doing this ...But still throws the error...

Pls is there any other idea??

[Former Member]

What is the error message now ..Can you paste it here ?

It cannot be same as you have converted LC to UC .

[Former Member]

Hi,

Just go to RSKC and make the invalid charecteristics to be accepted by the system, or else you need to change the same in the source system.

Regards,

Gattu

[Former Member]

hi

Could u pls wht r the settings to make the invalid char..acceptable??

Thnx for ur ideas..