InfoObject SOLD_TO contains non-alpha compliant value 99111

[Former Member]

Hello Experts,

this issue is coming in quality system when im trying to load data.

pls help me on this ....!!

Diagnosis

    The system checked whether the loaded InfoObject value conforms to the

    conversion exit. The check failed.

    Example:

    The value '1' was loaded into an InfoObject with alpha exit, even though

    the value '0000000001' was expected.

System Response

    The load process has failed or erroneous records are displayed in the

    monitor, depending on how error handling is set up.

Procedure

    Determine why the data does not conform to the conversion exit, and, if

    possible, correct the cause. Possible causes are errors in BI Content or

    an error in a customer exit in the source system.

    If you cannot correct the problem, you have the option of removing the

    conversion exit on the InfoObject. However, since the system has already

    been converted, duplicates appear in the system again.

Regards

Madhu

[former_member209895 · Accepted solution]

Hi Madhu,

    The error itself indicates that BW infoobject is expecting a value 0000000001 instead of just 1. If you are loading data from a flat file then make sure to add the required number of zeros so that the total length is 10.

If the load is from R/3 then you can either ask the functional guys to maintain data with the preceeding zeros or you can use the function module "Conversion_exit_alpha_input" in the start routine to convert 1 to 0000000001.

Hope this helps,

Regards,

  Manohar. D

[Former Member · Accepted solution]

Manohar,

but in my development system it is running perfect there is no error at all ..... problem in quality only.

Regards

Madhu

[Former Member · Accepted solution]

Hi,

Please check infoobject properties in Dev and Quality.

Conversion routine is selected or not? and check the links provided me.

[former_member209895 · Accepted solution]

That is because this is a DATA ISSUE and not a DESIGN ISSUE. If the data being supplied in the DEV R/3 is correct with all the left padded zeros then the Development will obviously not display any errors, but in quality the data is not being supplied in the BW expected format which is why the error is occuring only in quality.

So you can request R/3 team / Functional team to work on it, so that the data is sent up to BW in the proper format or add a routine as suggested by me before in DEV, QA and PROD, so that in future if at all there is the same error again due to mismanaged data then BW will rectify the issue and spare you from this error again.

Regards,

  Manohar. D

[RamanKorrapati · Accepted solution]

Hi Madhu,

is data is same in dev and quality? if data was same then check for quality error records how its stored in target level and psa in dev syatem compare with quality.

Thanks

[Former Member · Accepted solution]

Aakash,

I checked the properties in Dev and Quality,same in both systems.

where we select Conversion routine...?

Regards

Madhu

[Former Member · Accepted solution]

Hi ,

Please select your Infoobject and Under general tab there is one Option Conversion Routine Under lower case check box and provide Alpha and check.

[Former Member · Accepted solution]

Aakash,

Already selected Conversion routine as alpha.

Regards

Madhu

[former_member209895 · Accepted solution]

Hi Madu,

    If writing a routine is too much then try the below:

1.Right click on the datasource which is supplying data for sold to party and choose CHANGE.

2. Click on the fields tab

3. Here the 5th column should have the heading as Conv. Routines. Check what is mentioned against Sold To party.

4. If nothing this mentioned then use the F4 help and select the value "Conversion_exit_alpha_input".

5. Save and activate the datasource and repeat the load.

Please find the below screenshot:

Hope this helps,

Regards,

  Manohar. D

[Former Member · Accepted solution]

Manohar,

we are in BW 3.5 .... we already selected alpha at info object level.

Regards

Madhu

[former_member209895 · Accepted solution]

Hi Madhu,

   If you are in BW 3.5 then you can choose the ALPHA conversion routine from the transfer structure:

Hope this helps.

Regards,

  Manohar. D

[Former Member · Accepted solution]

Manohar,

I'm unable to add ALPHA for field WEMPF (0SOLD_TO) in Transfer Structure, its not taking ... do i need to delete transfer rules, transfer structure and rebuild it.

Regards

Madhu

[Former Member · Accepted solution]

In the transfer rules tab, select the conversion check box for the info object which you are facing the issue...

This should ix your issue...

Check the below link for more details...

http://help.sap.com/saphelp_nw04/helpdata/en/2b/e9a20d3347b340946c32331c96a64e/content.htm

Do revert back if you are not able to find the option...

Thanks,

Nithesh.

[former_member209895 · Accepted solution]

Hi Madhu,

     You cannot directly add it, all you have to do is check the CONVERSION checkbox in the transfer rules as shown below, and this would enable the conversion routine which is mentioned in the infoobject General tab screen:

I'm not sure why some of the checkboxes are greyed out even though the corresponding info objects have a conversion routine in their design. But please try the above first.

Hope this helps,

Regards,

   Manohar. D

[Former Member · Accepted solution]

Hi Manohar,

Thanx for giving clear explanation i appreciate you.

I  checked the CONV checkbox in the transfer rules for field 0SOLD_TO and saved it.

and re-triggered Info Package after doing all this some new issue coming its says .... Value hex of characteristic 0CUSTOMER contains invalid character.

Regards

Madhu

[RamanKorrapati · Accepted solution]

Hi Madhu,

at PSA Level 0Customer may have invalid char like '#' '/' or space, or lower case letters kind. first find out invalid char data and edit psa and relaod master data for 0customer.this error may repeat every day when master data load happens. so with help source team, make corrections in ecc and load to psa.

For lower case issue, you can select lowercase check box at info object level. you can usee T-Code - RSKC to maintain special chars,

ALL_CAPITAL_PLUS_HEX

please share the error log details or screen shot.

http://scn.sap.com/docs/DOC-40684

Thanks

[former_member209895 · Accepted solution]

Hi Madhu,

     Great to know that it works, kindly take time to mark the answer which helped you as correct so that others searching answers for the same issue would know what helped you and also the contributor could get some points. Also I would request you to open a new thread for a new error. Please provide a few details on what exactly the error message is, when you open a new thread.

Regards,

  Manohar. D

[Former Member]

see this thread

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

http://scn.sap.com/message/14010710

[Former Member]

Hi ,

Pls check http://scn.sap.com/thread/3165862

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

http://scn.sap.com/thread/740641 this may helps you

[RamanKorrapati]

Hi Madhu,

If your getting error for only one record, then you can delete request at target level and edit data at PSA. for info object 0SOL_TO if length defined as 10, the record value at psa having 1 or 12, you can add padding zero, like 0000000001 or 0000000012 . save data at psa and load further.

If you thought that facing this error daily basis, then you can follow Manohar suggestion.

Thanks

[former_member209895]

The error will mostly be on daily basis as we are speaking of master data here, hence a full load. So a permanent fix would be better than temporary work arounds.

Regards,

  Manohar. D

[RamanKorrapati]

Agree With you Manu , but he is in quality system for test cases think so. that's i suggested to go further without delaying  his test cases.

Thank you

[Former Member]

Raman,

If there are few error records then i can able to edit it but here i could see 1000-2000 error records in one data packet.

Regards

Madhu

[Former Member]

This is just an data error, hope it should not be the case in prod system...

For safer side, try padd zeros to the values using the FM Conversion_exit_alpha_input....

Using this you can avoid the non-alpha complaint error...

Thanks,

Nithesh.