cancel
Showing results for 
Search instead for 
Did you mean: 

Error: InfoObject does not contain alpha-conforming value 20030729

Former Member
0 Kudos

Hi everyone,

I got this problem, that i tried to fix yesterday, but all i did was that i got realy frustrated...

I created an infoobject which is copy of 0DOC_NUMBER and has alpha coversion routine.

Mapping field in DataSource is also type character 10(VBELN) as my infoobject.

But there are some values in this field that i am trying to load, less then 10 characters long (20030729,20051116...) and shouldn't be there, because the values are dates and not document numbers.

But anyway on R/3 side this values are in field which is defined as character 10 (VBELN), and when I am trying to load Infopackage(17500 records) I get 52 errors: InfoObject does not contain alpha-conforming value 20030729.

I don't get it, since both fields are type character 10 and the values are only digits, why do I get this error message and how can I fix it?

PS:One solution is to remove alpha conversion routine from infoobject, but i don't want that.

Regards,

Uroš

View Entire Topic
edwin_harpino
Active Contributor
0 Kudos

hi,

rsa->infosource->locate your infosource, change transfer rules, and locate 0DOC_NUMBER, tab 'transfer rules', left side 'Communication str./Transfer r', scroll to right, to last column 'conversion', mark it, activate transfer rules again. and reload data.

hope this helps.

Former Member
0 Kudos

wow, thanks.

That seems to work for that infoobject. What does that mark do?

But now I get another error when activating data records from ODS object.

Subseq. processing:

- Value 'h ' (hex. '0068 ') of characteristic ZVBTYP_N contains invalid characters.

My infoobject ZVBTYP_N is the same type as mapping field CHAR(1) and value'h' is CHAR value.

What is the problem here?

Regards, Uroš

edwin_harpino
Active Contributor
0 Kudos

hi,

you are welcome.

that mark tell system to do conversion for that char, will add zero(s).

the problem here may cause by lower case 'h ' used, your infoobject ZVBTYP_N doesn't allow lower case, RSD1 you can check it's not mark 'lower case'.

to fix this, you can change transfer rules again, and ZVBTYP_N use method 'routine' and create routine and put code

result = tran_structure-/bic/zvbtyp_n.

translate result to upper case.

hope this helps.

Former Member
0 Kudos

Thanks...

I had to mark the field to use lower case.

This was very helpful....

Regards,

Uroš

edwin_harpino
Active Contributor
0 Kudos

dear Uroš,

please be remind, by mark ZVBTYP_N lower case,

you won't be able to use this characteristic as navigational attribute purpose in reporting/query,

you can go with translate to upper case if you want it as navigational attribute (remove the mark).

hope this helps.

Former Member
0 Kudos

But i can translate to upper case, because the value 'H' and value 'h' has different meaning.

So if i translate to upper case then i lose values with lower case which aren't the same.

Why can't i use this characteristic as navigational attribute?

edwin_harpino
Active Contributor
0 Kudos

hi,

sorry... correction, it's 'Exclusive attributes' that cannot be used for navigational attribute, you can set lower case to differentiate ... check the impact of lower case setting here ...

http://help.sap.com/saphelp_bw33/helpdata/en/b7/f470375fbf307ee10000009b38f8cf/frameset.htm

Lowercase letters allowed / not allowed

If this indicator is set, the system differentiates between lowercase letters and capital letters when you use a screen template to input values. If this indicator is not set, the system converts all the letters into capital letters when you use a screen template to input values.

If you choose to allow the use of lowercase letters, you must be aware of what happens when you input variables:

If you want to use the characteristic in variables, the system is only able to find the values for the characteristic if the lowercase letters and the capital letters are typed in accurately on the input screen for variables. If, on the other hand, you do not allow the use of lowercase letters, any characters that you type onto the input screen, are converted automatically into capital letters.

Exclusive attributes:

If you select Exclusively Attributes, the created characteristic can be used only as a display attribute for another characteristic, and not as a dedicated characteristic in the InfoCube. Furthermore, you then cannot transfer the characteristic into InfoCubes. However, you can use it in ODS objects or InfoSets.

Former Member
0 Kudos

Thanks, for all your answers they were very helpful.

Regards,

Uroš