Setup Overview

This chapter covers the following topics:

Setting Up Oracle Applications Technology

This overview explains how to implement the parts of Oracle Applications. You need to complete several setup steps including:

Also, if your product uses Oracle Workflow to manage the approval of change requests (for example) or to send change notifications, you need to set up Oracle Workflow.

Related Topics

Oracle Workflow Guide

Setup Prerequisites

Before setting up this application, you must complete the required setup steps for the following:

Using Oracle iSetup

If you are implementing a new instance of the Oracle e-Business Suite and have relatively standard implementation requirements, you can use Oracle iSetup to rapidly configure the following applications:

Oracle iSetup simplifies the setup process by providing templates and predefined setup steps that may or may not apply to your enterprise.

Setup Steps

Following is a summary of the setup steps:

Profile Options

Profile options enable or change the behavior of certain features in the application. Following is a description of each of the system profiles used in this application, and their default values.

Profile Description Default Value
EGO: Enable exporting to Excel Governs the action of exporting search results.
Changing the value to Yes enables users to export certain search results data.		 No
EGO: Enable GTIN Validation Governs whether GTIN validations are performed.
Changing the value to No disables all GTIN validations.

Additional Information: GTIN validations include:

  • Length is 14.

  • Contains a valid check digit.

  • The GTIN is unique and only assigned to one item.

  • Does not contain more than 6 leading zeros.

  • The third digit from the left in a GTIN must be 0, 1, 3, 6, 7, 8, or 9 when the second digit from the left is 0.

  • If a GTIN in a RCI message has six leading zeros, digits 7-9 must be between 301-968.

  • GTINs submitted in RCI messages cannot contain values 0980-0989 or 099 in the first 4 digits.

  • GTINs submitted in RCI messages cannot contain values 02, 04, 05, and 10-29 in the second and third digits from the left.

 Yes
EGO: Enable Oracle Collaborative Development Enables edit options for structures in HTML.
Oracle recommends leaving the value as No.		 No
EGO: Enable Product Information Management Data Librarian Enables the use of Product Information Management-specific features such as Import Workbench if the value is Yes. See: Setup Overview of Inbound Product Data Synchronization. No
EGO: Enable Product Lifecycle Management Enables the use of Product Lifecycle Management-specific features such as Document Management if the value is Yes. No
EGO: Internal User Default Role for Items Governs the default role that is set up for internal users who access items. This role is assigned to internal users for all items in the organizations to which the users have access.
Design Reviewer is seeded for Forms interoperability.

Additional Information: Forms does not have data security, so users must be given additional privileges on specific items (either directly or via inheritance) to perform actions on itemsC.


Users with the Design Reviewer role can view/access all item information. If you want to restrict access further, define a custom role and then reset the default role for all enterprise internal users.
It is recommended that you always specify a role that minimally has the View Item privilege.		 Design Reviewer
EGO: ITEM RULE PROCESS SIZE During item import, all item business rules are applied at one time to a certain number of items, specified in this profile option, during one iteration. If the profile option value is left blank (null), the number of items defaults to 100 internally.
Adjust the number to achieve the best item import performance for your system configuration. This profile option applies to the following item import methods:

  • Importing Items Using a Spreadsheet

  • Import Workbench

  • Import Catalog Items


See: Managing Item Imports, Oracle Product Information Manaagement User's Guide.		 Null
EGO: Maximum Match Results In Import Workbench while importing items from external source systems, users can run Match Rules to discover existing items in PIM Data Hub that match based on the criteria defined in the Match Rule. This option restricts the number of matches the matching process finds for every item. The matches display in the Matching Items section within the Unconfirmed tab. 50
EGO: Maximum number of attribute groups in Search. This site level profile option specifies the maximum number of attribute groups you can use as search criteria and in display formats.

Caution: Increasing the value could result in slow item search performance.

 5
EGO: Maximum number of rows for sorting Specifies the maximum number of rows to sort during an item search. If a search retrieves more than the maximum number of rows, the search results are displayed without sorting (a warning is displayed).

Additional Information: Specifying a value greater than 2000 may have a negative impact on search performance.

 2000
EGO: Number of recent links to display Specifies the number of links to display in the Recently Visited list 20
EGO: Restrict actions in Item form Governs the Forms actions for items.
Set to Yes to ensure that data level role-based security is honored in Forms. When set to Yes users will be unable to access the following functionality in Forms:

  • Categories

  • Catalog

  • Revisions

  • Organization Assignments

  • Attachments (disables attachments)


Keep the default value No if you wish to make all actions available in Forms.		 No
EGO: Stats Collection Threshold This option sets the threshold for the number of records at which the statistics collection program will be executed on the interface table. 100
EGO: Thesaurus for Matching Enables the use of a synonym search when matching incoming external items to Oracle Product Information Management Data Hub (PIMDH) items if the value is Yes. See: Creating Match Rules.
A thesaurus is not included by default in the database. If you load a thesaurus into the database, then set this option to Yes.		 No
EGO: User Organization Context This option stores the organization selected by a user. When the user logs in to the system, the system retrieves the organization from this option and uses it for the session.
Change the organization stored in this profile option by using the Change Organization function within the Development Manager responsibility.		 -1
ENG: Internal User Default Role for Changes Governs the default role that is set up for internal users who access change objects. This role is assigned to internal users for all change objects in the organizations to which the users have access.
Reviewer is seeded for Forms interoperability.

