Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ Manufacturing Execution System 2023 R2

Considerations regarding inherited raw reason codes

Considerations regarding inherited raw reason codes

  • Last UpdatedNov 04, 2024
  • 1 minute read

When planning your UCO templates and instances, it is important to understand raw reason code inheritance.

Raw reason code definitions are inherently locked at the level at which they are created. Therefore, when an UCO instance (child) inherits another object’s raw reason code list and allowable reasons, you cannot alter the existing parents' raw reason code list or allowable reasons by editing the child UCO instance. However, you can add new raw reason codes to the child instance that are interleaved between the parent raw reason codes. You can also add new allowable reasons.

Changing a parent UCO’s raw reason codes or allowable reasons will invalidate all derived object instances. You will have to run the Entity Model Builder and redeploy the object to cascade the changed raw reason codes list to its derived object instances.

TitleResults for “How to create a CRG?”Also Available in