How to Read the Report

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: Verify access authority to the source and target Object Librarian. Check the JDE.LOG for insert or delete errors on the F986* tables.
  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.