Loaction Data in Standard Material Repository

[Former Member]

The Material repository that has been provided as a part of standard business content with SAP MDM 5.5 SP5 does not have the fields corresponding to Storage Locations and Warehouse Management views of ECC6. Is there a specific reason for doing so?

In our scenario , one material can be stored in multiple storage location within a plant. A logical way to deal with this is to create Storage Location as Qualified Flat table within the Location Data Qualified Flat that has been provided . But SAP MDM does have this feature ( a qualified table nested within a qualified table).

What are the other alternatives to incorporate Storage Location fields into the standard repository ?

[Former Member]

Per SAP this capabilty will be only available in MDM 7.1

[former_member201266]

Hi Swampn,

Might be you already got your answer from above posts, but I would like to add another point, which I guesss might be another reason, SAP mainly conentrated on SRM and had that business content. And as much i have worked with SRM there are not storing any information about the material on hand; but they have some purchase type as Inventroy Request; where in they have just information of the material already existing; but not about its location or any other details, one think is we can customise that repository or yes ask SAP for an repository for Material Management(MM) or even union of both.

Cheers,

Cherry.

[Former Member]

Hi,

It is correct that nesting of Qualified tables are not possible but the alternative is create the storage location as Multivalued Lookup table with multiple display fields in it.So in Location Data you will be able to select multiple values from storage location along with the display.

Regards,

Jitesh Talreja

[Former Member]

Jitesh,

Defining Storage Location as a multi valued lookup field wont suffice because there are other data that has to be defined at the storage location level.

Edited by: Swapan Dutta on May 9, 2008 5:49 PM

[Former Member]

Swapan,

For your initial question, yes SAP has not provided the storage locations and WM screens in standard repository, I believe they have considered those fields as local attribute. If you look at the standard repositories, they have mostly provided the repositories with global attributes where the data can be used for any system(even for non SAP system). you can notice this in any repository(ex: customer, vendor, material)

You cannot have nested qualified lookup table. you may have to create multiple Q.lookup table for each views if necessary. The moment you add more Q.lookup tables, more the complex your repository becomes. Every thing is driven based on the business requirement. If you can justify that these fields are need to be maintained as a global attribute and should be part of MDM repository, you should be able to add those tables.

Every view should be treated as a seperate Q.lookup table, once again it's purely driven by business requirement.

Suresh.G

[Former Member]

hi Swapan

you are right. for storing material data at different plant levels we have the Location Data table of qualified type wherein we can have the same material stores/defined for several plants.

Same approach can be used for storage location and nested qualified table is one option for that though this is not part of the std business content. it has to be defined in console and added in repository structure.

hope it helps.

Regards-

Ravi Kumar

[Former Member]

The point is SAP MDM does not allow us to have a qualified table nested within a qualified table !