Oracle Web Services On Demand Guide > Oracle CRM On Demand Objects Accessible Through Web Services > Core Parent Objects (Web Services v2.0) >

Contact

The contact object stores information on individuals with whom your organization has a relationship. It allows the user to store information on individuals who are external to your company, but who are associated with the business process. Contacts stored in the Oracle CRM On Demand database can also be associated with an account.

Adding and Updating Contact Addresses

The information in this topic is applicable when the Enable Shared Addresses check box in the company profit is deselected, that is, when addresses are not shared.

NOTE:  When Enable Shared Addresses is selected, the address child object, (<ListOfAddress>) cannot be used, and instead the shared address child object (<ListOfSharedAddress>) must be used to associate or dissociate addresses and flag addresses as billing, shipping, or primary addresses. For more information about the shared address child object, see Shared Address and for more information about the address child object, see Address.

The contact object has three types of address:

1. Primary address
2. Alternate address
3. Simple address

If the contact is associated with an account, the account's billing address becomes the contact's primary address, that is, the account's billing address fields populate the contact's primary address fields. The primary address fields are read-only in the contact record. The primary address might also be called the account address.

The alternate address is simply the contact's address. Alternate address fields at the parent level are editable and this address is added to address children with the Primary checkbox in the UI selected. The alternate address might also be called the contact address.

You can use either ContactInsert, ContactUpdate or ContactExecute calls to insert or update primary or alternate addresses for a contact. With ContactInsert or ContactUpdate calls, the contact parent node with primary and alternate address fields must be present, and there must not be any child node. If an address child is present, only a simple address can be added, and not primary and alternate addresses. If the address child or any other child node is not present, only primary and alternate addresses can be added, and not simple addresses.

With the ContactExecute call, both the contact parent node and address child node can be present along with primary and alternate address fields at the parent level.

NOTE:  A PrimaryAddressLine1 field is used to dynamically map the primary address field from an external application to the primary address field in Oracle CRM On Demand. For more information, see Mapping Primary Address Fields Using Web Services.

Child Objects

Account, Activity, Address, Attachment, Book, Business Plan, Blocked Product, Call Activity History, Campaign. Claim, Contact Best Times, Contact State License, Coverage, Custom Object 1 through 3, Deal Registration, Financial Account, Financial Account Holder, Financial Plan, HCP Contact Allocation, Household, Image, Interests, Involved Party, Lead, Message Response, Note, Objective, Opportunity, Plan Contact, Policy, Policy Holder, Portfolio, Related Contact, Revenue, Sales Assessment, Sales Assessment Value, Service Request, Signature, Shared Address,Social Profile Special Pricing Product, Team.

NOTE:  When Enabled Shared Addresses is selected on the company profile, the address child object (<ListOfAddress>) cannot be used for insert, update, or delete operations. Only association and dissociation is allowed for the shared address child object. To update a shared address, you must access the top-level shared address object.

Methods Called

Table 359 details the methods called by the Contact service.

Fields

Table 360 details the required and read-only fields for the contact object.

Table 361 details the pick map fields for the contact object.

Table 362 provides a list of the user key combinations for the contact object.

Table 363 details the picklists available for the contact object.

Table 364 details a number of contact object fields that you must not use for customer integrations.