cancel
Showing results for 
Search instead for 
Did you mean: 

Project was released on PD Level, but networks assigned were not released

0 Kudos

Hi,

This is about the releasing effect on projects.

Scenario:

Project was created using an "unreleased" standard project thus the message Standard (WBS Code) has not been released appears.

After the creation, the status of the object are as follows:

WBS - CRTD

Networks - ACAS CRTD MANC NMAT PRC RELR


Now, when being released by topmost level (Project Definition), I assume that all objects, including networks will be released. However, these are the object statuses after release:

WBS - REL

Networks - ACAS CRTD MANC NMAT PRC RELR


As you can see, the network status was not changed to REL


What do you think is the root cause of this inconsistency? Is this a program error?

Accepted Solutions (0)

Answers (1)

Answers (1)

kenmelching
Active Contributor
0 Kudos

Are the network headers assigned to a WBS or Project Definition? The activities can be assigned without the header assigned. Please post a screenshot.

0 Kudos

Hi Ken,

Included on this screenshot is the change document. REL status on Network was 25.01.2018 since they manually released it after we found out that it doesn't adopt the status of the upper objects.

Would you know what caused this?

0 Kudos

Hi Ken,

Also to add, you might ask why network has RELR, the project was created using a standard template. During creation, we encountered this message.

Standard WBS XXXXX-XXX has not been released.

This is normal since we don't want to automatically released it upon creation.

kenmelching
Active Contributor
0 Kudos

I don't think releasing the Standard objects will automatically release the operative project when it is created.