Default field mappings for OpenText PPM and ALM

This topic introduces the default field mappings between PPM and ALM.

Default field mappings for ALM defects

The table below describes the default defect mappings that can be modified for the integration between the Defects Module in ALM and the ALM - Defect Template with Quality Center Integration request type in OpenText PPM. To modify the default mappings, see Configure field mappings.

Table 6-10. Default defect mappings you can modify
ALM Field Name, Database ID, and Field Type	OpenText PPM Field Name, Database ID ^a, and Field Type	Control
Detected on Date BG_DETECTION_DATE Date	Created On CREATION_DATE Date	PPM
Summary BG_SUMMARY Text (255)	Summary DESCRIPTION Text (200)	BIDIRECTIONAL
Severity BG_SEVERITY Enumeration	Severity SEVERITY Drop-down list	BIDIRECTIONAL
Detected By BG_DETECTED_BY Quality Center users list	Created by CREATED_BY Text (40) Note: If your ALM runs in SSO mode, do not use the default PPM field to map to the Detected By BG_DETECTED_BY field in ALM in order to prevent synchronization errors. Instead, create a new field mapping. For details, see Create a new field mapping.	QC/ALM
Priority BG_PRIORITY Enumeration	Defect Priority DEFECT_PRIORITY_CODE Drop-down list	PPM
Actual Fix Time BG_ACTUAL_FIX_TIME Date	Actual Fix Time (days) ACTUAL_FIX_TIME Date	BIDIRECTIONAL
Estimated Fix Time BG_ESTIMATED_FIX_TIME Number	Estimated Fix Time (days) ESTIMATED_FIX_TIME Numeric Text (10 digits)	BIDIRECTIONAL
Reproducible BG_REPRODUCIBLE Y/N	Reproducible REPRODUCIBLE Y/N	QC/ALM
Detected in Version BG_DETECTION_VERSION List	Detected in Version DETECTION_VERSION Text (40)	QC/ALM
Closed in Version BG_CLOSING_VERSION List	Closed in Version CLOSING_VERSION Text (40)	QC/ALM
Description BG_DESCRIPTION Memo	Detailed Description DEFECT_DESCRIPTION Text (1800)	BIDIRECTIONAL
Assigned To RQ_USER_XX^b User list	Quality Center Assigned To User KNTA_QC_ASSIGNED_TO	QC/ALM
Closing Date BG_CLOSING_DATE Date	Closed on CLOSING_DATE Date	QC/ALM
a. The listed OpenText PPM database IDs are the same as in the PPM Workbench. The exact database IDs are displayed by the integration tool. b. The ALM fields with the database ID of RQ_USER_XX are user fields that are added to ALM when using the integration tool or running the script to enable a project. The value of XX is determined when the user field is added to ALM.

Default field mappings for ALM requirements

The table below describes the default requirement mappings that can be modified for the integration between the Requirements Module in Quality Center and the ALM - Request for Change (RFC) request type or the ALM - Release Management request type in OpenText PPM. To modify the default mappings, see Configure field mappings.

Table 6-11. Default requirement mappings you can modify
ALM Field Name, Database ID, and Field Type	OpenText PPM Field Name, Database ID ^a, and Field Type	Control
Name RQ_REQ_NAME Text (255)	RFC Summary DESCRIPTION Text (200)	BIDIRECTIONAL
Description RQ_USER_XX^b Memo	RFC Description RFC_DESCRIPTION Text (1800)	BIDIRECTIONAL
Comments DEV-COMMENTS Text (255)	Effect of no change RFC_EFFECT_NO_CHANGE Text Area - 1800	BIDIRECTIONAL
a. The listed OpenText PPM database IDs are the same as in the PPM Workbench. The exact database IDs are displayed by the integration tool. b. The ALM fields with the database ID of RQ_USER_XX are user fields that are added to ALM when using the integration tool to enable a project. The value of XX is determined when the user field is added to ALM.