cancel
Showing results for 
Search instead for 
Did you mean: 

Problems when maintaining 0MATERIAL

Former Member
0 Kudos

Hi,

I have found a problem with 0MATERIAL characteristic. when you double-clic on it, a message displays:

"Settings for material number conversion not found"

And the create/maintain infoobject shows all the text boxes blank.

¿does any one knows what is happening?

thanks for the help.

Mauricio

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Go to SPRO in BI and enter values for SAP NetWeaver -> Business Intelligence -> General BI Settings -> Set Material Number Display.

Tip: The value here shall be same as value displayed in the transaction OMSL in source system.

Answers (3)

Answers (3)

Former Member
0 Kudos

Elangovan,

thanks for the help. yor suggestion solved the problem.

points awarded.

Mauricio.

Former Member
0 Kudos

Hi.......

Try oss note 555675, it tells you to use transaction OMSL.

Symptom

One of the following errors occurs:

1. The following message appears when you create or schedule an InfoPackage: RC = 4'.

2. When you display the 0MATERIAL InfoObject or when you use the InfoObject in a query, the message 'Settings for the material number conversion do not exist' appears (message number BMG 135).

3. When you display the master data for the 0PRODUCT InfoObject in transaction RSD1, the 'Setting for the material number conversion does not exist' (message number BMG 135).

4. The error message BMG 135 is written to the log when you execute the after-import method of an InfoSpoke. The transport receives the return code 8.

Other terms

BMG135, MATN1, conversion exit, OMSL, TMCNV, InfoSpoke, transport

Reason and Prerequisites

There are no settings for the material number conversion.

Solution

Make the settings for the material number conversion.

In BW Release 2.1C, the settings are maintained for the material number conversion via report RSCC_V_TMCNV.

As of BW Release 3.0A, the settings are maintained for the material number conversion via transaction OMSL.

Select the same settings as the settings made in the OLTP system.

Note that you must also perform the setting in client 000 if the error occurred while you were importing a transport request.

Hope this helps.......

Regards,

Debjani.......

Edited by: Debjani Mukherjee on Oct 21, 2008 7:20 AM

Former Member
0 Kudos

I think you need to set the conversion routine to MATN1.

Also, if the Dictionary area under the General tab is all unfilled, you may want to reinstall the characteristic from Business content again.

Or you can fill it with these values:

Data Type CHAR

Length 18

Lowercase letters (unchecked)

Convers. Rout. MATN1

Output length 18

However, this is typically a very important characteristic in BW, so I would reinstall if it doesn't look right.

Brian