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

Conversion Notes

  • Last UpdatedDec 18, 2018
  • 1 minute read
  • The initial values for the non-nullable "created_by" fields added to the item_prod and item_cons should be gotten from the then-current values of last_edit_at from the same table.

  • The user-defined type "notes" will be changed from LONG to CLOB in Oracle.

  • Create a record in the lot table for every distinct combination of item_id and lot_no in the lot_attr and item_inv tables (where lot_no is not null).

  • Update all "severity" values > 4 in error_log to 1. 5, 10 through 13, and 100 are no longer used.

  • Change pred_msg.id to its string equivalent.

  • The following tables and their primary keys are in the PRIMARY filegroup in V. 3.1 and should be moved to FI_DATA_2 for V. 3.2: spc_char_std_oper_link, std_oper_attr (except for its textimage, which is already on FI_DATA_2), std_oper_ent_spec, std_oper_spec_ver, and std_oper_step_file. Also, IX_std_oper_step is in PRIMARY in V. 3.1 as well and should instead be in FI_INDEX_2. Ent_logon and its clustered index CIX_ent_logon_ent_user are in FI_INDEX_2 in V. 3.1 and should be moved to FI_DATA_2 for V. 3.2, and oper_prod_rule and its primary key are in FI_INDEX in V. 3.1 and should instead be in FI_DATA.

  • Any null job_priority in the job table should be set to the default of 1.

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