topic Re: Database design in Application Development and Automation Discussions

Database design

Former Member — Fri, 31 Mar 2006 04:07:29 GMT

Dear All ,

Client procure the tool from outside , and he gives that tool to another vendor who inturn produces the material from that tool and supply the produced component from that tool to client .

Now Client want to enter the tool no , vendor from whom the tool has procured , vendor to whom tool is issued and component that can be produced from that tool . Major Issue is one tool can produce many componenets like one PO can have many line items .

I am not able to desgin the database which will hold all data . And when we design the database is it compalsry to have MANDT field .pls give me some idea .

Re: Database design

Former Member — Fri, 31 Mar 2006 04:11:00 GMT

Raghavendra,

I am not sure if I understand your business process, can you explain in detail.

Coming to MANDT, if you want your table to be CLIENT DEPENDENT, then MANDT is mandatory. A instance of SAP can have multiple CLIENTS and the transactional / master data is usually different in each of the clients, that means its CLIENT DEPENDENT.

Regards,

Ravi

Note : please mark the helpful answers

Re: Database design

Former Member — Fri, 31 Mar 2006 04:15:59 GMT

Well, like a PO, maybe you need two tables: one for the tool which would have MANDT and TOOL as the key fields and information about the tool in that table. The other table would be for the tool components and would have MANDT, TOOL and COMPONENT as the key fields. The other fields would have data particular to the fields.

Rob

Re: Database design

Former Member — Fri, 31 Mar 2006 04:16:44 GMT

You have four different values here. TOOL, FROM_VENDOR, TO_VENDOR, COMPONENT_PRODUCED. Now if I assume that you procure a tool from only one vendor, then I can have a table that stores the information between TOOL and FROM_VENDOR. Similarly I can have another table that stores the TOOL and TO_VENDOR. Another table for TOOL and COMPONENT_PRODUCED. If all of them are tied together with a document like a work order, then that number will be the link. If you need to figure out how many times this tool is given to the same vendor to produce the same component several times, then the date comes into picture. So you can do it as one table or multiple tables linked together with some master, transactional type of data relationships.

MANDT represents client dependency. When you have multiple clients and you want to separate the data from one client to another, then you will have to have the MANDT field. If your data is cross-client(which I don't think yours is), then you don't need this field.

Re: Database design

Former Member — Fri, 31 Mar 2006 04:18:18 GMT

Hello ravi ,

company outsource some components to outside vendor .The tool required to prodce those components is supllied by the main company . While issuing tool to vendor he wnat one screen where he can enter the details of the tool , vendor and the components that can be produced from that tool . But one tool can be used to produce different component .

This is the scnario . I have to design database which having field as folows

tool_no

vendo to whom tool is issued

date of issue

components

since the primary key will be the TOOL_no how to store the components that are produced from that tool . Because one tool can produce many components . and key will repaet . This is my idea .