Bookshelf Home | Contents | Index | PDF | ![]() ![]() |
Integration Platform Technologies: Siebel Enterprise Application Integration > EAI Siebel Adapter Business Service > Enabling Effective Dating on FieldsThis topic explains how effective dating works on fields. It contains the following topics:
Configuring Integration Components for Effective Dating on FieldsYou can enable effective dating on a field in an existing integration object if the corresponding field in the business component is effective dating-enabled. You enable fields for effective dating through the Siebel Web Client administration Effective Dating screen. To enable effective dating on fields
You use Siebel Tools to synchronize the object from your current repository, with its underlying business object in the Siebel database which contains the new EDEnabled user property. For more information on synchronizing integration objects, see Synchronizing Integration Objects. To enable effective dating on an integration object
How the XML Converter Reads Effective Dating Data from FieldsThe XML converter reads effective dating attributes contained in an XML file, maps them to a property set, and converts the property set to an integration object instance by embedding the EDStartDate and EDEndDate attributes inside the field name. For example: If a SOAP request contains the following query for an effective dating field: <acc:FirstName EDStartDate="04/01/2012" EDEndDate=">James</acc:FirstName> The data will be converted into a child property set of the integration component instance as follows: c[0] CCFPropertySet@1DA79960 p#0 c#1 type="ListOfRelated Contact" vt=0 value=" c[0] CCFPropertySet@1D9FD870 p#1 c#2 type="Related Contact" vt=0 value=" c[0] CCFPropertySet@1FD92BB0 p#0 c#1 type="EDListOfFirst Name" vt=0 value=" c[0] CCFPropertySet@13258470 p#2 c#0 type="First Name" vt=3 value="James" ["EDStartDate"] = "04/25/2012"; The dates are now embedded into the field name. WSDL Schema Generation for Effective Dating on FieldsEffective dating requires two complex type attributes StartDate and EndDate for each effective dating-enabled field. In the following schema example the location field is enabled for effective dating, as shown by the two additional attributes EDStartDate and EDEndDate. Historical data can be retrieved by setting the cardinality of the effective dating-enabled XSD element to unbounded. WSDL Schema Example<xsd:complexType name="RelatedContact"> <xsd:element name="ContactId" maxOccurs="1" minOccurs="0" type="xsd:string"/> <xsd:element name="EDListOfFirstName" maxOccurs="1" minOccurs="0" type="xsdLocal1:EDListOfFirstName"/> <xsd:element name="ContactIntegrationId" maxOccurs="1" minOccurs="0" type="xsd:string"/> <xsd:element name="EDListOfLastName" maxOccurs="1" minOccurs="0" type="xsdLocal1:EDListOfLastName"/> <xsd:complexType name="EDListOfFirstName"> <xsd:element name="FirstName" maxOccurs="unbounded" minOccurs="0" type="xsdLocal1:FirstName"/> <xsd:complexType name="FirstName"> <xsd:extension base="xsd:string"> <xsd:attribute name="EDStartDate" type="xsd:string"/> <xsd:attribute name="EDEndDate" type="xsd:string"/> SOAP Query ExampleThe previous WSDL schema example allows you to generate the following SOAP query: <ElementName EDStartDate=dd1/mm1/yyyy1, EDEndDate = dd2/mm2/yyy2>value</ElementName> <acc:ContactId>88-30ARL</acc:ContactId> <acc:FirstName EDStartDate="04/01/2012" EDEndDate=">James</acc:FirstName> <acc:LastName EDStartDate="04/01/2012" EDEndDate=">Bond</acc:LastName> Similarly you can perform insert, update, and synchronize operations on data using the WSDL Schema Example. |
![]() ![]() |
Integration Platform Technologies: Siebel Enterprise Application Integration | Copyright © 2014, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |