Deltek Open Plan Help

Using the Help Search
Using the Help Search
  • Phrase:Returns all topics that contain the exact phrase in the search criteria. Use quotation marks around the phrase.
    Ex."system administration"
  • And:Returns all topics that contain all the words in the search criteria, in any combination. Insert a plus sign between all words in the search criteria.
    Ex.system + administration
  • Or:Returns all topics with any combination of words in the search criteria. This is the default.
    Ex.system administration
For more information:Searching Online Help

P6 Code Fields

Open Plan imports the entire WBS code hierarchy when it imports a project.

The top-level P6 WBS (usually the project name in P6) is stripped out. A code hierarchy for P6 activity codes other than the WBS hierarchy may be implicitly built in Open Plan by assigning a P6 activity user code field to an Open Plan code field.

The WBS Code field in P6 is called the Code ID field in Open Plan, and the WBS Code Name in P6 is called the Code Description in Open Plan. By default, the P6 WBS code is stored at code index #1 in Open Plan; however, you can change the WBS code index number using the Open Plan API. For more information, see Assigning the P6 WBS Hierarchy to a User-Specified Index.

There is no limit to the number of levels that you can create in a P6 code hierarchy. The type of Open Plan fields to which you assign P6 code fields determines how Open Plan treats the P6 code hierarchy.

Assigning a P6 Code Field to an Open Plan Code Field

During an import, if you assign a P6 code field to an Open Plan code field, Open Plan preserves the code hierarchy. Whenever Open Plan finds a value in the imported data that is mapped to an Open Plan code, Open Plan imports that value and its DIRECT parent hierarchy to the Open Plan code file. Direct means parents, grand-parents, great-grand-parents, and so on, not uncles or aunts. In this way, Open Plan dynamically creates the code hierarchy while only importing the values that are being used in the project.

Assigning a P6 Code Field to an Open Plan User (Non-Code) Field

During an import, if you assign a P6 code field to an Open Plan user field, no code hierarchy is created. Instead, Open Plan uses the format <Parents>.Child. For example, if you have the following WBS code hierarchy in P6:

  • PRJ_OR_USR_001
  • PRJ_OR-CHLD
  • PRJ_OR_GCHLD

Open Plan lists the WBS codes as follows:

  • PRJ_OR_USR_001
  • PRJ_OR_USR_001.PRJ_OR-CHLD
  • PRJ_OR_USR_001.PRJ_OR-CHLD.PRJ_OR_GCHLD

Assigning a P6 Non-Code Field to an Open Plan Code Field

If you assign a P6 non-code field to an Open Plan code field, the P6 values are added to the appropriate Open Plan code file, but the hierarchical structure is flat (that is, all added elements are top-level codes).

Activity Codes

Open Plan matches up activity codes, other than the main WBS code, based on the code ID (for example, “Code 1”) instead of the P6 numeric object ID (for example, "1067") associated with the code.

Related Topic