9 Custom Modifications and Packages

This chapter contains the following topics:

9.1 Understanding Custom Modifications and Packages

At this point, you are ready to retrofit your custom modifications into the objects delivered in the update. You may also choose to apply Oracle's suggested UDC description Data Dictionary glossary changes. This portion of the update process may involve several iterations of retrofitting and testing, so you will also be building update packages to deliver the modifications to the testing environments. This chapter also explains how to build and test the packages that you will deploy to the workstations.

Note:

As of Tools Release 9.2, customers could perform custom modifications only after the upgrade process. Beginning with Tools Release 9.2 Update 2, customers can retrofit the custom modifications for the objects that are part of the deployed ESU bundle.

If you made a backup of original specifications and business functions, you can restore this backup.

See Restoring a Backup.

9.2 Identifying Custom Modifications Using the Customization Workbench

The Customization Workbench (P98UCUST) is an application that provides a customer a way of easily identifying and managing the merge of EnterpriseOne customized objects that have been changed in the most recent delivery.

To identify custom modifications using the Customization Workbench:

  1. Fastpath to OMW.

  2. Create an OMW project. Make sure that you are a developer on this project and that this project is at a development status of 21.

  3. Use Fastpath to launch P96UCUST.

    This image is described in the surrounding text.

    Available Form Exits:

    • Refresh All - calls BSFN to refresh the F96UCUST data based on the merge modification flag in the F9861 table.

    • Load COA Data - launches batch versions for the Report R9840DL - Object Customizations Data Load Report.

    • Launch XRef - will launch the entry point form of the cross reference application in order that the end user may gather more information about the currently checked in object.

    • Launch OMW - will Launch OMW (P98220) where more actions can be taken on the object and project as needed.

  4. If the F96UCUST table has been loaded with customization objects information, then click "Find". Otherwise, click the form exit "Load COA Data". This will take a while for the table to load.

    This image is described in the surrounding text.
  5. The grid will appear with the data. The counters in the form header will indicate how many objects are complete and how many are still in need of review. Select an object from this list.

    This image is described in the surrounding text.
  6. An OMW Project Search and Select form will appear. Select the project that you will add the objects to. A popup window will appear.

    This image is described in the surrounding text.
  7. Confirm that you want to check out the object to the project. If you choose "No", you will have the option to check out the object later.

    This image is described in the surrounding text.
  8. Once on the form, there are several options that will change based upon the specific object.

    • Is the object on the project or not?

    • Is the object checked out or not?

    • What is the object type?

    This image is described in the surrounding text.
  9. Perform the tasks necessary to add the appropriate customized objects.

Button Function
Rmv frm Project Removes the object from the current project.
Add To Project Will launch the OMW Project Search and Select form to all for the end user to choose the project to which to add the object.
Check In Will check the object in on the current project.
Check Out Will check the object out to the current project.
Design Will launch the appropriate design application for the object type (i.e. FDA for APPL type objects, RDA for UBE type objects, etc.).
ER Compare Will launch the ER Compare tool for APPL, UBE and BSFN (NER) type objects. The default comparison will be between the local specs and the specs of the login pathcode (both can be modified in the tool once it is launched).
Build Available for BSFN type objects.
Launch OMW Will launch OMW (P98220) where more actions can be taken on the object and project as needed.
OK When complete and a value of "D' is entered and the OK button clicked, the object will be checked (confirmation pending).
Next/Previous Will scroll through the records on the previous screen for quick completion.

Field Value
Object Name The object name.
Path Code The path code.
Modification Flag The modification flag with a value of "C" indicates that the object has been customized.
OMW Project Name Name of the OMW project.
Status  

If the object is finished, it can be marked as D - Done. When the object is checked in the number of completed objects will change.

Available Form Exit:

Cross Reference - for reference purposes, will launch the appropriate cross reference form based on the object selected.

9.3 Retrofitting Custom Modifications

