Siebel Correspondence, Proposals, and Presentations Guide > Correspondence >

Configuring Additional Merge Fields For Correspondence Templates


The exported data is taken from two places:

  • If the correspondence was created from a view based on service requests, the data is taken from the Service Request Recipient business component.
  • If the correspondence was created from the Correspondence list view, or from a view not based on service requests (such as the Opportunities screen), the data is taken from the Recipients business component.

New fields in the Recipients business component are restricted to those based on columns in the S_CONTACT table or those obtained through join relationships. Joins can be added for tables that have a master-detail relationship with S_CONTACT, where S_CONTACT is the detail table. You need to add the join to the Recipients business component.

New fields in the Service Request Recipient business component are restricted to those based on columns in the S_CONTACT table, the S_SRV_REQ table, or columns available through joins to these tables.

Table 4 summarizes the contents of the two business components and the contexts in which they are used. For more information on adding fields, see Developing and Deploying Siebel eBusiness Applications and Configuring Siebel Business Applications.

Table 4. Summary of Merge Fields Sources and Uses
Source Business Component
Source Tables
Used In

Recipients

  • S_CONTACT
  • Joins with tables that have a master-detail relationship with S_CONTACT (with S_CONTACT as the detail table).

Correspondence created:

  • Directly in the Correspondence List View.
  • From any view not based on service requests.

Service Request Recipient

  • S_CONTACT
  • S_SRV_REQ
  • Joins with tables that have a master-detail relationship with one of these two (with S_CONTACT or S_SRV_REQ as the detail table).

Correspondence created from views based on service requests.

To configure an additional merge field

  1. In Siebel Tools, add the new field to either the Recipients business component or the Service Request Recipient business component.

    CAUTION:  Make sure that the field's database column name does not exceed 38 characters. (This is because Microsoft Word cannot handle merge fields with long names.)

  2. Add the name of the new field to the business component's user property called Export Field #, where # is an integer.

    If necessary, you can create additional user properties by incrementing the integer.

  3. Update the SIEBEL.HTML file (Creating and Updating the SIEBEL.HTML File) before creating a correspondence template containing the new field.

NOTE:  You can have up to 63 merge fields in the SIEBEL.HTML file; Microsoft Word does not display fields beyond this limit.

Siebel Correspondence, Proposals, and Presentations Guide