autanabp
In Siebel, whenever we need to teach information in an Applet, but that information is not in the base table (or its extension tables) that support the Business Component on which the Applet is based, we have to bring the information from other sources. These sources can be other tables or other related Business Components. This is done through the use of Joins, Links or Multivalue Links and each one has its particularity and form of use.
Then we teach them the differences between them.
Joins
- They are configured between a Business Component and a Table
- Has a cardinality of 1:1 or 1:M
- They are configured as child properties of the BC
Example:
A service order can only have one owner. For that, a Join is created in the BC Service Request to receive the owner's information from S_USER
Links
- They are configured between two Business Compomets. Represent a Father-Child relationship
- It has a cardinality 1:M and M:M
- They are created through Siebel Tools Link objects
- They are referenced by Business Objects and Multivalue Links (MVL) to establish a Parent-Child relationship
- Primary Id Field. Use Primary Join and Auto Primary to implement the Primary Id Field
Example:
An account can have multiple addresses. A link between BC's Account and Business Address reflects the 1:M ratio
Multivalue Links
- Use a Link to access the child BC
- Return records taught in Multivalue Fields
- Aggregation functions can be applied to numeric fields, such as Count(), Sum(), Average(), Max(), Min(), etc.
- You can apply the Count() function to non-numeric fields, to know how many children the MVL returns to me
- Primary Id Field. Use Primary Join and Auto Primary to implement the Primary Id Field
