Value '1019400000 ' for characteristic 0MAT_PLANT is in external format

[Former Member]

Hi All,

iam loading master data to 0mat_plant in BW from 0mat_plant_attr in R/3 and the data load failed with an error "@5C@ Value '1019400000 ' for characteristic 0MAT_PLANT is in external format RRSV 9" .but i didnt get this error in Dev nor in QA ,i got this error in production. i think its some thing with Alpha conversion.

do we need to check the conversion fallg in the transfer rules for that infoobject? or

doi need to give alpha conversion in the info object definition?or do i need to do some thing inthe transaction RSMDCNVEXIT ........ if so can i do directly in the production with the above transaction?

so kindly explain the steps to perform in order to avoid the error in detail.

thanks in advance

jay

[Former Member · Accepted solution]

Hi All,

i for got to mention one more point and it is .......the conversion which is existing now for 0MAT_PLANT is MATN1 and i changed it in to Alpha in the info object definiton and also checked in the transfer rules and loaded data and it failed giving an error "Processing 1 finished" under status tab and when i check under details tab ofcourse iam getting the same error which currently iam facing in production and the error is "Record 1 :Value '1007400001 ' for characteristic 0MAT_PLANT does not have the right internal format "

later i tried to load data by not selecting any conversion in the info object definition and also in the transfer rules and the data load was succesful.so if i move these changes to production will it work ?.or else do i need to do any thing so that the data load will be successful in all the 3 environments.

so can any one guide me in this aspect

thanks in advance

jay

[former_member188972 · Accepted solution]

What is the configuration in OMSL transaction? (R/3 side)

If there isn't any particular customization on display material code the MATN1 will be identical to ALPHA.

Don't change the ALPHA routine in IO definition.

Without the routine, the risk is to have two different record in master data and transactional data:

1019400000

and

00000001019400000

they are logically the same material but not for the BW system.

With routine conversion you don't have this kind of problem.

Try to insert the function module

CONVERSION_EXIT_ALPHA_INPUT

into the transfer rule for your 0MAT_PLANT.

[Former Member · Accepted solution]

Hi Sergio,

when i repaired the info object 0mat_plant in RSRV the changes reflected in the transfer structure . imean the conversion flag got checked .( the conversion which is set to 0mat_plant in the info object definition is MAtN1 , after repairing the change is visible in the transfer structure .earlier the change was not there ).so i loaded the data in both Dev and in QA and the data load was successfull. so i migrated the changes to production with a new transport and even in the production the change had taken place with see the flag checked but when loaded data it failed throwing the same error.

1)in OMSL transaction , for the Material no length it is defined as 6.

2)0mat_Plant is mapped to material number in BW.

3) initially i changed the conversion form MATN1 to ALPHA in the info object definiton and tried loading data but it failed so i reverted back to the same conversion of MATN1.

4) i changed the conversion in the info object definition from MATN1 to empty and then loaded data and even it was successful.

so can any one guide me how to over come this issue ?

thanks in advance

jay

[Former Member]

Hi,

thanks to all especially sergio and i assigned points to all the useful answers.

thanks,

jay

[Former Member]

Hi,

I see a blank space after the the value '1019400000 ' for the char.

correct that blank space either in PSA or in source system and then do the reload.

This will solve the problem

Regards,

Vijay

[Former Member]

Hi in Transaction code omsl change the length from 1 to 18 .

[Former Member]

Hi Jay,

You need to carry ou the following steps:

1. Goto your dev box -> transfer rules of 0mat_plant -> In the "Data Str/Transfer str" side -> check the "conversion" checkbox for 0mat_plant. (the conversion checkbox is at the end of the row).

2. Transport your transfer rules and transfer structure along with the infosource to QA and then to Prod and then retry the load. It should work fine.

Bye

Dinesh

[Former Member]

Check the conversion flag in transfer rules for the infoobject; if customizing is open, you can do it directly in production and try loading, but do it also in dev.

Hope it helps.

Regards

[former_member188972]

You can set the alpha conversion also in the transfer rule.

See:

/people/sergio.locatelli2/blog/2006/11/02/upload-file-in-bw-common-mistakes-and-hints-to-take-in-mind

Regards,

Sergio