|Bookshelf Home | Contents | Index | PDF|
An integration object instance most often has multiple integration component instances. For example, an Account can have multiple Business Addresses but only one of these addresses is marked as the primary address. A business requirement may require that only the integration component instance that corresponds to the primary MVG be part of the integration object instance. In relation to Account and Business Addresses this means that only the primary address should be part of the Account integration object instance. The primary address can be obtained by one of the following steps:
For example, as illustrated in Figure 5, the Account business component contains a multi-value group field, the Address Id.
As shown in Figure 6, the multivalue link property has the value Business Address. If you navigate to the Multi Value Link screen, you see that the Business Address multivalue link has the value Business Address as its Destination Business Component.
As shown in Figure 7, the Business Address multivalue link has Business Address as its Destination Business Component. This means that there is another business component named Business Address that contains the fields that are collectively represented by Address Id in the Account business component.
Figure 8 shows a graphical way to represent the relationship between Account business component and the Business Address multivalue link.
The more table-like representation in Figure 8 shows how the Business Address multivalue link connects the two business components. The child points to the Business Address business component, which contains the multiple fields that make up the MVG.
Figure 9 shows an integration component based on an MVG and its user property value in Siebel Tools.
The EAI Siebel Adapter needs to know the names of the MVG fields as they are defined in the parent business component—in this example, Account—and also the names of the MVG fields as they are known in the business component that represents the MVG—in this example, Account Business Address. As shown in Figure 10, the integration component fields represent the MVG.
To represent both names, each field is assigned an integration component field user property that contains the entry MVGFieldName or AssocFieldName if the user property is MVGAssoc. Its value is the name of the field shown in the parent business component—in this example, Business Address.
|Integration Platform Technologies: Siebel Enterprise Application Integration||Copyright © 2008, Oracle and/or its affiliates. All rights reserved. Legal Notices.|