Material Number range inconsistency

[Former Member]

HI All,

I am facing a material range inconsistency in our Dev environment.

MDM gets number range generated in ECC and that is sent back to MDM.

Incidently,a material creation this way has resulted in duplicate material no in MDM,

Please tell me where to look for.

[Former Member · Accepted solution]

Hi,

Refer below thread

[http://www.sap-img.com/mm003.htm]

[;

Thanks,

[Former Member · Accepted solution]

Thanks for helpful links Gaurav.

Issue is that material is one in ECC but there are 2 records with same material no as ECC.

pls help me with pointers.

[Former Member · Accepted solution]

Hi,

I think you are getting duplicate Records in a Qualified table,its not possible that qualifiers also become unique then its not possible, but you can create Non-qualifier as unique using that property. and in actual only non-qualifiers are stored in qualified lookup record.

no record maintains all fields as unique and primary key. it is not possible to make a record in a qualified table unique.

Thanks

[Former Member · Accepted solution]

Hi Gaurav,

Issue is not with qualified table data.

For 1 record in SAP I have 2 records in MDM with same material no.

The Material no is not set unique as it is getting created in SAP n being sent to MDM.

[rajesh_chavan · Accepted solution]

I feel it should work in this way...

You need to have MDM ID while posting data back to SAP ECC from MDM. The MDM ID can be saved in some unused field in SAP ECC, (may be Name4 or search term2). Once material number created change pointer should trigger idoc to send Material Number, MDM ID back to MDM. This time u need to pull data based on MDM ID which will update your material number for same record.

Hope this helps

Cheers,

Rc

[Former Member · Accepted solution]

Hi,

The problem can be solved by exploring the areas i suggested.

What is your frontend?

Thanks,

Ravi

[Former Member · Accepted solution]

Hi Experts,

No generation takes place in ECC and BAPI populates no in MDM.Glabal data is created in MDM and sent to ECC by idoc,No so generated in ECC gets activated this way.

Please help me find possible causes.

[Former Member · Accepted solution]

HI,

This could occur because of many reasons.

Try looking at all the integration points between the systems.

This is a scenario of data mismatch as i see.

Thanks,

Ravi

[Former Member · Accepted solution]

Hi,

The most probable reason could be change in range defined in SAP system.

Data creation by other methods is second most probable scenario for me.

Try discovering these areas.Check update dates and corresponding dates in SAP system.

Check for the record which is not in SAP system.

Hope it helps.

Thanks,

Ravi

[Former Member]

Create a field in MDM with Unique constraint and use this field in Import map for matching records. Send this field also to ECC and make sure that it is stored in ECC and returned back with data back to MDM.

Maintain a Remote System ECC with the Material number as Remote Key in MDM repository.

Thanks,

Shambhu.

[former_member188878]

rav343,

Please try to use the remote key concept whil imporing the data in MDM.

regards

shankar

[Former Member]

Hi,

Data consistency can be because of:

->Different environment MDM repository usage

->Different environment SAP system configurations transported

->Change in SPRO config

->Different mode of creation apart from what you mentioned.

Thanks,

Ravi

[Former Member]

Hi,

This should never happen.

Check your import maps "Match Records" tab. Also refer to the Import Manager guide - http://help.sap.com/saphelp_mdm550/helpdata/en/43/534033ebfc2bf2e10000000a422035/frameset.htm

Are you using the concept of Remote Key Mapping in your MDM repository?

Thanks,

Shambhu.