Please also check the pages for the ENOVIA Manufacturing Hub for related topics.
Avoid object under CCZ to have multiple CCZ Owners |
While working with CCZ, special care should be taken so that, an object should not have multiple CCZ owners. This situation, is known to cause downstream problems with versioning. An example on how this can occur is explained below. Consider the following case. 1. A Workplan (WP1) has a child Operation (OP1). 2. Now there is another Workplan (WP2) which is a sibling of WP1. 3. For the relation between Workplan and Operation, Workplan is the CCZ owner. 4. Now OP1 is linked to WP2 5. In this case, OP1 has two CCZ owners - WP1 and WP2. This type of scenario is known to have problems. Suggestion is not to link, but copy and paste by which new component is created under WP2. |
None |
|
Modification to PES : PES_DELMIA_V5R19_Manufacturing Hub Infrastructure_ENOVIA Manufacturing Hub_R19GSI238_CCZLimitedDepth. (Page 6 – Programming Interface) |
Reason: If DeleteVersion
(Delete Version Forced calls this API internally) is called on CCZ
Member which is at Version 2 (latest) there will be no way to get
Version 1 (previous version). To get the Version 1
back user has to again delete (DeleteVersionForced
) the latest versions till parent
(Similar to DeleteVersionForced when called on CCZ Owner). The other reason is it
is not possible to check out (create new version) CCZ Members,
similarly deletion of version for CCZ Member is also not possible. User
could use delete component flat instead (this cuts back effectivity and
does not remove component from database) |
||||||
Manufacturing Change Management | From R19 onwards, Deep Delete button is disabled for components created and versioned under MCM. Since Deep Delete is not supported for MCM objects. |