One to many relation

[CR]

Hi,
If a relationship of one field with the other is one to many, then is it possible to make that as an attibute of the master data.

Eg. 1 material can have multiple Serial nos.

Hence, is that possible to have Serial no. as an attribute of 0material, such that all serial nos. are displayed for that material.

Is there any call function or a routine that can be used to built up this relationship?

Urgent. Pl. help,

thanks,
CR

[SRV]

Usually it is the other way around. For example series code (KONDM). Several materials can belong to one series code, but one material can belong to only one series code. Hence you can define series code as an attibute on material, that is material to series code is a 1-to-1 relation.

In you case, you must probably make material an attribute of serial number. because one serial number can point to only one material.

What happens when a product comes for re-work or repair? Does it go out under the same material number? If another number is assigned, then you could have the same serial number assigned to 2 different material numbers.

For assigning attributes you dont need a function call, but for updating the attribute (user created) you need some simple transfer routine in the transfer rules.

Hope this drives you in the right direction.