Validating a Software Master Definition

This task explains how to run Oracle's JD Edwards EnterpriseOne Pre-Mastering CD Validation report (R9640A) to validate the software master definition that you set up and what to review in the report to help with the validation. The report runs in final mode. The report lists whether the build step is validated. The report will change the status of build steps that do not have errors.

To validate a software master definition:

1. From the Product Packaging menu (GH962), select Product Packages (P9640).

2. On Work With Software Mastering, click Find.

   The existing software master definitions appear.

3. Select the master that you want to validate, and then select Validate from the Row menu.

4. On Report Output Destination, select to view the report on screen and click OK.

   The report runs. All steps without errors whose statuses were In Definition (10) or Defined (20) are promoted to the status of Validated (30); they will work properly during the software mastering process. Otherwise, the build step will have either a warning or an error message. Error messages will stop the creation of a software master. You must fix any build steps that contain error messages. The message specifies the error.

   Warning messages will not stop the creation of a software master. If a build step has a warning message, you should verify that the build step is as you want it before proceeding.

   Note: The report will always include a warning stating that the build step is different from the template. This warning is always true because the process uses a custom package build.

5. Continue to the next task, which explains how to create the final software master.