This section provides an overview of retrofitting custom modifications, discusses prerequisites, and discusses how to retrofit custom modifications for:

  • Interactive applications

  • Reports

  • Table conversions

  • Tables

  • Named event rules

  • C business functions

9.3.1 Understanding Retrofitting Custom Modifications

Most users modify their software to make the functionality more applicable to their business situations. When you update to a new release, you need to transfer your modifications to the new release.

Because re-creating custom modifications each time you update the software would be a laborious process, this chapter explains how to integrate the custom modifications that you made in your current software into the updated software. This integration, called retrofitting, enables you to refit the customizations that can be merged into each new version of the software.

9.3.2 Prerequisites

To retrofit modifications, you need a workstation with the upgraded software and the development tools. These tools enable you to compare the customizations that your current software merged into the new software with any path code in the system. This enables you to easily compare the upgraded modifications with a version of your modifications before the upgrade or with the pristine environment of the new release.

This table lists the requirements to retrofit custom modifications.

Requirement Details
Personnel A programmer, preferably the same one who did the custom modifications, should perform this task.
Logon status You must be able to log on to the workstation on which you will retrofit object modifications, typically in the development or prototype environment.
Package The environment must be updated and a package must be built and deployed to the workstation being used.
Modified Objects The modified objects must be checked out.

See JD Edwards EnterpriseOne Tools Object Management Workbench Guide.


9.3.3 Retrofitting Custom Modifications for an Interactive Application

To retrofit custom modifications for an interactive application:

  1. From Object Management Workbench (OMW), use Form Design Aid (FDA) to copy custom objects into the target application.

    You can use Compare Mode, under the File menu, to help with this process. Everything custom must be copied in FDA, except for Event Rule (ER) variables and ER statements that do not reference any custom objects.

  2. Save your changes.

  3. Within FDA, select Edit and Event Rules.

    This option enables you to use EditER to reenter all ER statements that reference any custom objects other than custom ER variables.

  4. Save your work.

  5. Use the JD Edwards ER Compare tool (ER Compare button in OMW or ER Compare command in FDA) to compare the updated local specifications (target) with the original, customized (source) specifications.

  6. Copy ER variables and then ER statements from source to target.

    Do not copy any statements that reference objects that existed only in the source (customized) environment. Those should have been created in step 3.

  7. Validate the resulting ER. Save and exit JD Edwards ER Compare.

  8. When you finish retrofitting and testing the modifications, check them back in and rebuild the package.

  9. Test and fix the modifications, and then rebuild and redeploy the corrected package. Repeat this step until all the modifications are functioning properly.

9.3.4 Retrofitting Custom Modifications for a Report

To retrofit custom modifications for a report:

  1. From OMW, use Report Design Aid (RDA) to re-create all custom report objects in the target UBE (universal batch engine).

  2. Within RDA, select Edit and Event Rules.

    This option enables you to use EditER to reenter all ER statements that reference custom objects other than custom ER variables.

  3. Save your work.

  4. Use the JD Edwards ER Compare tool (ER Compare button in OMW) to compare the updated local specifications (target) with the original, customized (source) specifications.

  5. Copy ER variables and then ER statements from source to target.

    Do not copy any statements that reference objects that existed only in the source (customized) environment. Those should have been created in step 2.

  6. Validate the resulting ER. Save and exit JD Edwards ER Compare.

  7. When you finish retrofitting and testing the modifications, check them back in and rebuild the package.

  8. Test and fix the modifications, and then rebuild and redeploy the corrected package. Repeat this step until all the modifications are functioning properly.

9.3.5 Retrofitting Custom Modifications for a Table Conversion

