1. Applications Upgrade Guide for Microsoft Windows with Oracle
  2. Object Analysis Characteristics

Object Analysis Characteristics

The hierarchy of the Impact Analysis Report lists objects with these characteristics:

Total Number of Objects in Manifest

This is the total number of objects that is the sum of the Total Number of New Objects and Total Number of Existing Objects.

  • Total Number of New Objects

    These are net new objects for Release 9.2 and will be delivered by the Simplified Upgrade.

  • Total Number of Existing Objects

    This is the total count of the objects that exist in the target release. Of this object total, the report compares those objects against the manifest and makes these distinctions which will have the described result: These objects need to be retrofitted after the Spec Merge.

    • Number of Modified Objects (With Mismatched Dates)

      These objects have been modified by JD Edwards EnterpriseOne for Release 9.2. These objects will be replaced or merged by the Simplified Upgrade as outlined by the standard JD Edwards EnterpriseOne spec merge rules.

    • Number of Modified Objects (With Matched Dates)

      These objects have been flagged by the customer as having been modified by the user. Such objects will be replaced by the Simplified Upgrade because JD Edwards has modified them for Release 9.2.

      If these objects were modified, objects might need to be retrofitted with their custom modifications. The date match means these objects might not have customer modification, because the Object Librarian dates match the ESU dates.

      If the customer feels these objects were not actually customized, in order to prevent them from being merged by the spec merge rules, the merge setting should be set to option to '2'. This turns off the modified flag so the objects will be replaced and these objects are not marked as requiring to be retrofitted.

    • Number of Unmodified Objects (With Mismatched Dates)

      Typically this means that these objects do not have custom modifications. However, these objects have mismatched dates which may indicate they have been modified. These objects will be replaced or merged by the Simplified Upgrade as outlined by the standard JD Edwards EnterpriseOne merge rules.

      If the customer feels these objects were actually customized, they can turn on the modified flag before the merge.

    • Number of Unmodified Objects (With Matched Dates)

      These are the objects that have not been modified by the customer, as confirmed by matching date stamps. These objects that will be replaced by the Simplified Upgrade process.

  • Total Number of Obsolete Objects (Modified)

    • The reports lists the total number of objects that are marked as obsolete by JD Edwards Release 9.2. These objects will be deleted by the Simplified Upgrade process.

    • Number of Obsolete Objects (Unmodified)

      These are the objects that Release 9.2 has identified as obsolete but which have their customization flag set to Customized. These objects will be deleted by the Simplified Upgrade process.

  • Total Number of Modified Objects

    • Number of JDE Modified Objects

      These are standard JDE objects that are delivered with Release 9.2 through the Simplified Upgrade process.

    • Number of Custom Modified Objects

      These are non-JDE objects with System Codes 55-69 and Z*, and which are not in the manifest.

    • Number of Obsoleted Objects

      These are the objects that are marked as obsolete by Release 9.2. Regardless of whether these objects are marked as customized or not, all obsolete objects will be removed by the Simplified Upgrade process.

      These are the modified objects that have System Code 88 in the F9860 table or marked as obsolete in the Manifest.

    • Number of Orphan Objects

      These are the objects that exist in the F9861 table but which do not exist in the F9860 table. These objects will not be preserved (migrated to Release 9.2) by the Simplified Upgrade process.