This appendix describes the concurrent programs available to either the Oracle Configurator Administrator or Oracle Configurator Developer responsibility.
This appendix covers the following topics:
This appendix explains how to use the Oracle Configurator concurrent programs that are available to the Oracle Configurator Developer and Oracle Configurator Administrator responsibility in Oracle Applications:
For general information about concurrent requests, programs, and processes, see the Oracle E-Business Suite System Administrator's Guide - Maintenance.
For general information about running Oracle Configurator concurrent programs, see Running Configurator Concurrent Programs.
The configurator administration concurrent programs are:
The View Configurator Parameters concurrent program allows the viewing of parameter values stored in the CZ_DB_SETTINGS table. See CZ_DB_SETTINGS Table for details about the parameters in that table.
Use the procedure described in Running Configurator Concurrent Programs to run this concurrent program.
Oracle Configurator Administrator or Oracle Configurator Developer
Navigator window > Oracle Configurator Administrator or Oracle Configurator Developer > Concurrent Programs > Schedule
The following table describes the parameters for the View Configurator Parameters concurrent program
| Parameter | Description |
|---|---|
| Section Name | From the list of values, select the SECTION_NAME of the section in the Oracle Configurator CZ_DB_SETTINGS Table where the setting resides. For example IMPORT. See Settings in CZ_DB_SETTINGS Table for more information. |
| Setting ID | From the list of values, select the SETTING_ID in the Oracle Configurator CZ_DB_SETTINGS Table for the setting. For example, CommitSize. See for more information. |
The output containing the values for the specified SECTION_NAME and SETTING_ID is recorded in a log file (see Viewing the Status of a Configurator Concurrent Request).
The Modify Configurator Parameters concurrent program allows the changing of parameter values in the CZ_DB_SETTINGS table. Configurator parameters are stored in the CZ_DB_SETTINGS table. See CZ_DB_SETTINGS Table for details about the parameters in that table.
Use the procedure described in Running Configurator Concurrent Programs to run this concurrent program.
Oracle Configurator Administrator
Navigator window > Oracle Configurator Administrator > Concurrent Programs: Schedule
The following table describes the parameters for the Modify Configurator Parameters concurrent program
| Parameter | Description |
|---|---|
| Section Name | From the list of values, select the name of the section in the Oracle Configurator CZ_DB_SETTINGS table where the setting resides. See Settings in CZ_DB_SETTINGS Table. |
| Setting ID | From the list of values, select the setting in the Oracle Configurator CZ_DB_SETTINGS table you want to modify. See Settings in CZ_DB_SETTINGS Table for more information on the settings in each SECTION_NAME. |
| Value | Enter the value for the particular parameter. See CZ_DB_SETTINGS Table for more information on valid values for each of the settings in each SECTION_NAME. |
| Type | From the list of values, select the data type (1= number or 4= string) of the setting you are modifying. |
| Description | Enter a brief description for this value selection. |
The output containing the modified values of the CZ_DB_SETTINGS Parameters you specified is recorded in a log file. For details, see Viewing the Status of a Configurator Concurrent Request.
The Purge Configurator Tables concurrent program physically removes all logically-deleted records in the tables and subschemas of the CZ schema. Periodically running this concurrent program improves database performance. See CZ Schema Maintenance for more information about purging the CZ schema. See the Oracle Configurator Performance Guide for additional information about improving database performance.
Use the procedure described in Running Configurator Concurrent Programs to run this concurrent program.
Oracle Configurator Administrator
Navigator window > Oracle Configurator Administrator > Concurrent Programs: Schedule
None
To see if there are any errors or warnings for the concurrent program, you must examine the log file. See Viewing Log Files.
The Purge Configurator Import Tables concurrent program deletes all data in the CZ_IMP tables, and the corresponding data in the CZ_XFR_RUN_INFOS, and CZ_XFR_RUN_RESULTS control tables. Periodically running this concurrent program improves import performance. See CZ Schema Maintenance for more information about purging the CZ schema. See the Oracle Configurator Performance Guide for additional information about improving database performance.
Use the procedure described in Running Configurator Concurrent Programs to run this concurrent program.
Oracle Configurator Administrator or Oracle Configurator Developer
Navigator window > Oracle Configurator Administrator or Oracle Configurator Developer > Concurrent Programs: Schedule.
None
To see if there are any errors or warnings for the concurrent program, you must examine the log file. See Viewing Log Files.
The Purge To Date Configurator Import Tables concurrent program deletes data in the CZ_IMP tables, and the corresponding data in the CZ_XFR_RUN_INFOS and CZ_XFR_RUN_RESULTS control tables. The data for the number of days specified in the input parameter is retained. Periodically running this concurrent program improves import performance. See CZ Schema Maintenance for more information about purging the CZ schema. See the Oracle Configurator Performance Guide for additional information about improving database performance.
Use the procedure described in Running Configurator Concurrent Programs to run this concurrent program.
Oracle Configurator Administrator or Oracle Configurator Developer
Navigator window > Oracle Configurator Administrator or Oracle Configurator Developer > Concurrent Programs: Schedule.
The following table lists the parameters for the Purge To Date Configurator Import Tables Concurrent Program.
| Parameter | Description |
|---|---|
| Number of Days | This is the number of days back that you want to retain your imported data. All data imported prior to the specified number of days back is deleted. |
To see if there are any errors or warnings for the concurrent program, you must examine the log file. See Viewing Log Files.
The Purge To Run ID Configurator Import Tables concurrent program deletes data in the CZ_IMP tables, and the corresponding data in the CZ_XFR_RUN_INFOS, and CZ_XFR_RUN_RESULTS control tables. All subsequent data from the specified Run ID input parameter is retained. Periodically running this concurrent program improves import performance. See CZ Schema Maintenance for more information about purging the CZ schema. See the Oracle Configurator Performance Guide for additional information about improving database performance.
Use the procedure described in Running Configurator Concurrent Programs to run this concurrent program.
Oracle Configurator Administrator or Oracle Configurator Developer
Navigator window > Oracle Configurator Administrator or Oracle Configurator Developer > Concurrent Programs: Schedule.
Th following table lists the parameters for the Purge To Date Configurator Import Tables concurrent program.
| Parameter | Description |
|---|---|
| Run ID | This is the earliest import run ID that you want to retain. All data imported prior to the specified run ID is deleted. |
To see if there are any errors or warnings for the concurrent program, you must examine the log file. See Viewing Log Files.
This concurrent program converts a database that is flagged as a remote publication target instance to an instance on which you can run Oracle Configurator Developer (or use as a target when migrating Models). If, for example, a user publishes a Model from Instance A to Instance B, the latter instance becomes a publication target and users can no longer run Configurator Developer on that instance.
Caution: Frequent use of this concurrent program can result in corrupt publication data or other issues. Therefore, run this program only when absolutely necessary, such as when a development instance is accidentally converted to a publication target instance.
Converting a publication target instance is a form of publication synchronization. The existing data in CZ_SERVERS, CZ_MODEL_PUBLICATIONS, and associated tables are modified to reflect the change in the network mapping of the publication. Existing publications are modified to make them consistent with the new mapping. The concurrent program updates the server definition on the source instance to indicate that the target instance has been converted.
If an error occurs while changing the instance from a remote publication target instance to a development instance, then the conversion is cancelled and the instance reverts to its prior state. This does not interrupt any Developer sessions as Developer remains disabled in the instance.
The concurrent program is run on the instance that is to be converted. Note that existing published Models are not visible in the Repository after this concurrent program is run. Once converted to a development instance, the Models can be migrated to this instance.
Oracle Configurator Administrator or Oracle Configurator Developer
Navigator window > Oracle Configurator Administrator or Configurator Administrator > Concurrent Programs: Convert Publication Target Instance to Development Instance.
None
The server administration concurrent programs are:
See Database Instances for information about a multi-server environment requiring use of these concurrent programs.
The Add Application to Publication Applicability List concurrent program adds a registered Oracle application to the CZ_EXT_APPLICATIONS table. Entries in the CZ_EXT_APPLICATIONS table are displayed in the Applications list of values parameter on the Publications page. For more information on the Applications parameter, see Applications.
Oracle Configurator Administrator
Navigator window > Oracle Configurator Administrator > Concurrent Programs: Schedule.
The following table describes the parameters for the Add Application to Publication Applicability List concurrent program.
| Parameter | Description |
|---|---|
| Application Name | From the list of values, select the desired application. The displayed applications are registered Oracle Applications found in the FND_APPLICATION table. |
To see if there are any errors or warnings for the concurrent program, you must examine the log file. See Viewing Log Files.
The Define Remote Server concurrent program creates a new remote server definition and adds the name of the remote database instance to the:
CZ_SERVERS table (see the CZeTRM on MetaLink, Oracle’s technical support Web site for details)
Database Instance publication applicability parameter list in Oracle Configurator Developer
Target Database Instance list in Oracle Configurator Developer (used when migrating Models)
Target Instance parameter for the Models synchronization concurrent programs
Source Name parameter for the Setup Configurator Data Migration concurrent program
Target Instance parameter for the Publication synchronization concurrent programs and (after running the Enable Remote Server concurrent program) the Configuration Model Publication concurrent programs
Use the procedure described in Running Configurator Concurrent Programs to run this concurrent program.
Oracle Configurator Administrator
Navigator window > Oracle Configurator Administrator > Concurrent Programs: Schedule.
The following table describes the parameters for the Define Remote Server concurrent program
To see if there are any errors or warnings for the concurrent program, you must examine the log file. See Viewing Log Files.
Enable Remote Server concurrent program performs all the operations needed to enable a remote server for import, publishing, synchronizing and migrating data. When a remote server is enabled, the list of remote BOM Models are linked into the local instance for use by the Populate/Refresh Configuration Models concurrent program. If a remote server is going to be the source for importing data, then the Import Enabled parameter must be set to Y. If the remote server will be a publication target instance, then the Import Enabled parameter must be set to N.
For more information about importing data, see Populating the CZ Schema.
Use the procedure described in Running Configurator Concurrent Programs to run this concurrent program.
Oracle Configurator Administrator
Navigator window > Oracle Configurator Administrator > Concurrent Programs: Schedule.
The following table describes the parameters for the Enable Remote Server concurrent program
| Parameter | Description |
|---|---|
| Server Local Name | Select from the list of values or enter the name of the server entry that you want to enable. "FOREIGN" (-1) and the local server (0) are invalid parameters. |
| Password | This is the password for the Oracle Applications schema (FNDNAM) on this remote server. |
To see if there are any errors or warnings for the concurrent program, you must examine the log file. See Viewing Log Files.
The View Servers concurrent program writes each defined server’s information to the concurrent program log.
Use the procedure described in Running Configurator Concurrent Programs to run this concurrent program.
Oracle Configurator Administrator
Navigator window > Oracle Configurator Administrator > Concurrent Programs: Schedule.
None
The log file lists each defined server’s Server Name (corresponding input parameter is Local Name), Host Name, Port, Instance Name, Server Db Version, FND Name, Global Name, Notes (corresponding input parameter is Description), FND Link Name, Import Enabled. There is no indication whether the defined server has been enabled.
To see if there are any errors or warnings for the concurrent program, you must examine the log file. See Viewing Log Files.
The Modify Server Definition concurrent program allows the changing of the server’s previously defined input parameters. For example, if you are changing your import source from the local server to a remote server, you must run the Modify Server Definition concurrent program to change the value of the Import Enabled parameter for the local server in addition to defining and enabling the remote server for import.
Use the procedure described in Running Configurator Concurrent Programs to run this concurrent program.
Oracle Configurator Administrator
Navigator window > Oracle Configurator Administrator > Concurrent Programs: Schedule.
The following table describes the parameters for the Modify Server Definition concurrent program
To see if there are any errors or warnings for the concurrent program, you must examine the log file. See Viewing Log Files.
The publication concurrent programs include:
These concurrent programs create a copy of a configuration model’s structure, rules, and UI by copying the data from the development database instance to the CZ_MODEL_PUBLICATIONS table on the target Database Instance specified in the Oracle Configurator Developer Model Publication page.
These concurrent programs must be run in the source database. The source database is the database in which the configuration model and its publication record are defined. The target database for the publication process is specified by the publication’s applicability parameters. See the Oracle Configurator Developer User’s Guide and Publication Applicability Parameters for more information about applicability parameters.
Typically, concurrent programs are scheduled to run automatically. If for some reason you do not have these concurrent programs scheduled, or you cannot wait to publish your Model until the next scheduled request run, you can run either program manually.
The target publication database instance must be defined and enabled as a remote server unless the target server is the same as the source server. If the target server is the same as the source server, then the target server does not have to be enabled. See Server Administration Concurrent Programs .
Running the publication concurrent programs includes BOM Model synchronization. For details, see Checking BOM and Model Similarity and Publishing a Configuration Model.
The Process Pending Publications concurrent program copies all Model data (source publications) in the CZ_PB_MODEL_EXPORTS table that have a STATUS of PEN (pending) to the instance specified when creating the publication in Configurator Developer.
Use the procedure described in Running Configurator Concurrent Programs to run this concurrent program in the database where the configuration model and its publication are defined.
Note: When running the Process Pending Publications concurrent program, all affected Models including referenced Models are temporarily locked while the program is running. If any affected Model is already locked by a user other than the one making the request, the concurrent program logs an error without completing the request. For details about locking objects, see the Oracle Configurator Developer User’s Guide.
Oracle Configurator Administrator or Oracle Configurator Developer
Navigator window > Oracle Configurator Administrator or Oracle Configurator Developer > Concurrent Programs: Schedule.
None
To see if there are any errors or warnings for the concurrent program, examine the log files. See Viewing Log Files.
The Process a Single Publication concurrent program copies a specific Model publication to a the instance specified when creating the publication in Configurator Developer..
Use the procedure described in Running Configurator Concurrent Programs to run this concurrent program in the database where the configuration model and its source publication are defined.
Note: When running the Process a Single Publication concurrent program, all affected Models including referenced Models are temporarily locked while the program is running. If any affected Model is already locked by a user other than the one making the request, the concurrent program logs an error without completing the request. For details about locking objects, see the Oracle Configurator Developer User’s Guide .
Oracle Configurator Administrator or Oracle Configurator Developer
Navigator window > Oracle Configurator Administrator or Oracle Configurator Developer > Concurrent Programs: Schedule.
The following table describes the parameters for the Process a Single Publication concurrent program
| Parameter | Description |
|---|---|
| Publication | Select from the list of values or enter the publication ID of the publication you want to export to the database instance specified in the publication record. The publication ID is displayed in the Model Publication page in Oracle Configurator Developer, and is stored in the CZ_MODEL_PUBLICATIONS table. |
To see if there are any errors or warnings for the concurrent program, you must examine the log file. See Viewing Log Files.
The concurrent programs for populating and refreshing configuration models are:
Use the Populate/Refresh Configuration Models concurrent programs to import data into the CZ schema, including:
Extracting BOM Model data into the correct format for transfer (Standard Import, only)
Loading the data into the import tables (Standard Import, only)
Populating the online CZ schema with the data from the import tables
For more information about data import, see Populating the CZ Schema.
Note: The Populate and Refresh Configuration Models concurrent programs do not provide an automated or scheduled mechanism that clears the import tables.
Oracle does not recommend running Populate and Refresh Configuration Models Concurrent Programs and Import Configuration Rules concurrent program at the same time.
The Populate Configuration Models concurrent program populates the CZ schema online tables with data for creating configuration models that are based on existing BOMs or legacy data.
Use the procedure described in Running Configurator Concurrent Programs to run this concurrent program in the database into which you are importing data.
Note: When running the Populate/Refresh Configuration Models concurrent program, all affected BOM Models including referenced Models are temporarily locked while the program is running. If any affected BOM Model is already locked by a user other than the one making the request, the concurrent program logs an error without completing the request. For details about locking objects, see the Oracle Configurator Developer User's Guide.
You cannot run simultaneous Populate/Refresh Configuration Models requests. If there is another Populate/Refresh Configuration Models running when you start the concurrent program, then your request will terminate.
Oracle Configurator Administrator or Oracle Configurator Developer
Navigator window > Oracle Configurator Administrator or Oracle Configurator Developer > Concurrent Programs: Schedule.
If no data is available in the list of values for the following parameters, see Populate Configuration Models Concurrent Program Error Messages.
The following table describes the parameters for the Populate Configuration Models concurrent program
| Parameter | Description |
|---|---|
| Organization Code | Required. Select from the list of values or enter the BOM Models’ Inventory organization that you want to import the BOM Models from. |
| Model Inventory Item From | Select the first Model Inventory Item in the range of BOM Models you want to import. All Model Inventory Items between and including the first and last specified in this and the next field, are included in the data import. The range can include multiple types of Model Inventory Items. For example, from ATO800 to PTO500 is a valid range. |
| Model Inventory Item To | Select the last Model Inventory Item in the range of items for which you want to import data. If you want to import a single model, enter the same Model Inventory Item that you entered for the Model Inventory Item From parameter. |
To see if there are any errors or warnings for the concurrent program, you must examine the log file. See Viewing Log Files.
On certain error conditions there is no data in the extraction views and the list of values for a new import does not have any data. In these cases, the list of values for the Populate Configuration Models concurrent program displays a ’No entries found for List of Values’ message. Possible reasons for the missing data include:
The server’s Enabled for Import parameter has not been set to Y
The Enable Remote Server concurrent program did not complete successfully
The database link is down
The remote database is down
The extraction views are invalid
If the database link is down, the following message appears:
’error 2019: connection description for remote database not found’
(The SQL statement that is currently running follows this message.)
The Oracle Configurator Administrator must run the Modify Server Definition concurrent program and Enable Remote Server for import (if one is not already selected). See Parameters for the Modify Server Definition Concurrent Program and Parameters for the Enable Remote Server Concurrent Program.
Run Enable Remote Server if the enabled server is not LOCAL. See Parameters for the Enable Remote Server Concurrent Program. Rerunning this concurrent program recreates the extraction views.
The Refresh a Single Configuration Model concurrent program updates the imported BOM Model data in the CZ schema when information in Oracle Applications Bills of Material and Inventory has changed.
Use the procedure described in Running Configurator Concurrent Programs to run this concurrent program in the database in which you are refreshing data.
Note: When running the Refresh a Single Configuration Model concurrent program, all affected BOM Models including referenced Models are temporarily locked while the program is running. If any affected BOM Model is already locked by a user other than the one making the request, the concurrent program logs an error without completing the request. For details about locking objects, see the Oracle Configurator Developer User’s Guide.
Oracle Configurator Administrator or Oracle Configurator Developer
Navigator window > Oracle Configurator Administrator or Oracle Configurator Developer > Concurrent Programs: Schedule.
Parameters for the Refresh a Single Configuration Model and Disable/Enable Refresh Concurrent Programs lists the parameters used for the Refresh a Single Configuration Model concurrent programs.
The following table describes the parameters for the Refresh a Single Configuration Model and the Disable/Enable Refresh concurrent programs.
| Parameter | Description |
|---|---|
| Folder | Enter the name of the Configurator Developer Repository Folder in which the configuration model resides, or select a Folder from the list of values. |
| Configuration Model ID | Select a Model from the list of values. |
To see if there are any errors or warnings for the concurrent program, examine the log files. See Viewing Log Files.
The Refresh All Imported Configuration Models concurrent program updates all of your imported BOM Model data.
Use the procedure described in Running Configurator Concurrent Programs to run this concurrent program in the database in which you are refreshing data.
Note: When running the Refresh All Imported Configuration Models concurrent program, all affected BOM Models including referenced Models are temporarily locked while the program is running. If any affected BOM Model is already locked by a user other than the one making the request, the concurrent program logs an error without completing the request. For details about locking objects, see the Oracle Configurator Developer User’s Guide.
Oracle Configurator Administrator
Navigator window > Oracle Configurator Administrator > Concurrent Programs: Schedule.
None
The Disable/Enable Refresh of a Configuration Model concurrent program prevents (disables) or allows (enables) either of the Refresh Configuration Model concurrent programs to update a specific configuration model. You may want to prevent a configuration model from being updated if you are currently designing its configuration rules in Configurator Developer. This concurrent program is run in the database instance where the configuration model resides.
Use the procedure described in Running Configurator Concurrent Programs to run this concurrent program in the database containing the configuration model whose refresh is being controlled.
Oracle Configurator Administrator or Oracle Configurator Developer
Navigator window > Oracle Configurator Administrator or Oracle Configurator Developer > Concurrent Programs: Schedule.
The following table lists the parameters for the Disable/Enable Refresh of a Configuration Model concurrent program.
| Parameter | Description |
|---|---|
| Folder | Enter the name of the Configurator Developer Repository Folder in which the configuration model resides, or select a Folder from the list of values. |
| Configuration Model ID | Select a Model from the list of values. |
| Refresh Enabled (Y/N) | The response of Yes or No indicates whether the specified Model is refreshed when the Refresh concurrent programs are run. |
The Import Configuration Rules concurrent program imports rules that are written in Constraint Definition Language format into the CZ schema. For more information, see Rule Import.
Note: You cannot run simultaneous Import Configuration Rules requests. If there is another Import Configuration Rules request running, then your rule import request will terminate.
If the rule’s Model is locked, then an appropriate message is returned and the configuration rules are not imported into the CZ schema.
Oracle Configurator Administrator or Oracle Configurator Developer
Navigator window > Oracle Configurator Administrator or Oracle Configurator Developer > Concurrent Programs: Schedule.
Thefollowing table lists the parameters for the Import Rules concurrent program.
| Parameter | Description |
|---|---|
| Run ID | This is an optional import session parameter. Run ID identifies a set of source data that is converted into rules after the data is imported into the CZ schema. If this parameter is null, then the records in CZ_IMP_RULES with RUN_ID, REC_STATUS, and DISPOSITION that are NULL are imported into the CZ schema and will have a generated RUN_ID. If Run ID is not null, then all records in CZ_IMP_RULES with the given RUN_ID are processed and refreshed in the CZ schema. If the Run ID is an invalid Run ID, then the following message is returned: ’No data found in the CZ_IMP_RULES table with RUN_ID = &RUNID’. |
Note: If you want to refresh a set of rules that have the same Run ID, you must first manually set CZ_IMP_RULES.REC_STATUS, CZ_IMP_RULES.DISPOSITION, CZ_IMP_LOCALIZED_TEXTS.REC_STATUS, and CZ_IMP_LOCALIZED_TEXTS.DISPOSITION to NULL for those records that have the desired Run ID. You then run the Import Configuration Rules concurrent program with the Run ID. Note that any changes made to the rule in Configurator Developer will be overridden with the newly imported rule.
Rules are validated for CDL structure and rule participants. If an imported rule has a parsing error, the parsing error is written in both the concurrent program log file and CZ_IMP_RULES.MESSAGE. The REC_STATUS for CZ_IMP_RULES and CZ_IMP_LOCALIZED_TEXTS is ERR, and CZ_IMP_LOCALIZED_TEXTS.DISPOSITION is R. Rules imported into the CZ schema can be edited either in Configurator Developer or the source environment.
The rule import run data is logged in the CZ_XFR_RUN_INFOS table as well as the CZ_XFR_RUN_RESULTS table. For more information about these tables and the tables used during rule import, see the CZ eTRM on MetaLink, Oracle’s technical support Web site.
Any concurrent program errors or warnings are in the FND log file. See Viewing Log Files.
The model synchronization concurrent programs include:
Check Model/Bill Similarity and Check All Models/Bills Similarity compare the imported model and the BOM Model to see if they are similar enough to synchronize. If key validation fields are not equal, then the requests generate a Model/Bill Similarity Check Report listing the fields with discrepancies. The user must resolve the discrepancies before synchronizing the models. This is an iterative process. Once the validation fields are corrected and the report no longer returns discrepancies, the Synchronize All Models can be run.
See Synchronizing Datafor more information.
The Check Model/Bill Similarity concurrent program compares a single configuration model with the BOM Model on which it is based, and produces a Model/Bill Similarity Check Report of discrepancies, if any. See Criteria for BOM Model Similarity for information about the validation criteria used by this concurrent program.
Use the procedure described in Running Configurator Concurrent Programs to run this concurrent program in the database containing the configuration model that must be checked.
Oracle Configurator Administrator or Oracle Configurator Developer
Navigator window > Oracle Configurator Administrator or Oracle Configurator Developer > Concurrent Programs: Schedule.
The following table describes the parameters for the Check Model/Bill Summary concurrent program
| Parameter | Description |
|---|---|
| Target Instance | A list of available instances, as defined by the Define Remote Server concurrent program. Select the instance that contains the source BOM Model with which the configuration model must be synchronized. |
| Folder | A list of folders (Configurator Developer Repository Folders) on the specified Target instance. Select the Folder that contains the Model to be checked against the BOM Model in the Target Instance. |
| List of Models | A list of all Models in the specified Folder on the specified Target instance. Select a Model from the list of values. |
A report is generated with the results. See Model/Bill Similarity Check Report.
To see if there are any errors or warnings for the concurrent program, you must examine the log file. See Viewing Log Files.
The Check All Model/Bill Similarity concurrent program compares all configuration modes in the local database instance with the BOM Models on which they are based, and produces a Model/Bill Similarity Check Report of discrepancies, if any. See Criteria for BOM Model Similarity for information about the validation criteria used by this concurrent program.
Use the procedure described in Running Configurator Concurrent Programs to run this concurrent program in the database containing the configuration models that need to be checked.
Oracle Configurator Administrator or Oracle Configurator Developer
Navigator window > Oracle Configurator Administrator or Oracle Configurator Developer > Concurrent Programs: Schedule.
The following table describes the parameters for the Check All Models/Bills Similarity concurrent program
| Parameter | Description |
|---|---|
| Target Instance | A list of available instances, as defined by the Define Remote Server concurrent program. Select the instance that contains the source BOM Model with which the configuration model must be synchronized. |
A report is generated with the results. See Model/Bill Similarity Check Report.
To see if there are any errors or warnings for the concurrent program, you must examine the log file. See Viewing Log Files.
The Synchronize All Models concurrent program modifies the configuration models on the local database instance to match the corresponding BOM Models in the Bills of Material schema that is to serve as the new import server or publication target. All imported models in the CZ schema of the current instance are synchronized with the corresponding structures of the bills on a target instance.
The Synchronize All Models concurrent program is run after all errors and discrepancies in the report generated by the Check All Models/Bills Similarity concurrent program have been corrected (see Model/Bill Similarity Check Report).
Use the procedure described in Running Configurator Concurrent Programs to run this concurrent program in the database containing the configuration model that must be synchronized.
Warning: Oracle Configurator Developers must not modify Models when the Synchronize All Models concurrent program is running.
Oracle Configurator Administrator
Navigator window > Oracle Configurator Administrator > Concurrent Programs: Schedule.
None
A report is generated with the results. See Model/Bill Similarity Check Report.
To see if there are any errors or warnings for the concurrent program, you must examine the log file. See Viewing Log Files.
The Model/Bill Similarity Check Report is generated every time you run the Check Model/Bill Similarity, Check All Models/Bills Similarity and Synchronize All Models concurrent programs. The report is displayed in a standard report log file generated by concurrent programs. For detailed information on concurrent processing reporting options, see the Oracle Application’s User’s Guide. For a list of validation criteria used to generate the report, see Criteria for BOM Model Similarity.
The Model/Bill Similarity Check Report contains a comprehensive message describing the list of problems that were encountered. The list starts with a message providing the version of the package and the run time. For example, the following message occurs when the BOM Model does not exist on the target server:
BOM Synchronization, version 115.15, started 2001/10/23/14:05:16, session run ID: 12017 There is no root bill for configuration model Name of the Model, unable to verify the model."
The following message occurs when there is a discrepancy with an Inventory Item.
BOM Synchronization, version 115.15, started 2001/10/29/14:05:16, session run ID: 12018 'PTO_OC1' with parent 'BOM_SYNCH' in configuration model 'BOM_SYNCH' cannot be matched with any inventory item.
Use this concurrent program to run all Populators defined for a specific Model. This concurrent program allows you to automate the process of updating a Models with data that has changed in the Item Master For information about Populators, see the Oracle Configurator Developer User’s Guide.
Do not confuse the Execute Populators in Model concurrent program with the Populate Configuration Models concurrent program. You run the Populate Configuration Models program to import data from Oracle Bills of Material. The Execute Populators in Model concurrent program updates Model structure that was created in Configurator Developer from data in the CZ schema's Item Master.
Use the procedure described in Running Configurator Concurrent Programs to run this concurrent program in the database containing the Models you want to repopulate.
Oracle Configurator Administrator or Oracle Configurator Developer
Navigator window > Oracle Configurator Administrator or Oracle Configurator Developer > Concurrent Programs: Schedule.
The following table describes the parameters for the Execute Populators in Model concurrent program
| Parameter | Description |
|---|---|
| Folder | A list of folders (Configurator Developer Repository Folders) on the current instance. Select the Folder that contains the Model in which you want Populators to be implemented. |
| Configuration Model ID | Select a Model from the list of values. Configuration Model ID is the same ID as the DEVL_PROJECT_ID. |
To see if there are any errors or warnings for the concurrent program, examine the log files. See Viewing Log Files.
Migration concurrent programs move data from a source CZ schema to an empty target CZ schema, or copy Models from one database instance to another development database instance.
The migration concurrent programs that move data from a source CZ schema to an empty target CZ schema are:
See Migrating Data from Another CZ Schema for prerequisites before running the migration concurrent programs.
The source database server must be defined and enabled as the remote server (see Server Administration Concurrent Programs).
The migration concurrent program that copies Models from one database instance to another development database instance is:
The Setup Configuration Data Migration concurrent program identifies the source database instance of a data migration.
Use the procedure described in Running Configurator Concurrent Programs to run this concurrent program in the target database into which you are migrating data.
Oracle Configurator Administrator
Navigator window > Oracle Configurator Administrator > Concurrent Programs: Schedule.
The following table describes the parameters for the Setup Configurator Migration concurrent program
| Parameter | Description |
|---|---|
| Source | Enter the name of the source database instance containing the data to be migrated, or select a source from the list of values defined by the Define Remote Server concurrent program. |
To see if there are any errors or warnings for the concurrent program, you must examine the log file (see Viewing Log Files Program).
In the Request concurrent program, view the log file to verify that no issues were found during the migration setup. Possible issues are:
Specified instance name does not have an associated database link
Associated database link is not functional
Database error occurred during the population of the control tables
Schema versions for the source and target databases are not the same
Difference in table structure
If any issues are reported, correct them and run Setup Configuration Data Migration again.
The Migrate Configurator Data concurrent program migrates the data from the source database instance to the target database instance. See Migrating Data for migration requirements.
Use the procedure described in Running Configurator Concurrent Programs to run this concurrent program in the empty target database into which you want to migrate data.
Oracle Configurator Administrator
Navigator window > Oracle Configurator Administrator > Concurrent Programs: Schedule.
The following table describes the parameters for the Migrate Configurator Data concurrent program
| Parameter | Description |
|---|---|
| Proceed when database not empty? | Enter Yes or No to this prompt. The migration should only be run against an empty target database. However, if for some reason the original migration does not complete successfully (for example a roll back segments problem), then the migration must be rerun after the roll back segments problem has been resolved. If the migration is repeated after such a correction, then the Proceed when database not empty? prompt can be answered Yes |
To see if there are any errors or warnings for the concurrent program, you must examine the log file. See Viewing Log Files.
The Functional Companion migration concurrent programs are:
These concurrent programs transform existing Functional Companion association data in the database to the new form of association data used for Configurator Extensions.
After you upgrade to the release of Oracle Configurator described in this document, you may need to migrate Functional Companions that were created with previous releases.
See the Oracle Configurator Installation Guide for background information.
The Migrate All Functional Companions concurrent program creates Configurator Extension associations for all Functional Companions in the database.
Note: You must perform some setup tasks before and after running this concurrent program. See the Oracle Configurator Installation Guide.
Oracle Configurator Administrator
Navigator window > Oracle Configurator Administrator > Concurrent Programs: Schedule.
None
If the migration finishes without errors, then Configurator Extension Rules (association data) are created for all Functional Companions in the database.
Warning: After you successfully migrate Functional Companions to Configurator Extensions, all existing Functional Companion data is logically deleted from the database.
To see if there are any errors or warnings for the concurrent program, you must examine the log file. See Viewing Log Files. If errors occur while processing a Model, the migration for that Model stops, and all transactions are rolled back. Processing continues for other Models in the database.
The Migrate Functional Companions for a Single Model concurrent program creates Configurator Extension associations for the Functional Companions associated with a specified Model.
Note: You must perform some setup tasks before and after running this concurrent program. See the Oracle Configurator Installation Guide.
Oracle Configurator Administrator
Navigator window > Oracle Configurator Administrator > Concurrent Programs: Schedule.
The following table describes the parameters for the Migrate Functional Companions for a Single Model concurrent program.
| Parameter | Description |
|---|---|
| Model ID | This is the Model that contains Functional Companions to be migrated. A list of all Models is available to select from, including those that do not contain Functional Companions at all and those that do not contain Functional Companions but whose child Models contain Functional Companions. If you choose a Model that does not contain Functional Companions then the migration still runs, but the migration log shows that the Model contained no Functional Companions. To migrate Functional Companions that are contained in any child Models, you must choose the option for deep migration. |
| Migrate Child Model’s FC | This is a Yes/No flag indicating whether you want the concurrent program to perform a deep migration. A Yes response means that all of the Functional Companions associated with the selected Model and its child Models will be migrated. |
If the migration finishes without errors, then Configurator Extension Rules (association data) are created for all Functional Companions associated with the selected Model.
Warning: After you successfully migrate Functional Companions for a Model to Configurator Extensions, the existing Functional Companion data for the Model is logically deleted from the database.
To see if there are any errors or warnings for the concurrent program, you must examine the log file. See Viewing Log Files. If no errors occur in the migration, then all transactions related to the specified Model are committed. If errors occur while processing the Model, the migration process stops and all transactions are rolled back.
The Model Management concurrent programs are:
Before the Model migration functionality was introduced, the persistent node ID was a consistent set of references to the same Model node. When Models are migrated to other development database instances, the persistent node ID becomes a one-to-many relationship, and can no longer be relied upon when identifying a saved configuration.
The Add Model Node Names to Configurations by Model Items concurrent program adds Model node names to saved configurations of a Model based on the Item or range of Items that you specify. It enables Oracle Configurator to uniquely identify Model nodes using their names rather than persistent_node_id values when restoring saved configurations. This is required to successfully restore configurations that were saved against migrated Models.
Alternatively, you can use the Add Model Node Names to Configurations by Model Product Key concurrent program to update saved configurations.
You run this concurrent program in the database instance where the migrated Models are located. To run this concurrent program, use the procedure described in the Running Configurator Concurrent Programs.
If the Model for a deleted publication exists, then the configurations for the deleted publication are upgraded using the configuration’s source Model. The example Saved Configurations and a Copied Model shows what can prevent Oracle Configurator from identifying all of the inputs in a saved configuration, resulting in a validation failure message.
Saved Configurations and a Copied Model
There are two Models, ModelA and its copy, ModelA’. In Oracle Configurator Developer, a new node called Option1 is added to ModelA. ModelA is published and a configuration is saved against ModelA. A new node Option1 is added to ModelA’, and ModelA’ is published.
When restoring an order saved against ModelA, a validation failure message appears because Oracle Configurator is unable to match Option1 that was added to ModelA’ with Option1 in ModelA.
Oracle Configurator Administrator or Configurator Administrator
Navigator window > Oracle Configurator Administrator > Concurrent Programs: Schedule.
The following table describes the parameters for the Add Model Node Names to Configurations by Model Items concurrent program.
The parameters you specify determine which published Models will be used to update the configurations. The values of the profile options CZ: Publication Usage and CZ: Publication Lookup Mode are also used to further refine the search for published Models. Oracle Configurator profile options are described in the Oracle Configurator Installation Guide.
| Parameter | Description |
|---|---|
| Organization | The Inventory Organization of the Item(s) you want to update |
| Model Inventory Item From | The beginning of a range of Models to be processed (To update saved configurations of a single Model, enter the same value for this parameter and the 'Model Inventory Item To' parameter.) |
| Model Inventory Item To | The end of a range of Models to be processed |
| Application | Enter a valid host application to update only configurations published for that application. |
| Configuration Begin Date | The date of the oldest configuration to be updated (use the format DD-MON-YYYY) |
| Configuration End Date | The date of the newest configuration to be updated (use the format DD-MON-YYYY) The default date is the system date. |
To see if there are any errors or warnings for the concurrent program, examine the CZ_DB_LOGS file. For details, see Viewing Log Files.
This concurrent program is similar to Add Model Node Names to Configurations by Model Items, but this program adds Model node names to saved configurations based on the Product Key that you specify, rather than an Item or range of Items.
You run this concurrent program in the database instance where the migrated Models are located. To run this program, use the procedure described in Running Configurator Concurrent Programs.
Oracle Configurator Administrator or Configurator Administrator
Navigator window > Oracle Configurator Administrator > Concurrent Programs: Schedule.
The following table lists the parameters for the Add Model Node Names to Configurations by Model Product Key concurrent program.
The parameters you specify determine which published Models will be used to update the configurations. The values of the profile options CZ: Publication Usage and CZ: Publication Lookup Mode are also used to further refine the search for published Models. Oracle Configurator profile options are described in the Oracle Configurator Installation Guide.
| Parameter | Description |
|---|---|
| Product key | The Item's Inventory Organization and Item number. For example: 204:5717. |
| Application | Enter a valid host application to update only configurations published for that application. |
| Configuration Begin Date | The date of the oldest configuration to be updated (use the format DD-MON-YYYY) |
| Configuration End Date | The date of the newest configuration to be updated (use the format DD-MON-YYYY) The default date is the system date. |
To see if there are any errors or warnings for the concurrent program, examine the log files. See Viewing Log Files.
This concurrent program migrates (copies) a configuration model its to another database instance. For details about what data is migrated, see Migrating Models.
For information about how data is synchronized when Models are migrated, see Synchronizing Migrated Model Data.
Before running this concurrent program, you must:
Define and enable the target instance as a remote server.
For details, see Define Remote Server and Enable Remote Server
Note: Models cannot be migrated to a remote publication target instance. For details, see Convert Publication Target Instance to Development Instance.
Identify the Models you want to migrate in Oracle Configurator Developer.
For details, see the Oracle Configurator Developer User’s Guide.
When you identify the Models to be migrated, Configurator Developer generates a Migration Group ID. You specify this value for the Migration Group parameter when running the Migrate Models concurrent program.
While the Migrate Models concurrent program is running, the specified root Model and all of its referenced Models are locked in Configurator Developer. If the program cannot lock any of the Models (for example, because they are locked by another user), the program fails and displays an error. Model locking is explained in the Oracle Configurator Developer User’s Guide.
To migrate Models, the target and source instances must be at the same Oracle Configurator patch level, and the same sets of languages must be installed on each instance.
When the Migrate Models concurrent program completes successfully, review the log file to review the results of the migration. For details, see Synchronizing Migrated Model Data.
Important: After running the Migrate Models program, review Restoring Saved Configurations of Migrated Models for important information.
Oracle Configurator Administrator
Navigator window > Oracle Configurator Administrator > Concurrent Programs: Schedule.
The following table describes the parameters for the Migrate Models concurrent program.
| Parameter | Description |
|---|---|
| Migration Group | The Migration Group ID that is generated when you identify the Model(s) to be migrated in Oracle Configurator Developer. This number identifies the Models to be migrated from the source instance and the destination folder on the target instance. |
To see if there are any errors or warnings for the concurrent program, examine the log files. See Viewing Log Files.
The publication synchronization concurrent programs are:
These concurrent programs resolve data inconsistencies that result when a source or target database instance is cloned or migrated from a different database instance.
Publication synchronization updates publication record pointers to servers, checks overlaps of applicability parameters and item definitions, and realigns relationships between publication records that became invalid.
Before running these concurrent programs, the target database instance must be defined and enabled to establish the database link. See Server Administration Concurrent Programs for information about defining and enabling a remote server.
The Synchronize Cloned Target Data ensures that publication data on the cloned publication target database instance matches that on the publication source database instance. For example, you have published models and are working with two database instances: a publication source and a publication target. You then clone the publication target. The publication data on the cloned publication target does not recognize the publication source until you run the Synchronize Cloned Target Data. For more information see Synchronizing Publication Data after a Database Instance is Cloned.
If the publication records on the target exist on the source database instance, then the SERVER_ID of the target publication is updated and a new publication record is created on the source database instance with updated references.
Note: Do not:
Publish or republish Models when the synchronization concurrent programs are running
Synchronize publications when publishing or republishing Models
The Synchronize Cloned Target Data concurrent program must be run in the database instance that serves as the publication source for the cloned publication target. Use the procedure described in Running Configurator Concurrent Programs to run this concurrent program.
Oracle Configurator Administrator
Navigator window > Oracle Configurator Administrator > Concurrent Programs: Schedule.
The following table describes the parameters for Synchronize Cloned Target Data.
| Parameter | Description |
|---|---|
| Target database instance | Enter the name of the cloned publication target database instance, or select a cloned publication target from the list of values defined by the Define Remote Server concurrent program. |
To see if there are any errors or warnings for the concurrent program, you must examine the log file. See Viewing Log Files.
If the Model and UI in the target database instance publication record do not match the Model and UI in the source database instance publication record from which the Synchronize Cloned Target Data concurrent program is running, then the program logs an error, and the concurrent program terminates. The Model Publication page in Oracle Configurator Developer displays Error in the Status column (see the Oracle Configurator Developer User’s Guide).
The Synchronize Cloned Source Data ensures that publication data on the publication target database instance points to the cloned publication source database instance. For example, you have published models and are working with two database instances: a publication source and a publication target. You then clone the publication source. The publication data on the publication target does not recognize the publication source until you run the Synchronize Cloned Source Data. For more information see Example of Synchronizing Publication Data on a Cloned Source.
Before running the concurrent program, the cloned source database instance must be defined and enabled to establish the database link. See Define Remote Server and Enable Remote Server. This concurrent program is run from the cloned source database instance.
Oracle Configurator Administrator
Navigator window > Oracle Configurator Administrator > Concurrent Programs: Schedule.
The following table describes the parameters for the Synchronize Cloned Source Data concurrent program
| Parameter | Description |
|---|---|
| Decommission Original Source? (Yes/No) | If the original source server is decommissioned, then the CZ_SERVERS.SOURCE_SERVER_FLAG on the target is updated to no longer point to the original source server. If the original source server is not decommissioned, then the publication entries are logically deleted from the tables on the cloned source server to avoid conflicts with the original publication source. |
To see if there are any errors or warnings for the concurrent program, you must examine the log file. See Viewing Log Files.
You may want to specify only a group of tables from which extracted data is loaded into the import tables. The CZ_XFR_TABLES.DISABLED field determines if a specific table is enabled or disabled for import.
Oracle Configurator Administrator
Navigator window > Oracle Configurator Administrator > Concurrent Programs: Schedule.
All parameters for this concurrent program are required.
The following table describes the parameters Import Data into Specific Tables concurrent program
Importing Data into a Specific Table
The following is an example that enables a table for importing data.
Destination Table Name: CZ_ITEM_MASTERS Import Group: Import Enable:Y
After specifying the parameters click OK. In the Submit Request window, click Submit.
To see if there are any errors or warnings for the concurrent program, you must examine the log file. See Viewing Log Files.
You can display the tables that are currently enabled for import.
Oracle Configurator Administrator
Navigator window > Oracle Configurator Administrator > Concurrent Programs: Schedule.
The following table describes the parameters Show Tables to be imported requested task.
| Parameter | Description |
|---|---|
| Table Name | Enter the table in the CZ schema that you are querying the import disability. |
| Import Group: | Enter either Extract, Generic, or Import for which you want to display the Import Enable setting. |
The following example displays the current Disable setting for the CZ_XFR_TABLES.
Table Name: CZ_ITEM_MASTERS Phase Name: Import
After specifying the parameters click OK. In the Submit Request window, click Submit.
To see if there are any errors or warnings for the concurrent program, examine the log files. See Viewing Log Files. The return for Show Tables to be Imported:
Return from the Show Tables to be Imported Concurrent Program
DST_TABLE = CZ_ITEM_MASTERSXFR_GROUP = IMPORTDISABLED_FLAG = 0