Change Table Configuration

This example illustrates why change table configurations are needed:

Create change table configurations to indicate to the JD Edwards EnterpriseOne Product Packaging Tools the change tables that you want included with the software master. When you install the finished software master, the installation process will update the control tables of the enterprise with the change tables that you indicate.

Assume that the home office in Denver, USA, makes software changes and wants to update an enterprise that is not networked to the Denver enterprise. The other enterprise, which has its own set of JD Edwards EnterpriseOne software and control tables, is in Paris, France. The Denver enterprise creates a software master that includes the package containing the software changes, as well as the change tables that contain data dictionary and user-defined codes changes, which, for this example, are the only control table changes since the Paris enterprise was last updated. The Denver enterprise writes the software master to a CD and ships it to Paris. When the Paris enterprise installs the software master, the change tables update the Paris control tables, making the tables concurrent with the Denver control tables.