Part Planner general functionality > Displaying information

Recovering a manufacturing session

If you are working in a four-tier environment and a server or network failure or time-out occurs, Teamcenter reassigns the client session to another server. It also attempts to use the client cache to reconstruct the run-time configured structure views and minimize loss of information.

If the server connection is lost, Teamcenter displays two dialog boxes:

Server Reassigned Informs you that the server connection was lost. Click OK to dismiss the dialog box.
BOM Session Recovery Informs you that a BOM recovery session has started. Click OK to dismiss the dialog box.

Additional error messages may appear, depending on the state of the recovered session.

The primary structure views are recovered and the secondary views have one of the following states:

Where possible, the view remains open.
The view stays open, but its content is cleared.
The view is closed.

The following limitations apply to BOM session recovery:

BOM sessions are recovered only for the four-tier rich client.
Teamcenter recovers the BOM session to a usable status, but not necessarily the exact state before failure or time-out occurred. For example, if you expanded multiple levels of the structure, Teamcenter recovers only the first-level expansion of the structure.
The recovery may take an appreciable time to complete, depending on the quantity of data Teamcenter must process.
Unsaved changes are lost. For example, if you modified the effectivity date on a revision rule but had not yet saved the change, the changes are not recovered.
If you copied BOM lines to the clipboard before the server terminated, Teamcenter removes them.
If the server terminated after encountering bad data during expansion, the recovery process may expand the same structure and encounter the same bad data. You must resolve these data issues in the database manually.
If the server terminated due to memory shortage when expanding the first level of the structure, the recovery process may expand the same structure and encounter the same memory shortage. You must resolve such memory issues separately.
The Report view is not recovered.
The knowledge of which variant rule is in effect at the time of the crash is not recovered.