The keys for the Projects Master Data set are defined to support OOTB allocation strategies and should not be altered. If additional keys are needed they can be added to the master data. **You should not unmaster a Master Data set.
|
Key
|
Field key is based on
|
Logic
|
|
Cost Source_Project Key
|
Project ID
|
Appended the text “CS Project_Key” && Project ID (If Time Tracking component is not installed this key is used to allocate from cost source to projects)
|
|
Labor_Project Key
|
User Defined
|
User defined key to create relationship between projects object and labor object
|
|
Project_Application Key
|
Application ID
|
IF Application ID is not BLANK then Append the text “Project_App” && Application ID else “Project_App_Null”
|
|
Project_BU Key
|
Business Unit Name, BU Key Metafield
|
IF Application ID is BLANK and Service ID is NOT BLANK then append the text “Project_Service && Service ID &&Project_Service Key Metafield else “Project_Service_null”
|
|
Project_Service Key
|
Service ID, Service Key Metafield
|
IF Application ID is BLANK and Service ID is BLANK and Business Unit Name is NOT BLANK then append the text “Project_BU && Business Unit Name &&Project_BU Key Metafield else “Project_BU_null”
|
|
Time Tracking_Project Key
|
Project ID
|
Append text “Time Tracking_Project” && Project ID
|
|
ITRT_Project Key
|
|
N/A key is no longer used
|
The keys for the Time Tracking Master Data set are all pre-defined and should not be altered.
|
Key
|
Field key is based on
|
Logic
|
|
Labor_Time Tracking Key
|
Labor ID
|
Append the text “Labor_Time Tracking” && Labor ID
|
|
Time Tracking_Project Key
|
Project ID
|
Append the text “Time Tracking_Project” && Project ID
|
|
Time Tracking_IT Tower Key
|
IT Resource Tower, IT Resource Sub-Tower
|
IF Project ID is BLANK then append the text “Time Tracking_IT Tower Key && IT Resource Tower && IT Resource Sub-tower else “Time Tracking_IT Tower_null”
|