AppendixAPackageContent-27snn.html
A package contains objects that are defined in the Oracle Primavera Portfolio Management (PPM) system. These objects include:
- Items and Portfolios
- Maps
- Scorecards
- Forms
- Dashboards
- Graphs
- Tabs
- Tables
- Categories
- Versions
- Value Lists
- Life Cycles
- Phases
- Users
- Groups
- Processes
- Modules Security
- Library Functions
- Imported Data Scheme
- Imported Phases Scheme
- Function INCLUDE file
- Indicators
Note: For definitions and descriptions of the PPM objects, refer to Portfolio Management Software for Technology Leaders. For information regarding library functions and imported data tables, refer to Defining an Imported Data Source in Working with Categories.
Packages cannot include data and portfolio specific information such as data from scorecard cells and form fields, portfolio phases and deliverables, goals, or investor map version information.
When designing a package, select all the objects you want included in the package. When an object is included in a package, the export wizard will automatically include all the derived objects.
These objects or items are automatically derived and included in the export package:
- Categories: When a category is added to a package, that category's drill-down dashboards, reference category, default graphs, values list, and any other categories used by its functions are automatically added as well.
- Scorecards: When a scorecard is added to a package, all of its included categories are automatically included, as well as referenced versions.
- Investor Maps: When an investor map is added to a package, all the categories it uses are included, including the additional categories, as well as referenced versions.
- Life Cycles: When a life cycle is added to a package, all of its phases and deliverables are automatically included.
- Dashboards: When a dashboard is added to a package, all of its graphs are automatically included.
- Graphs: When a graph is added to a package, all of its categories are automatically included.
- Users: When a user is added to a package, only the references to the user's default objects are included. If the default objects are found during the import process in the target database, then the references are resolved.
The packager behaves as follows with users:
- Users are exported without their password
- When importing users, new users get a blank password, existing users retain their old passwords.
- Processes: Only a processes folder can be selected during package export. That folder and its links and sub-folders will be included in the package. The objects the links referenced are NOT included. If these objects are found during the import process in the target database, then the links are resolved
- Items: When an item is added to a package, its life cycle is included.
- Portfolios: When a portfolio is added to a package, its life cycle is automatically included. If a query based portfolio is selected, all the categories associated with the query are included. If the query mentions a user, this user is also included.
- User Groups: When a user group is added to a package, its user groups are automatically included. If the Include user permissions and object owners checkbox is selected, its member users are also included.
- Forms: When a form is added to a package, all its tabs are automatically included. If the form contains default values, users may also be included.
- Tabs: When a tab is added to a package, all its associated categories are automatically included, as well as referenced versions.
Packages are XML files, with readable content that can be edited in any text editor. In addition to the included objects, each package contains administrative information, such as:
- The PPM software release version with which the package was created.
- The date the package was created.
- The name of the user who created the package.
- A description of the package.
- If the package is a solution module, the name of the module and origin ID number and organization name is included.