The following business objects are supported in Gateway format:
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 according to the organization's and project's needs. |
ActivityCodeType | Activity code types provide a way of classifying activity codes. Activity codes are user-defined codes to classify and categorize activities according to the organization's and project's needs. |
ActivityExpense | Activity expenses are non-resource costs associated with a project and assigned to a project's activities. They are typically one-time expenditures for non-reusable items. |
ActivityRisk | The activity risk object stores the relationship between a single activity and a single risk. |
BaselineType | BaselineType fields |
Business Unit | Organization hierarchy - Business Unit |
Calendar | Calendars defined the available work hours in each calendar day, and includes global and resource types. |
CBS | CBS business object |
CBSDurationSummary | CBSDurationSummary business object |
CBSExpenseSpread | Summarized spread data per CBS per expense category |
CBSResourceSpread | Summarized spread data per CBS per resource assignment |
CostAccount | Cost accounts contain the organization's cost account IDs. Available across all projects, they support tracking of costs and earned value based on the organization's cost account IDs. Cost accounts are hierarchical objects. |
Currency | Currency fields |
EPS | EPS |
ExpenseCategory | Expense categories are used to categorize project expenses. They are used for standardizing expenses and for rolling up expenses across projects. |
FinancialPeriod | Financial periods are used to provide accurate display and reporting of actual units and costs. Financial periods may not overlap each other and do not have to be contiguous. |
Location | The location is used to store address information including latitude and longitude. Locations can be assigned to resources, projects and/or activities. |
NotebookTopic | Notebook topics are used to categorize notes on EPS, project, WBS,and activity objects. |
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. |
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. |
ProjectFinance | EnterpriseTrack Project Finance. |
ProjectFinanceElement | EnterpriseTrack Project Finance Element. |
ProjectFinanceSnapshot | EnterpriseTrack Project Finance Snapshot. |
ProjectResource | Primavera's resource planning feature allows you to do high-level project planning for future project or project that does not require resource assignments at the activity level. |
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 all projects. |
ResourceCodeType | Resource Code Types provide a way of classifying resource codes. Resource codes areuser-defined codes to classify and categorize resources across all projects. |
ResourceRate | Resource rates provide a way of specifying multiple resource prices and maximum units per time values that vary over time. |
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. |
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 enable you to select a predefined price per unit for cost calculating when assigning the role to an activity. |
UDFType | User-defined fields (UDFs) enable users to add custom fields and values to the project database. |
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. |
WBSCategory | As their name implies, WBS categories are used to categorize WBS elements. They are defined globally. |
WBSExpenseSpread | Expense spread data per WBS per ExpenseCategory |
WBSResourceSpread | Spread data per WBS per Resource |
WBSSpread | Summarized spread data per WBS |
Legal Notices
Copyright © 2013, 2015,
Oracle and/or its affiliates. All rights reserved.
Last Published Monday, March 30, 2015