Add WBS from Template

What a planner means

Add WBS from Template is Context (or Row Actions) Add WBS from Template of a project or WBS on the EPPM Activities page. The how-to Oracle names is Creating a WBS from a Template. The dialogs Oracle names are Select WBS then Copy WBS Options. "The new WBS element is created and saved automatically as a child of the selected WBS element." It is a command. It is not stored data. It is not Copy WBS, not Cut WBS, not Delete WBS, not Add Sibling WBS / Add Child WBS, not Professional Edit > Add, not Creating a project from a template, not Copy Project, not Copy Activity, not Dissolve, not a WBS Summary activity, and not Fill Down.

Oracle Creating a WBS from a Template (EPPM; G48897):

1. "On the Navigation Menu, expand Projects and click Activities."
2. "In the Activity Table, select a project or WBS element and select Context then select Add WBS from Template."
3. "In the Select WBS dialog box, select a WBS from the list of templates and click Select."
4. "In the Copy WBS Options dialog box, select the data items you want to include with the pasted WBS element and click OK."

Opening sentence Oracle printed: "You can add a predefined WBS element from a template to a project."

Tips Oracle printed:

• "The application automatically assigns the WBS element a name based upon the selected WBS."
• "The new WBS element is created and saved automatically as a child of the selected WBS element."

A same-numbered EPPM page (F88966) prints Row Actions then Add WBS from Template for the same Select WBS / Copy WBS Options steps. Oracle printed both Context and Row Actions. Do not collapse them.

Quote list of templates as printed. About Project Templates also says "specific WBS branches and their activities can be copied from projects or templates and inserted wherever you need them." Do not invent that Select WBS lists only project templates, or that it also lists open-project WBS. Oracle printed both sentences. Do not invent a reconciliation.

Copy WBS Options — the how-to opens it and says "select the data items you want to include with the pasted WBS element." Oracle printed no checkbox catalog on that how-to. The EPPM dialog page Oracle fetched (Copy Project Options Dialog Box of the EPS Page or Copy WBS Options Dialog Box of the Activities Page) Getting Here is Context Copy / Paste, not Add WBS from Template. Do not invent that this command shows every checkbox on that page. Do not copy Professional Copy WBS Options (Notebook, WBS Milestones, WPs & Docs, Activities) onto this command. Do not invent a Template Options dialog. Do not invent an always-copied field catalog.

Copy WBS is a different command. Professional Project > WBS → Edit > Copy / Paste plus Copy WBS Options. EPPM Context Copy of a WBS already in the open project. That is not Add WBS from Template. See Copy WBS.

Add Sibling WBS / Add Child WBS are different commands. Oracle Creating a WBS: Context → Add Sibling WBS / Add Child WBS / Add WBS from Template. The first two are new empty nodes. That page also says Click Save. This how-to says created and saved automatically. Do not collapse them. Do not copy the Creating a WBS name example (Business Project 1.5 → 1.6) onto this command.

Professional Edit > Add is a different command. Oracle Add a WBS element: Project, WBS → Edit, Add. "The new WBS element is indented one level under the selected WBS element." That how-to does not open Select WBS or Copy WBS Options.

Creating a project from a template is a different command. Oracle Creating Projects from Existing Projects or Templates: EPS page → Context Add Project → copy from a project or template. That creates a project, not a child WBS on the Activities page.

Cut WBS / Delete WBS are different commands. See Cut WBS and Delete WBS.

WBS Summary is not this command. WBS Summary is a TASK activity type. See P6 Activity Types (Six) — Not MSP Task Type and P6 WBS.

Professional vs EPPM

EPPM web — the how-to above. Working with WBS Elements: "In addition to creating a brand new WBS element, you can create one from a template, or by copying a current WBS element and modifying the content." Add/copy/cut/edit/delete of WBS requires the view Level 1 Field set to WBS, and the Add/Edit/Delete WBS Except Costs/Financials project privilege. Working with Project Templates: "If you select to copy a project or template, you can copy the entire template, or you might insert only the WBS portion into a project."

Professional — Defining the WBS names Add a WBS element, Copy and paste, Cut and paste, Delete. It does not name Creating a WBS from a Template or a menu Add WBS from Template. Do not invent one. Professional Select WBS is a different dialog: "assign a work breakdown structure (WBS) element to an activity, threshold or issue" / "specify the WBS element to which you want to add a project's WBS." That is not this command. When connected to a P6 EPPM database, Copy an EPS node or project: "When you copy an EPS node, any template projects in that EPS are copied even though you cannot see them in P6 Professional." That is Copy Project, not this command.

Primavera Cloud — terminology map: P6 Add WBS from Template → Cloud Add WBS from Project. That is a rename table, not this EPPM command.

XER

None. Oracle’s project XER map TOC has no ADDWBSFROMTEMPLATE / COPYWBSFROMTEMPLATE / WBSTEMPLATE table. After the command you see another PROJWBS (and any TASK rows that came with the included data). Do not treat a new PROJWBS row as “the planner used Add WBS from Template.” A Viewer parse of one XER cannot reconstruct whether the planner used Add WBS from Template, Copy WBS, typed a new WBS, or imported.

Microsoft Project

Desktop Project has no WBS table and no Add WBS from Template. Microsoft Create a new project from another project or template / Create a project in Project desktop: File > New from a template creates a new project. Microsoft Save a project file as a template saves a .mpt. Microsoft Organizer: "You can’t copy task information using the Organizer." "If you want specific tasks to be part of each project, save the project file as a regular template." Microsoft Copy of a summary task copies subtasks. They are not the same command. Do not invent an analog named insert WBS from template. Do not claim MPXJ writes a real MPP.

Don't

• Treat Add WBS from Template as Copy WBS, Cut WBS, Delete WBS, Add Sibling / Add Child, Professional Edit > Add, Creating a project from a template, Copy Project, Copy Activity, Dissolve, a WBS Summary activity, or Fill Down.
• Invent a Professional menu named Add WBS from Template, or treat Professional Edit > Copy / Edit > Add as this command.
• Invent Copy WBS Options checkboxes for this path, or copy Professional Notebook / WBS Milestones / WPs & Docs / Activities onto it.
• Copy the EPPM Context Copy/Paste Getting Here checkbox catalog onto this command as verified for this path.
• Collapse Context and Row Actions into one invented control.
• Collapse Creating a WBS Click Save / Business Project 1.5 → 1.6 onto this auto-save / "name based upon the selected WBS" tip.
• Invent that Select WBS lists only project templates, or that it also lists open-project WBS.
• Invent an ADDWBSFROMTEMPLATE / COPYWBSFROMTEMPLATE / WBSTEMPLATE XER table, or treat a new PROJWBS row as “the planner used Add WBS from Template.”
• Claim a Viewer reconstructed that the planner last used Add WBS from Template from an XER.
• Map P6 Add WBS from Template to MSP File > New from a template / Organizer / Copy of a summary as the same command.
• Claim MPXJ writes a real MPP.