During the installation, upgrade, and cumulative update processes, JD Edwards EnterpriseOne creates reports that show detailed information about the plan and summarize the status of the environment builds. During upgrades and cumulative updates, additional reports summarize the status of tables merges.
This chapter discusses:
Section 25.1, "Installation Planner Validation Report (R9840B)"
This report is for installation, upgrade, and cumulative update customers.
Section 25.2, "Table and Index Creation (R98407)"
This report is for upgrade and cumulative update customers.
Section 25.3, "Environment Database Creation Report (R98403)"
This report is for installation, upgrade and cumulative update customers.
Section 25.4, "Object Librarian Modifications Report (R9840D)"
This report is for upgrade and cumulative update customers only.
Section 25.5, "Async Launch (R98405A)"
This report is for upgrade and cumulative update customers only.
Section 25.6, "Report on Table Conversions (R984052)"
This report is for upgrade and cumulative update customers only.
Section 25.7, "Object Specification Merge Report (R98700)"
This report is for upgrade and cumulative update customers only.
Section 25.8, "Index Recreation (R9698713)"
This report is for installation, upgrade and cumulative update customers.
Section 25.9, "Pathcode Copy (R9800942)"
This report is for installation, upgrade and cumulative update customers.
Note:
This report is used by installation, upgrade, and cumulative update customers.All processes use version XJDE0001 of this report.
The Installation Planner Validation report summarizes the status of the installation plan and verifies that the plan information is correct before you run the Installation Workbench
The Extra Info tab contains these options:
| Option | Value |
|---|---|
| Additional data source information flag | Enter Y to include additional information. |
| OCM Information Flag | Enter Y to see all Object Configuration Manager (OCM) information for the current data selection.
Enter D to select all default records. Enter N to prevent OCM records from being displayed. |
| OCM Differences Flag | Enter Y to see OCM differences between the new environment and the previous environment. |
| Path Code Information Flag | Enter Y to display all path code information for the plan(s) in the data selection |
| Update the Plan Status (10 – 60) | Enter 30 |
Use the Installation Planner Validation report summary section to review basic information about the installation, upgrade, or cumulative update; the number of records validated; and the types of processes run.
Review the main body of the report to verify that each data source, machine, and package build in the plan was created successfully. To verify, each detail line should have the value Record Validated in the far right column.
The report includes the status of the following record types:
Location
Data sources (listed by database type)
Environments
Path codes
Object Configuration Manager (OCM)
Machines
Table conversions
Control table merges
Specification table merges
Packages
A summary should appear at the end of the report verifying that all records were validated and the plan status was updated to 30.
JD Edwards EnterpriseOne creates a report for each environment that is being upgraded. It creates new tables and indexes and recreates changed tables and indexes based on the F9698710 and F9698712 tables. It also reads the F9843 table to regenerate additional tables that do not have spec changes or to prevent regeneration of tables or indexes that will be converted in table conversion workbench or in post-workbench conversions.
The R98407 program creates a log of the actions it will perform against the database. The log table is the F984072 table. When the R98407 program is rerun it creates any items that are not at successful status and prints all items on the report.
Release 9.1 creates an Environment Database Creation report for each environment that is part of your plan. For each environment, you can choose to load either production or demonstration data.
Users performing installations and upgrades should run version XJDE0001.
Users performing cumulative updates should run version XJDE0004.
Upgrade users should run XJDE0005 because the update process updates only generic text. When running against pristine data, these users should run version XJDE0024.
The environment database creation copies the System data source (previous release) to the System - 910 data source. The System data source is release specific. The report is read and errors are processed in the same way as they are for the regular Environment Database Creation.
These processing options are the typical processing options for each version of the Environment Database Creation report.
The Environment Tab contains these options:
| Option | Values |
|---|---|
| Enter the Environment for the database to be created. | Leave this field blank. |
| Enter the Data Source for the database to be created. | Leave this field blank. |
| Enter a 1 to load Production Data or a 2 to load Demonstration Data. | Enter 2. The default is 1.
If this report is called from another process, the system passes in this flag. |
| Enter the source Data Source for Loading of Data. | Enter OneWorld Local.
If this report is called from another process, the system passes in this flag. |
| Enter the Source Environment for the database to be copied from. | Leave this field blank.
If this report is called from another process, the system passes in this flag. |
The Update Tab contains the following options:
| Option | Value |
|---|---|
| Enter a 1 for Proof Mode or a 2 to create the Environment Database. | Enter 2.
The default is Proof Mode. |
| Enter a A to recreate existing tables in data sources that allow automatic table creation. | Leave this field blank.
The default is not to recreate tables. |
| Enter a 1 to only copy tables that exist in the source data source. | Leave this field blank. |
| Enter a Y to add records without clearing the target table. | Leave this field blank.
This is used for language tables. The default is to clear the target table. |
The Print Tab contains these options:
| Option | Value |
|---|---|
| Enter a 1 to only print exceptions. | Leave this field blank.
The default is to print all lines. |
The Licensing Tab contains these options:
| Option | Value |
|---|---|
| Enter a Y to create all tables or a N to create licensed tables only. | Leave this field blank.
The default is to create all tables. |
| Enter a Y to print all tables in the report or an N to print licensed tables only. | Leave this field blank.
The default is to print all tables. |
The Environment Tab contains these options:
| Option | Value |
|---|---|
| Enter the Environment for the database to be created. | Leave this field blank. |
| Enter the Data Source for the database to be created. | Leave this field blank. |
| Enter a 1 to load Production Data or a 2 to load Demonstration Data | Enter 1.
The default is to load production data. If this report is called from another process, the system passes in this flag. |
| Enter the source Data Source for Loading of Data. | Leave this field blank.
If this report is called from another process, the system passes in the data source. |
| Enter the Source Environment for the database to be copied from. | Leave this field blank.
If this report is called from another process, the system passed in the Source Environment. |
The Update Tab contains these options:
| Option | Value |
|---|---|
| Enter a 1 for Proof Mode or a 2 to create the Environment Database. | Enter 2.
The default is Proof Mode. |
| Enter a A to recreate existing tables in data sources that allow automatic table creation | Leave this field blank.
The default is not to recreate tables. |
| Enter a 1 to only copy tables that exist in the source data source | Leave this field blank.
The default is to copy all tables. |
| Enter a Y to add records without clearing the target table. | Enter N.
to indicate you do not want to add records without clearing the target table. This is used for language tables. The default is to clear the target table. |
The Print Tab contains this option:
| Option | Value |
|---|---|
| Enter a 1 to only print exceptions. | Leave this field blank.
The default is to print all lines. |
The Licensing Tab contains these options:
| Option | Value |
|---|---|
| Enter a Y to create all tables or an N to create licensed tables only. | Leave this field blank.
The default is to create all tables. |
| Enter a Y to print all tables in the report or an N to print licensed tables only. | Leave this field blank.
The default is to print all tables. |
The Environment Tab contains these options:
| Option | Value |
|---|---|
| Enter the Environment for the database to be created. | Leave this field blank. |
| Enter the Data Source for the database to be created. | Leave this field blank. |
| Enter a 1 to load Production Data or a 2 to load Demonstration Data. | Enter 2.
The default is to load production data. If this report is called from another process, the system passes in this flag. |
| Enter the source Data Source for Loading of Data. | Enter OneWorld Local.
If this report is called from another process, the system passes in the data source. |
| Enter the Source Environment for the database to be copied from. | Leave this field blank.
If this report is called from another process, the system passes in the Source Environment . |
The Update Tab contains these options:
| Option | Value |
|---|---|
| Enter a 1 for Proof Mode or a 2 to create the Environment Database. | Enter 2.
The default is Proof Mode. |
| Enter a A to recreate existing tables in data sources that allow automatic table creation. | Enter A.
The default is not to recreate tables. |
| Enter a 1 to only copy tables that exist in the source data source. | Leave this field blank.
The default is to copy all tables. |
| Enter a Y to add records without clearing the target table. | Leave this field blank.
This is used for language tables. The default is to clear the target table. |
The Print Tab contains these options:
| Option | Value |
|---|---|
| Enter a 1 to only print exceptions. | Leave this field blank.
The default is to print all lines. |
The Licensing Tab contains the following options:
| Option | Value |
|---|---|
| Enter a Y to create all tables or a N to create licensed tables only. | Leave this field blank.
The default is to create all tables. |
| Enter a Y to print all tables in the report or a N to print licensed tables only. | Leave this field blank.
The default is to print all tables. |
Review the reports to make sure the environments were created and configured successfully. The report includes a status for each table:
Tables that have been created correctly have a status of Success.
Tables that had errors have a status of Failure.
Tables can have a status of No Action.
The Environment Database Creation report does not have a cover page. The reports list the following properties of each table (object) created:
| Object headings | Description |
|---|---|
| Syst Code | System Code. Shows the JD Edwards EnterpriseOne product code for the database listed in the Member Description column. |
| Object Name | Displays the alphanumeric name of the database. |
| Member Description | Displays the full name of the database being created. |
| Data Source | Displays the data source toward which this member points. |
| Crt Tbl | Create Table. Shows whether tables are being created for this database. |
| Copy Data | Shows whether the table was copied with data. |
| Rec Insrt | Record Insert. Displays the number of records inserted. |
| Rec Fail | Record Failure. Displays the number of records that failed. |
| Copied from Data Source | Displays whether the table was copied with data and the data source from which it was copied. |
| Status | Displays one of the following statuses for the table creation: Success, Failure, or No Action. |
| Source DS Warnings | Displays any errors or warnings associated with the source data source. |
| Target DS Warnings | Displays any errors or warnings associated with the target data source. |
A report occasionally lists a status of Failure for tables that are created successfully. These failures are generally due to problems creating indices and are not critical for the successful installation of the software.
During an upgrade or cumulative update, you could receive failures for some tables. To confirm successful table creation, verify that the following tables were created successfully:
F0007Z1
F00092
F0086
F03B11
F03B14
F03B112
F060116
F06106
F08042
F08330
F0911
F1501B
F1721
F1731
F17111
F30006Z1
F3002Z1
F3003Z1
F3460Z1
F39062
F4077
F4106
F4111
F41508
F4600
F4812H
F5215
F7302
F986113
Reports frequently list a status of No Action for tables the system created successfully. This status is accompanied by source and target data source warnings for these tables to explain why no action was taken. These warnings are normal and you can ignore them. The most common reasons for the warnings are because the source and target data sources are the same or the table was created by a previously installed environment.
When the source and target are the same, the report lists the following warnings:
| Source data source warning | Target data source warning |
|---|---|
| Source Same as Target | Existing table |
This commonly occurs when the "copied from" data source is the same as the "target" data source (where the table is mapped), and often occurs for the following tables:
| UDC tables | Menu tables |
|---|---|
| F0004 and F0005 | F0082, F00821, F0083, and F0084 |
If you load multiple environments that share the same mappings (for example, DV910 and TS910), the first environment loaded (DV910 in this case) lists the tables with a Success status. The second environment (TS910) lists any tables already created during the first environment load with a status of No Action and a target data source warning of Existing Table.
The No Action status and Existing Table warning for the second (TS910) environment are normal. You can verify that any table with a target data source warning of Existing Table has been created successfully by verifying it was created while loading a previous environment.
Note:
This report is used only by upgrade and cumulative update customers.The Object Librarian Modifications report is created when running the Installation Workbench program before you merge any objects. It shows which objects from the previous release are flagged to be merged into the new release as well as which components of that object have been changed or added.
This report does not have processing options.
If you have made custom modifications to your business data, you can use the Customization Object Analyzer to identify customizations in order to determine the impact and level of effort to retro-fit the customizations into the newer release of JD Edwards EnterpriseOne. The Customization Object Analyzer is a summary and detail report that reads the custom modifications that have been made to your system. The reports are:
Object Customization Summary Report
Object Customization Detail Report
See Also
The section entitled Customization Object Analyzer in the JD Edwards EnterpriseOne Tools Software Updates Guide.
Table conversion workbench launches the R98405A program for every conversion when running them asynchronously, regardless of whether they will be run on the Deployment Server or Enterprise Server. The R98405A program launches the conversion. When all conversions complete, you can review their status by running the R984052 report, which is described in Report on Table Conversions (R984052).
Report on Table Conversions is created by Table Conversion Workbench when conversions are run asynchronously. The report shows the results for each table conversion and merge. Review this report to verify that each table conversion or merge completed normally.
The following column headings appear in this report:
| Object headings | Description |
|---|---|
| Environment | The new environment being converted or merged to. |
| Previous Environment | The environment being converted or merged from. |
| Obj Name | Object Name. The name of the table being converted or merged. |
| Program Name | The identification number of the table conversion or merge program. |
| Version | The version of the table conversion or merge. |
| Status | The status of the table creation. A successful completion is indicated by Completed Normally. |
Note:
This report is used only by upgrade and cumulative update customers.The Object Specification Merge report is closely related to the Object Librarian Modification report. This report is created during the Specification Table Merge Workbench. It shows the results of the merge for each modification and summarizes the activity shown on each Specification Merge Multithread Driver Report (R987001). Review this report to verify that all modifications were successfully merged.
This report has processing options for each of the following versions:
| Version number | Version Title |
|---|---|
| ZJDE0001 | UPGRADE – normal processing |
| ZJDE0002 | UPDATE – normal processing |
| ZJDE0003 | UPGRADE – restart |
| ZJDE0004 | UPDATE – restart |
| ZJDE0005 | UPGRADE – reprint |
| ZJDE0006 | UPDATE – reprint |
| ZJDE0007 | Internet Code Change Merge |
This report is designed to help you review the objects that will be merged. If the report shows any objects that you do not want to be merged, you can change the modification flag and the merge option so that the modification will not be merged into the new release. Similarly, you can verify that all modifications you want to be merged into the new release are flagged appropriately.
Two sets of headings appear on this report: one for the modified object, and a subheading for the modified components of that object.
| Object headings | Description |
|---|---|
| Obj Type | Type of object. For example, APPL for application or BSFN for business function. |
| Object Name | Alphanumeric identifier for the object. |
| Member Description | Brief description of the object. |
| Syst Code | Product code the object belongs to. |
| Location | The machine the object is on, which is typically the Deployment Server. |
| Path Code | Path code in the previous release that the object belongs to. |
| Mod Flag | Whether the object has been changed (C). |
| Mrg Opt | Whether the object will be merged (1 is yes, 0 is no). |
| Date Modified | Last date the object was changed. |
| Component headings | Description |
|---|---|
| Object Component | Part of the object that was changed or added (for example, forms and event rules). |
| Status | Successfully read components will have a status of changed or added. If the status is "failed," the batch application could not read the modified component. |
| Description | Brief description of the change. If the status is "failed," the description will be a brief explanation of the error. These errors usually result from a failure to read the file. |
The report includes the status of the following record types:
Package names
Source environments
Target environments
Advanced options
The report is broken into four sections:
The first section is a cover page which summarizes the processing options used to generate the report.
The second section is a list of the completion statuses of these objects as described in this table:
| Object | Status | Description |
|---|---|---|
| Object Librarian | Success | Indicates the number of objects successfully added or updated. |
| System 88 Warning | Indicates the system detected custom modifications for an object in a JD Edwards EnterpriseOne product code that does not exist in the new Object Librarian. Object Librarian objects were obsoleted by JD Edwards EnterpriseOne, so you, as the customer, need to decide how this affects your procedures. | |
| Errors: Setup issues | Indicates setup issues. To verify that your setup is correct you should:
|
|
| Versions List | Success | Indicates the number of copies successfully added or updated. Specification Merge totals indicate the number of added, replaced, and merged objects. |
| PO Change Warning | Indicates the processing options format for a ZJDE version has changed. Review and update options on these versions. | |
| Errors | Indicates the number of errors that occurred during the merge. Check the JDE.LOG for more complete messages dealing with F983051 or F98306. | |
| Central Objects | No Action Taken | This category is applicable for ZJDE versions. It shows that the version data was transferred but that no specification merges occurred. |
| Warnings and Errors | Indicates that details for warnings and errors occured. You can locate these in the detailed fourth section of the report. | |
| Not Processed | Indicates that the merge did not finish. Evaluate the errors and rerun the merge using a Restart version number. | |
| In Process | Indicates a fatal error occurred in the merge business function before completing the object. Evaluate and fix the error conditions before restarting the merge. |
The third section summarizes the merge statuses of each object in one line per object with these column headings:
| Object headings | Description |
|---|---|
| Obj Type | Object type, such as BSFN is a business function and TBLE is a table. |
| Object Name | Alphanumeric identifier for the object. |
| Version | The report version number run for this object. |
| Syst Code | Product code. |
| Merge Action | Indicates the object on source was added, replaced, or merged on the target. |
| Object Librarian Merge | Completion status for Object Librarian updates for this object. |
| Versions List Merge | Completion status for Versions List updates for this object. |
| Merge Status | Completion status for Specification merge for this object. |
| Date Completed | Date the object was merged. |
| Time Updated | Time the object was updated. |
The fourth section contains detail information for each merged object and includes these common errors:
Insert errors.
Header and source files that fail to copy.
Invalid dictionary items for tables or views.
Invalid files name or column in business views.
This table explains the column headings in the section:
| Object headings | Description |
|---|---|
| Object Name | Alphanumeric identifier for the object. |
| Version | The report version number run for this object. "+" indicates a template for a report. |
| Obj Type | Object type. For example, BSFN is a business function and TBLE is a table. |
| Syst Code | Product code. |
| Merge Action | Indicates the object on target source was added, replaced, or merged. |
| Merge Status | Success means that the object and all modified components were merged successfully. Warning means that one or more components did not merge correctly. |
| Mod Flag | Modification flag. |
| Date Completed | Last date the object was modified. |
| Time Updated | Last time the object was updated. |
This table describes the column subheadings:
| Object headings | Description |
|---|---|
| Description | Type of object component, such as a template, a field or an event rule. |
| Status | Status of the merge for that particular component. Success is denoted by a status of Added or Changed. Unsuccessful merges are noted with Failed or Error. |
| Description | This can be a brief description of the component or, in the case of a failure, an error message describing the failure. Disable and Append indicates event rules which require developer fixes. |
If an error occurs which stops the merge process there are two ways to recover, RESTART or RERUN. If the process stops during the Object Librarian merge or the Versions List merge, no recovery of specifications is necessary. Just rerun the merge after fixing the problem that initially caused the error. If the Merge Status column indicates that some items have merged or started merging, you must do a RESTART.
A RESTART merges items which are at a merge status of "Not Processed". All other statuses are skipped. Whether original specifications must be restored for objects with a status of "Error," "Warning," or "In Process," the status must be evaluated based on the merge action type.
| Merge ActionRestore Target Specifications | Merge Status |
|---|---|
| ADDNO | Any |
| REPLACENO | Any |
| CHANGENO | NOT PROCESSED |
| CHANGENO | SUCCESS |
| CHANGEYES | ERROR |
| CHANGEYES | IN PROCESS |
| CHANGEYES | WARNING |
To restore specifications for a single object, use Object Transfer to copy the object from the new pristine environment to the target environment.
This release contains a new application (P98700) for an interactive view of the progress during merges. F988810 is a new table used to control and track the merge process. Each record is time stamped as processing occurs. Before a RESTART operation it is possible to change the merge status to Not Processed, following the rules above, to repeat a merge for a specific object.
See Also
Restarting the Specification Merge
Release 9.1 on a Cluster section in the JD Edwards EnterpriseOne Tools Server and Workstation Administration Guide.
The summary report shows the status of the completed Object Librarian, Versions List, and Specifications Merges.
You can run the R9698711 program from Batch Versions after an install or upgrade. The report compares database tables and indexes against Release 9.1 Central Objects or TAM specifications. Use this report to verify the format of Release 9.1 tables in your database.
Note:
These reports are used only by upgrade and cumulative update customers.The UDC Merge, Data Dictionary Merge, and Menu Merge programs produce these reports:
UDC Merge and Exception report (R987241)
Data Dictionary Merge and Exception report (R989200)
Menu Merge report (R989751B)
These three merge reports are created when you run Control Table Workbench during Running Installation Workbench in the JD Edwards EnterpriseOne Upgrade Guide. These reports show the status of the UDCs, data dictionary items, and menus that were merged.
The processing options are the same for all of these merge reports.
The Release Info tab contains these options:
| Option | Value |
|---|---|
| Update Mode | Enter 2.
Default is Update Mode. |
| Environment Name for the Old Release | Enter a valid environment name. For example, PRODB7334. |
| Old Release Name | Enter the name of the old release. For example, B7334. |
| New Release Name | Enter the name of the new release. For example, E910. |
| Merge Language Codes | Enter N if language codes do not need to be merged. |
The Merge tab contains these options:
| Option | Value |
|---|---|
| Update Mode | Enter 2.
The default is update mode. |
| Environment Name for the Old Release | Enter the name of the old release environment. For example, PRODB7334. |
| Old Release Name | Enter the name of the old release. For example, E910. |
| New Release Name | Enter the name of the new release. For example, E910. |
Each report has a cover page that contains a summary of and basic information about your upgrade, release information, source mappings, mappings from replication, additional table mappings, and the mode in which the report was run.
The main text of the report indicates the status of Environment and Release Information, Source UDC Table Mappings, UDC Table Mappings from Replication, Additional Table Mappings, and Mode.
If the entire merge is successful, a message appears at the end of each report:
For the UDC Merge and Exception report: "UDC Merge process completed successfully with no errors and warnings."
For the Data Dictionary Merge report: "Data dictionary merge process completed successfully with no errors and warnings."
For the Menu Merge report: "Menu merge process completed successfully with no errors and warnings."
Note:
Tools Release 9.1 Update 2.If you have made custom modifications to your business data, you can use the Application Configuration Analyzer to verify that your changes were carried forward to the new release. The Application Configuration Analyzer is a set of reports which identify differences for processing options, data dictionary (DD) items, and user defined codes (UDCs) between releases or environments. These reports are:
Versions Compare
User Defined Codes Compare
Data Dictionary Compare
See Also
The section entitled: Application Configuration Analyzer in the JD Edwards EnterpriseOne Tools Software Updates Guide.
If warnings appear in the report, the merge finished. Check the warning log printed at the end of the report to diagnose any problems that may have occurred.
Errors appear only when the problem is severe enough to stop processing. If the report contains error messages, the merge process was not completed. Information regarding any errors is also printed in the log at the end of the report.
This following error message appears if change tables do not have records associated with the From Release and To Release settings: "DD Merge process terminated: Check Error Log."
The R9698713 program is run from Batch Versions after an install or upgrade. It compares database indexes versus Release 9.1 index specifications in F98712 and F98713. If you run the program in Update mode, it recreates incorrect indexes.
Environment Workbench runs the R9800942 program for each custom environment whose path code is to be copied from an existing path code. It copies the directory structure of the existing path code on the Deployment Server. It also copies package.inf and records in the package definition tables F9603, F9631, F96021 and F96215, replacing the path code names in those items.