RSDMD 194: 0MATERIAL Datarecord is invalid

[Former Member]

Hi together,

I tried to load the attributes for 0Material and receive the following error message for all data lines:

Diagnosis

Data record 1 & with the key '000000000000000020 &' is invalid in value

'000000000000000020 &' of the attribute/characteristic 0MATERIAL &.

System Response

The system has recognized that the value mentioned above is invalid, and

has processed this general error message. A subsequent message may give

you more information on the error. This message refers to the same

value, even though it does not state this explicitly.

****

Maybe you have a idea what's wrong?

Thanks!!!

[Former Member · Accepted solution]

Problem solved.

Found another discussion thread. Solution: use "Lowercase letters" option in infoobject or convert all text into upper case.

[Former Member · Accepted solution]

It really helped to solve similar problem.

Thank you.

[Former Member]

Hi Everyone,

I have a similar problem with the attributes for 0customer. We created an info provider based on 0customer (CHAR 10) and feed the attributes into our own infoprovider. I receive the same message

"PCPAC0023 (which is the Field technical name for post code) : 43316 ('0000167009') (which is the customer number) Version 'FY2 0UZ' is not valid." The strange thing here is that they have many customers with post codes from great britain that are in the same format and have a combination of letters and numbers. I can see no reason as to why this post code is not valid when all the others are.

On the test system I had another case with a Portguese post code being '4470 - 605 ', but again, this format is acceptable for the other portuguese customers.

I dont have lower case letters checked (but there are no lowercase letters in either of these cases) Every thing else seems to be in order.  What am I missing? Can you help me find a solution please?

Regards

Cynthia

[rahul_nagpal]

Hello All,

To solve the above issue , Log on to BW system

Open Transaction OMSL and then  maintain the 0Material length i.e. 18 Char.

Save it and then Close.

You  can then load the data without any issues,

Regards

Rahul

[Former Member]

Hi Xmchx,

I got the same "invalid in value" error message when I was loading master bank data. I know you fixed your problem as you indicated in your last post. I don't think I understand what "OMSL has to be maintained in BW" mean. Could you please explain a little more?

My situation is: I created a datasource in R3 system and tested fine. Then, I replicated it in BI system and try to execute DTP in BI. I got the following error. I am using BI 7.0.

Data record 11 & with the key '000000022334455668 &' is invalid in value

'Hausbank &' of the attribute/characteristic ZBANKA &.

Could you please give me some help. Thanks!

Tim

[Former Member]

Hi Tim,

While loading master data I got the same issue.Proble sdscription is

Diagnosis

    Data record 387 & with the key '0000007334 &' is invalid in value '21676
    &' of the attribute/characteristic ZECOMPORT &.

System Response

    The system has recognized that the value mentioned above is invalid, and
    has processed this general error message. A subsequent message may give
    you more information on the error. This message refers to the same
    value, even though it does not state this explicitly.

Procedure

    If this message appears during a data load, maintain the attribute in
    the PSA maintenance screens. If this message appears in the master data
    maintenance screens, leave the transaction and call it again. This

    allows you to maintain your master data.

Can you tell me how can I solve this issue??

Thanks In advance.

Regards,

Rakesh

[RamanKorrapati]

hi rakesh,

As per Tim solution,

You need to check the "lower case" option at info object--> Double click--> Edit mode--> general tab, tick lower case, bcaz of this option, object can carry lower and upper case letters in descrption.

if you want only upper case in your descrption text, use field routine to conver to upper case.

thanks

[Former Member]

Hi Tim,

Thanks for reply but in this IO the option is ticked and the data is coming as numbers.

Regards,

Rakesh

[Former Member]

use Tcode RSA3 in source system and look of the same material. I feel that it is having some character which is not acceptable by BW.

In that case go to psa correct the errorus record and reload the data maually.

Regards,

Mahendra

[Former Member]

I now found the problem: OMSL was maintained in the source system only. OMSL has to be maintained in BW, too

[Former Member]

Hello XmchX,

As you can see in the error message, a material identification consists of a number (20), followed by a blank and an ampersand.

Probably 0MATERIAL in your system is identified by a numeric key. As the above mentioned key is not numeric the record cannot be loaded.

I hope that this hint helps to solve your problem.

Kind regards,

Stefan

[Former Member]

Hi,

thank you for your answer. The point is, that the info-object 0Material is defined as CHAR Lengh 18. Also in the ERP-Source System, we have defined the Material number with 18 digits (TA OMSL) for BW.

We have activated the SAP Standard Content (no changes) - so why is SAP not loading correctly, if we are using the standard?

The other thing I am wondering is, that in the Standard-Content for MM we can not load the Material Number directly. Predefined transfer structures are only availabe for HIERARCHIES 0MATERIAL, ATTRIBUTES 0MATERIAL, TEXTS 0MATERIAL.

Thanks for the help!

XmxhX