Go to primary content
Oracle Agile Engineering Data Management Upgrade Tool
Release e6.2.0.0
E52564-02
  Go To Table Of Contents
Contents

Previous
Previous
 
Next
Next
 

4 Additional Information

Following special handling modules are integrated into the Upgrade Tool. Therefore, no additional actions are required to migrate the involved content. The steps described below are already integrated in the upgrade process and will be executed automatically.

4.1 Browser Upgrade

With Agile e6.0 release a new browser was introduced. It is based on new database tables having a prefix T_EXP_*.

During the upgrade, standard content of these new tables is inserted. In addition, non-standard entries from the "old" browser are migrated.

4.2 Cleanup BVB_ARTIKEL

Some inconsistencies in the existing item data structure are eliminated during this specific upgrade step. Here a list of executed activities:

  • Redundant BVB_ARTIKEL entries are dropped.

  • All BVB_ARTIKEL records without corresponding T_MASTER_DAT entries are deleted.

  • Missing BVB_ARTIKEL records are inserted.

  • Missing values of T_MASTER_DAT.UNIT are inserted into BVB_MASSEH.

4.3 STA_LUT

For each entry in T_CHK_STA a valid reference to T_STA_LUT is established with values in T_CHK_STA.EDB_STA_REF. Additionally, EDB_LEVEL is filled within the table T_STA_LUT.


Note:

The values of the table T_STA_LUT must be reviewed after the customizing upgrade.

4.4 Project References in Processes

There is a known problem within the project workflow in Agile e6.0. In case of creating a relation between a process and a project, which has several versions, several entries are shown in the list, because the PROJ_ID (project name shortcut) is not unique over the stored versions. For this reason, a new database field is added: T_PRC_DAT.EDB_PRO_REF.

If necessary, this field is filled with values during the upgrade step upg08_postaction.

4.5 BVB_ARTMEH Upgrade

During this step, an upgrade of BVB_ARTMEH* tables is performed. SQL script artmeh_1.sql and artmeh_2.sql is executed within the upg08_postaction step.

4.6 Favorites Upgrade

The Upgrade Tool inserts several data items into browser tables to make favorites and stored queries visible in the Agile e6 client browser window.

4.7 Classification

  • Overview of attribute concept (old):

    • Attributes are defined class specific in the ATT concept.

    • Domain values for an attribute are defined in static menus.

    • No release procedures and status management for classes and attributes.

  • Overview of new pool concept:

    • Attributes can be defined class independent.

    • Pool attributes can be assigned to more than one class.

    • Domain values for a pool attribute can be stored in special domain tables.

    • For every class it can be specified which domain value is valid.

  • The migration includes:

    • Merge attribute definitions. Attributes are considered as identical if the following values are identical:

      • C_LETTER

      • C_TITLE

      • C_TYPE

If you have defined C_LETTER and C_TITLE as multi-lingual fields (standard since axalant 2000), then you have to define with the Parameter "DB language" which language will be the default for the merge.

  • Initial load of the attribute value pool including the activation of the attributes for special classes.

  • Update classification lists.

  • Update used field name.

  • Set of attribute ATT_VAL_REF in the classification lists.

  • Update field and mask definition, if you have defined your own forms for classes.

    Surrounding text describes ch4001.gif.

    Note:

    If possible, do not create or modify basic definitions of classes and attributes between customization upgrade and takeover data from production system. This influences the migration steps which must be executed after the takeover process.

  • No new classes and attributes were created. Only classification list tables must be defined as reference tables.

    • T_GRP_ART

    • T_GRP_DOC

    • T_GRP_ORD

    • T_GRP_PRO

  • Customers have created new classes and attributes in the production system after the customization upgrade. In addition to the classification list table classes, attributes, and domain values must be copied and migrated.

    • T_GROUP_DAT

    • T_GROUP_STR

    • T_GRP_FLD

4.8 Workflow Takeover


Note:

For the customers using an Upgrade Tool version older than Agile e6.0.2, special generic workflow masks are copied during the takeover phase.

After taking over of the common tables, workflow masks are deleted, which are currently presented in the customer dump. Generic workflow masks are copied from the production database. The following tables are involved in this procedure:

  • T_MASK

  • T_MAS_FLD

  • T_FIELD

  • T_MENU

  • T_MEN_SEL

Workflow masks have a special naming convention: EDB-WFL-<CID_OF_ACTIVITY>

Entries within T_FIELD follow naming rule EDB-DEC<CID_OF_ACTIVITY>

  • T_MEN_SEL entries contain names like EDB-SEL-<CID> and EDB-NSEL-<CID>

  • T_MENU entries of C_BUT_EDT / C_BUT_SEL / C_BUT_NOS are considered only for this action.

During the takeover phase, all statements will be generated and executed within the Upgrade Tool and additionally written to the full.log file.