According to the Oracle Applications customization standards, you should create views, triggers, and packages under the APPS schema. Tables, indexes, and sequences should be created under a custom user schema, and private synonyms for these tables and sequences should be created under the APPS schema.

Typically each schema should have a corresponding data tablespace and index tablespace. You can use any name for the tablespace where you intend to store the tables (for example, WM_TRACKCHANGES) and indexes (if there are any).

Before running the database scripts, create a custom user and a corresponding data tablespace and index tablespace. We suggest a user name of WEBM, a data tablespace name of WEBMD, and an index tablespace name of WEBMI. However, you can also use an existing data tablespace and index tablespace.

When you execute database scripts to install objects in the database, you are prompted to supply an APPS username/password, a custom user username/password, custom tablespaces (for data and index), and a connection string.

Note that the custom user schema and APPS schema must be different.

The required grants and synonyms are already incorporated in the database scripts.