The following Primavera Cloud business objects are available in the Data Dictionary menu of the Gateway user interface. Select a specific business object to review a detailed list of fields supported for that business object.
Business Object | Description |
|---|---|
Activity | An activity is a unit of work performed during the course of a project. |
ActivityCode | Activity codes are user-defined codes to classify and categorize activities across the enterprise. |
ActivityCodeType | Activity code types provide a way of classifying activity codes. Activity codes are user-defined codes to classify and categorize activities across the enterprise. |
ActivityRisk | The activity risk object stores the relationship between a single Activity and a single Risk. |
Calendar | Calendars defined the available work hours in each calendar day, and includes global and resource types. |
CBSSegment | CBS Segment Fields |
CBSTemplate | CBS Template Fields |
CBSTemplateCode | CBS TemplateCode Fields |
CostCategory | CostCategory Fields |
CostSheetWorkspaceTotalCostRow | CostSheetWorkspaceTotalCostRow |
CostSheetWorkspaceTotalItem | CostSheetWorkspaceTotalItem |
Currency | Currencies are the monetary units used to store costs for all projects in the database. |
EPS | To use this object, please contact support. This object will be removed in a future release. |
ExchangeRate | ExchangeRate Fields |
Location | The location is used to store address information including latitude and longitude. Locations can be assigned to resources, projects and/or activities. |
Project | A project is a temporary endeavor undertaken to create a unique product, service, or result. Projects usually contain a work breakdown structure (WBS) and activities. |
ProjectBudget | ProjectBudget Fields |
ProjectBudgetChange | ProjectBudgetChange Fields |
ProjectBudgetTransfer | ProjectBudgetTransfer Fields |
ProjectCode | Project codes are user-defined codes to classify and categorize projects across the enterprise. |
ProjectCodeType | Project code types provide a way of classifying project codes. Project codes are user-defined codes to classify and categorize projects across the enterprise. |
Relationship | A relationship defines how an activity relates to the start or finish of another activity or assignment. These relationships, which form the logic of the project network, are used together with activity durations to determine schedule dates. |
Resource | Resources include labor, nonlabor, and materials that are used for activities across all projects. |
ResourceAssignment | Resource assignments track the work of resources or roles that are performing various activities. |
ResourceCode | Resource codes are user-defined codes to classify and categorize resources across the enterprise. |
ResourceCodeType | Resource code types provide a way of classifying Resource codes. Resource codes are user defined codes to classify and categorize resources across the enterprise |
ResourceRate | Resource rates provide a way of specifying multiple resource prices and maximum units per time values that vary over time. |
ResourceRoleAssignment | ResourceRoleAssignment Fields |
Risk | The risk object represents a probabilistic event or condition which if it occurs has an impact on the project. |
RiskImpact | The risk impact object stores the pre-response qualitative value assigned to a risk for each of the risk thresholds. |
RiskMatrix | The risk matrix object contains the name and description of each probability and impact diagram (PID). The Risk Matrix is then used to qualitatively assess each risk and assign a score. |
RiskMatrixScore | The risk matrix score object stores the score values from the probability and impact diagram (PID) of the risk score matrix. |
RiskMatrixThreshold | The risk matrix threshold object creates a relationship between a RiskThreshold object and a RiskMatrix object. This allows a single RiskThreshold object to be associated with multiple RiskMatrix objects. |
RiskOverrideCost | The risk override object allows for cost overrides on a risk. |
RiskOverrideOther | The risk override object allows for Probability and Schedule overrides on a risk. |
RiskResponseAction | The risk response action object contains the detailed steps that need to occur to complete the risk response plan. Multiple actions can be associated with one response plan and each action can be linked to an activity in the project. |
RiskResponseActionImpact | The risk response action impact object is a post-risk response action qualitative value that is assigned to a risk for each of the risk thresholds. |
RiskResponsePlan | The risk response plan object communicates how the project team plans to address the identified risk. |
RiskThreshold | The risk threshold object contains the name, description, and type of each risk threshold. Risk thresholds provide a mechanism for setting up the criteria that is used to assess the risk. |
RiskThresholdLevel | The risk threshold level object stores the level information (e.g. Low, Medium, High) for each risk threshold. |
Role | Roles are project personnel job titles or skills, such as mechanical engineer, inspector, or carpenter. They represent a type of resource with a certain level of proficiency rather than a specific individual |
RoleRate | Role rates provide a way to specify multiple role prices and maximum units per time values that vary over time. |
UDFType | User-defined fields (UDFs) enable users to add custom fields and values to the project database. |
UnitOfMeasure | UnitOfMeasure Fields |
WBS | The project work breakdown structure (WBS) is a hierarchical arrangement of the products and services produced during and by a project. Each element of a WBS may contain more-detailed WBS elements, activities, or both. WBS are hierarchical objects. |
WBSSpread | Project phase/curve/spread data for the project cash flow. |
WorkManagerTask | Tasks make it possible to describe and report progress for activity work at a granular level by breaking an activity into its component parts. |
Workspace | The workspace object contains the information on the workspace hierarchy. |