CostCenterPhaseAmounts

Contains numeric values associated with budgetary data.

Properties

Name	Data Type	Description
CostCenter	`CostCenter`	Refer to data type’s documentation for further information
Phase	`Phase`	Refer to data type’s documentation for further information
MTDBudget	`Double`	Budget amount as measured from the beginning of the current month to the end of the current month
MTDActual	`Double`	Actual amount as measured from the beginning of the current month to the end of the current month
YTDBudget	`Double`	Budget amount as measured from the beginning of the current year to the end of the current month
YTDActual	`Double`	Actual amount as measured from the beginning of the current year to the end of the current month
PrevYTDActual	`Double`	Actual amount as measured from the beginning of the previous year to the end of the month in the previous year that corresponds to the current month
YTDHours	`Double`	Hours as measured from the beginning of the current year to the end of the current month
PTDActual	`Double`	Actual amount as measured with no lower bound to the end of the current month
AnnualBudget	`Double`	Budget amount as measured from the beginning of the current year to the end of the current year
PrevTotalActual	`Double`	Actual amount as measured from the beginning of the previous year to the end of the previous year
TotalActual	`Double`	Actual amount as measured from the beginning of the current year to the end of the current year
TotalBudget	`Double`	Budget amount as measured with no bounds
YTDMetric	`Double`	Metric amount as measured from the beginning of the current year to the end of the current month

Remarks

This object inherits properties from a common abstract base class. As such, not all properties exposed may be applicable.

The Phase property references the common phase model but may be returned as one of two specialized types depending on endpoint context:

Phase (Facility) for facility budgeting endpoints
Phase (Farming) for orchard budgeting endpoints

For historical reasons, the properties TotalActual and TotalBudget share a similar naming convention even though their temporal duration is not synonymous.

Budgetary values are exposed using binary floating point numerics. The justification for utilization of double over decimal is:

Values generally become approximations due to dynamic allocation of costs among accounting units
Binary rounding errors present in totals are not a concern
The long series of numeric calculations required to dynamically produce budgetary data benefit from the speed of double over decimal