Integration Platform Technologies: Siebel eBusiness Application Integration Volume ll > External Business Components > Configuring External Business Components >

Mapping External Columns to Siebel System Fields

Once the external business component has been defined, you must map the Siebel system fields to the corresponding external table column. Starting with Siebel 7.7, System Field mapping is accomplished at the column definition rather than using business component user properties. You need to specify the System Field Mapping column attribute if you wish to map a Siebel system field to a column.

NOTE:  At a minimum, the Id field must be mapped to a unique column defined in the external table and in the Table object definition, which is specified in the business component's Table property.

By default, Siebel system fields will be not be included in the generated SQL for external tables.

System Field Mapping is used to specify the mapping between table columns and Siebel internal fields.

Following is a list of the Siebel internal fields that may be mapped to external table columns:

• Conflict Id. Optional.
• Created. Optional. Datetime corresponding to when the record was created.
• Created By. Optional. String containing the user name of the person and the system that created the records.
• Extension Parent Id. Optional.
• Mod Id. Optional.
• Non-system. Optional.
• Updated. Optional. Datetime corresponding to when the record was last updated.
• Updated By. Optional. String containing the user name of the person and system that last updated the record.
• Id. Mandatory. The single column unique identifier of the record. A column in the external table must be mapped to the Id field.

NOTE:  The System Field Mapping property should be used in conjunction with external tables only.