Guidelines for Managing Modules in Application Taxonomy
In the application taxonomy hierarchy, when you create a module, it becomes a child of the currently selected node. Once created, you can't delete the module or move it elsewhere in the hierarchy.
From the Manage Taxonomy Hierarchy page, navigate to the Create Child Module or Edit Module page to manage the modules. As you create or edit modules, consider the following points regarding specific fields.
Identifiers
Module ID is the unique primary key for nodes in the taxonomy table. When you create a module, a unique read-only ID is automatically generated. The module contains two other identifiers: Module key and alternative ID. The module key is a string identifier, for example AP for the Oracle Fusion Payables application. The alternative ID is a numeric identifier, for example 1 for the Oracle Fusion product line. These additional identifiers are provided for the product line, product family, and application modules. However, you can optionally add them for logical business areas and new modules.
The product code is relevant only to application and logical business area modules. You can leave the field blank for other module types. The product code for applications is the short name that can be displayed in lists of application values. For example, FND for Oracle Fusion Middleware Extensions for Oracle Application.
Names
Module name is the logical name for the module. The name must be unique among nodes within the hierarchy level with the same parent, but Oracle recommends keeping it unique in the entire hierarchy. The user name and description can appear to users in other parts of Oracle Applications Cloud.
Usage Types
Though you can update the usage type to reflect the current state of the module, just doing so doesn't affect the actual state. For example, setting a module as installed doesn't mean the module is actually installed if the installation itself didn't take place. Installation refers to operations related to laying down all the components required to create an Oracle Applications Cloud environment. Deployment is the process that starts the managed servers and clusters and facilitates the actual use of product offerings. A licensed module is available for installation and deployment, and a deployed module is considered actively used when actually used by users.
Seed Data
If seed data is allowed, then data residing in flexfields and lookups can be extracted for the module using seed data loaders. By default, extract is allowed for all predefined modules of type application and logical business area.
Associations
You can associate a logical domain to modules of the type Product Family, as well as one or more enterprise applications to modules of type Application. This association represents the relationship between the taxonomy modules and the corresponding domain and enterprise applications stored in the Oracle Applications Cloud Functional Core (ASK) tables.