Loading and Saving the Planning Context

The Load Planning Context command allows you to quickly load products within a specified volume in DPM.

Loading the Planning Context

Select Load Planning Context in the Process Context Builder toolbar.
The Load from Volume dialog box is displayed.

The Load from Volume dialog box presents the following options:

Load Existing Context Representation

If context information was previously saved on the loaded process or one of its parents (in the form of a rollup CGR), this option is enabled. When this option is selected, the rollup CGR is loaded into the DPM session under the Context Parts folder in the Product list.

This option is enabled only when the previously saved context data meets the following requirements:

For an MCM project, if the extended effectivity specified at the time of project selection (i.e., when the project is opened) matches the effectivity on the planning context.

For a non-MCM project, if the filters specified during the project selection match the effectivity on the planning context.

Load Existing Context Objects

If context information (either with or without a rollup CGR) was previously saved on the loaded process or one of its parents, this option is enabled. When this option is selected, all of the products in the saved context are created as child nodes of Context Parts in the Product list of the PPR tree. Each product has a graphical representation that is extracted from ENOVIA, and the position of each product is retrieved from the Manufacturing Hub.

Specify Volume and Load

This option is always enabled, and allows you to define a new volume using a bounding box. All of the products belonging to the specified volume are loaded into DPM.

When this option is selected, the Specify Volume Filter Criteria dialog box is displayed.

Here, a volume filter may be defined in the same manner as is described for Loading the Manufacturing Context.

Once the volume filter has been defined, click OK.
The Load Planning Context dialog box indicates the number of products that will be loaded as part of the planning context.

Click Yes to load all products child nodes of Context Parts in the Product list of the PPR tree. The graphical representation of each product is extracted from ENOVIA, and the position of each product is retrieved from the Manufacturing Hub.

Saving the Planning Context

With a planning context loaded (i.e., a list of products under the Context Parts node of the PPR tree), select File > Save or File > Save to Manufacturing Hub with new Detailing.

The following information is then saved back to the Manufacturing Hub:
Each context product identifier

Rollup CGR filename, if one has been generated.
Context information is saved as a detailing on the loaded process. The effectivity of the XML detailing will be the same as the effectivity specified when saving a regular detailing.

Notes

For an MCM project, the saved planning context will inherit the effectivity of the modification statement selected during the project load.
For a non-MCM project, the effectivity on the planning context will be that of the filters specified when the project was opened.
For a given filter set (for a non-MCM project) and for a given extended effectivity (for an MCM project) only one planning context can be saved. A process can have any number of planning contexts saved, however, for a given filter there can be only one planning context.

Modifying the Planning Context

Specific objects may be removed from the Context Parts folder in the PPR tree. When File > Save is then invoked, all modifications are saved to the Manufacturing Hub.

Notes

When context information is loaded in a DPM session, redefining a volume filter triggers the removal of the current Context Parts folder (and all its children), and then reloads the entire context based on the new volume.
When context information is loaded in a DPM session from a parent of the loaded process, a subsequent File > Save triggers the save of the context information on the loaded process.
In an MCM project, modifying an existing planning context and subsequently saving it results in a cut back of effectivity of the planning context. For example:

Create a planning context with a modification statement valid for {1-100}.
Save the planning context.
Re-open the planning context with extended effectivity {10-100} and a mod {10-100}.
Modify the planning context by selecting Load Existing Context Objects in the Load from Volume dialog box, and then remove some of the loaded objects.
Select File > Save to save the planning context.
The original planning context (saved in Step b) now has an extended effectivity of {1-9}. The new planning context (saved in Step e) has an extended effectivity {10-100}.

Limitations

Reloading the product planning context through volume filtering removes the existing context and creates a new context. A subsequent File > Save permanently deletes the old context, and the new context is saved for future use.
If any relations are created between processes and contextual products (such as process to product, visibility activity, or any other exposed activity in the Manufacturing Hub), a subsequent load causes the contextual products to be created in the Product tree (provided that the products are included in the selected BOM).
The planning context consists only of Product objects (not Resource objects).
The planning context will be loaded as a flat list of products (Context Parts). If the defined volume incorporates a component assembly that contains child products, the context loads the component assembly as an individual product and the children of the component assembly are loaded as siblings.
The creation of any applicative data (not exposed in the Manufacturing Hub) on the contextual products is not saved. Therefore, reloading the context will lose such applicative data.
Any changes to contextual products in DPM (such as modifying the position, modifying the attribute values or changing the product hierarchy) is not saved to the Manufacturing Hub.
If a planning context was loaded because it was defined on a parent process, any modification done to the context is saved on the currently loaded process. (The parent context is not overwritten.)
When defining the planning context via the volume filter, only the Fully In and Partly In filtering modes are supported.
The locking and user rights information are not valuated on the products that belong to the planning context. The Get edit information command does not display lock or user rights on the products that belong to the planning context.