1. Business View Design Guide
  2. External Developer Considerations for Naming Business Views

External Developer Considerations for Naming Business Views

The term external development refers to applications that are created by developers who are not employed by Oracle's JD Edwards, such as consultants who create custom applications for clients. To prevent interference between JD Edwards EnterpriseOne and non-JD Edwards EnterpriseOne objects, you must use caution when naming an external business view. When you create business views for an application that is created by external developers, format the business view name as:

Vssss9999,where:

V is the business view.

ssss is the system code for the enterprise.

9999 is a unique next number or character pattern within the enterprise.

Provide a business view description with a maximum of 60 characters. It should reflect the application description followed by the form type, for example, Item Master Browse and Item Master Revisions.

Primary key fields should remain in the business view and should not be reorganized. If you try to remove a primary key field, you receive an error message.

Note: At least one business view for each table should include all columns from the table. Only one business view is allowed for each form type, except for a header detail form. You can use two business views on header detail forms, one for the header portion of the form and one for the detail portion.