Additional Information: Forms does not have data security, so users must be given additional privileges on specific change objects (either directly or via inheritance) to perform actions on change objects.


Users with the Reviewer role can view/access all information for a change object. If you want to restrict access further, define a custom role and then set reset the default role for all enterprise internal users.
It is recommended that you always specify a role that minimally has the View Item privilege.		 Reviewer
EGO GDSN Enabled Governs the GDSN Synchronization functionality.
Changing the value to Yes enables GDSN functionality.
Once you turn the flag to yes, then

  • the GDSN default functional area appears

  • the GDSN attributes appear in setup list page

  • the GDSN attributes become associated with the Item Catalog Categories

  • the GDSN Syndicated functional area flag on the Create Item and Functional Classification page becomes enabled.

 No
Enable PIM for Telco Features This site (organization) profile option enables the use of telecommunications industry features such as item catalog category/value set versions and transaction attributes if the value is set to Yes. No

Other Default Options

The EGO_DEFAULT_OPTIONS table enables you to specify default behavior during the item creation process. Your database administrator can use SQL to access this table and set the default value for each option. The following table lists all of the options available in EGO_DEFAULT_OPTIONS:

Option Description Default Value
EGO_ASSIGN_PACK_SUPPLIER Controls whether or not all lower levels of a packaging hierarchy are assigned the same suppliers as those assigned to the parent pack level. See: Assigning Suppliers to Items, Oracle Product Information Management User's Guide. Y
EGO_ASSIGN_PACK_SUP_SITE Controls whether or not all lower levels of a packaging hierarchy are assigned the same supplier sites as those assigned to the parent pack level. See: Assigning Suppliers to Items, Oracle Product Information Management User's Guide. Y
EGO_ASSIGN_PACK_SS_ORG Controls whether or not all lower levels of a packaging hierarchy are assigned the same supplier site organizations as those assigned to the parent pack level. See: Assigning Suppliers to Items, Oracle Product Information Management User's Guide. Y
EGO_ASSIGN_PACK_CATEGORY Controls whether or not all lower levels of a packaging hierarchy are assigned the same item catalog category as the parent pack level. See: Assigning an Item to a Category, Oracle Product Information Management User's Guide. Y
EGO_UNASSIGN_PACK_CATEGORY Controls whether or not you must individually assign an item catalog category to each level of a packaging hierarchy. See: Assigning an Item to a Category, Oracle Product Information Management User's Guide. Y
EGO_ASSIGN_PACK_ORG Controls whether or not any packs associated with an item are assigned to the same organizations as the item. See: "To assign a pack to an organization:" in Enabling Organization Assignments, Oracle Product Information Management User's Guide. Y
EGO_DEFAULT_STYLE_SUP_AND_SUP_SITE Controls whether or not any suppliers and supplier sites associated with a style item are assigned during item creation to the style's SKU items. See: Assigning Suppliers to Items, Oracle Product Information Management User's Guide. Y
EGO_DEFAULT_STYLE_ITEM_ORG Controls whether or not the SKU items associated with a style item are assigned to the same organizations as the style item during item creation. See: Enabling Organization Assignments, Oracle Product Information Management User's Guide. Y
EGO_DEFAULT_STYLE_SUP_SITE_ORG Controls whether or not any supplier site organizations associated with a style item are assigned during item creation to the style's SKU items. See: Assigning Suppliers to Items, Oracle Product Information Management User's Guide. Y
EGO_DEFAULT_STYLE_ALTERNATE_CATALOG Controls whether or not any alternate catalogs associated with a style item are assigned during item creation to the style's SKU items. See: Assigning an Item to a Category, Oracle Product Information Management User's Guide. Y
EGO_DEFAULT_STYLE_LC_PHASES Controls whether or not a lifecycle and phases associated with a style item are assigned during item creation to the style's SKU items. See: Managing Item Phases, Oracle Product Information Management User's Guide. Y
EGO_DEFAULT_STYLE_LC_PROJS Controls whether or not a lifecycle tracking project associated with a style item is assigned during item creation to the style's SKU items. Y
EGO_DEFAULT_STYLE_PEOPLE Controls whether or not roles assigned to a style item are assigned during item creation to the style's SKU items. See: Implementing Role Based Security. Y
EGO_SKU_CONCAT_VA_DELIM This delimiter value is used when creating function generated SKU item numbers and descriptions by concatenating the variant attribute values. For example, if the delimiter value is 3, then a shirt SKU item number with the variant attribute values of Color = Blue and Size = Medium might be shirtBluMed. See: Creating Style and SKU Items, Oracle Product Information Management User's Guide. (blank)