Purpose
[FACT_PROJ_ACTIVITY_INFO_OL] unique based on ACTIVITY_SEQ, CONTROL_CATEGORY_KEY
This table plans to be unique for ACTIVITY_SEQ only
Use Case
Owner: Martyn Cole
Typical Use Case: Provide details for ACTIVITY_SEQ and Sub Project ID
Style: Dimension, Dimension i.e. Single row per ACTIVITY_SEQ
Source
DIM_ACTIVITY_OLKey Parameters
Company
Project
Customer
ActivitySeq
Sample Exec
EXEC get.myView @dataMart = 'Project', @viewName = 'ActivityDetails', @token = '<myToken>', @version = '<202404>'Response
proj.COMPANY,
src.PROJECT_ID,
proj.CUSTOMER_ID,
src.ACTIVITY_SEQ,
SEQ
ACTIVITY_NO,
ACTIVITY_DESCRIPTION,
SUB_PROJECT_ID,
Dates
CONVERT(varchar(10),try_parse([EARLY_START] as date),23) as [EARLY_START],
CONVERT(varchar(10),try_parse([EARLY_FINISH] as date),23) as [EARLY_FINISH],
CONVERT(varchar(10),try_parse(src.[ACTUAL_START] as date),23) as [ACTUAL_START],
CONVERT(varchar(10),try_parse(src.[ACTUAL_FINISH] as date),23) as [ACTUAL_FINISH]
2 thoughts on “Project.ActivityDetails”