Setting Up Packager

Before using Packager, you must check your Packager customer preferences and register any unregistered custom applications, which are populated automatically if a primary assessment has been performed.

Optionally modify this information or, if a primary assessment has not been performed, enter the information manually:

Setting Packager Customer Preferences

If your Packager customer preferences have not been set already, follow this procedure. Once set, these preferences are used for all subsequent Packager tasks.

Note:

If you select the Allow Auto Header check box, file headers are automatically inserted in all CEMLI files with object types that require them. For a detailed description of object types, see CEMLI File Object Types.

To set up Packager customer preferences:

  1. On the CEMLI home page, verify that your customer details are displayed.

  2. Click Packager.

    The Upload Customized Files tab is displayed by default.

  3. Click Set Customer Preferences.

  4. From the Apps Release list, select the Oracle E-Business Suite release used in the environment.

  5. From the Patch Driver Format list, select one of the following formats:

    • u (recommended)

    • cdg (for older Oracle E-Business Suite releases)

  6. From the Base Language list, select the base language for the Oracle E-Business Suite environment.

  7. If you have implemented NLS Languages support, optionally use the Change NLS Language(s) list to select from the available NLS languages.

    The Base Language list is refreshed to reflect your selections.

  8. If you want to enable automatic inclusion of headers, select the Allow Auto Header check box.

  9. Click Save.

    The Set Customer Preferences page shows the updated preferences.

Registering Custom Applications in Packager

As part of the initial setup, you must also register any custom applications that have not been already registered in Packager settings.

To register custom applications:

  1. On the CEMLI home page, verify that your customer details are displayed.

  2. Click Packager.

    The Upload Customized Files tab is displayed by default.

    Note:

    You must register only custom applications that are not already registered in Packager. Please only register custom applications that have Oracle Automated CEMLI Execution setup completed in your E-Business Suite environment.

    If a custom application is displayed in the Packager | Existing Products area, you do not need to register it again.

  3. Click Manage Custom Products.

  4. In the Register New Product area, enter the following information:

    • Product Name: Specifies the short name of the custom application, in lower case with no spaces.

    • Application Id: Specifies the ID for the application. Use a query to retrieve this value from the APPSFND_APPLICATION_VL view. See Sample Query.

    • Description: Provides a free-text description of the custom application.

    • DB Schema: Specifies the name of the database schema associated with the custom product.

    Note:

    You will not be able to modify this information once it is saved.

  5. Click Create.

    The page is refreshed, displaying the custom application name and details in the Product List area, as follows:

    • Application Id: Specifies the ID for the application.

    • Name: Specifies the short name of the custom application, in lower case with no spaces.

    • Description: Provides a free-text description of the custom application. The information in this field can be edited and saved.

    • Active: Specifies whether the custom product is active or not. The information in this field can be edited and saved.

    • Schema: Specifies the name of the database schema associated with the custom product. The information in this field can be edited and saved.

    • Created By: Specifies the email address of the user who registered the product.

    • Created On: Specifies the date when the product was registered.

Sample Query

The following query retrieves custom application information from the Oracle E-Business Suite database (DB):

select app.application_short_name, prod.application_id
from fnd_product_installations prod,
      fnd_application app
where app.application_id>20000
and app.application_id= prod.application_id

Where:

app.application_short_name is the short name of the application

prod.application_id is the production application ID

This example shows a typical output from this query:

APPLICATION_SHORT_NAME         APPLICATION ID  ORACLE_ID  PRODUCTION_VERSION
----------------------         --------------  ---------  ------------------
XBOL                           20003           0          11.5.0