Welcome to Release 12.2 of the Oracle Configurator Constraint Definition Language Guide.
This guide describes the semantics and syntax of the Constraint Definition Language, or CDL. Use this document together with the other books in the Oracle Configurator documentation set to prepare for and implement rule definitions that are entered as text rather than created interactively in Oracle Configurator Developer. Typically, CDL is used to create Statement Rules in Configurator Developer. Rules can also be defined in another environment and then imported into the CZ schema.
This preface describes how the guide is organized, who the intended audience is, and how to interpret the typographical conventions and syntax notation.
This guide is intended for anyone responsible for creating and supporting rule definitions written in CDL, including Statement Rules in Oracle Configurator Developer. This guide assumes that you understand the kinds and behavior of configuration rules that are available in Oracle Configurator.
See Related Information Sources for more Oracle Applications product information.
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.
Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.
This chapter provides a high-level overview of CDL and the criteria for valid, executable rule definitions.
This chapter introduces the principles of defining configuration rules using CDL.
This chapter introduces an example Model that is used to illustrate correct CDL semantics and syntax.
This chapter presents detailed information about the elements of CDL.
For an overview of CDL elements, as well as details about case sensitivity and quotation marks, see Anatomy of a Configuration Rule Written in CDL.
For syntax abstracts, see Notation Used in Presenting CDL Grammar.
This appendix provides a programmer’s reference of CDL syntax.
This appendix provides additional information about the Oracle Configurator parser’s expectations and requirements during rule validation.
Important: The Fusion Configurator Engine (FCE) is an alternative to the configuration engine described in this document, and provides significant enhancements. For all information about the Fusion Configurator Engine, see the Oracle Configurator Fusion Configurator Engine Guide.
For a full list of documentation resources for Oracle Configurator, see the Oracle Configurator Release Notes for this release.
For a full list of documentation resources for Oracle Applications, see Oracle Applications Documentation, on the Oracle Technology Network.
Additionally, be sure you are familiar with current release or patch information for Oracle Configurator on the Oracle Support Web site.
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.
You can navigate to the Oracle Integration Repository through Oracle E-Business Suite Integrated SOA Gateway.
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.