Maintenance Objects - Main
Select Admin Menu, Maintenance Object to view information about a maintenance object.
Maintenance Object - Main
Description of Page
Most maintenance objects are provided with the base package. An implementation can introduce custom maintenance objects when needed. Most fields may not be changed if owned by the base package.
Enter a unique Maintenance Object name and Description. Owner indicates if this business object is owned by the base package or by your implementation (Customer Modification).
Program Com ID is the name of the program used to call the maintenance object's page program for validating constraints when objects are archived, purged, or compared.
Service Name is the name of the internal service associated with the maintenance object.
The grid displays the following for each table defined under the maintenance object:
Table The name of a given table maintained as part of the maintenance object.
Table Role The table's place in the maintenance object hierarchy. Only one Primary table may be specified within a maintenance object, but the maintenance object may contain many Child tables.
Parent Constraint ID Specifies the constraint used to link the table to its parent table within the maintenance object table hierarchy.
Compare Method Either Normal or Large Table; specifies the comparison method used by the compare utility in the ConfigLab utility.
Owner Indicates if this is owned by the base package or by your implementation (Customer Modification).
Click the View XML hyperlink to view the XML document associated with the maintenance object service in the Service XML Viewer.
Note:
Oracle recommends that customers using Oracle Utilities Application Framework version 4.2 or later and currently using ConfigLab switch to Configuration Migration Assistant (CMA) for their configuration data migration needs and retain ConfigLab for migration of master and transaction data migration. Also note that CMA functionality is not available to every Framework-based product. For details, including tips and requirements for moving from ConfigLab to CMA for configuration data migrations, see the "Configuration Migration Assistant" section in the Oracle Utilities Application Framework Aministration Guide.
Oracle recommends that customers using Oracle Utilities Application Framework version 4.2 or later and currently using ConfigLab switch to Configuration Migration Assistant (CMA) for their configuration data migration needs and retain ConfigLab for migration of master and transaction data migration. Also note that CMA functionality is not available to every Framework-based product. For details, including tips and requirements for moving from ConfigLab to CMA for configuration data migrations, see the "Configuration Migration Assistant" section in the Oracle Utilities Application Framework Aministration Guide.
Parent topic