Integration Platform Technologies: Siebel Enterprise Application Integration > EAI Siebel Adapter Business Service >

Enabling Effective Dating on Links

This topic explains how to enable effective dating on links. It contains the following topics:

• Enabling Effective Dating on Links
• Siebel EAI Adapter Operations for Effective Dating on Links

Enabling Effective Dating on Links

You can enable effective dating on a link in an existing integration object if the corresponding link in the business component is effective dating-enabled. You enable link for effective dating through the Siebel Web Client administration Effective Dating screen.

To enable effective dating on links

1. In the Siebel Web Client, navigate to Administration - Effective Dating, then Child Buscomp.
2. In the Effective Dating Buscomp list, select the required business component, then in the Child Buscomp view select the required link if it is shown.

   If you need to create a new link, see Step 3.

3. Click New, then in the Link Name field click the Select button.
4. In the Link window select the required link, then click OK.

Web Service Schema Example

The following Web service schema example shows a link between the Household and Related Contact business components which have been enabled for effective dating. The effective dating attributes are displayed in bold text.

<xsd:complexType name="Household">

<xsd:complexType name="RelatedContact">

<xsd:attribute name="EDStartDate" type="xsd:string" />

<xsd:attribute name="EDEndDate" type="xsd:string" />

<xsd:sequence>

<xsd:element name="ContactIntegrationId" maxOccurs="1" minOccurs="0" type="xsd:string" />

<xsd:element name="EDListOfFirstName" maxOccurs="1" minOccurs="0" type="xsdLocal1:EDListOfFirstName"/>

<xsd:element name="EDListOfLastName" maxOccurs="1" minOccurs="0" type="xsdLocal1:EDListOfLastName"/>

<xsd:element name="MiddleName" maxOccurs="1" minOccurs="0" type="xsd:string" />

<xsd:element name="PersonUId" maxOccurs="1" minOccurs="0" type="xsd:string" />

<xsd:element name="PersonalContact" maxOccurs="1" minOccurs="0" type="xsd:string" />

<xsd:element name="ContactId" maxOccurs="1" minOccurs="0" type="xsd:string" />

<xsd:element name="DateEnteredHousehold" maxOccurs="1" minOccurs="0" type="xsd:string" />

<xsd:element name="DateExitedHousehold" maxOccurs="1" minOccurs="0" type="xsd:string" />

<xsd:element name="PrimaryOrganizationId" maxOccurs="1" minOccurs="0" type="xsd:string" />

<xsd:element name="Relationship" maxOccurs="1" minOccurs="0" type="xsd:string" />

</xsd:sequence>

<xsd:attribute name="IsPrimaryMVG" type="xsd:string" />

</xsd:complexType>

</xsd:complexType>

This will produce the following XML:

<hous:Household>

<hous:ListOfRelatedContact>

<hous:RelatedContact EDStartDate="1/1/2003" EDEndDate="">

<hous:ContactId>88-30KSP</hous:ContactId>

< hous:EDListOfFirstName>

< hous:FirstName EDStartDate="04/01/2012" EDEndDate="">SF1N6</acc:James>

</ hous:EDListOfFirstName>

< hous:EDListOfLastName>

< hous:LastName EDStartDate="04/01/2012" EDEndDate=">SL1N6</acc:Bond>

</ hous:EDListOfLastName>

< hous:MiddleName>MN1</hous:MiddleName>

</hous:RelatedContact>

</hous:ListOfRelatedContact>

</hous:Household>

Siebel EAI Adapter Operations for Effective Dating on Links

The Siebel EAI Adapter receives the integration object in the format described in the Web Service Schema Example. Depending on the specified operations the effective dates are used as described in the following:

Insert operation

Once the record is inserted into the parent and child business component, the Siebel EAI Adapter reads the EDStartDate and the EDEndDate from the integration object and inserts these values into the corresponding effective dating business component.

Update operation

Once the record is inserted into the parent and child business component, the Siebel EAI Adapter removes all history records from the effective dating enabled business component and then reads the EDStartDate and EDEndDate values from the integration object and inserts these dates as fresh records into the business component.

NOTE:  The Update operation is only possible for currently active links (in other words, update is not possible if a link has been soft deleted by giving a end date value for most recent history record).

Upsert and Synchronize Operations

If the upsert attribute is specified for the operation in the integration component then no history records are deleted, instead the history given in the XML input is inserted into the history table.

The synchronize operation can result in the insert, update or deletion of the child integration component as specified in the conditions set in the Synchronize Method.

XML Example

This example illustrates what is required if you want to perform an insert or upsert operation to insert or update multiple history records for the same child business component.

NOTE:  Multiple entries must be specified in the input XML code with same user key.

<hous:Household>

<hous:ListOfRelatedContact>

<hous:RelatedContact EDStartDate="1/1/2003" EDEndDate=">

<hous:ContactId>88-30KSP</hous:ContactId>

</hous:RelatedContact>

<hous:RelatedContact EDStartDate="1/1/2002" EDEndDate="12/31/2002">

<hous:ContactId>88-30KSP</hous:ContactId></hous:RelatedContact>

<hous:RelatedContact EDStartDate="1/1/2001" EDEndDate="12/31/2001">

<hous:ContactId>88-30KSP</hous:ContactId>

</hous:RelatedContact>

<hous:RelatedContact EDStartDate="1/1/2000" EDEndDate="12/31/2000">

<hous:ContactId>88-30KSP</hous:ContactId>

</hous:RelatedContact>

<hous:ListOfRelatedContact>

</hous:Household>