To retrofit custom modifications for a table conversion (TC):

  1. Within OMW, use Table Conversion Design Aid to re-create all custom parts of the target UBE.

  2. Within Table Conversion Design Aid, click the Advanced ER button within the Mapping dialog.

    This option enables you to use EditER to reenter all ER statements that reference custom objects other than custom ER variables.

  3. Use the JD Edwards ER Compare tool (ER Compare button in OMW) to compare the updated local specifications (target) with the original, customized (source) specifications.

  4. Copy ER variables and then ER statements from source to target.

    Do not copy any statements that reference objects that existed only in the source (customized) environment. Those should have been created in step 2.

  5. Validate the resulting ER. Save and exit JD Edwards ER Compare.

  6. When you finish retrofitting and testing the modifications, check them back in and rebuild the package.

  7. Test and fix the modifications, and then rebuild and redeploy the corrected package. Repeat this step until all the modifications are functioning properly.

9.3.6 Retrofitting Custom Modifications for a Table

To retrofit custom modifications for a table:

  1. Within OMW, on the Design Tools tab, click the Table Trigger Design Aid button and use EditER to reenter all ER statements that reference custom objects other than custom ER variables.

  2. Use the JD Edwards ER Compare tool (ER Compare button in OMW) to compare the updated local specifications (target) with the original, customized (source) specifications.

  3. Copy the ER variables and then the ER statements from the source to the target.

    Do not copy any statements that reference objects that existed only in the source (customized) environment. Those should have been created in step 1.

  4. Validate the resulting ER. Save and exit JD Edwards ER Compare.

  5. Use the Table Design Aid tool within OMW to update each table that needs further work.

  6. When you finish retrofitting and testing the modifications, check them back in and rebuild the package.

  7. Test and fix the modifications, and then rebuild and redeploy the corrected package. Repeat this step until all the modifications are functioning properly.

9.3.7 Retrofitting Custom Modifications for a Named Event Rule

To retrofit custom modifications for a named event rule (NER):

  1. Within OMW, use the JD Edwards ER Compare tool to compare the updated local specifications (target) with the original, customized (source) specifications.

  2. Copy the ER variables and then the ER statements from the source to the target.

    Do not copy any statements that reference objects that exist only in the source (customized) environment.

  3. Save and exit JD Edwards ER Compare.

  4. Use the Business Function Design Aid tool from OMW to select and update each business function that needs further work.

  5. Within the Business Function Design Aid tool, select Form and Edit.

    The edit option enables you to use EditER to reenter ER statements that reference custom objects. Save your work.

  6. Validate the resulting ER.

  7. When you finish retrofitting and testing the modifications, check them back in and rebuild the package.

  8. Test and fix the modifications, and then rebuild and redeploy the corrected package. Repeat this step until all the modifications are functioning properly.

9.3.8 Retrofitting Custom Modifications for a C Business Function

To retrofit custom modifications for a C business function:

  1. Within OMW, use the JD Edwards ER Compare tool to compare the updated local business function source code (target) with the original, customized (source) code.

  2. Select Edit, Auto Merge Application to merge the code. Save and exit JD Edwards ER Compare.

  3. Start the Business Function Design Aid tool from OMW.

  4. Select Form and Edit to use Microsoft Visual Studio to finish editing the code.

  5. Select the Build Business Function button in OMW to build the business function.

  6. When you finish retrofitting and testing the modifications, check them back in and rebuild the package.

  7. Test and fix the modifications, and then rebuild and redeploy the corrected package. Repeat this step until all the modifications are functioning properly.

9.4 Using JD Edwards EnterpriseOne Package Management

The package management process provides a means to create a package, to define and build a package, and to deploy packages to both servers and workstations using a step-by-step director process.

Note:

The software update process creates the package definition; you simply build and test the package.

Several instances occur in which you will need to update or set up a workstation or server with the JD Edwards EnterpriseOne software. You might need to set up a new workstation, deploy custom solutions to all or to selected users, create a new path code for development, or deploy a fix.

To include any modifications (changed or added business functions or applications) into a package for deployment to workstations (for example, DV900FB or DV900PB), you must define and build one of your own.