If you have custom objects or custom schemas that need to be tightly integrated with Oracle E-Business Suite, follow the instructions in this section.

1. Create custom schemas.

   If you have custom objects in Oracle E-Business Suite schemas, you must move them to custom schemas before you integrate with an APPS schema.

   Create one new schema to hold your custom data objects for each Oracle E-Business Suite schema in which your objects currently reside. Export your custom tables, indexes, and sequences from these schemas and then import them into the new custom schemas.

   Your data objects will be integrated with an APPS schema and your code objects will be created in Step 5.

   Attention: Make sure your custom objects follow Oracle E-Business Suite naming conventions.

   See: Naming Standards

2. Register custom schemas.

   If you have not done so already, register your custom schema by using the System Administrator responsibility in Oracle E-Business Suite. Use the navigator to select Security: ORACLE: Register.

3. Determine and set install group number.

   If you have not done so already, set the install group number for each custom schema. You can do this by using the System Administrator responsibility in Oracle E-Business Suite. Use the navigator to select Security: ORACLE: Register.

   Use install group number 0 to represent your custom schemas that need only single installations.

   If you use Multi-Org or have only one product installation group, enter 0 for the install group number for your custom schemas and skip to the next step.

   For the remaining custom schemas, you must choose an install group number that matches the install group number of the Oracle E-Business Suite product it customizes. For instance, if the schema PO2 lists an install group number of 2 and your custom schema CUST_PO2 is based upon it, then you set 2 as the install group number for CUST_PO2 also.

4. Change your data groups to use the APPS schema.

   Using the System Administrator responsibility in Oracle E-Business Suite, select Security: ORACLE: Register from the Navigator. Change the name in the ORACLE schema column to be the appropriate APPS schema for each data group that previously used your custom schema.

5. Create custom objects and grant access to APPS schema.

   If you use Multi-Org or have only one product installation group, perform the following:

   • Grant ALL privileges from each custom data object to APPS.

   • Create a synonym in APPS to each custom data object in every custom schema.

   • Create custom code objects in APPS.

   Otherwise, create synonyms for each table and sequence in the appropriate APPS schema for the related custom schema. To do this perform the following:

   • Grant ALL privileges from each custom data object to each APPS schema.

   • Create a synonym in the APPS schema with the same install group number as your custom schema for every custom data object. For instance, create synonyms in APPS2 for CUST_PO2 objects.

   • Create custom code objects in each APPS schema.

6. Drop duplicate code objects.