Therefore I decided to give them a H.U.G. (Hopefully Useful Graphic).
So if you want to read along, please have a look at this diagram which shows the Siebel Repository objects involved in implementing a one-to-many multi value field.
Easy, isnt't it?
Let's explain the above diagram a bit from bottom to top:
- Base tables store the entity data in Siebel CRM.
- The master business component represents the "one" side in a 1:M relationship.
- The child business component represents the "many" side in a 1:M relationship.
- A multi value field references a multi value link and a field in the child BC.
- The multi value link references a link (which establishes the 1:M relationship between master and child BC), the child BC and a primary Id field.
- The primary Id field references the foreign key column in the master BC's base table which points to the primary child record (this record has the Primary flag set in the MVG applet).
- MVG applets and associate applets (for M:M relationships) always reference the child BCs.
You might also want to check out my previous post on MVG applets.
The Siebel CRM 8 Developer's Handbook also lays out these concepts in great detail.
have a nice day