Skip Headers

Oracle Configurator Implementation Guide
Release 12.1 for
Part Number E14322-03
Go to Table of Contents
Go to previous page
Go to next page


Intended Audience

Welcome to Release 12.1 of the Oracle Configurator Implementation Guide .

This guide presents tasks and information useful in implementing Oracle Configurator.

See the Oracle Configurator Installation Guide for installation information, the Oracle Configurator Developer User’s Guide for information about developing configuration models in Oracle Configurator Developer, the Oracle Configurator Modeling Guide for information about designing configuration models that are best suited to Oracle Configurator, Oracle Configurator Methodologies for information and tasks useful in implementing Oracle Configurator, the Oracle Configurator Extensions and Interface Object Developer’s Guide for information about writing Configurator Extensions, the Oracle Configurator Constraint Definition Language Guide for information about writing Statement Rules, and the Oracle Configurator Performance Guide for information needed for optimizing runtime performance of Oracle Configurator.

This guide is intended for anyone responsible for supporting the use of Oracle Configurator. This includes supporting the development environment (Oracle Configurator Developer) as well as the runtime environment that is created for deployment.

Ordinarily, the tasks presented in this book are performed by a Database Administrator (DBA) or an Oracle Configurator implementer with DBA experience.

See Related Information Sources for more Oracle E-Business Suite product information.

Deaf/Hard of Hearing Access to Oracle Support Services

To reach Oracle Support Services, use a telecommunications relay service (TRS) to call Oracle Support at 1.800.223.1711. An Oracle Support Services engineer will handle technical issues and provide customer support according to the Oracle service request process. Information about TRS is available at, and a list of phone numbers is available at

Documentation Accessibility

Our goal is to make Oracle products, services, and supporting documentation accessible to all users, including users that are disabled. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Accessibility standards will continue to evolve over time, and Oracle is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For more information, visit the Oracle Accessibility Program Web site at

Accessibility of Code Examples in Documentation

Screen readers may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, some screen readers may not always read a line of text that consists solely of a bracket or brace.

Accessibility of Links to External Web Sites in Documentation

This documentation may contain links to Web sites of other companies or organizations that Oracle does not own or control. Oracle neither evaluates nor makes any representations regarding the accessibility of these Web sites.


1  Implementation Tasks

This chapter presents an overview of all known tasks in an Oracle Configurator implementation, including custom tasks.

2  Configurator Architecture

This chapter describes the elements of the Oracle Configurator product and how they fit together.

3  Database Instances

This chapter describes the uses to which databases are put when implementing Oracle Configurator, and specifics about using multiple database instances.

4  The CZ Schema

This chapter describes the basic characteristics of the CZ schema, the schema settings and how they are used, and provides some schema maintenance tips.

5  Populating the CZ Schema

This chapter provides an overview of why and how to import data from Oracle Applications and non-Oracle Applications databases. It describes the import processes, the import tables used during data import, how to import data into the CZ schema, data import verification, the process for refreshing or updating imported data, and customizing data import.

6  Migrating Data

This chapter describes how to migrate a CZ Release 12 instance into an empty CZ instance, and how to migrate Model data from one instance to another development instance.

7  Synchronizing Data

This chapter describes when and how data is synchronized. This includes synchronizing BOM data after the import server has changed and synchronizing publication data after a database has been cloned.

8  CZ Schema Maintenance

This chapter explains how to maintain data when it exists in more than one place and is potentially unsynchronized.

9  Session Initialization

This chapter describes the format and parameters of the initialization message for the runtime Oracle Configurator.

10  Session Termination

This chapter describes the format and parameters of the termination message for the runtime Oracle Configurator Servlet.

11  Batch Validation

This chapter describes using Oracle Configurator in a programmatic mode.

12  Custom Integration

This chapter explains how to modify certain Oracle Configurator files as well as the purpose of the files and where they can be found.

13  Pricing and ATP in Oracle Configurator

This chapter provides an overview of how pricing works in a runtime Oracle Configurator.

14  Multiple Language Support

This chapter explains how Item descriptions are entered in Oracle Applications and can be displayed in multiple languages when deploying an Oracle Configurator User Interface.

15  Controlling the Development Environment
16  Publishing Configuration Models

This chapter explains the database processes for publishing configuration models to make them available to host applications.

17  Programmatic Tools for Development

This chapter describes a set of programmatic tools (PL/SQL procedures and functions) that may be useful in developing a configuration model and deploying a runtime Oracle Configurator.

18  Programmatic Tools for Maintenance

This chapter describes a set of programmatic tools (PL/SQL procedures) that you can use primarily to maintain a deployed runtime Oracle Configurator.

19  User Interface Deployment

This chapter describes the activities required to complete the User Interface deployment of a runtime Oracle Configurator embedded in a host Oracle Application such as Order Management or iStore.

20  Deployment Considerations

This chapter describes the strategies you should consider when you are ready to complete the deployment of a runtime Oracle Configurator.

21  Managing Configurations

This chapter describes the data structures produced by Oracle Configurator during a configuration session, and how to manage the life cycle of a configuration.

A  Terminology

This appendix defines the terms that found in the Oracle Configurator Implementation Guide that are not defined in the Glossary.

B  Common Tasks

This appendix describes certain tasks that may be required while implementing an Oracle Configurator.

C  Concurrent Programs

This appendix describes the concurrent programs available to either the Oracle Configurator Administrator or Oracle Configurator Developer responsibility.

D  CZ Subschemas

This appendix lists the CZ tables that make up each of the subschemas in the CZ schema. For table details, see the CZ eTRM on MetaLink, Oracle’s technical support Web site.

E  Code Examples
Common Glossary for Oracle Configurator

Related Information Sources

Important: There is new functionality available for the Runtime Oracle Configurator when using the Fusion Configurator Engine (FCE). The FCE is an alternative to the configuration engine described in this document. For all information about the FCE, see the Oracle Configurator Fusion Configurator Engine Guide.

For more information, see the following resources:

Integration Repository

The Oracle Integration Repository is a compilation of information about the service endpoints exposed by the Oracle E-Business Suite of applications. It provides a complete catalog of Oracle E-Business Suite's business service interfaces. The tool lets users easily discover and deploy the appropriate business service interface for integration with any system, application, or business partner.

The Oracle Integration Repository is shipped as part of the E-Business Suite. As your instance is patched, the repository is automatically updated with content appropriate for the precise revisions of interfaces in your environment.

Do Not Use Database Tools to Modify Oracle E-Business Suite Data

Oracle STRONGLY RECOMMENDS that you never use SQL*Plus, Oracle Data Browser, database triggers, or any other tool to modify Oracle E-Business Suite data unless otherwise instructed.

Oracle provides powerful tools you can use to create, store, change, retrieve, and maintain information in an Oracle database. But if you use Oracle tools such as SQL*Plus to modify Oracle E-Business Suite data, you risk destroying the integrity of your data and you lose the ability to audit changes to your data.

Because Oracle E-Business Suite tables are interrelated, any change you make using an Oracle E-Business Suite form can update many tables at once. But when you modify Oracle E-Business Suite data using anything other than Oracle E-Business Suite, you may change a row in one table without making corresponding changes in related tables. If your tables get out of synchronization with each other, you risk retrieving erroneous information and you risk unpredictable results throughout Oracle E-Business Suite.

When you use Oracle E-Business Suite to modify your data, Oracle E-Business Suite automatically checks that your changes are valid. Oracle E-Business Suite also keeps track of who changes information. If you enter information into database tables using database tools, you may store invalid information. You also lose the ability to track who has changed your information because SQL*Plus and other database tools do not keep a record of changes.