Recommended Configurations

EnterpriseOne can be configured in many ways. Examples and recommendations for the setup follow.

You should follow EnterpriseOne-recommended setup and naming standards wherever possible, unless a strong business case exists to support the need to change. Following the typical setup and naming standards enhances the likelihood of success and minimizes confusion when communicating with individuals outside the core project team who are not aware of your specific configuration.

If you want to customize your configuration, you should change only the descriptions with the typical setup, not the names. Upgrades will be easier with fewer manual steps if you use the EnterpriseOne-recommended naming standards.

An environment description is important because the description appears on the environment list of the login screen where the user selects the environment. The environment description should define:

• Path code

• Data type (such as production, test, or prototype)

• Data location

• Location that batch applications will execute