alrtrm

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CAUTION!This document contains proprietary,

confidential information that is the exclusiveproperty of Oracle Corporation.

See back cover forimportant information.

��

��

��

��

Oracle� Alert TechnicalReference Manual RELEASE 11iVOLUME 1

December 1999

Oracle� Alert Technical Reference ManualRelease 11iVolume 1

To order this book, ask for Part No. A80845–01

Copyright � 1994, 1999. Oracle Corporation. All rights reserved.

Major Contributors: Kristi Jentoff–Nilsen

Contributors: Anne Carlson, Martin Taylor

This Technical Reference Manual (TRM) in any form, software or printed matter, contains proprietary information of Oracle Corporation; it isprovided under an Oracle Corporation agreement containing restrictions on use and disclosure and is also protected by copyright, patent, andother intellectual property law. Restrictions applicable to this TRM include, but are not limited to: (a) exercising either the same degree of care tosafeguard the confidentiality of this TRM as you exercise to safeguard the confidentiality of your own most important Confidential Information ora reasonable degree of care, whichever is greater; (b) maintaining agreements with your employees and agents that protect the ConfidentialInformation of third parties such as Oracle Corporation and instructing such employees and agents of these requirements for this TRM; (c)restricting disclosure of this TRM to those of your employees who have a ”need to know” consistent with the purposes for which this TRM wasdisclosed to you; (d) maintaining this TRM at all times on your premises; (e) not removing or destroying any proprietary or confidential legendsor markings placed upon this TRM in whatever form, software or printed matter; and (f) not reproducing or transmitting this TRM in any form orby any means, electronic or mechanical, for any purpose, without the express written permission of Oracle Corporation. You should not use thisTRM in any form, software or printed matter, to create software that performs the same or similar functions as any Oracle Corporation products. The information in this TRM is subject to change without notice. If you find any problems in the TRM in any form, software or printed matter,please report them to us in writing. Oracle Corporation does not warrant that this TRM is error–free. This TRM is provided to customer ”as–is”with no warranty of any kind. This TRM does not constitute Documentation as that term is defined in Oracle’s agreements.

Reverse engineering of the Programs (software and documentation) associated with this TRM are prohibited. The Programs associated with thisTRM are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be licensee’sresponsibility to take all appropriate fail–safe, back–up, redundancy and other measures to ensure the safe use of such applications if thePrograms are used for such purposes, and Oracle disclaims liability for any damages caused by such use of the Programs.

Restricted Rights LegendThis TRM and the Programs associated with this TRM delivered subject to the DOD FAR Supplement are ’commercial computer software’ anduse, duplication and disclosure of the TRM and the Programs associated with this TRM shall be subject to the licensing restrictions set forth in theapplicable Oracle license agreement. Otherwise, this TRM and the Programs associated with this TRM delivered subject to the FederalAcquisition Regulations are ’restricted computer software’ and use, duplication and disclosure of the TRM and the Programs associated with thisTRM shall be subject to the restrictions in FAR 52.227–14, Rights in Data –– General, including Alternate III (June 1987). Oracle Corporation, 500Oracle Parkway, Redwood City, CA 94065.

Oracle is a registered trademark, and Context, Financial Analyzer, Oracle7, Oracle8, Oracle Alert, Oracle Applications, Oracle Discoverer, OracleFinancials, Object Library, Oracle Work in Process, Oracle Workflow, SmartClient, PL/SQL, SQL*Calc, SQL*Forms, SQL*Loader, SQL*Menu,SQL*Net, SQL*Plus, SQL*Report, SQL*ReportWriter, Oracle Web Employees, and SQL*QMX are trademarks or registered trademarks of OracleCorporation. All other company or product names are mentioned for identification purposes only, and may be trademarks of their respective owners..

T

CAUTION

his Technical Reference Manual in any form –– software orprinted matter –– contains proprietary, confidential information

that is the exclusive property of Oracle Corporation. If you do nothave a valid contract with Oracle for the use of this Technical ReferenceManual or have not signed a non–disclosure agreement with Oraclecovering this Technical Reference Manual, then you received thisdocument in an unauthorized manner and are not legally entitled topossess or read it.

Use, duplication, and disclosure are subject to restrictions stated inyour contract with Oracle Corporation.

iContents

Oracle Proprietary, Confidential Information––Use Restricted by Contract

Contents

Chapter 1 Introduction 1 – 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 2 High–Level Design 2 – 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview of High–Level Design 2 – 2. . . . . . . . . . . . . . . . . . . . . . . . . . Summary Database Diagram 2 – 5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . Database Diagrams 2 – 9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Public Table List 2 – 15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Forms and Table View List 2 – 18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Internal View List 2 – 19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Module List 2 – 20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 3 Detailed Design 3 – 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview of Detailed Design 3 – 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table and View Definitions 3 – 3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Index

ii Oracle Alert Technical Reference Manual


Reader’s Comment Form

Oracle Alert Technical Reference ManualA80845–01

Oracle Corporation welcomes your comments and suggestions on the quality and usefulnessof this publication. Your input is an important part of the information we use for revision.

• Did you find any errors?

• Is the information clearly presented?

• Do you need more information? If so, where?

• Are the examples correct? Do you need more examples?

• What features did you like most about this manual? What did you like least about it?

If you find any errors or have any other suggestions for improvement, please indicate the topic, chapter,and page number below:

Please send your comments to:

Oracle Applications Documentation ManagerOracle Corporation500 Oracle ParkwayRedwood Shores, CA 94065 USAPhone: (650) 506–7000 Fax: (650) 506–7200

If you would like a reply, please give your name, address, and telephone number below:

Thank you for helping us improve our documentation.

C H A P T E R

1T

1 – 1Introduction


Introduction

he Oracle Payables Technical Reference Manual provides theinformation you need to understand the underlying structure of

Oracle Alert. After reading this manual, you should be able to convertyour existing applications data, integrate your existing applicationswith your Oracle Alert application, and write custom reports for yourOracle Alert application, as well as read data that you need to performother tasks.

This chapter introduces you to the Oracle Payables Technical ReferenceManual, and explains how to use it.

1 – 2 Oracle Alert Technical Reference Manual


Introduction

At Oracle, we design and build applications using Oracle Designer, oursystems design technology that provides a complete environment tosupport developers through all stages of a systems life cycle. Becausewe use a repository–based design toolset, all the information regardingthe underlying structure and processing of our applications is availableto us online. Using Oracle Designer, we can present this information toyou in the form of a technical reference manual.

This Oracle Payables Technical Reference Manual contains detailed,up–to–date information about the underlying structure of Oracle Alert.As we design and build new releases of Oracle Alert application, weupdate our Oracle Designer repository to reflect our enhancements. Asa result, we can always provide you with an Oracle Payables TechnicalReference Manual that contains the latest technical information as of thepublication date. Note that after the publication date we may haveadded new indexes to Oracle Alert to improve performance.

About this Manual

This manual describes the Oracle Applications Release 11i data model,as used by Oracle Alert; it discusses the database we include with afresh install of Oracle Applications Release 11i. If you have not yetupgraded to Release 11i, your database may differ from the databasewe document in this book.

If you have upgraded from a previous release, you might find it helpfulto use this manual with the appropriate Oracle Applications ProductUpdate Notes manual. The product update notes list database changesand seed data changes in Oracle Alert between releases. The OracleApplications Product Update Notes Release 11 manual describes thechanges between Release 10.7 and Release 11, and the OracleApplications Product Update Notes Release 11i manual describes thechanges between Release 11 and Release 11i.

You can contact your Oracle representative to confirm that you havethe latest technical information for Oracle Alert. You can also useOracleMetaLink which is accessible through Oracle’s Support WebCenter (http://www.oracle.com/support/elec_sup).

Finding the Latest Information

The Oracle Payables Technical Reference Manual contains the latestinformation as of the publication date. For the latest information we

1 – 3Introduction


encourage you to use OracleMetaLink which is accessible throughOracle’s Support Web Center (http://www.oracle.com/support/elec_sup).

Audience

The Oracle Payables Technical Reference Manual provides useful guidanceand assistance to:

• Technical End Users

• Consultants

• Systems Analysts

• System Administrators

• Other MIS professionals

This manual assumes that you have a basic understanding ofstructured analysis and design, and of relational databases. It alsoassumes that you are familiar with Oracle Application Object Libraryand your Oracle Alert application. If you are not familiar with theabove products, we suggest that you attend one or more of the trainingclasses available through Oracle Education (see: Other InformationSources: page 1 – 7).

How This Manual is Organized

This manual contains two major sections, High–Level Design andDetailed Design.

High–Level Design

This section, Chapter 2, contains database diagrams and lists eachdatabase table and view that Oracle Alert uses. This chapter also has alist of modules.

Detailed Design

This section, Chapter 3, contains a detailed description of the OracleAlert database design, including information about each database tableand view you might need for your custom reporting or other datarequirements.



How to Use This Manual

The Oracle Payables Technical Reference Manual is a single, centralizedsource for all the information you need to know about the underlyingstructure and processing of your Oracle Alert application. Forexample, you can use this manual when you need to:

• Convert existing application data

• Integrate your Oracle Alert application with your otherapplications systems

• Write custom reports

• Define alerts against Oracle Applications tables

• Configure your Oracle Self–Service Web Applications

• Create views for decision support queries using query tools

• Create business views for Oracle Discoverer

You need not read this manual cover to cover. Use the table of contentsand index to quickly locate the information you need.

How Not To Use This Manual

Do not use this manual to plan modifications

You should not use this manual to plan modifications to your OracleAlert application. Modifying Oracle Alert limits your ability toupgrade to future releases of your Oracle Alert application. Inaddition, it interferes with our ability to give you the high–qualitysupport you deserve.

We have constructed your Oracle Alert application so that you cancustomize it to fit your needs without programming, and you canintegrate it with your existing applications through interface tables.However, should you require program modifications, you shouldcontact our support team (see: Other Information Sources: page 1 – 7).They can put you in touch with Oracle Services, the professionalconsulting organization of Oracle. Their team of experiencedapplications professionals can make the modifications you need whileensuring upward compatibility with future product releases.

☞

1 – 5Introduction


Do not write data into non–interface tables

Oracle reserves the right to change the structure of Oracle Applicationstables, and to change the meaning of, add, or delete lookup codes anddata in future releases. Do not write data directly into or change datain non–interface tables using SQL*Plus or other programming toolsbecause you risk corrupting your database and interfering with ourability to support you.

Moreover, this version of the Oracle Payables Technical Reference Manualdoes not contain complete information about the dependenciesbetween Oracle Alert applications tables. Therefore, you should writedata into only those tables we identify as interface tables. If you writedata into other non–interface tables, you risk violating your dataintegrity since you might not fulfill all the data dependencies in yourOracle Alert application.

You are responsible for the support and upgrade of the logic within theprocedures that you write, which may be affected by changes betweenreleases of Oracle Applications.

Do not rely on upward compatibility of the data model

Oracle reserves the right to change the structure of Oracle Alertapplication tables, and to change the meaning of, add, or delete lookupcodes and other data in future releases. We do not guarantee theupward compatibility of the Oracle Alert application data model. Forexample, if you write a report that identifies concurrent requests thatend in Error status by selecting directly from Oracle Application ObjectLibrary tables, we do not guarantee that your report will work properlyafter an upgrade.

About Oracle Application Object Library

Oracle Application Object Library is a collection of pre–builtapplication components and facilities for building Oracle Applicationsand extensions to Oracle Applications. Oracle Application CodingStandards use the Oracle Application Object Library and containsshared components including but not limited to –– forms, subroutines,concurrent programs and reports, database tables and objects,messages, menus, responsibilities, flexfield definitions and online help.

Attention: Oracle does not support any customization ofOracle Application Object Library tables or modules, not even



by Oracle consultants. (Oracle Application Object Librarytables generally have names beginning with FND_%.)

Accordingly, this manual does not contain detailed informationabout most Oracle Application Object Library tables used byyour Oracle Alert application.

A Few Words About Terminology

The following list provides you with definitions for terms that we usethroughout this manual:

Relationship

A relationship describes any significant way in which two tables maybe associated. For example, rows in the Journal Headers table mayhave a one–to–many relationship with rows in the Journal Lines table.

Database Diagram

A database diagram is a graphic representation of application tablesand the relationships between them.

Summary Database Diagram

A summary database diagram shows the most important applicationtables and the relationships between them. It omits tables andrelationships that contribute little to the understanding of theapplication data model. Typically, a summary database diagram showstables that contain key reference and transaction data.

Module

A module is a program or procedure that implements one or morebusiness functions, or parts of a business function, within anapplication. Modules include forms, concurrent programs and reports,and subroutines.

Application Building Block

An application building block is a set of tables and modules (forms,reports, and concurrent programs) that implement closely–relateddatabase objects and their associated processing. Said another way, anapplication building block is a logical unit of an application.

1 – 7Introduction


QuickCodes

QuickCodes let you define general purpose, static lists of values forwindow fields. QuickCodes allow you to base your program logic onlookup codes while displaying user–friendly names in a list of valueswindow. QuickCodes simplify name and language changes by lettingyou change the names your end users see, while the codes in yourunderlying programs remain the same.

Form

A form is a module comprised of closely related windows that are usedtogether to perform a task. For example, the Enter Journals form inOracle General Ledger includes the Enter Journals window, the Batchwindow, and the More Actions window among others. The EnterJournals window is the main window, and from it, you can use buttonsto navigate to other windows in the form. The form name usuallycorresponds to the main window in the form, and is frequently awindow you open directly from the Navigator.

Other Information Sources

There are additional information sources, including otherdocumentation, training and support services, that you can use toincrease your knowledge and understanding of Oracle Designer, OracleApplication Object Library, and your Oracle Alert application. Wewant to make these products easy for you and your staff to understandand use.

Oracle Designer Online Documentation

The online help for Oracle Designer describes how you can use OracleDesigner for your development needs.

Oracle Applications Developer’s Guide

This guide contains the coding standards followed by the OracleApplications development staff. It describes the Oracle ApplicationObject Library components needed to implement the OracleApplications user interface described in the Oracle Applications UserInterface Standards. It also provides information to help you build yourcustom Developer forms so that they integrate with OracleApplications.



Oracle Applications User Interface Standards

This manual contains the user interface (UI) standards followed by theOracle Applications development staff. It describes the UI for theOracle Applications products and how to apply this UI to the design ofan application built using Oracle Forms 6.

Oracle Self–Service Web Applications Online Documentation

This documentation describes how Oracle Self–Service WebApplications enable companies to provide a self–service and secureWeb interface for employees, customers, and suppliers. Employees canchange their personal status, submit expense reports, or requestsupplies. Customers can check on their orders, and suppliers can shareproduction schedules with their trading partners. This documentationis available in HTML only.

Oracle Applications Flexfields Guide

This guide provides flexfields planning, setup and referenceinformation for the Oracle Alert implementation team, as well as forusers responsible for the ongoing maintenance of Oracle Applicationsproduct data. This manual also provides information on creatingcustom reports on flexfields data.

Oracle Workflow Guide

This manual explains how to define new workflow business processesas well as customize existing Oracle Applications–embedded workflowprocesses. You also use this guide to complete the setup stepsnecessary for any Oracle Applications product that includesworkflow–enabled processes.

Oracle Alert User Guide

This manual explains how to define periodic and event alerts tomonitor the status of your Oracle Applications data.

Multiple Reporting Currencies in Oracle Applications

If you use the Multiple Reporting Currencies feature to report andmaintain accounting records in more than one currency, use thismanual before implementing Oracle Alert. This manual detailsadditional steps and setup considerations for implementing OracleAlert with this feature.

1 – 9Introduction


Oracle Manufacturing, Distribution, Sales and Service OpenInterfaces Manual

This manual contains up–to–date information about integrating withother Oracle Manufacturing applications and with your other systems.This documentation includes open interfaces found in OracleManufacturing.

Oracle Applications Messages Manual

The Oracle Applications Messages Manual contains the text ofnumbered error messages in Oracle Applications. (Oracle Applicationsmessages begin with the prefix ”APP–”.) It also provides informationon the actions you take if you get a message. Note: This manual isavailable only in HTML format.

Installation and System Administration

Oracle Applications Installation Release Notes

This manual contains a road map to the components of the release,including instructions about where to access the Release 11idocumentation set.

Oracle Applications Concepts

Designed to be the first book the user reads to prepare for aninstallation of Oracle Applications. It explains the technology stack,architecture, features and terminology for Oracle Applications Release11i. This book also introduces the concepts behind and major uses ofApplications–wide features such as MRC, BIS, languages and charactersets (NLS, MLS), BIS, Self–Service Web Applications and so on.

Installing Oracle Applications

Describes the One–Hour Install process, the method by which Release11i will be installed. This manual includes all how–to steps, screenshots and information about Applications–wide post–install tasks.

Using the AD Utilities

This manual contains how–to steps, screen shots and other informationrequired to run the various AD utilities such as AutoInstall, AutoPatch,AD Administration, AD Controller, Relink and so on. It also containsinformation about when and why you should use these utilities.



Upgrading Oracle Applications

This manual contains all the product specific pre– and post–upgradesteps that are required to upgrade products from Release 10.7 (NCA,SC and character–mode) or Release 11 of Oracle Applications. Thismanual also contains an overview chapter that describes all the tasksnecessary to prepare and complete a upgrade of Oracle Applications.

Oracle Applications System Administrator’s Guide

This manual provides planning and reference information for theOracle Applications System Administrator. It contains information onhow to define security, customize menus and manage concurrentprocessing.

Oracle Applications Product Update Notes

This book contains a summary of each new feature we added sinceRelease 11, as well as information about database changes and seeddata changes that may affect your operations or any custom reportsyou have written. If you are upgrading from Release 10.7 you alsoneed to read Oracle Applications Product Update Notes Release 11.

Oracle Self–Service Web Applications Implementation Manual

This manual describes the setup steps for Oracle Self–Service WebApplications and the Web Applications Dictionary.

Oracle Applications Implementation Wizard User Guide

If you are implementing more than one Oracle product, you can use theOracle Applications Implementation Wizard to coordinate your setupactivities. This guide describes how to use the wizard.

Other Information

Training

Oracle Education offers a complete set of training courses to help youand your staff master Oracle Applications. We can help you develop atraining plan that provides thorough training for both your projectteam and your end users. We will work with you to organize coursesappropriate to your job or area of responsibility.

1 – 11Introduction


Training professionals can show you how to plan your trainingthroughout the implementation process so that the right amount ofinformation is delivered to key people when they need it the most. Youcan attend courses at any one of our many Educational Centers, or youcan arrange for our trainers to teach at your facility. In addition, wecan tailor standard courses or develop custom courses to meet yourneeds.

Support

From on–site support to central support, our team of experiencedprofessionals provides the help and information you need to keep yourOracle Alert application working for you. This team includes yourTechnical Representative, Account Manager, and Oracle’s large staff ofconsultants and support specialists with expertise in your businessarea, managing an Oracle server, and your hardware and softwareenvironment.



About Oracle

Oracle Corporation develops and markets an integrated line ofsoftware products for database management, applicationsdevelopment, decision support, and office automation, as well asOracle Applications, an integrated suite of more than 75 softwaremodules for financial management, supply chain management,manufacturing, project systems, human resources, and sales andservice management.

Oracle products are available for mainframes, minicomputers, personalcomputers, network computers, and personal digital assistants,allowing organizations to integrate different computers, differentoperating systems, different networks, and even different databasemanagement systems, into a single, unified computing and informationresource.

Oracle is the world’s leading supplier of software for informationmanagement, and the world’s second largest software company.Oracle offers its database, tools, and applications products, along withrelated consulting, education, and support services, in over 145countries around the world.

Thank You

Thanks for using Oracle Alert application and this technical referencemanual!

We appreciate your comments and feedback. At the back of thismanual is a Reader’s Comment Form that you can use to explain whatyou like or dislike about your Oracle Alert application or this technicalreference manual. Mail your comments to the following address or callus directly at (650) 506–7000.

Oracle Applications Documentation ManagerOracle Corporation500 Oracle ParkwayRedwood Shores, California 94065 U.S.A.

Or, send electronic mail to [email protected] .

C H A P T E R

2T

2 – 1High–Level Design


High–Level Design

his chapter presents a high–level design for Oracle Alert thatsatisfies the business needs we specify during Strategy and

Analysis. It contains database diagrams for Oracle Alert applicationbuilding blocks, lists of database tables and views, and a list ofmodules.



Overview of High–Level Design

During High–Level Design, we define the application components(tables, views, and modules) we need to build our application. Wespecify what application components should do without specifying thedetails of how they should do it.

You can refer to this High–Level Design chapter to quickly acquaintyourself with the tables, views, and modules that comprise OracleAlert applications. And, you can prepare yourself to understand thedetailed design and implementation of Oracle Alert.


The Summary Database Diagram section graphically represents themost important application tables and the relationships between them.It omits tables and relationships that contribute little to theunderstanding of the application data model. Typically, a summarydatabase diagram shows tables that contain key reference andtransaction data.

We prepare a summary database diagram to describe, at a conceptuallevel, the key information on which our business depends. Later, werefine this summary database diagram, breaking it into multipledatabase diagrams (generally, one per application building block) torepresent all the tables and relationships we need to implement ourapplication in the database.

Review the Summary Database Diagram section to see at a glance themajor tables and relationships on which your Oracle Alert applicationdepends.

Database Diagrams

The Database Diagrams section graphically represents all Oracle Alertapplications tables and the relationships between them, organized bybuilding block.

Use this section to quickly learn what tables each Oracle Alertapplication building block uses, and how those tables interrelate. Then,you can refer to the Table and View Definitions sections of Chapter 3for more detailed information about each of those tables.



Table Lists

The Table List sections list the Oracle Alert applications tables.Because a product might not include at least one table for each type,this Technical Reference Manual might not include each of thefollowing sections.

Public Tables

Use the Public Table List section to quickly identify the tables you aremost interested in. Then, you can refer to the Table and ViewDefinitions sections of Chapter 3 for more detailed information aboutthose tables.

In addition, this manual may contain full documentation for one ormore of the following Application Object Library tables: FND_DUAL,FND_CURRENCIES, and FND_COMMON_LOOKUPS.

View Lists

The View List sections list the Oracle Alert views, with one section foreach type of view. Because a product might not include at least oneview for each type, this Technical Reference Manual might not includeeach of the following sections.

Use this section to quickly identify the views you are most interestedin. Then, you can refer to the Table and View Definitions sections ofChapter 3 for more detailed information about those views.

Public Views

This section lists views that may be useful for your custom reporting orother data requirements. The list includes a description of the view,and the page in Chapter 3 that gives detailed information about thepublic view.

Internal Views

This section includes each private, internal view that Oracle Alert uses.



Module List

The Module List section briefly describes each of the Oracle Alertapplications modules. This section lists forms, reports, and concurrentprograms.

A form is a module comprised of closely related windows that are usedtogether to perform a task. For example, the Enter Journals form inOracle General Ledger includes the Enter Journals window, the Batchwindow, and the More Actions window. The Enter Journals window isthe main window, and from it, you can use buttons to navigate to otherwindows in the form. The form name usually corresponds to the mainwindow in the form, and is frequently a window you can open directlyfrom the Navigator.

The Reports and Concurrent Programs lists include processes you cansubmit from the Submit Requests window or other windows, as well asprocesses that are submitted automatically by Oracle Alert. Use youruser ’s guide to learn more about reports and concurrent processes.




This Summary Database Diagram graphically represents the mostimportant Oracle Alert applications tables and the relationshipsbetween them. It describes, at a conceptual level, the key informationon which your Oracle Alert application depends.

This diagram does not represent the complete database implementationof Oracle Alert applications tables. It shows tables that contain keyreference and transaction data, and omits tables and relationships thatcontribute little to the understanding of the Oracle Alert applicationsdata model. For example, a foreign key relationship shown betweentwo tables may actually be implemented by an intervening table, notshown in this diagram.

For more detailed graphical representations of Oracle Alertapplications tables and the relationships between them, see theDatabase Diagrams section in this chapter.



Database Diagramming Conventions

We use the following notational conventions in our database diagrams:

Figure 2 – 1Database DiagramConventions

Mandatory and Optional Foreign Keys

A value entered in the column in the foreign keymust match a value in the primary key column.

��

��

��

��

��

��

� ��

��

��

�� !

��

"��#��$

%� ��

�� %��

&�� !��

'�� (�� !�� (� (��)��!� �!

��!� �!��"�$

��%� ��!��"�$

Server Model Diagram Elements and Notation

A value entered in the column in the foreign keymust match either a value in the primary key column,or else it must be null.



Tables – are the basic unit of storage in the database. A hand symbolpreceding the title in the table’s title bar indicates that the table is notowned by this application but shared with another.

Foreign key constraint – is a type of referential integrity constraint forchecking the integrity of data entered in a specific column or set ofcolumns. This specified column or set of columns is known as theforeign key.

Delete rule indicator – determines the action to be taken when anattempt is made to delete a related row in a join table. A line throughthe foreign key constraint, as shown on the above diagram, indicatesthat this action is restricted.

Arcs – specify that, for any given row in a table, a value must beentered in one of the arc columns. The remaining columns within thearc must be null.



Oracle Alert Summary Database Diagram



Database Diagrams

This section graphically represents most of the significant Oracle Alertapplication tables and the relationships between them, organized bybuilding block. Use this section to quickly learn what tables eachOracle Alert application building block uses, and how these tablesinterrelate. Then, you can refer to the Table and View Definitionssections of Chapter 3 for more detailed information about each of thosetables.

This section contains a database diagram for each of the followingOracle Alert application building blocks:

• Diagram 1: Event Alerts

• Diagram 2: Periodic Alerts

• Diagram 3: Alert History

• Diagram 4: Response Processing

Some tables, especially important reference tables, appear in more thanone database diagram. When several building blocks use a table, weshow that table in each appropriate database diagram.

Event Alerts

Diagram 1 shows the tables and relationships that define event alertprocessing. In particular, the table FND_TABLES contains base tableinformation for the Oracle Applications forms. A user triggers anevent alert by insert or update through any application form whosebase table is the defined event table for that alert.

Periodic Alerts

Diagram 2 shows the table and relationships that define periodic alertprocessing, including periodic sets and periodic set members.

Alert History

Diagram 3 shows the tables and relationships that store history for eachalert check and each action set check. Oracle Alert uses alert history toperform duplicate checking and action escalation, and to reconstructactions performed and exceptions found during an alert check.



Response Processing

Diagram 4 shows the table and relationships used in responseprocessing, including actions, response actions, response variables, andresponse variable values.

How to Use These Database Diagrams

Here is an example of how you might use these database diagrams:

Suppose you want to create an alert that notifies you on a daily basis ofthe alert activity that took place on the previous day. To find the storeddata for previous alert checks, you turn to Diagram 3 to see the tablestructure for the Alert History building block. The diagram shows youthat alert check history resides in the table ALR_ALERT_CHECKS andALR_ACTION_SET_CHECKS. You also need to use the tableALR_ALERTS so you can organize alert check history by alert. And,you can use the shared Oracle Application Object Library tableFND_APPLICATION to report alert activity by application.

Next, you turn to the Table and View Definitions section in Chapter 3to learn about the columns in each of these tables. Using thisinformation, you can create an alert that sends you a summary messagecontaining all the alert check results from the previous day.



Event Alerts



Periodic Alerts



Alert History



Responce Processsing



Public Table List

This section lists each public database table that Oracle Alert uses andprovides a brief description of each of those tables. The page reference isto the table description in Chapter 3.

Note that ”public” tables are not necessarily intended for write access bycustom code; Oracle Corporation supports write access using onlystandard Oracle Applications forms, reports, and programs, or any SQLwrite access to tables explicitly documented as API tables. For moreinformation, see the How Not To Use This Manual section of this book’sIntroduction.

Oracle Alert uses the following Public tables:

Table Name Description

ALR_ACTIONS Alert and response actions (See page 3 – 7)

ALR_ACTION_DATA Exceptions found during an action set check (See page3 – 10)

ALR_ACTION_GROUPS Alert action, threshold, and escalation groups (See page3 – 12)

ALR_ACTION_GROUP_MEMBERS Member actions of an alert action group (See page 3 – 14)

ALR_ACTION_HISTORY Actual action execution history (See page 3 – 16)

ALR_ACTION_OUTPUTS Critical outputs used in a summary action (See page 3 – 18)

ALR_ACTION_SETS Alert action sets (See page 3 – 20)

ALR_ACTION_SET_CHECKS Action set check information (See page 3 – 22)

ALR_ACTION_SET_INPUTS Alert action set inputs (See page 3 – 24)

ALR_ACTION_SET_MEMBERS Member actions and action groups of alert action sets (Seepage 3 – 26)

ALR_ACTION_SET_OUTPUTS Alert action set outputs (See page 3 – 28)

ALR_ACTUAL_RESPONSES Responses expected and received for an alert message (Seepage 3 – 30)

ALR_ALERTS Alerts defined on application tables (See page 3 – 32)

ALR_ALERT_CHECKS Alert check information (See page 3 – 35)

ALR_ALERT_INPUTS Alert inputs (See page 3 – 37)



ALR_ALERT_INSTALLATIONS Alert installation information (See page 3 – 39)

ALR_ALERT_OUTPUTS Alert outputs (See page 3 – 40)

ALR_DISTRIBUTION_LISTS Distribution lists (See page 3 – 42)

ALR_LOOKUPS Oracle Alert lookup types and codes (See page 3 – 44)

ALR_MESSAGE_SYSTEMS Electronic mail system information (See page 3 – 45)

ALR_ORACLE_MAIL_ACCOUNTS Oracle*Mail mail account information (See page 3 – 46)

ALR_OUTPUT_HISTORY Exception output history (See page 3 – 48)

ALR_PERIODIC_SETS Periodic alert sets (See page 3 – 50)

ALR_PERIODIC_SET_MEMBERS Member alerts and periodic sets of periodic sets (See page3 – 51)

ALR_PROFILE_OPTIONS Oracle Alert profile options and values (See page 3 – 53)

ALR_RESPONSE_ACTIONS Member actions of a response set (See page 3 – 55)

ALR_RESPONSE_ACTION_HISTORY Response processing history (See page 3 – 56)

ALR_RESPONSE_MESSAGES Messages received in reply to an alert message (See page3 – 57)

ALR_RESPONSE_SETS Response sets (See page 3 – 59)

ALR_RESPONSE_VARIABLES Response set variables (See page 3 – 60)

ALR_RESPONSE_VARIABLE_VALUES Actual variable and alert output values returned in aresponse message (See page 3 – 62)

ALR_VALID_RESPONSES Response text for each possible response to an alert message(See page 3 – 64)

FND_APPLICATION Applications registered with Oracle Application ObjectLibrary (See page 3 – 66)

FND_CONCURRENT_PROGRAMS Concurrent programs (See page 3 – 67)

FND_CONCURRENT_REQUESTS Concurrent requests information (See page 3 – 71)

FND_DATA_GROUPS Data groups registered with Oracle Application ObjectLibrary (See page 3 – 78)

FND_FORM Application forms registered with Oracle ApplicationObject Library (See page 3 – 79)



FND_LOOKUP_VALUES QuickCode values (See page 3 – 80)

FND_ORACLE_USERID ORACLE accounts that contain application data (See page3 – 82)

FND_PRINTER Printers registered with Oracle Application Object Library(See page 3 – 84)

FND_PRODUCT_INSTALLATIONS Oracle Applications products installed at your site (See page3 – 85)

FND_RESPONSIBILITY Responsibilities (See page 3 – 87)

FND_TABLES Tables registered in applications (See page 3 – 89)

FND_USER Application users (See page 3 – 91)



Forms and Table View List

This section lists supplementary views that are not essential to theRelease 11 data model, but simplify coding or improve performance ofDeveloper/2000. For example, many of these views are used as basetables in Oracle Alert forms.

Warning: We do not recommend you query or alter data usingthese views. Furthermore, these views may changedramatically in subsequent minor or major releases of OracleAlert.

Oracle Alert uses the following Forms and Table views:

• ALR_ACTIONS_V

• ALR_GROUPS_AND_ACTIONS_VIEW



Internal View List

This section lists each private, internal view that Oracle Alert uses.

Warning: Oracle Corporation does not support access to OracleApplications data using these views, except from standardOracle Applications forms, reports, and programs.

Oracle Alert uses the following internal views:

• ALR_ALERT_ACTIONS_VIEW

• ALR_ALERT_HISTORY_VIEW

• ALR_CHECK_ACTION_HISTORY_VIEW

• ALR_INSTALLATIONS_VIEW

• ALR_PERIODIC_ALERTS_VIEW

• ALR_RESPONSE_ACTIONS_VIEW

• ALR_SCHEDULED_PROGRAMS

• ALR_VARIABLES_AND_OUTPUTS



Module List

This section lists each form, report and concurrent program comprisingOracle Alert.

Forms

ALRALERT Alerts

ALRASDDL Distribution Lists

ALRASDPG Periodic Sets

ALRPRRPA Request Periodic Alert Check

ALRPRSAP Schedule Alert Programs

ALRRHRAA Review Alert Actions

ALRRHRAC Review Alert Checks

ALRRHRAE Review Alert Exceptions

ALRRHRAH Review Alert History

ALRSSDAO Oracle Alert Options

Concurrent Programs

ALDTCA Test concurrent request action in diagnostic alerts

ALECDC Check named periodic alert concurrent program

ALECTC Check named event alert concurrent program

ALEPPE Periodic alert checker

ALPPIM Process incoming messages concurrent program

ALUTAD Transfer alert definitions from one database to anotherdatabase

C H A P T E R

3T

3 – 1Detailed Design


Detailed Design

his chapter presents a detailed design for implementing OracleAlert. It contains detailed definitions of tables and views that

you may need to reference to write custom reports or use for other dataextraction.



Overview of Detailed Design

During Detailed Design, we specify in detail how each applicationscomponent should work. We prepare detailed definitions of tables andviews.

You can refer to this Detailed Design chapter to gain a detailedunderstanding of the underlying structure and processing of OracleAlert that enables you to:

• Convert existing application data

• Integrate your Oracle Alert application with your otherapplications systems

• Write custom reports

• Define alerts against Oracle Applications tables

• Create views for decision support queries using query tools

• Configure your Oracle Self–Service Web Applications

Table and View Definitions

The Table and View Definitions section contains a detailed definition ofOracle Alert applications tables. For each table, it provides informationabout primary keys, foreign keys, QuickCodes, indexes, triggers, andsequences. It also gives you a detailed description of each column andits characteristics. In addition, it provides the SQL statement thatdefines each view. Review this section to get a detailed understandingof what tables your Oracle Alert application contains, and how it usesthem to hold and access the information it needs.



Table and View Definitions

This section contains a detailed description of each Oracle Alert tableand view that you may need to reference. For each table, it presentsdetailed information about:

• Primary keys

• Foreign keys

• Column descriptions

• Indexes

• Oracle sequences

• Triggers

• View derivations

The following sections appear in each table or view description:

Foreign Keys

To help you understand the relationships between tables, we list eachforeign key contained in a table. For each foreign key in a table, we listthe primary key table name (the table to which a foreign key refers), itscorresponding primary key columns, and the foreign key columns thatrefer to those primary key columns.

When the primary key table has a composite primary key, we list eachcolumn of the composite key sequentially.

If a table contains two or more distinct foreign keys that refer to thesame primary key table, we repeat the primary key table name and listeach of the distinct foreign keys separately.

QuickCodes Columns

When a database column contains a QuickCodes value, which weimplement using a foreign key to FND_LOOKUPS, MFG_LOOKUPS,or to some other lookup table, we list the QuickCodes type (lookuptype) to which the QuickCodes value must belong and a complete listof QuickCodes values and meanings. Some QuickCodes can bedefined by you in the application. These values are designated asUser–defined.



Column Descriptions

We list the important characteristics of each column in a table or view.These characteristics include whether the column is part of the table’sprimary key, whether Oracle8i requires a value for this column, and thedata type of the column. We also give you a brief description of howyour Oracle Alert application uses the column.

When a column is part of a table’s primary key, we append the notation(PK) to the name of that column.

To help you understand which columns your Oracle Alert applicationuses and which columns it does not use, we alert you to any unusedcolumn. When no module uses a database column, we show one of thefollowing legends in the Description column:

Your Oracle Alert application does not use thiscolumn, although the column might be used in afuture release.

Your Oracle Alert application no longer uses thiscolumn. AutoInstall installs this column.Subsequent versions of your Oracle Alertapplication might not include this column.

Your Oracle Alert application no longer uses thiscolumn. If you upgraded your software from anearlier version, you may still have this column,depending upon whether you chose to delete itduring an upgrade process. If you install yourOracle Alert application, you do not have thiscolumn.

Standard Who Columns

Most Oracle Alert application tables contain standard columns tosupport \ Row Who. When your program or SQL*Plus commandselects a row from a table, use these columns to determine who lastupdated the row. If your program or SQL*Plus command updates orinserts a row in an interface table, you must populate each of the fivestandard Who columns:

Date when a user last updated this row

User who last updated this row (foreignkey to FND_USER.USER_ID)

Date when this row was created

Not currentlyused

No longer used

No longerinstalled

LAST_UPDATE_DATE

LAST_UPDATED_BY

CREATION_DATE



User who created this row (foreign key toFND_USER.USER_ID)

Operating system login of user who lastupdated this row (foreign key toFND_LOGINS.LOGIN_ID). You shouldset this to NULL, or to 0 if NULL is notallowed

Since every table containing Who columns has several foreign keys tothe tables FND_USER and FND_LOGINS, we do not include theforeign key columns LAST_UPDATED_BY, CREATED_BY, orLAST_UPDATE_LOGIN in a table’s list of foreign keys.

Additional Who Columns for Concurrent Programs

Some Oracle Alert application tables also contain several additionalWho columns to distinguish between changes a user makes with a formand changes a concurrent program makes. When a concurrentprogram updates or inserts a row in a table, the concurrent programpopulates the following additional Who columns:

Concurrent request ID of program that lastupdated this row (foreign key toFND_CONCURRENT_REQUESTS.RE -QUEST_ID)

Application ID of program that lastupdated this row (foreign key toFND_APPLICATION.APPLICATION_ID)

Program ID of program that last updatedthis row (foreign key to FND_CONCUR-RENT_PROGRAM.CONCURRENT_PRO -GRAM_ID)

Date when a program last updated thisrow

Since every table containing these additional Who columns has severalforeign keys to the tables FND_CONCURRENT_REQUESTS,FND_APPLICATION, and FND_CONCURRENT_PROGRAM, we donot include the foreign key columns REQUEST_ID,PROGRAM_APPLICATION_ID, or PROGRAM_ID in a table’s list offoreign keys.

CREATED_BY

LAST_UPDATE_LOGIN

REQUEST_ID

PROGRAM_APPLICATION_ID

PROGRAM_ID

PROGRAM_UPDATE_DATE



Indexes

If an Oracle Alert application table uses an Oracle8i index, we list thedatabase columns that comprise that index, in sequential order.

Note: The indexes we document in this manual correspond tounique keys we specified during product development and testing.In some cases, we may add additional indexes during the portingprocess to fine–tune performance on specific platforms; therefore,there may be minor differences between the indexes documented inthis book and the indexes for production versions of Oracle Alert.

Sequences

Your Oracle Alert application uses Oracle8i sequence generators togenerate unique integers. If any table column gets its value from anOracle8i sequence generator, we list the name of the correspondingsequence generator and the name of the column that stores the uniqueinteger.

Database Triggers

If a table has one or more active database triggers, we provide a briefexplanation of each database trigger and when it fires.

View Derivation

For each Oracle Alert application view you may need to reference, weinclude important elements from the SQL statement that defines orcreates a view. By studying this view definition, you can understandexactly how a view derives its contents.



ALR_ACTIONS

ALR_ACTIONS stores information about the alert actions and responseactions you define. You need one row for each alert action or responseaction.

Each row includes the action name and definition, and the recipients ifthe action is a message. Oracle Alert uses this information to knowwhat instructions to perform based on the result of an alert check or aparticular type of response to an alert message.

Each action includes the text of the message, the operating system script,or the SQL statements (BODY), or the path and name of the file thatcontains the text of the message, the operating system script, the SQLstatements, or the concurrent process (FILE_NAME).

To identify the intended recipients of a message action, Oracle Alert usesthe foreign key LIST_ID to get the recipients fromALR_DISTRIBUTION_LISTS, or uses the values in theTO_RECIPIENTS, CC_RECIPIENTS, BCC_RECIPIENTS,PRINT_RECIPIENTS, and PRINTER columns for that row in this table.You cannot enter a value into LIST_ID if you have values in any of thefour recipient columns.

When you use the Define Actions form to update an action, Oracle Alertcloses off the previous version of the action(by setting ENABLED_FLAGto ’N’ for the previous version), and inserts a new row with anincremented VERSION_NUMBER.However, if Oracle Alert has neverused the most recent version of an action during an alertcheck(DATE_LAST_EXECUTED is null), Oracle Alert simply updatesthe action row with the new action information (leavingend_DATE_ACTIVE null) and does not insert a new action row –– theprevious, unused action version is lost.

Oracle Alert uses the most recent version of an action when executing anaction during an action set check. Oracle alert uses the appropriateversion of an action when recreating the action in the Review AlertActions form by comparing LAST_UPDATE_DATE inALR_ALERT_CHECKS to end_DATE_ACTIVE in this table, andlocating the version that was active at the time of the alert check.

Foreign KeysPrimary Key Table Primary Key Column Foreign Key Column

ALR_ALERTS APPLICATION_ID APPLICATION_IDALERT_ID ALERT_IDALR_DISTRIBUTION_LISTS APPLICATION_ID LIST_APPLICATION_IDLIST_ID LIST_IDEND_DATE_ACTIVE END_DATE_ACTIVE



FND_CONCURRENT_PROGRAMS APPLICATION_ID PROGRAM_APPLICATION_IDCONCURRENT_PROGRAM_ID CONCURRENT_PROGRAM_ID

QuickCodes ColumnsColumn QuickCodes Type QuickCodes Table

ACTION_LEVEL_TYPE ACTION_LEVEL ALR_LOOKUPSD DetailN No ExceptionS Summary

ACTION_TYPE ACTION_TYPE ALR_LOOKUPSC Concurrent Program RequestM MessageO Operating System ScriptS SQL Statement Script

COLUMN_WRAP_FLAG YES_NO FND_LOOKUPSN NoY Yes

ENABLED_FLAG YES_NO FND_LOOKUPSN NoY Yes

Column DescriptionsName Null? Type Description

APPLICATION_ID (PK) NOT NULL NUMBER Application identifierACTION_ID (PK) NOT NULL NUMBER Action identifierNAME NOT NULL VARCHAR2(80) Action nameALERT_ID NOT NULL NUMBER Alert identifierACTION_TYPE NOT NULL VARCHAR2(1) Action type lookup codeLAST_UPDATE_DATE NOT NULL DATE Standard Who columnLAST_UPDATED_BY NOT NULL NUMBER Standard Who columnCREATION_DATE NULL DATE Standard Who columnCREATED_BY NULL NUMBER Standard Who columnLAST_UPDATE_LOGIN NULL NUMBER Standard Who columnEND_DATE_ACTIVE (PK) NULL DATE Last date action is enabledENABLED_FLAG NULL VARCHAR2(1) Enabled flagDESCRIPTION NULL VARCHAR2(240) DescriptionACTION_LEVEL_TYPE NULL VARCHAR2(1) Action level lookup codeDATE_LAST_EXECUTED NULL DATE Date action was last performedFILE_NAME NULL VARCHAR2(240) Name of message, operating

system script or SQL scriptwhose body resides in anoperating system file

ARGUMENT_STRING NULL VARCHAR2(240) Argument list for SQL,operating system, andconcurrent program actions

PROGRAM_APPLICATION_ID NULL NUMBER Application identifier forconcurrent program

CONCURRENT_PROGRAM_ID NULL NUMBER Concurrent program identifierLIST_APPLICATION_ID NULL NUMBER Application identifier for

distribution listLIST_ID NULL NUMBER Distribution list identifierTO_RECIPIENTS NULL VARCHAR2(240) List of primary message

recipientsCC_RECIPIENTS NULL VARCHAR2(240) List of copy message recipientsBCC_RECIPIENTS NULL VARCHAR2(240) List of blind copy message

recipients



PRINT_RECIPIENTS NULL VARCHAR2(240) List of print messagerecipients

PRINTER NULL VARCHAR2(30) Printer nameSUBJECT NULL VARCHAR2(240) Message subject text

Column Descriptions (Continued)Name Null? Type Description

REPLY_TO NULL VARCHAR2(240) Reply to mail IDRESPONSE_SET_ID NULL NUMBER Response set identifierFOLLOW_UP_AFTER_DAYS NULL NUMBER Number of days after which

outstanding responses areautomatically closed

COLUMN_WRAP_FLAG NULL VARCHAR2(1) Column wrap flagMAXIMUM_SUMMARY_MESSAGE_WIDTH NULL NUMBER Right margin of summary messageBODY NULL VARCHAR2(2000) Body of message, SQL script, or

operating system scriptVERSION_NUMBER NOT NULL NUMBER Verion number of action

Indexes

This table does not have any indexes.

IndexesIndex Name Index Type Sequence Column Name

ALR_ACTIONS_N1 NOT UNIQUE 1 APPLICATION_ID2 ALERT_ID3 ACTION_LEVEL_TYPE4 ACTION_TYPE5 NAMEALR_ACTIONS_N2 NOT UNIQUE 1 APPLICATION_ID2 LIST_APPLICATION_ID3 LIST_IDALR_ACTIONS_N3 NOT UNIQUE 1 APPLICATION_ID2 RESPONSE_SET_IDALR_ACTIONS_U1 UNIQUE 1 APPLICATION_ID2 ACTION_ID3 END_DATE_ACTIVEALR_ACTIONS_U2 UNIQUE 1 APPLICATION_ID2 ALERT_ID3 NAME4 END_DATE_ACTIVEALR_ACTIONS_U3 UNIQUE 1 APPLICATION_ID2 ACTION_ID3 VERSION_NUMBER4 END_DATE_ACTIVE

SequencesSequence Derived Column

ALR_ACTIONS_S ACTION_ID



ALR_ACTION_DATA

ALR_ACTION_DATA stores information about the exceptions foundduring an action set check. You need one row for each action executedfor each exception. For example, OracleAlert checks an alert with asummary action. If the alert check finds ten exceptions for the summaryaction, it inserts ten rows in ALR_ACTION_DATA.

Oracle Alert uses this information to recreate an action when you usethe Review Alert Actions form, and to perform duplicate checking andaction escalation.

If you choose not to save history for an alert, OracleAlert does notpopulate this table.

The Periodic Alert Checker purges rows from this table that representactions executed earlier than is defined by the value in theMAINTAIN_HISTORY_DAYS column of the ALR_ALERTStable.


ALR_ACTION_HISTORY APPLICATION_ID APPLICATION_IDACTION_HISTORY_ID ACTION_HISTORY_IDALR_ACTION_SET_CHECKS APPLICATION_ID APPLICATION_IDCHECK_ID CHECK_ID


DUPLICATE_FLAG YES_NO FND_LOOKUPSN NoY Yes


APPLICATION_ID (PK) NOT NULL NUMBER Application identifierACTION_HISTORY_ID (PK) NOT NULL NUMBER Action history identifierROW_NUMBER (PK) NOT NULL NUMBER Exception identifierCHECK_ID NOT NULL NUMBER Action set check identifierDUPLICATE_FLAG NULL VARCHAR2(1) Flag indicating duplicate

exception

Indexes



ALR_ACTION_DATA_N1 NOT UNIQUE 1 APPLICATION_ID2 CHECK_IDALR_ACTION_DATA_U1 UNIQUE 1 APPLICATION_ID2 ACTION_HISTORY_ID3 ROW_NUMBER



Sequences

This table does not use a sequence.



ALR_ACTION_GROUPS

ALR_ACTION_GROUPS stores information about each actiongroup(threshold or escalation), if defined. Each alert can have many orno rows in this table. You need one row for each action group youdefine.

Each row includes the name and description of each action group.

Oracle Alert uses this information to identify two or more actions thatyou want to treat as a group. All actions in a group must be of the sametype, identified by action_GROUP_TYPE.


ALR_ALERTS APPLICATION_ID APPLICATION_IDALERT_ID ALERT_ID


GROUP_TYPE GROUP_TYPE ALR_LOOKUPSA ActionE Escalation GroupT Threshold Group


APPLICATION_ID (PK) NOT NULL NUMBER Application identifierACTION_GROUP_ID (PK) NOT NULL NUMBER Action group identifierNAME NOT NULL VARCHAR2(80) Action group nameALERT_ID NOT NULL NUMBER Alert identifierACTION_GROUP_TYPE NOT NULL VARCHAR2(1) Action group lookup typeLAST_UPDATE_DATE NOT NULL DATE Standard Who columnLAST_UPDATED_BY NOT NULL NUMBER Standard Who columnCREATION_DATE NOT NULL DATE Standard Who columnCREATED_BY NOT NULL NUMBER Standard Who columnLAST_UPDATE_LOGIN NULL NUMBER Standard Who columnEND_DATE_ACTIVE NULL DATE Last date action group is

enabledENABLED_FLAG NULL VARCHAR2(1) Enabled flagDESCRIPTION NULL VARCHAR2(240) DescriptionGROUP_TYPE NOT NULL VARCHAR2(1) Escalation Group or Threshold

Group

Indexes



ALR_ACTION_GROUPS_N1 NOT UNIQUE 1 APPLICATION_ID2 ALERT_ID3 ACTION_GROUP_TYPE



Indexes (Continued)Index Name Index Type Sequence Column Name

ALR_ACTION_GROUPS_U1 UNIQUE 1 APPLICATION_ID2 ACTION_GROUP_IDALR_ACTION_GROUPS_U2 UNIQUE 1 APPLICATION_ID2 ALERT_ID3 NAME4 GROUP_TYPE


ALR_ACTION_GROUPS_S ACTION_GROUP_ID



ALR_ACTION_GROUP_MEMBERS

ALR_ACTION_GROUP_MEMBERS stores information about theactions included in action groups. You need one row for each action thatis a member of an action group.

Oracle Alert uses this information to know which group of actions toconsider when determining which action to execute during an action setcheck.

ACTION_LEVEL records the sequence in which Oracle Alertshouldperform detail actions if it locates a duplicate exception during an alertcheck. If, during the previous alert check, Oracle Alert performed actionlevel 2, then during the current alert check, Oracle Alert performs actionlevel 3. If there is no action level 3, OracleAlert performs action level 2(if the SUPPRESS_FLAG column of ALR_ACTION_SETS is ’N’) or doesnothing (if suppress_FLAG is ’Y’).


ALR_ACTIONS APPLICATION_ID APPLICATION_IDACTION_ID ACTION_IDEND_DATE_ACTIVE END_DATE_ACTIVEALR_ACTION_GROUPS APPLICATION_ID APPLICATION_IDACTION_GROUP_ID ACTION_GROUP_IDALR_ALERTS APPLICATION_ID APPLICATION_IDALERT_ID ALERT_ID




APPLICATION_ID (PK) NOT NULL NUMBER Application identifierACTION_GROUP_MEMBER_ID (PK) NOT NULL NUMBER Action group member identifierACTION_GROUP_ID NOT NULL NUMBER Action group identifierACTION_ID NOT NULL NUMBER Action identifierALERT_ID NOT NULL NUMBER Alert identifierLAST_UPDATE_DATE NOT NULL DATE Standard Who columnLAST_UPDATED_BY NOT NULL NUMBER Standard Who columnCREATION_DATE NOT NULL DATE Standard Who columnCREATED_BY NOT NULL NUMBER Standard Who columnLAST_UPDATE_LOGIN NULL NUMBER Standard Who columnEND_DATE_ACTIVE NULL DATE Last date action is enabledENABLED_FLAG NOT NULL VARCHAR2(1) Enabled flagACTION_LEVEL NULL NUMBER Detail action escalation level



Indexes



ALR_ACTION_GROUP_MEMBERS_N1 NOT UNIQUE 1 APPLICATION_ID2 ALERT_ID3 ACTION_GROUP_ID4 ACTION_LEVELALR_ACTION_GROUP_MEMBERS_U1 UNIQUE 1 APPLICATION_ID2 ACTION_GROUP_MEMBER_ID


ALR_ACTION_GROUP_MEMBERS_S ACTION_GROUP_MEMBER_ID



ALR_ACTION_HISTORY

ALR_ACTION_HISTORY stores information about each action thatOracle Alert executes during an action set check. You need one row foreach action Oracle Alert performed. For example, Oracle Alert checksan alert with three action sets. If each action set has at least one action,there will be at least one row in this table for each of the three actionsets. If one of the actions is dynamically defined and results in tenactions performed for the single action set, there will be ten rows in thistable for that action set.

Oracle Alert uses this information to recreate an action when you usethe Review Alert Actions form, and to perform duplicate checking andaction escalation.


The Periodic Alert Checker purges rows from this table that representactions executed earlier than is defined by the value in theMAINTAIN_HISTORY_DAYS column of the ALR_ALERTStable for thealert.


ALR_ACTION_SETS APPLICATION_ID APPLICATION_IDACTION_SET_ID ACTION_SET_IDALR_ACTION_SET_CHECKS APPLICATION_ID APPLICATION_IDCHECK_ID CHECK_IDALR_ACTION_SET_MEMBERS APPLICATION_ID APPLICATION_IDACTION_SET_MEMBER_ID ACTION_SET_MEMBER_IDALR_ACTUAL_RESPONSES NODE_HANDLE NODE_HANDLEMESSAGE_HANDLE MESSAGE_HANDLEALR_ALERTS APPLICATION_ID APPLICATION_IDALERT_ID ALERT_ID


ACTION_EXECUTED_FLAG YES_NO FND_LOOKUPSN NoY Yes

COLUMN_WRAP_FLAG YES_NO FND_LOOKUPSN NoY Yes

SUCCESS_FLAG YES_NO FND_LOOKUPSN NoY Yes


APPLICATION_ID (PK) NOT NULL NUMBER Application identifier




ACTION_HISTORY_ID (PK) NOT NULL NUMBER Action history identifierALERT_ID NOT NULL NUMBER Alert identifierACTION_SET_ID NOT NULL NUMBER Action set identifierCHECK_ID NOT NULL NUMBER Alert check identifierACTION_ID NULL NUMBER Action identifierACTION_SET_MEMBER_ID NOT NULL NUMBER Action set member identifierLAST_UPDATE_DATE NOT NULL DATE Standard Who columnACTION_LEVEL NOT NULL NUMBER Detail action escalation levelCOLUMN_WRAP_FLAG NULL VARCHAR2(1) Column wrap flagMAXIMUM_SUMMARY_MESSAGE_WIDTH NULL NUMBER Right margin of summary messageACTION_EXECUTED_FLAG NULL VARCHAR2(1) Flag recording whether or not

Oracle Alert executed an actionSUCCESS_FLAG NOT NULL VARCHAR2(1) Flag denoting whether the

action was performedsuccessfully

VERSION_NUMBER NOT NULL NUMBER Action version numberMESSAGE_HANDLE NULL NUMBER Response message identifierNODE_HANDLE NULL NUMBER Response node identifier

Indexes



ALR_ACTION_HISTORY_N1 NOT UNIQUE 1 APPLICATION_ID2 ALERT_ID3 ACTION_SET_ID4 ACTION_SET_MEMBER_ID5 ACTION_ID6 VERSION_NUMBERALR_ACTION_HISTORY_N2 NOT UNIQUE 1 APPLICATION_ID2 CHECK_IDALR_ACTION_HISTORY_U1 UNIQUE 1 APPLICATION_ID2 ACTION_HISTORY_ID


ALR_ACTION_HISTORY_S ACTION_HISTORY_ID



ALR_ACTION_OUTPUTS

ALR_ACTION_OUTPUTS stores information about the outputs that arepart of each action definition. Each action can have many outputs ornone. You need one row for each action output. Each row includes theoutput name and whether or not Oracle alert considers the outputcritical. Critical outputs area characteristic of summary actions. Forsummary message actions, critical outputs are those outputs that resideoutside the summary message template. For summary SQLandoperating system script actions, critical outputs are all outputs found inthe BODY and ARGUMENTS fields, and any output used as the filename (FILE). For Concurrent Programrequest actions, critical outputsare those outputs used as arguments..


ALR_ACTIONS APPLICATION_ID APPLICATION_IDACTION_ID ACTION_IDEND_DATE_ACTIVE END_DATE_ACTIVEALR_ALERTS APPLICATION_ID APPLICATION_IDALERT_ID ALERT_ID


CRITICAL_FLAG YES_NO FND_LOOKUPSN NoY Yes


APPLICATION_ID (PK) NOT NULL NUMBER Application identifierACTION_ID (PK) NOT NULL NUMBER Action identifierALERT_ID (PK) NOT NULL NUMBER Alert identifierNAME (PK) NOT NULL VARCHAR2(30) Action output nameCRITICAL_FLAG NOT NULL VARCHAR2(1) Flag denoting whether or not

the output is critical in thesummary action

END_DATE_ACTIVE NULL DATE Last Date the action is enabledLAST_UPDATE_DATE NOT NULL DATE Standard Who columnLAST_UPDATED_BY NOT NULL NUMBER(15) Standard Who columnCREATION_DATE NOT NULL DATE Standard Who columnCREATED_BY NOT NULL NUMBER(15) Standard Who columnLAST_UPDATE_LOGIN NULL NUMBER(15) Standard Who column

Indexes





ALR_ACTION_OUTPUTS_N1 NOT UNIQUE 1 APPLICATION_ID2 ACTION_ID3 CRITICAL_FLAGALR_ACTION_OUTPUTS_U1 UNIQUE 1 APPLICATION_ID2 ALERT_ID3 ACTION_ID4 NAME

Sequences




ALR_ACTION_SETS

ALR_ACTION_SETS stores information about the action sets definedfor each alert. Each alert can have one or many action sets. You needone row for each alert action set.

Each row includes the name and description of the action set, as well asinformation about duplicate checking and action escalation definitionfor the action set.

SUPPRESS_FLAG records whether you want to suppress duplicateexceptions found for this action set. If the value is ’N’, Oracle Alertexecutes each member of the action set each time an exception is found.If the value is ’Y’, Oracle Alert checks the exception against those foundduring the last action set check.

SEQUENCE is the user––defined sequence number that identifies theorder of execution of the action sets for alerts with multiple action sets.





SUPPRESS_FLAG YES_NO FND_LOOKUPSN NoY Yes


APPLICATION_ID (PK) NOT NULL NUMBER Application identifierACTION_SET_ID (PK) NOT NULL NUMBER Action set identifierNAME NOT NULL VARCHAR2(50) Action set nameALERT_ID NOT NULL NUMBER Alert identifierLAST_UPDATE_DATE NOT NULL DATE Standard Who columnLAST_UPDATED_BY NOT NULL NUMBER Standard Who columnCREATION_DATE NOT NULL DATE Standard Who columnCREATED_BY NOT NULL NUMBER Standard Who columnLAST_UPDATE_LOGIN NULL NUMBER Standard Who columnEND_DATE_ACTIVE NULL DATE Last date action set is enabledENABLED_FLAG NOT NULL VARCHAR2(1) Enabled flagRECIPIENTS_VIEW_ONLY_FLAG NOT NULL VARCHAR2(1) Not used since Version 5.0DESCRIPTION NULL VARCHAR2(240) DescriptionSUPPRESS_FLAG NULL VARCHAR2(1) Flag recording whether you want

to suppress duplicateexceptions found for the actionset




SUPPRESS_DAYS NULL NUMBER Not used since Version 5.0SEQUENCE NOT NULL NUMBER User–defined sequence number

that identifies the executionorder of enabled action setsfor an alert

Indexes



ALR_ACTION_SETS_U1 UNIQUE 1 APPLICATION_ID2 ACTION_SET_IDALR_ACTION_SETS_U2 UNIQUE 1 APPLICATION_ID2 ALERT_ID3 NAME


ALR_ACTION_SETS_S ACTION_SET_ID



ALR_ACTION_SET_CHECKS

ALR_ACTION_SET_CHECKS stores information about the checks foreach action set. Each action set has one row in this table for each timeOracle Alert checked the action set.


ALR_ACTION_SETS APPLICATION_ID APPLICATION_IDACTION_SET_ID ACTION_SET_IDALR_ALERTS APPLICATION_ID APPLICATION_IDALERT_ID ALERT_IDALR_ALERT_CHECKS APPLICATION_ID APPLICATION_IDALERT_CHECK_ID ALERT_CHECK_IDFND_ORACLE_USERID ORACLE_ID ORACLE_IDFND_PRODUCT_INSTALLATIONS APPLICATION_ID APPLICATION_IDORACLE_ID ORACLE_ID




APPLICATION_ID (PK) NOT NULL NUMBER Application identifierCHECK_ID (PK) NOT NULL NUMBER Action set check identifierALERT_ID NOT NULL NUMBER Alert identifierACTION_SET_ID NOT NULL NUMBER Action set identifierORACLE_ID NULL NUMBER Oracle User identifierALERT_CHECK_ID NOT NULL NUMBER Alert check identifierROW_COUNT NULL NUMBER Number of exceptions found for

an action set checkACTION_COUNT NULL NUMBER Number of actions performed for

an action set checkSUCCESS_FLAG NULL VARCHAR2(1) Success flag

Indexes



ALR_ACTION_SET_CHECKS_N1 NOT UNIQUE 1 APPLICATION_ID2 ALERT_CHECK_IDALR_ACTION_SET_CHECKS_N2 NOT UNIQUE 1 APPLICATION_ID2 ALERT_ID3 ACTION_SET_ID4 ORACLE_ID5 CHECK_IDALR_ACTION_SET_CHECKS_N3 NOT UNIQUE 1 SUCCESS_FLAGALR_ACTION_SET_CHECKS_N4 NOT UNIQUE 1 APPLICATION_ID2 ACTION_SET_IDALR_ACTION_SET_CHECKS_U1 UNIQUE 1 APPLICATION_ID2 CHECK_ID




ALR_ACTION_SET_CHECKS_S CHECK_ID



ALR_ACTION_SET_INPUTS

ALR_ACTION_SET_INPUTS stores information about the inputs foreach action set. Each action set can have many or no rows in this table,but the number of rows must equal then umber of enabled rows inALR_ALERT_INPUTS for this alert.You need one row for each action setinput that is not an implicit input.

Each row includes the name and value of the input for this action set.

Oracle Alert uses this information to customize the alert for each actionset by substituting the value in VALUE fort he input name whenexecuting the alert Select statement(stored in SQL_STATEMENT_TEXTof ALR_ALERTS).

Oracle Alert automatically inserts, updates, and deletes the informationin this table using information from enabled rows inALR_ALERT_INPUTS. When you use the DefineAlerts form to add orchange the value nils_STATEMENT_TEXT (ALR_ALERTS), Oracle Alertautomatically inserts, updates or deletes rows in this table to match theinputs used in SQL_STATEMENT_TEXT.


ALR_ACTION_SETS APPLICATION_ID APPLICATION_IDACTION_SET_ID ACTION_SET_IDALR_ALERTS APPLICATION_ID APPLICATION_IDALERT_ID ALERT_ID


APPLICATION_ID (PK) NOT NULL NUMBER Application identifierACTION_SET_ID (PK) NOT NULL NUMBER Action set identifierNAME (PK) NOT NULL VARCHAR2(30) Action set input nameALERT_ID (PK) NOT NULL NUMBER Alert identifierLAST_UPDATE_DATE NOT NULL DATE Standard Who columnLAST_UPDATED_BY NOT NULL NUMBER Standard Who columnCREATION_DATE NOT NULL DATE Standard Who columnCREATED_BY NOT NULL NUMBER Standard Who columnLAST_UPDATE_LOGIN NULL NUMBER Standard Who columnVALUE NULL VARCHAR2(240) Default action set input value

Indexes



ALR_ACTION_SET_INPUTS_U1 UNIQUE 1 APPLICATION_ID2 ALERT_ID3 ACTION_SET_ID4 NAME



Sequences




ALR_ACTION_SET_MEMBERS

ALR_ACTION_SET_MEMBERS stores information about the actionsand action groups included in action sets. You need one row for eachaction or action group that is a member of an action set.

Oracle Alert uses this information to know which actions and/or actiongroups to consider when determining the actions to execute during anaction set check.


ALR_ACTIONS APPLICATION_ID APPLICATION_IDACTION_ID ACTION_IDEND_DATE_ACTIVE END_DATE_ACTIVEALR_ACTION_GROUPS APPLICATION_ID APPLICATION_IDACTION_GROUP_ID ACTION_GROUP_IDALR_ACTION_SETS APPLICATION_ID APPLICATION_IDACTION_SET_ID ACTION_SET_IDALR_ALERTS APPLICATION_ID APPLICATION_IDALERT_ID ALERT_ID


ABORT_FLAG YES_NO FND_LOOKUPSN NoY Yes



APPLICATION_ID (PK) NOT NULL NUMBER Application identifierACTION_SET_MEMBER_ID (PK) NOT NULL NUMBER Action set member identifierACTION_SET_ID NOT NULL NUMBER Action set identifierACTION_ID NULL NUMBER Action identifierACTION_GROUP_ID NULL NUMBER Action group identifierALERT_ID NOT NULL NUMBER Alert identifierSEQUENCE NOT NULL NUMBER User–defined sequence number

identifying the order ofexecution of an action oraction group during an actionset check

LAST_UPDATE_DATE NOT NULL DATE Standard Who columnLAST_UPDATED_BY NOT NULL NUMBER Standard Who columnCREATION_DATE NOT NULL DATE Standard Who columnCREATED_BY NOT NULL NUMBER Standard Who columnLAST_UPDATE_LOGIN NULL NUMBER Standard Who columnEND_DATE_ACTIVE NULL DATE Last date action set member is

enabledENABLED_FLAG NOT NULL VARCHAR2(1) Enabled flag




SUMMARY_THRESHOLD NULL NUMBER Only used if the action setmember is a group, contains thenumber of exceptions abovewhich Oracle Alert performs thesummary action. A null valuecauses Oracle Alert to alwaysperform detail level action; 0causes summary level action.

ABORT_FLAG NOT NULL VARCHAR2(1) Flag denoting whether to abortthe action set when an actionset member fails

ERROR_ACTION_SEQUENCE NULL NUMBER The next action to perform whenan error occurs

Indexes



ALR_ACTION_SET_MEMBERS_N1 NOT UNIQUE 1 APPLICATION_ID2 ALERT_ID3 ACTION_SET_ID4 ENABLED_FLAGALR_ACTION_SET_MEMBERS_U1 UNIQUE 1 APPLICATION_ID2 ACTION_SET_MEMBER_ID


ALR_ACTION_SET_MEMBERS_S ACTION_SET_MEMBER_ID



ALR_ACTION_SET_OUTPUTS

ALR_ACTION_SET_OUTPUTS stores information about the outputs foreach action set. Each action set can have many or no rows in this table,but the number of rows must equal then umber of enabled rows inALR_ALERT_OUTPUTS for this alert.You need one row for each actionset output.

If you are suppressing duplicates for this action set,Oracle Alert uses theinformation in this table when checking an alert to determine whichoutputs define a duplicate: if SUPPRESS_FLAG is ’Y’, Oracle Alertincludes this output in its duplicate definition. If you are notsuppressing duplicates for this action set, Oracle Alertdoes not refer tothis table when checking an alert.

Oracle Alert automatically inserts, updates, and deletes information inthis table using information from enabled rows inALR_ALERT_OUTPUTS. When you use the Define Alertsform to addor change the value in SQL_STATEMENT_TEXT(ALR_ALERTS), OracleAlert automatically inserts, updates,or deletes rows in this table tomatch the outputs used nils_STATEMENT_TEXT.


ALR_ACTION_SETS APPLICATION_ID APPLICATION_IDACTION_SET_ID ACTION_SET_IDALR_ALERTS APPLICATION_ID APPLICATION_IDALERT_ID ALERT_ID


SUPPRESS_FLAG YES_NO FND_LOOKUPSN NoY Yes


APPLICATION_ID (PK) NOT NULL NUMBER Application identifierACTION_SET_ID (PK) NOT NULL NUMBER Action set identifierNAME (PK) NOT NULL VARCHAR2(30) Action set output nameALERT_ID (PK) NOT NULL NUMBER Alert identifierSEQUENCE NOT NULL NUMBER Action set output sequence

(comes from the output sequencein the alert Select statement)

LAST_UPDATE_DATE NOT NULL DATE Standard Who columnLAST_UPDATED_BY NOT NULL NUMBER Standard Who columnCREATION_DATE NOT NULL DATE Standard Who columnCREATED_BY NOT NULL NUMBER Standard Who columnLAST_UPDATE_LOGIN NULL NUMBER Standard Who columnSUPPRESS_FLAG NULL VARCHAR2(1) Flag determines which outputs

define a duplicate



Indexes



ALR_ACTION_SET_OUTPUTS_U1 UNIQUE 1 APPLICATION_ID2 ALERT_ID3 ACTION_SET_ID4 NAME

Sequences




ALR_ACTUAL_RESPONSES

ALR_ACTUAL_RESPONSES stores information about the responsesexpected and returned for an alert message. You need one row for eachresponse expected by Oracle Alert.

Each row includes a message unique identifier, the text of the response,and whether or not Oracle Alert could process this response. OracleAlert uses this information to keep track of the outstanding responsemessages as well as those that Oracle Alert has already successfullyprocessed.

When Oracle Alert sends out a message that expects a response, one rowis added to this table for the response expected.


ALR_ACTION_SET_CHECKS APPLICATION_ID APPLICATION_IDCHECK_ID ALERT_CHECK_IDALR_ALERTS APPLICATION_ID APPLICATION_IDALERT_ID ALERT_IDALR_RESPONSE_SETS APPLICATION_ID APPLICATION_IDALERT_ID ALERT_IDRESPONSE_SET_ID RESPONSE_SET_IDALR_VALID_RESPONSES APPLICATION_ID APPLICATION_IDALERT_ID ALERT_IDRESPONSE_SET_ID RESPONSE_SET_IDRESPONSE_ID RESPONSE_ID


ACTION_SET_PASS_FAIL YES_NO FND_LOOKUPSN NoY Yes


APPLICATION_ID NOT NULL NUMBER Application identifierALERT_ID NOT NULL NUMBER Alert identifierRESPONSE_SET_ID NOT NULL NUMBER Response set identifierRESPONSE_ID NULL NUMBER Response identifierMESSAGE_HANDLE (PK) NOT NULL NUMBER Message identifierNODE_HANDLE (PK) NOT NULL NUMBER Node identifierOPEN_CLOSED NULL VARCHAR2(1) Response statusCLOSE_RESPONSE_ON NULL DATE Date after which Oracle Alert

performs No Response actions ifno response is received fromany user

ACTION_SET_PASS_FAIL NULL VARCHAR2(1) Denotes processing status ofall actions associated with theresponse

TEXT NULL VARCHAR2(240) Text of possible responseSENT_BY NULL VARCHAR2(240) User ID of responderALERT_CHECK_ID NOT NULL NUMBER Alert check identifier



Indexes



ALR_ACTUAL_RESPONSES_N1 NOT UNIQUE 1 CLOSE_RESPONSE_ON2 OPEN_CLOSEDALR_ACTUAL_RESPONSES_N2 NOT UNIQUE 1 APPLICATION_ID2 ALERT_IDALR_ACTUAL_RESPONSES_N3 NOT UNIQUE 1 APPLICATION_ID2 RESPONSE_SET_IDALR_ACTUAL_RESPONSES_U1 UNIQUE 1 NODE_HANDLE2 MESSAGE_HANDLE


ALR_ACTUAL_RESPONSES_S MESSAGE_HANDLE



ALR_ALERTS

ALR_ALERTS stores information about the alerts you define.You needone row for each alert.

Each row includes the alert name, application that owns the alert andthe Select statement, as well as frequency information for periodic alertsor event information fore vent alerts. Oracle Alert usesALERT_CONDITION_TYPE to identify whether an alert is periodic orevent. Frequency is further defined by the value in FREQUENCY_TYPEcoupled with a value in the appropriate field,WEEKLY_CHECK_DAY,MONTHLY_CHECK_DAY_NUM, orDAYS_BETWEEN_CHECKS. Oracle alert uses the fields CHECK_TIME,CHECK_START_TIME,CHECK_END_TIME,SECONDS_BETWEEN_CHECKS, and check_ONCE_DAILY_FLAG todetermine when and how often to check the periodic alert on thescheduled day. An event alert is further defined by an insert orupdate(INSERT_FLAG, UPDATE_FLAG) transaction occurring in anapplication form whose base table is the one identified by the value inTABLE_ID and TABLE_APPLICATION_ID.


FND_TABLES APPLICATION_ID TABLE_APPLICATION_IDTABLE_ID TABLE_ID


ALERT_CONDITION_TYPE ALERT_CONDITION_TYPE ALR_LOOKUPSE EventP Periodic

FREQUENCY_TYPE ALERT_FREQUENCY_TYPE ALR_LOOKUPSB Every N Business DaysC Every N Calendar DaysM MonthlyO On DemandW Weekly

CHECK_ONCE_DAILY_FLAG YES_NO FND_LOOKUPSN NoY Yes

INSERT_FLAG YES_NO FND_LOOKUPSN NoY Yes

UPDATE_FLAG YES_NO FND_LOOKUPSN NoY Yes




APPLICATION_ID (PK) NOT NULL NUMBER Application identifierALERT_ID (PK) NOT NULL NUMBER Alert identifierALERT_NAME NOT NULL VARCHAR2(50) Alert nameLAST_UPDATE_DATE NOT NULL DATE Standard Who columnLAST_UPDATED_BY NOT NULL NUMBER Standard Who columnCREATION_DATE NOT NULL DATE Standard Who columnCREATED_BY NOT NULL NUMBER Standard Who columnLAST_UPDATE_LOGIN NULL NUMBER Standard Who columnALERT_CONDITION_TYPE NOT NULL VARCHAR2(1) Identifies whether an alert is

periodic or eventENABLED_FLAG NOT NULL VARCHAR2(1) Enabled flagSTART_DATE_ACTIVE NOT NULL DATE Creation date of alertEND_DATE_ACTIVE NULL DATE Last date alert is enabledTABLE_ID NULL NUMBER Event table identifierTABLE_APPLICATION_ID NULL NUMBER Application identifier for

event tableDESCRIPTION NULL VARCHAR2(240) DescriptionFREQUENCY_TYPE NULL VARCHAR2(1) Periodic alert frequency type

lookup codeWEEKLY_CHECK_DAY NULL VARCHAR2(3) Day on which Oracle Alert

checks a weekly periodic alertMONTHLY_CHECK_DAY_NUM NULL NUMBER Day number on which Oracle

Alert checks a monthly periodicalert

DAYS_BETWEEN_CHECKS NULL NUMBER Number of days Oracle Alertskips between Every N CalendarDays or Every N Business Daysperiodic alerts

CHECK_BEGIN_DATE NULL DATE Date to start Periodic ChecksDATE_LAST_CHECKED NULL DATE Date the alert was last checkedINSERT_FLAG NULL VARCHAR2(1) Flag denoting whether or not

event alert fires on insertUPDATE_FLAG NULL VARCHAR2(1) Flag denoting whether or not

event alert fires on updateDELETE_FLAG NULL VARCHAR2(1) No longer usedMAINTAIN_HISTORY_DAYS NULL NUMBER Number of days for which to

save historyCHECK_TIME NULL NUMBER Alert check time for alerts

checked only once on day ofcheck

CHECK_START_TIME NULL NUMBER Time at which first periodicalert check is submitted for analert scheduled to be checkedmore than once on a particularday

CHECK_END_TIME NULL NUMBER Time at which last periodicalert check is submitted for analert scheduled to be checkedmore than once on a particularday

SECONDS_BETWEEN_CHECKS NULL NUMBER Interval (in seconds) for analert scheduled to be checkedmore than once on a particularday

CHECK_ONCE_DAILY_FLAG NULL VARCHAR2(1) Flag denoting whether periodicalert is single–check ormultiple checks on check day

SQL_STATEMENT_TEXT NULL LONG Select statementONE_TIME_ONLY_FLAG NULL NUMBER(1) No longer usedTABLE_NAME NULL VARCHAR2(31) Table name for event alert



Indexes



ALR_ALERTS_N1 NOT UNIQUE 1 ALERT_CONDITION_TYPE2 APPLICATION_IDALR_ALERTS_U1 UNIQUE 1 APPLICATION_ID2 ALERT_IDALR_ALERTS_U2 UNIQUE 1 APPLICATION_ID2 ALERT_NAME


ALR_ALERTS_S ALERT_ID



ALR_ALERT_CHECKS

ALR_ALERT_CHECKS stores information about alert checks that oracleAlert performs. Each time Oracle Alert checks aperiodic alert, or atransaction triggers an event alert,Oracle Alert records that check byadding one row to this table.

Oracle Alert uses this information to recreate the check history of analert in the Review Alert Checks, ReviewAlert Exceptions, and ReviewAlert Actions forms.


ALR_ALERTS APPLICATION_ID APPLICATION_IDALERT_ID ALERT_IDFND_CONCURRENT_REQUESTS REQUEST_ID REQUEST_ID




APPLICATION_ID (PK) NOT NULL NUMBER Application identifierALERT_CHECK_ID (PK) NOT NULL NUMBER Alert check identifierLAST_UPDATE_DATE NOT NULL DATE Standard Who columnLAST_UPDATED_BY NOT NULL NUMBER Standard Who columnALERT_ID NOT NULL NUMBER Alert identifierREQUEST_ID NOT NULL NUMBER Concurrent request identifier

for the alert checkSUCCESS_FLAG NULL VARCHAR2(1) Flag to indicate if alert check

was successfulCHECK_TIME NULL NUMBER Time alert check completedHISTORY_PURGE_DATE NULL DATE Date on which Periodic Alert

Checker purges history for thisalert check. If null, OracleAlert did not save history forthe alert check.

Indexes



ALR_ALERT_CHECKS_N1 NOT UNIQUE 1 APPLICATION_ID2 ALERT_ID3 LAST_UPDATE_DATEALR_ALERT_CHECKS_N2 NOT UNIQUE 1 LAST_UPDATE_DATEALR_ALERT_CHECKS_U1 UNIQUE 1 APPLICATION_ID2 ALERT_CHECK_ID




ALR_ALERT_CHECKS_S ALERT_CHECK_ID



ALR_ALERT_INPUTS

ALR_ALERT_INPUTS stores information about the inputs for each alert.Each alert can have many or no rows in this table. You need one row foreach alert input that is not an implicit input.

Oracle Alert uses this information as the default values for automaticallycreating the rows nailer_ACTION_SET_INPUTS when you use theDefine Action Setsform. Oracle Alert does not use this table during alertchecks. Instead, Oracle Alert uses the information found inALR_ACTION_SET_INPUTS.

Oracle Alert automatically inserts rows into this table by parsing thevalue in the SQL_STATEMENT_TEXT column of thrall_ALERTS table.When you use the Define Alerts form to add or change the value inSQL_STATEMENT_TEXT, Oracle Alertautomatically inserts, updates, ordeletes rows in this table (and any rows in ALR_ACTION_SET_INPUTSthat exist forth is alert) to match the inputs in SQL_STATEMENT_TEXT.




DATA_TYPE DATA_TYPE ALR_LOOKUPSC CharacterD DateN Number



APPLICATION_ID (PK) NOT NULL NUMBER Application identifierALERT_ID (PK) NOT NULL NUMBER Alert identifierNAME (PK) NOT NULL VARCHAR2(30) Alert input nameLAST_UPDATE_DATE NOT NULL DATE Standard Who columnLAST_UPDATED_BY NOT NULL NUMBER Standard Who columnCREATION_DATE NOT NULL DATE Standard Who columnCREATED_BY NOT NULL NUMBER Standard Who columnLAST_UPDATE_LOGIN NULL NUMBER Standard Who columnENABLED_FLAG NOT NULL VARCHAR2(1) Enabled flagSTART_DATE_ACTIVE NOT NULL DATE Creation date of alert inputEND_DATE_ACTIVE NULL DATE Last date alert input is

enabledTITLE NOT NULL VARCHAR2(240) Alert input descriptionDATA_TYPE NOT NULL VARCHAR2(1) Input data type




DEFAULT_VALUE NULL VARCHAR2(240) Input default value

Indexes



ALR_ALERT_INPUTS_N1 NOT UNIQUE 1 APPLICATION_ID2 ALERT_ID3 ENABLED_FLAG4 NAME

Sequences




ALR_ALERT_INSTALLATIONS

ALR_ALERT_INSTALLATIONS stores information about alertinstallations at your site. Each row includes the application for whichthe alert is installed for. You need one row for each application againstwhich periodic and event alerts run.


ALR_ALERTS APPLICATION_ID APPLICATION_IDALERT_ID ALERT_IDFND_DATA_GROUPS DATA_GROUP_ID DATA_GROUP_IDFND_ORACLE_USERID ORACLE_ID ORACLE_ID


APPLICATION_ID (PK) NOT NULL NUMBER Application identifierALERT_ID (PK) NOT NULL NUMBER Alert identifierORACLE_ID (PK) NULL NUMBER Oracle usernameDATA_GROUP_ID (PK) NULL NUMBER Not currently usedENABLED_FLAG NOT NULL VARCHAR2(1) Enabled flagLAST_UPDATE_DATE NOT NULL DATE Standard Who columnLAST_UPDATED_BY NOT NULL NUMBER(15) Standard Who columnCREATION_DATE NOT NULL DATE Standard Who columnCREATED_BY NOT NULL NUMBER(15) Standard Who columnLAST_UPDATE_LOGIN NULL NUMBER(15) Standard Who column

Indexes



ALR_ALERT_INSTALLATIONS_U1 UNIQUE 1 APPLICATION_ID2 ALERT_ID3 ORACLE_ID4 DATA_GROUP_ID

Sequences




ALR_ALERT_OUTPUTS

ALR_ALERT_OUTPUTS stores information about the outputs for eachalert. Each alert can have many or no rows in this table. You need onerow for each alert output.

Oracle Alert uses this information as the default values for automaticallycreating the rows nailer_ACTION_SET_OUTPUTS when you use theDefine Action Setsform. Oracle Alert does not use this table during alertchecks. Instead, Oracle Alert uses the information found inALR_ACTION_SET_OUTPUTS. Oracle Alert inserts rows into this tableby parsing the value in the columns_STATEMENT_TEXT of theALR_ALERTS table. When you use the Define Alerts form to add orchange the value nils_STATEMENT_TEXT, Oracle Alert automaticallyinserts,updates, or deletes rows in this table (andnearly_ACTION_SET_OUTPUTS rows for this alert) to match theoutputs in your SQL_STATEMENT_TEXT.




DEFAULT_SUPPRESS_FLAG YES_NO FND_LOOKUPSN NoY Yes



APPLICATION_ID (PK) NOT NULL NUMBER Application identifierALERT_ID (PK) NOT NULL NUMBER Alert identifierNAME (PK) NOT NULL VARCHAR2(30) Alert output nameSEQUENCE NOT NULL NUMBER Output order for each alert,

ensuring that Oracle Alertselects the correct columnvalue into the correspondingoutput.

LAST_UPDATE_DATE NOT NULL DATE Standard Who columnLAST_UPDATED_BY NOT NULL NUMBER Standard Who columnCREATION_DATE NOT NULL DATE Standard Who columnCREATED_BY NOT NULL NUMBER Standard Who columnLAST_UPDATE_LOGIN NULL NUMBER Standard Who columnENABLED_FLAG NOT NULL VARCHAR2(1) Enabled flagSTART_DATE_ACTIVE NOT NULL DATE Alert output creation dateEND_DATE_ACTIVE NULL DATE Last date alert output is

enabled




TITLE NOT NULL VARCHAR2(240) Alert output descriptionDETAIL_MAX_LEN NULL NUMBER Maximum number of characters

displayed for an output in adetail level action

SUMMARY_MAX_LEN NULL NUMBER Maximum number of charactersdisplayed for an output in asummary level action

DEFAULT_SUPPRESS_FLAG NULL VARCHAR2(1) Default suppress flag for alertoutput

FORMAT_MASK NULL VARCHAR2(30) Number display format

Indexes



ALR_ALERT_OUTPUTS_N1 NOT UNIQUE 1 APPLICATION_ID2 ALERT_ID3 ENABLED_FLAG4 NAME

Sequences




ALR_DISTRIBUTION_LISTS

ALR_DISTRIBUTION_LISTS stores information about the distributionlists you define. You need one row for each distribution list.

You can reference a distribution list on as many actions within the sameapplication as the distribution list as you want. If Oracle Alert finds aLIST_ID in ALR_ACTIONS when checking an alert, it joins to this tableto identify the message recipients stored in TO_RECIPIENTS,CC_RECIPIENTS,BCC_RECIPIENTS, PRINT_RECIPIENTS, andPRINTER.

When you use the Define Distribution Lists form to update adistribution list, Oracle Alert closes off the previous version of the list(by storing the current date in end_DATE_ACTIVE), and inserts a newlist with the same list_ID and a null END_DATE_ACTIVE. However, ifOracleAlert has never used the most recent version of a list during analert check, Oracle Alert simply updates the list row with the new listinformation (leaving END_DATE_ACTIVEnull) and does not insert anew list row––the previous,unused list version is lost.

Oracle Alert uses the most recent version of a list when executing anaction during an action set check. Oracle alert uses the appropriateversion of a list when recreating the message in the Review AlertActions form by comparing LAST_UPDATE_DATE inALR_ALERT_CHECKS to end_DATE_ACTIVE in this table, andlocating the version that was active at the time of the alert check.


FND_APPLICATION APPLICATION_ID APPLICATION_IDFND_PRINTER PRINTER_NAME PRINTER




APPLICATION_ID (PK) NOT NULL NUMBER Application identifierLIST_ID (PK) NOT NULL NUMBER Distribution list identifierNAME NOT NULL VARCHAR2(30) Distribution list nameLAST_UPDATE_DATE NOT NULL DATE Standard Who columnLAST_UPDATED_BY NOT NULL NUMBER Standard Who columnCREATION_DATE NOT NULL DATE Standard Who columnCREATED_BY NOT NULL NUMBER Standard Who columnLAST_UPDATE_LOGIN NULL NUMBER Standard Who column




DESCRIPTION NULL VARCHAR2(240) DescriptionTO_RECIPIENTS NULL VARCHAR2(240) List of primary recipientsCC_RECIPIENTS NULL VARCHAR2(240) List of copy recipientsBCC_RECIPIENTS NULL VARCHAR2(240) List of blind copy recipientsPRINT_RECIPIENTS NULL VARCHAR2(240) List of print recipientsPRINTER NULL VARCHAR2(30) Printer nameREPLY_TO NULL VARCHAR2(240) Reply to mail IDEND_DATE_ACTIVE (PK) NULL DATE Last date distribution list is

enabledENABLED_FLAG NULL VARCHAR2(1) Enabled flag

Indexes



ALR_DISTRIBUTION_LISTS_U1 UNIQUE 1 APPLICATION_ID2 LIST_ID3 END_DATE_ACTIVEALR_DISTRIBUTION_LISTS_U2 UNIQUE 1 APPLICATION_ID2 NAME3 END_DATE_ACTIVE


ALR_DISTRIBUTION_LISTS_S LIST_ID



ALR_LOOKUPS

ALR_LOOKUPS stores codes and their meanings. You need one row foreach code. Oracle Alert uses LOOKUP_CODE as a foreign key in manyof its tables. Oracle Alert joins to this table to locate the MEANING todisplay in form fields.

LOOKUP_TYPE identifies the purpose of each LOOKUP_CODE.EachLOOKUP_TYPE can have many LOOKUP_CODES. Oracle Alertusesvalues in LOOKUP_CODE that remain constant across all languages.You can adjust the value in MEANING to your own language. OracleAlert displays the value in MEANING in all of its forms andQuickPicks. Users never see the value contained in LOOKUP_CODE.


LOOKUP_TYPE (PK) NOT NULL VARCHAR2(30) Oracle Alert lookup typeLOOKUP_CODE (PK) NOT NULL VARCHAR2(30) Lookup codeLAST_UPDATE_DATE NOT NULL DATE Standard Who columnLAST_UPDATED_BY NOT NULL NUMBER Standard Who columnMEANING NOT NULL VARCHAR2(80) Lookup code meaningENABLED_FLAG NOT NULL VARCHAR2(1) Enabled flagDESCRIPTION NULL VARCHAR2(80) Lookup code descriptionSTART_DATE_ACTIVE NULL DATE Lookup code initial active dateEND_DATE_ACTIVE NULL DATE Last date lookup code is

enabledLAST_UPDATE_LOGIN NULL NUMBER Standard Who columnCREATION_DATE NULL DATE Standard Who columnCREATED_BY NULL NUMBER Standard Who column

Indexes



ALR_LOOKUPS_U1 UNIQUE 1 LOOKUP_TYPE2 LOOKUP_CODE

Sequences




ALR_MESSAGE_SYSTEMS

ALR_MESSAGE_SYSTEMS stores information about electronic mailsystems.Each row includes the name and the code of an electronic mailsystem,and the command and arguments for using the system to sendelectronic mails. You need one row for each registered electronic mailsystem. Oracle Alert uses this information to send alert messages whenalerts are triggered. You can have only one electronic mail systemenabled at a time.




NAME (PK) NOT NULL VARCHAR2(80) Electronic mail system nameCODE NOT NULL VARCHAR2(1) Electronic mail system codeCOMMAND NULL VARCHAR2(240) Command to invoke electronic

mail systemARGUMENTS NULL VARCHAR2(240) Arguments to invoke electronic

mail systemENABLED_FLAG NULL VARCHAR2(1) Enabled flagLAST_UPDATE_DATE NOT NULL DATE Standard Who columnLAST_UPDATED_BY NOT NULL NUMBER Standard Who columnCREATION_DATE NOT NULL DATE Standard Who columnCREATED_BY NOT NULL NUMBER Standard Who columnLAST_UPDATE_LOGIN NULL NUMBER Standard Who column

Indexes



ALR_MESSAGE_SYSTEMS_U1 UNIQUE 1 NAME

Sequences




ALR_ORACLE_MAIL_ACCOUNTS

ALR_ORACLE_MAIL_ACCOUNTS stores information aboutOracle*Mail accounts. Each row includes the ORACLE username andencrypted password for the database, name of the mail account, a flag toindicate whether the mail account is used to send alert messages,andanother flag to indicate whether the mail account is the default responseaccount. You can only have one account for sending mails,but you canhave one or more default response accounts. This information is used tosend alert messages and response to return messages.

ALR_ORACLE_MAIL_ACCOUNTS is only used if your site is using theoracle*Mail electronic mail system.


FND_APPLICATION APPLICATION_ID APPLICATION_IDFND_ORACLE_USERID ORACLE_ID ORACLE_ID


DEFAULT_RESPONSE_ACCOUNT YES_NO FND_LOOKUPSN NoY Yes

SENDMAIL_ACCOUNT YES_NO FND_LOOKUPSN NoY Yes


APPLICATION_ID (PK) NOT NULL NUMBER Application identifierORACLE_ID (PK) NOT NULL NUMBER Oracle user identifierNAME NULL VARCHAR2(30) Electronic mail system account

nameENCRYPTED_PASSWORD NULL VARCHAR2(100) Encrypted Oracle passwordSENDMAIL_ACCOUNT NULL VARCHAR2(1) Flag indicating whether or not

this account is used to sendalert message

DEFAULT_RESPONSE_ACCOUNT NULL VARCHAR2(1) Flag indicating whether or notthis account is the defaultresponse account

LAST_UPDATE_DATE NOT NULL DATE Standard Who columnLAST_UPDATED_BY NOT NULL NUMBER(15) Standard Who columnCREATION_DATE NOT NULL DATE Standard Who columnCREATED_BY NOT NULL NUMBER(15) Standard Who columnLAST_UPDATE_LOGIN NULL NUMBER(15) Standard Who column

Indexes





ALR_ORACLE_MAIL_ACCOUNTS_U1 UNIQUE 1 APPLICATION_ID2 ORACLE_ID

Sequences




ALR_OUTPUT_HISTORY

ALR_OUTPUT_HISTORY stores information about the output valuesfound for each exception during each alert check.You need one row foreach output found for each exception for each action set during eachalert check.

When you use the Review Alert Exceptions form, Oracle Alertuses thisinformation to recreate a list of the exceptions found during an alertcheck. Oracle Alert also uses this table when analyzing whether anexception is a duplicate,or whether to escalate an action to the nextaction escalation level. Oracle Alert checks theSUPPRESS_FLAGcolumn of ALR_ACTION_SETS to determine if itneeds to examine this table for duplicates. If it does need to examinehistory, then Oracle Alert uses the value in the suppress_FLAG columnof ALR_ACTION_SET_OUTPUTS to determine which of the outputsstored in this table it needs to examine.


The Periodic Alert Checker purges rows from this table that representoutputs found earlier than is defined by the value in theMAINTAIN_HISTORY_DAYS column of the ALR_ALERTStable for thealert.


ALR_ACTION_SET_CHECKS APPLICATION_ID APPLICATION_IDCHECK_ID CHECK_ID




APPLICATION_ID (PK) NOT NULL NUMBER Application identifierNAME (PK) NOT NULL VARCHAR2(30) Output nameCHECK_ID (PK) NOT NULL NUMBER Action set check identifierROW_NUMBER (PK) NOT NULL NUMBER Exception numberDATA_TYPE NULL VARCHAR2(1) Output data typeVALUE NULL VARCHAR2(240) Actual value retrieved from the

database for this output duringthe alert check



Indexes



ALR_OUTPUT_HISTORY_N1 NOT UNIQUE 1 APPLICATION_ID2 CHECK_ID3 NAMEALR_OUTPUT_HISTORY_U1 UNIQUE 1 APPLICATION_ID2 CHECK_ID3 ROW_NUMBER4 NAME

Sequences




ALR_PERIODIC_SETS

ALR_PERIODIC_SETS stores information about periodic sets.You needone row for each periodic set.


APPLICATION_ID (PK) NOT NULL NUMBER Application identifierPERIODIC_SET_ID (PK) NOT NULL NUMBER Periodic set identifierLAST_UPDATED_BY NOT NULL NUMBER Standard Who columnLAST_UPDATE_DATE NOT NULL DATE Standard Who columnCREATED_BY NULL NUMBER Standard Who columnCREATION_DATE NULL DATE Standard Who columnLAST_UPDATE_LOGIN NULL NUMBER Standard Who columnNAME NOT NULL VARCHAR2(50) Periodic set nameDESCRIPTION NULL VARCHAR2(240) Description

Indexes



ALR_PERIODIC_SETS_U1 UNIQUE 1 APPLICATION_ID2 NAMEALR_PERIODIC_SETS_U2 UNIQUE 1 APPLICATION_ID2 PERIODIC_SET_ID


ALR_PERIODIC_SETS_S PERIODIC_SET_ID



ALR_PERIODIC_SET_MEMBERS

ALR_PERIODIC_SET_MEMBERS stores information about the alertsand periodic sets included in periodic sets. Youneed one row for eachalert or periodic set that is am ember of a periodic set.

Oracle Alert uses this information to know which alerts or periodic setsto check when you use the Request PeriodicAlert Check to submit aperiodic set.

In any given row, either CHILD_ALERT_ID orchild_PERIODIC_SET_ID will be used––the other column will be null.


ALR_ALERTS APPLICATION_ID CHILD_APPLICATION_IDALERT_ID CHILD_ALERT_IDALR_PERIODIC_SETS APPLICATION_ID APPLICATION_IDPERIODIC_SET_ID PERIODIC_SET_ID




APPLICATION_ID (PK) NOT NULL NUMBER Application identifierPERIODIC_SET_ID (PK) NOT NULL NUMBER Periodic set identifierSEQUENCE (PK) NULL NUMBER Periodic set member sequence

numberCHILD_APPLICATION_ID (PK) NOT NULL NUMBER Application identifier for

periodic set memberCHILD_ALERT_ID (PK) NULL NUMBER Alert identifier for periodic

set memberCHILD_PERIODIC_SET_ID (PK) NULL NUMBER Periodic set identifier for

periodic set memberLAST_UPDATED_BY NOT NULL NUMBER Standard Who columnLAST_UPDATE_DATE NOT NULL DATE Standard Who columnCREATED_BY NULL NUMBER Standard Who columnCREATION_DATE NULL DATE Standard Who columnLAST_UPDATE_LOGIN NULL NUMBER Standard Who columnENABLED_FLAG NOT NULL VARCHAR2(1) Enabled flagEND_DATE_ACTIVE NULL DATE Last date periodic set is

enabled

Indexes





ALR_PERIODIC_SET_MEMBERS_N1 NOT UNIQUE 1 APPLICATION_ID2 PERIODIC_SET_IDALR_PERIODIC_SET_MEMBERS_N2 NOT UNIQUE 1 CHILD_APPLICATION_ID2 CHILD_PERIODIC_SET_IDALR_PERIODIC_SET_MEMBERS_N3 NOT UNIQUE 1 CHILD_APPLICATION_ID2 CHILD_ALERT_IDALR_PERIODIC_SET_MEMBERS_N4 NOT UNIQUE 1 SEQUENCE2 CHILD_APPLICATION_ID3 CHILD_PERIODIC_SET_ID

Sequences




ALR_PROFILE_OPTIONS

ALR_PROFILE_OPTIONS stores general information that OracleAlertuses to connect to Oracle*Mail, construct messages,and submit ProcessIncoming Messages.Oracle Alert uses ’ALPPIM_START_TIME’,’ALPPIM_END_TIME’and ’ALPPIM_INTERVAL_MINUTES’ todetermine the schedule for process Incoming Messages. If these valuesare null,Oracle Alert submits Process Incoming Messages each day atmidnight. Using these profile options, the user can determine how oftenall occurrences of Process IncomingMessages runs.Oracle Alert uses thevalue of profile_MESSAGE_HEADER’ and’GENERIC_MESSAGE_FOOTER’to append standard text to thebeginning and end of every message action constructed.Oracle Alertuses the value of profile_RESPONSE_MESSAGE’ to include in any alertmessage that solicits a response from the user. This text explains how tocorrectly respond to an alert message.When sending alert messages,Oracle Alert connects to the oracle*Mail database using thePROFILE_OPTION_VALUE and encrypted_PASSWORD for the valueof profile importance_MAIL_USERNAME’. All messages that OracleAlertsends will come from this Oracle*Mailuser.’RESPONSE_PROCESSING_MAIL_USERNAME’ represents theusername and password of the Oracle*Mail account in whichOracleAlert processes responses to alert messages. If no account isspecified, Oracle Alert uses the account indicatedinterlace_MAIL_USERNAME’.You can define response accounts for anyapplication installations by choosing an application and an installationfor the application and specifying a response mail account.Oracle Alertuses the value of profile importance_MAIL_DATABASE’ to make theSQL*Net connection to the Oracle*Mail database when sending alertmessages and when you use the Define Oracle Alert Options form. Thevalue is a character string that includes a code for the SQL*Netconnectprotocol, the machine name upon which the oracle*Mail databaseresides, and the SID of the oracle*Mail database. The format of thisvalue is determined by the SQL*Net protocol you are using.If the tablecolumn MAXIMUM_SUMMARY_MESSAGE_WIDTH in thetabular_ACTIONS is NULL, then Oracle Alert uses the profile optionvalue for MAXIMUM_SUMMARY_MESSAGE_WIDTH to define theright margin of summary messages.The size of this table variesdepending upon whether you create additional response option rows,but is never less than ten rows.


PROFILE_OPTION_NAME (PK) NOT NULL VARCHAR2(80) Profile option name




PROFILE_OPTION_VALUE NULL VARCHAR2(240) Profile option value assignedby user

PROFILE_OPTION_LONG NULL LONG Profile option value foroptions defined in long fields

DESCRIPTION NULL VARCHAR2(240) Profile option descriptionvisible to user

LONG_FLAG NOT NULL VARCHAR2(1) Flag denoting whether profileoption value is present in longfield

ENCRYPTED_PASSWORD NULL VARCHAR2(100) Encrypted password value forprofile options with passwords(Oracle*Mail accounts)

LAST_UPDATE_DATE NOT NULL DATE Standard Who columnLAST_UPDATED_BY NOT NULL NUMBER Standard Who columnCREATION_DATE NOT NULL DATE Standard Who columnCREATED_BY NOT NULL NUMBER Standard Who columnLAST_UPDATE_LOGIN NULL NUMBER Standard Who columnLOOKUP_TYPE NULL VARCHAR2(30) Oracle Alert lookup type for

profile options whose valuesare a lookup code

Indexes



ALR_PROFILE_OPTIONS_U1 UNIQUE 1 PROFILE_OPTION_NAMEALR_PROFILE_OPTIONS_U2 UNIQUE 1 DESCRIPTION

Sequences




ALR_RESPONSE_ACTIONS

ALR_RESPONSE_ACTIONS stores information about actions that youinclude with a particular response in a response set.You need one rowfor each occurrence of an action in a response. Oracle Alert uses thisinformation to execute the actions, in the correct sequence, for eachresponse it processes.


ALR_ACTIONS APPLICATION_ID APPLICATION_IDACTION_ID ACTION_IDEND_DATE_ACTIVE END_DATE_ACTIVEALR_ALERTS APPLICATION_ID APPLICATION_IDALERT_ID ALERT_IDALR_RESPONSE_SETS APPLICATION_ID APPLICATION_IDALERT_ID ALERT_IDRESPONSE_SET_ID RESPONSE_SET_ID


APPLICATION_ID (PK) NOT NULL NUMBER Application identifierALERT_ID (PK) NOT NULL NUMBER Alert identifierRESPONSE_SET_ID (PK) NOT NULL NUMBER Response set identifierRESPONSE_ID (PK) NOT NULL NUMBER Response identifierACTION_ID NOT NULL NUMBER Action identifierSEQUENCE (PK) NOT NULL NUMBER Action sequence number within

possible responseLAST_UPDATE_DATE NOT NULL DATE Standard Who columnLAST_UPDATED_BY NOT NULL NUMBER Standard Who columnCREATION_DATE NOT NULL DATE Standard Who columnCREATED_BY NOT NULL NUMBER Standard Who columnLAST_UPDATE_LOGIN NULL NUMBER Standard Who columnENABLED_FLAG NOT NULL VARCHAR2(1) Enabled flagEND_DATE_ACTIVE NULL DATE Last date response member

action is enabled

Indexes



ALR_RESPONSE_ACTIONS_N1 NOT UNIQUE 1 APPLICATION_ID2 ALERT_IDALR_RESPONSE_ACTIONS_N2 NOT UNIQUE 1 APPLICATION_ID2 ACTION_IDALR_RESPONSE_ACTIONS_N3 NOT UNIQUE 1 APPLICATION_ID2 RESPONSE_SET_IDALR_RESPONSE_ACTIONS_U1 UNIQUE 1 APPLICATION_ID2 RESPONSE_ID3 SEQUENCE

Sequences




ALR_RESPONSE_ACTION_HISTORY

ALR_RESPONSE_ACTION_HISTORY stores information aboutresponse process history. One row is inserted for each response actionperformed.

Each row includes the action performed, the version number of theaction, a flag indicating whether the action was performed successfully,and the message handle for the response.


ALR_ACTUAL_RESPONSES NODE_HANDLE NODE_HANDLEMESSAGE_HANDLE MESSAGE_HANDLEALR_ALERTS APPLICATION_ID APPLICATION_IDALERT_ID ALERT_IDALR_RESPONSE_MESSAGES RESPONSE_MESSAGE_ID RESPONSE_MESSAGE_IDFND_ORACLE_USERID ORACLE_ID ORACLE_ID


RESPONSE_MESSAGE_ID (PK) NOT NULL NUMBER Response message identifierORACLE_ID NULL NUMBER Oracle user identifierSEQUENCE (PK) NOT NULL NUMBER Response action sequenceACTION_ID NOT NULL NUMBER Action identifierVERSION_NUMBER NOT NULL NUMBER Action version numberSUCCESS_FLAG NOT NULL VARCHAR2(1) Success flagMESSAGE_HANDLE NOT NULL NUMBER Message identifierNODE_HANDLE NOT NULL NUMBER Node identifierAPPLICATION_ID NOT NULL NUMBER Application identifierALERT_ID NOT NULL NUMBER Alert identifier

Indexes



ALR_RESPONSE_ACTION_HISTORY_U1 UNIQUE 1 RESPONSE_MESSAGE_ID2 SEQUENCE

Sequences




ALR_RESPONSE_MESSAGES

ALR_RESPONSE_MESSAGES stores information about responsesreceived in reply to an alert message that solicits a response. You needone row for each reply received in response to an alert message.

Each row includes an identifier of the original alert message,theresponse set identifier, the response type, the response identifier, theresponse message identifier, and the actual reply to the alert message.


ALR_ACTUAL_RESPONSES NODE_HANDLE NODE_HANDLEMESSAGE_HANDLE MESSAGE_HANDLEALR_RESPONSE_SETS APPLICATION_ID APPLICATION_IDALERT_ID ALERT_IDRESPONSE_SET_ID RESPONSE_SET_IDALR_VALID_RESPONSES APPLICATION_ID APPLICATION_IDALERT_ID ALERT_IDRESPONSE_SET_ID RESPONSE_SET_IDRESPONSE_ID RESPONSE_ID


RESPONSE_TYPE RESPONSE_TYPE ALR_LOOKUPSI Invalid ResponseN No ResponseV Valid Response


MESSAGE_HANDLE NOT NULL NUMBER Message identifierNODE_HANDLE NOT NULL NUMBER Node identifierAPPLICATION_ID NOT NULL NUMBER Application identifierALERT_ID NOT NULL NUMBER Alert identifierRESPONSE_SET_ID NOT NULL NUMBER Response set identifierRESPONSE_TYPE NOT NULL VARCHAR2(1) Response type codeRESPONSE_ID NULL NUMBER Response identifierRESPONSE_MESSAGE_ID (PK) NOT NULL NUMBER Response message identifierDATE_PROCESSED NOT NULL DATE Date on which the response

message was processedTO_RECIPIENTS NULL VARCHAR2(240) List of primary recipientsCC_RECIPIENTS NULL VARCHAR2(240) List of copy recipientsBCC_RECIPIENTS NULL VARCHAR2(240) List of blind copy recipientsSENT_FROM NULL VARCHAR2(240) Mail account from which the

message was sentREPLY_TO NULL VARCHAR2(240) Recipient of reply messageSUBJECT NULL VARCHAR2(240) Message headerRECEIVED NULL VARCHAR2(240) Time stamp of when the message

is receivedBODY NULL LONG Body of the message

Indexes





ALR_RESPONSE_MESSAGES_N1 NOT UNIQUE 1 MESSAGE_HANDLE2 NODE_HANDLE3 APPLICATION_ID4 RESPONSE_SET_ID5 RESPONSE_IDALR_RESPONSE_MESSAGES_U1 UNIQUE 1 RESPONSE_MESSAGE_ID


ALR_RESPONSE_MESSAGES_S RESPONSE_MESSAGE_ID



ALR_RESPONSE_SETS

ALR_RESPONSE_SETS stores information about response sets youdefine for your alerts. You need one row for each response set youdefine. Oracle Alert uses this information when determining the validresponses and associated actions fora response set.Each row includes thename of the response set and a description..




APPLICATION_ID (PK) NOT NULL NUMBER Application identifierRESPONSE_SET_ID (PK) NOT NULL NUMBER Response set identifierLAST_UPDATE_DATE NOT NULL DATE Standard Who columnLAST_UPDATED_BY NOT NULL NUMBER Standard Who columnCREATION_DATE NOT NULL DATE Standard Who columnCREATED_BY NOT NULL NUMBER Standard Who columnNAME NOT NULL VARCHAR2(30) Response nameALERT_ID (PK) NOT NULL NUMBER Alert identifierDESCRIPTION NULL VARCHAR2(240) DescriptionLAST_UPDATE_LOGIN NULL NUMBER Standard Who columnENABLED_FLAG NULL VARCHAR2(1) Enabled flagEND_DATE_ACTIVE NULL DATE Last date response set is

enabled

Indexes



ALR_RESPONSE_SETS_U1 UNIQUE 1 APPLICATION_ID2 RESPONSE_SET_IDALR_RESPONSE_SETS_U2 UNIQUE 1 APPLICATION_ID2 ALERT_ID3 NAME


ALR_RESPONSE_SETS_S RESPONSE_SET_ID



ALR_RESPONSE_VARIABLES

ALR_RESPONSE_VARIABLES stores information about the variablesthat belong to response sets. You need one row for each variable used ina response set.

Each row includes the variable name and description, as well as the typeand default value. Oracle Alert uses this information to verify that anyvariables used by an action that is associated with a response mustbelong to that response set. Oracle Alert also uses this information tocorrectly interpret the values of response variables from a user’sresponse.


ALR_ALERTS APPLICATION_ID APPLICATION_IDALERT_ID ALERT_IDALR_RESPONSE_SETS APPLICATION_ID APPLICATION_IDALERT_ID ALERT_IDRESPONSE_SET_ID RESPONSE_SET_ID



TYPE RESPONSE_TYPE ALR_LOOKUPSI Invalid ResponseN No ResponseV Valid Response


APPLICATION_ID (PK) NOT NULL NUMBER Application identifierALERT_ID (PK) NOT NULL NUMBER Alert identifierRESPONSE_SET_ID (PK) NOT NULL NUMBER Response set identifierVARIABLE_NUMBER (PK) NOT NULL NUMBER Variable identifierNAME NOT NULL VARCHAR2(30) Response variable nameDESCRIPTION NULL VARCHAR2(240) DescriptionLAST_UPDATE_DATE NOT NULL DATE Standard Who columnLAST_UPDATED_BY NOT NULL NUMBER Standard Who columnCREATION_DATE NOT NULL DATE Standard Who columnCREATED_BY NOT NULL NUMBER Standard Who columnLAST_UPDATE_LOGIN NULL NUMBER Standard Who columnTYPE NULL VARCHAR2(1) Response typeDEFAULT_VALUE NULL VARCHAR2(240) Default valueDATA_TYPE NOT NULL VARCHAR2(1) Variable data typeDETAIL_MAX_LEN NULL NUMBER Maximum length

Indexes





ALR_RESPONSE_VARIABLES_N1 NOT UNIQUE 1 APPLICATION_ID2 ALERT_IDALR_RESPONSE_VARIABLES_U1 UNIQUE 1 APPLICATION_ID2 RESPONSE_SET_ID3 VARIABLE_NUMBERALR_RESPONSE_VARIABLES_U2 UNIQUE 1 APPLICATION_ID2 RESPONSE_SET_ID3 NAME


ALR_RESPONSE_VARIABLES_S VARIABLE_NUMBER



ALR_RESPONSE_VARIABLE_VALUES

ALR_RESPONSE_VARIABLE_VALUES stores information about theactual values of the response variables that are associated with aparticular user response. You need one row for each variable of theresponse set corresponding to a particular response.

Each row includes the variable name, the value returned by the user andthe identification of the message in which the user returned the variable.

Oracle Alert uses this information to substitute these values into theactions that it takes for that particular response.


ALR_ACTUAL_RESPONSES NODE_HANDLE NODE_HANDLEMESSAGE_HANDLE MESSAGE_HANDLEALR_ALERTS APPLICATION_ID APPLICATION_IDALERT_ID ALERT_IDALR_RESPONSE_SETS APPLICATION_ID APPLICATION_IDALERT_ID ALERT_IDRESPONSE_SET_ID RESPONSE_SET_ID




MESSAGE_HANDLE (PK) NOT NULL NUMBER Message identifierNODE_HANDLE (PK) NOT NULL NUMBER Node identifierAPPLICATION_ID NOT NULL NUMBER Application identifierALERT_ID NOT NULL NUMBER Alert identifierRESPONSE_SET_ID NOT NULL NUMBER Response set identifierVARIABLE_NAME (PK) NOT NULL VARCHAR2(30) Response set variable nameVALUE NULL VARCHAR2(240) Response set variable value

returned by user in responsemessage

DATA_TYPE NOT NULL VARCHAR2(1) Variable data typeDETAIL_MAX_LEN NULL NUMBER Maximum length

Indexes



ALR_RESPONSE_VAR_VALUES_N1 NOT UNIQUE 1 APPLICATION_ID2 ALERT_ID




ALR_RESPONSE_VAR_VALUES_U1 UNIQUE 1 NODE_HANDLE2 MESSAGE_HANDLE3 VARIABLE_NAME

Sequences




ALR_VALID_RESPONSES

ALR_VALID_RESPONSES stores information about valid responses fora response set. You need one row for each possible response to an alertmessage a user can return.

Each row includes a response type and the text of the response. OracleAlert puts this template information in the alert message. The user usesone of the possible valid response templates to format her/his response.

Oracle Alert uses this information to identify a response once it isreceived from a user.


ALR_ALERTS APPLICATION_ID APPLICATION_IDALERT_ID ALERT_IDALR_RESPONSE_SETS APPLICATION_ID APPLICATION_IDALERT_ID ALERT_IDRESPONSE_SET_ID RESPONSE_ID


TYPE RESPONSE_TYPE ALR_LOOKUPSI Invalid ResponseN No ResponseV Valid Response


APPLICATION_ID (PK) NOT NULL NUMBER Application identifierRESPONSE_ID (PK) NOT NULL NUMBER Response identifierLAST_UPDATE_DATE NOT NULL DATE Standard Who columnLAST_UPDATED_BY NOT NULL NUMBER Standard Who columnCREATION_DATE NOT NULL DATE Standard Who columnCREATED_BY NOT NULL NUMBER Standard Who columnALERT_ID (PK) NOT NULL NUMBER Alert identifierRESPONSE_SET_ID (PK) NOT NULL NUMBER Response set identifierTYPE NOT NULL VARCHAR2(1) Possible response typeRESPONSE_TEXT NULL LONG Text of possible valid responseLAST_UPDATE_LOGIN NULL NUMBER Standard Who columnRESPONSE_NAME NULL VARCHAR2(240) Possible response name

Indexes



ALR_VALID_RESPONSES_N1 NOT UNIQUE 1 APPLICATION_ID2 ALERT_IDALR_VALID_RESPONSES_N2 NOT UNIQUE 1 APPLICATION_ID2 RESPONSE_SET_ID




ALR_VALID_RESPONSES_U1 UNIQUE 1 APPLICATION_ID2 RESPONSE_ID


ALR_VALID_RESPONSES_S RESPONSE_ID



FND_APPLICATION

FND_APPLICATION stores information about all of the applicationsregistered with Oracle Application Object Library. Each row includesthe name and description of the application. Each row also includes theapplication short name, which forms use for calling concurrentprograms, and the application prefix, which Message Dictionary uses togenerate application messages. Since the application code oftendepends upon application names and short names, you should neverchange their values. You need one row for each application you use ordevelop. Oracle Application Object Library uses this information toidentify most application objects, such as forms, windows,regions,menus,tables, and fields, and Oracle Application Object Libraryalso displays this information in LOVs.


APPLICATION_ID (PK) NOT NULL NUMBER Application identifierAPPLICATION_SHORT_NAME NOT NULL VARCHAR2(50) Application short nameLAST_UPDATE_DATE NOT NULL DATE Standard Who columnLAST_UPDATED_BY NOT NULL NUMBER(15) Standard Who columnCREATION_DATE NOT NULL DATE Standard Who columnCREATED_BY NOT NULL NUMBER(15) Standard Who columnLAST_UPDATE_LOGIN NULL NUMBER(15) Standard Who columnBASEPATH NULL VARCHAR2(20) The variable that stores the

directory path of the TOPdirectory for the application

Indexes



FND_APPLICATION_U1 UNIQUE 1 APPLICATION_IDFND_APPLICATION_U3 UNIQUE 1 APPLICATION_SHORT_NAME


FND_APPLICATION_S APPLICATION_ID



FND_CONCURRENT_PROGRAMS

FND_CONCURRENT_PROGRAMS stores information aboutconcurrent programs. Each row includes a name and description of theconcurrent program. Each row also includes the execution methods forthe program (EXECUTION_METHOD_CODE), the argumentmethod(ARGUMENT_METHOD_CODE), and whether the program isconstrained(QUEUE_METHOD_CODE). If the program is a specialconcurrent program that controls the concurrent managers,QUEUE_CONTROL_FLAGis set to Y. Each row also includes flags thatindicate whether the program is enabled and defined as run–alone, aswell as values that specify the print style the concurrent manager shoulduse to print program output, if any. There are also values that identifythe executable associated with the concurrent program and theapplication with which the executable is defined, and flags that specifywhether the concurrent program is a parent of a report set, whether tosave the output file, and whether a print style is required. Informationsuch as printer name and number of rows and columns on each page ofthe output file for the concurrent program is also included in thetable.You need one row for each concurrent program in eachapplication.Oracle Application Object Library uses this information torun concurrent programs.


FND_APPLICATION APPLICATION_ID APPLICATION_IDFND_CONCURRENT_REQUEST_CLASS APPLICATION_ID CLASS_APPLICATION_IDREQUEST_CLASS_ID CONCURRENT_CLASS_IDFND_EXECUTABLES APPLICATION_ID EXECUTABLE_APPLICATION_IDEXECUTABLE_ID EXECUTABLE_IDFND_PRINTER PRINTER_NAME PRINTER_NAMEFND_PRINTER_STYLES PRINTER_STYLE_NAME OUTPUT_PRINT_STYLE


ARGUMENT_METHOD_CODE CP_ARGUMENT_METHOD_CODE FND_LOOKUPS4 StandardD Database fetch


EXECUTION_METHOD_CODE CP_EXECUTION_METHOD_CODE FND_LOOKUPSA SpawnedF FlexSqlH HostI PL/SQL Stored ProcedureL SQL*LoaderP Oracle ReportsQ SQL*Plus



QuickCodes Columns (Continued)Column QuickCodes Type QuickCodes Table

R SQL*ReportS ImmediateX FlexRpt

PRINT_FLAG YES_NO FND_LOOKUPSN NoY Yes

QUEUE_CONTROL_FLAG YES_NO FND_LOOKUPSN NoY Yes

QUEUE_METHOD_CODE CP_QUEUE_METHOD_CODE FND_LOOKUPSB YesI No

REQUEST_SET_FLAG YES_NO FND_LOOKUPSN NoY Yes

REQUIRED_STYLE YES_NO FND_LOOKUPSN NoY Yes

RUN_ALONE_FLAG YES_NO FND_LOOKUPSN NoY Yes

SAVE_OUTPUT_FLAG YES_NO FND_LOOKUPSN NoY Yes

SRS_FLAG SRS_FLAG_TYPE FND_LOOKUPSN NoQ All ValuesY Yes


APPLICATION_ID (PK) NOT NULL NUMBER(15) Application identifierCONCURRENT_PROGRAM_ID (PK) NOT NULL NUMBER(15) Concurrent program identifierCONCURRENT_PROGRAM_NAME NOT NULL VARCHAR2(30) Internal name of the concurrent

programLAST_UPDATE_DATE NOT NULL DATE Standard Who columnLAST_UPDATED_BY NOT NULL NUMBER(15) Standard Who columnCREATION_DATE NOT NULL DATE Standard Who columnCREATED_BY NOT NULL NUMBER(15) Standard Who columnLAST_UPDATE_LOGIN NOT NULL NUMBER(15) Standard Who columnEXECUTABLE_APPLICATION_ID NOT NULL NUMBER(15) Identifier of the application

with which the executable isregistered

EXECUTABLE_ID NOT NULL NUMBER(15) Concurrent program executableidentifier

EXECUTION_METHOD_CODE NOT NULL VARCHAR2(1) Execution method for theconcurrent program

ARGUMENT_METHOD_CODE NOT NULL VARCHAR2(1) Code to indicate how programarguments are passed to theconcurrent program

QUEUE_CONTROL_FLAG NOT NULL VARCHAR2(1) Flag to indicate if theconcurrent program controlsconcurrent managers




QUEUE_METHOD_CODE NOT NULL VARCHAR2(1) Code to indicate whether theconcurrent program isconstrained

REQUEST_SET_FLAG NOT NULL VARCHAR2(1) Flag to indicate whether theconcurrent program is a parentof a report set

ENABLED_FLAG NOT NULL VARCHAR2(1) Enabled flagPRINT_FLAG NOT NULL VARCHAR2(1) Flag to indicate whether the

concurrent manager should printoutput of the concurrentprogram

RUN_ALONE_FLAG NOT NULL VARCHAR2(1) Flag to indicate if this is arun alone concurrent program

SRS_FLAG NOT NULL VARCHAR2(1) Flag to indicate if a requestcan be submitted for thisconcurrent program fromStandard Report Submission

CLASS_APPLICATION_ID NULL NUMBER(15) Identifier of application forwith which the request type ofthis program is identified

CONCURRENT_CLASS_ID NULL NUMBER(15) Request type identifierEXECUTION_OPTIONS NULL VARCHAR2(250) SQL*Report or Oracle Report

program running optionsSAVE_OUTPUT_FLAG NULL VARCHAR2(1) Flag to indicate whether to

save output file for theconcurrent program

REQUIRED_STYLE NOT NULL VARCHAR2(1) Flag to indicate if the printstyle associated with theconcurrent program is mandatory

OUTPUT_PRINT_STYLE NULL VARCHAR2(30) The print style for theconcurrent program output

PRINTER_NAME NULL VARCHAR2(30) Name of printer for printingthe concurrent program output

MINIMUM_WIDTH NULL NUMBER(4) Minimum number of columnsMINIMUM_LENGTH NULL NUMBER(4) Minimum number of rowsREQUEST_PRIORITY NULL NUMBER(15) Program level priority assigned

by the System Administrator toguarantee that programs run atthe same level regardless ofwho submits them(REQUEST_PRIORITY assigned toconcurrent programs overridesthe user profile value)

ATTRIBUTE_CATEGORY NULL VARCHAR2(30) Descriptive flexfield segmentATTRIBUTE1 NULL VARCHAR2(150) Descriptive flexfield segmentATTRIBUTE2 NULL VARCHAR2(150) Descriptive flexfield segmentATTRIBUTE3 NULL VARCHAR2(150) Descriptive flexfield segmentATTRIBUTE4 NULL VARCHAR2(150) Descriptive flexfield segmentATTRIBUTE5 NULL VARCHAR2(150) Descriptive flexfield segmentATTRIBUTE6 NULL VARCHAR2(150) Descriptive flexfield segmentATTRIBUTE7 NULL VARCHAR2(150) Descriptive flexfield segmentATTRIBUTE8 NULL VARCHAR2(150) Descriptive flexfield segmentATTRIBUTE9 NULL VARCHAR2(150) Descriptive flexfield segmentATTRIBUTE10 NULL VARCHAR2(150) Descriptive flexfield segmentATTRIBUTE11 NULL VARCHAR2(150) Descriptive flexfield segmentATTRIBUTE12 NULL VARCHAR2(150) Descriptive flexfield segmentATTRIBUTE13 NULL VARCHAR2(150) Descriptive flexfield segmentATTRIBUTE14 NULL VARCHAR2(150) Descriptive flexfield segmentATTRIBUTE15 NULL VARCHAR2(150) Descriptive flexfield segment




IPROG_ID NULL NUMBER(4) Conflict resolution managerinternal information

OUTPUT_FILE_TYPE NULL VARCHAR2(4) Format of output fileENABLE_TRACE NOT NULL VARCHAR2(1) Turns on tracing for requestsRESTART NOT NULL VARCHAR2(1) Indicates program may be

restartedNLS_COMPLIANT NOT NULL VARCHAR2(1) Indicates if the program is NLS

compliant. In particular,indicates if the programaccepts date and numberparameters in canonical format

ICON_NAME NULL VARCHAR2(30) Reserved for future useCD_PARAMETER NULL VARCHAR2(240) Parameter used to identify

conflict domainsINCREMENT_PROC NULL VARCHAR2(61) Procedure name used to

increment program parametersMLS_EXECUTABLE_APP_ID NULL NUMBER(15) Application identifier for MLS

language functionMLS_EXECUTABLE_ID NULL NUMBER(15) Identifier for MLS language

functionENABLE_TIME_STATISTICS NOT NULL VARCHAR2(1) Y or N. Timed statistics

collection is turned on for theprogram’s session when set to Y

SECURITY_GROUP_ID NULL NUMBER Security group identifierSTAT_COLLECT NULL VARCHAR2(1) Reserved for future useRESOURCE_CONSUMER_GROUP NULL VARCHAR2(30) Resource consumer groupROLLBACK_SEGMENT NULL VARCHAR2(30) Rollback segment for a

transactionOPTIMIZER_MODE NULL VARCHAR2(30) Optimization mode, such as

RULE, FIRST_ROW, etc.

Indexes



FND_CONCURRENT_PROGRAMS_U1 UNIQUE 1 APPLICATION_ID2 CONCURRENT_PROGRAM_IDFND_CONCURRENT_PROGRAMS_U2 UNIQUE 1 APPLICATION_ID2 CONCURRENT_PROGRAM_NAME


FND_CONCURRENT_PROGRAMS_S CONCURRENT_PROGRAM_ID



FND_CONCURRENT_REQUESTS

FND_CONCURRENT_REQUESTS stores information about individualconcurrent requests. Each row includes values that identify theparticular request and its parameters, such as who submitted it,therequest type, whether the request should run sequentially with otherrequests in the same logical database(SINGLE_THREAD_FLAG),whether the request is on hold(HOLD_FLAG), whether to display the request in the View Requestsform for the request submitter tore view, and what status and phase theconcurrent request is in.Each row also includes values that identify theconcurrent program,its execution and argument methods, and whetherthe program is constrained (QUEUE_METHOD_CODE). Each row alsoincludes flags that indicate there quest’s priority relative to otherrequests, as well as values that specify how the concurrent managershould print program output, if any. ARGUMENT1 throughARGUMENT25 contain any arguments the application passes to theconcurrent program. If the concurrent program needs more than 25arguments to run, the first arguments are stored in this table,ARGUMENT26 are stored in FND_CONC_REQUEST_ARGUMENTS.ARGUMENT_TEXTcontains the concatenation of concurrent requestarguments and COMPLETION_TEXT contains a message about how therequest completed. The row also contains dates that the request wassubmitted, requested to start and actually run. REQ_INFORMATION isused with report sets to remember the status of the request betweenruns.When the request is set to use automatic resubmission,RESUBMITTEDis a flag to indicate whether the request has beenresubmitted or not. RESUBMIT_INTERVAL_TYPE_CODE specifieswhether to start interval count down from the requested start time orthe completion of there quest. RESUBMIT_INTERVAL_UNIT_CODEindicates whether interval unit is in Days, Hours, Minutes, or Months.RESUBMIT_TIME sets the time of the day to rerun the concurrentrequest. RESUBMIT_INTERVALindicates the number of units of timewhen the identical request will be resubmitted.RESUBMIT_END_DATE is the date the requests tops resubmitting itself.IS_SUB_REQUEST is a flag that identifies a child request andHAS_SUB_REQUEST is a flag that identifies a parent request. Eachchild request also needs to have values in PARENT_REQUEST_ID toshow what parent request submitted the child request andPRIORITY_REQUEST_ID to tell what priority the parent request hasand what priority the child request should have.Oracle ApplicationObject Library does not use ENFORCE_SERIALITY_FLAG(always Y),CPU_SECONDS, LOGICAL_IOS, or PHYSICAL_IOS. You need onerow for each concurrent request. Though you should occasionallydelete from this table, you should not modify any of its data.Oracle



Application Object Library uses this information to run concurrentrequests, and automatically updates it as requests change their status.


FND_CONCURRENT_PROCESSES CONCURRENT_PROCESS_ID CONTROLLING_MANAGERFND_CONCURRENT_PROGRAMS APPLICATION_ID PROGRAM_APPLICATION_IDCONCURRENT_PROGRAM_ID CONCURRENT_PROGRAM_IDFND_CONCURRENT_REQUESTS REQUEST_ID PARENT_REQUEST_IDFND_CONCURRENT_REQUESTS REQUEST_ID PRIORITY_REQUEST_IDFND_CONCURRENT_REQUEST_CLASS APPLICATION_ID REQUEST_CLASS_APPLICATION_IDREQUEST_CLASS_ID CONCURRENT_REQUEST_CLASS_IDFND_CONC_RELEASE_CLASSES APPLICATION_ID RELEASE_CLASS_APP_IDRELEASE_CLASS_ID RELEASE_CLASS_IDFND_CONFLICTS_DOMAIN CD_ID CD_IDFND_LOGINS LOGIN_ID CONC_LOGIN_IDFND_NODES NODE_NAME LOGFILE_NODE_NAMEFND_NODES NODE_NAME OUTFILE_NODE_NAMEFND_ORACLE_USERID ORACLE_ID ORACLE_IDFND_PRINTER PRINTER_NAME PRINTERFND_PRINTER_STYLES PRINTER_STYLE_NAME PRINT_STYLEFND_RESPONSIBILITY APPLICATION_ID RESPONSIBILITY_APPLICATION_IDRESPONSIBILITY_ID RESPONSIBILITY_IDFND_USER USER_ID REQUESTED_BY


ENFORCE_SERIALITY_FLAG YES_NO FND_LOOKUPSN NoY Yes

HAS_SUB_REQUEST YES_NO FND_LOOKUPSN NoY Yes

HOLD_FLAG YES_NO FND_LOOKUPSN NoY Yes

IS_SUB_REQUEST YES_NO FND_LOOKUPSN NoY Yes

PHASE_CODE CP_PHASE_CODE FND_LOOKUPSC CompletedI InactiveP PendingR Running

QUEUE_METHOD_CODE CP_QUEUE_METHOD_CODE FND_LOOKUPSB YesI No

SAVE_OUTPUT_FLAG YES_NO FND_LOOKUPSN NoY Yes

SINGLE_THREAD_FLAG YES_NO FND_LOOKUPSN No



QuickCodes Columns (Continued)Column QuickCodes Type QuickCodes Table

Y Yes

STATUS_CODE CP_STATUS_CODE FND_LOOKUPSA WaitingB ResumingC NormalD CancelledE ErrorF ScheduledG WarningH On HoldI NormalM No ManagerQ StandbyR NormalS SuspendedT TerminatingU DisabledW PausedX TerminatedZ Waiting

UPDATE_PROTECTED YES_NO FND_LOOKUPSN NoY Yes


REQUEST_ID (PK) NOT NULL NUMBER(15) Concurrent request identifierLAST_UPDATE_DATE NOT NULL DATE Standard Who columnLAST_UPDATED_BY NOT NULL NUMBER(15) Standard Who columnREQUEST_DATE NOT NULL DATE Concurrent request submission

dateREQUESTED_BY NOT NULL NUMBER(15) Username of the requestorPHASE_CODE NOT NULL VARCHAR2(1) Code to indicate in what phase

the concurrent request isSTATUS_CODE NOT NULL VARCHAR2(1) The current status of the

concurrent requestPRIORITY_REQUEST_ID NOT NULL NUMBER(15) Request identifier of the

oldest ancestor or parentrequest

PRIORITY NOT NULL NUMBER(15) Priority of the concurrentrequest

REQUESTED_START_DATE NOT NULL DATE The date and time when userswant the request to startrunning

HOLD_FLAG NOT NULL VARCHAR2(1) Flag to indicate if concurrentrequest is on hold

ENFORCE_SERIALITY_FLAG NOT NULL VARCHAR2(1) Not currently usedSINGLE_THREAD_FLAG NOT NULL VARCHAR2(1) Flag to indicate whether to run

the request sequentially withother requests in the samelogical database

HAS_SUB_REQUEST NOT NULL VARCHAR2(1) Flag to identify the currentrequest as a parent request

IS_SUB_REQUEST NOT NULL VARCHAR2(1) Flag to identify the request asa child request




IMPLICIT_CODE NOT NULL VARCHAR2(1) Code to specify whether therequest appears in the ViewRequest form for the requestsubmitter

UPDATE_PROTECTED NOT NULL VARCHAR2(1) Flag to indicate if requestoris allowed to delete therequest or update any of therequest’s attributes

QUEUE_METHOD_CODE NOT NULL VARCHAR2(1) Code to indicate if concurrentprogram is constrained

ARGUMENT_INPUT_METHOD_CODE NOT NULL VARCHAR2(1) Flag to indicate if the requestuses token as argument inputmethod

ORACLE_ID NOT NULL NUMBER(15) The ORACLE account used to runthe concurrent request

PROGRAM_APPLICATION_ID NOT NULL NUMBER(15) Identifier of application withwhich that concurrent programis registered

CONCURRENT_PROGRAM_ID NOT NULL NUMBER(15) Concurrent program identifierRESPONSIBILITY_APPLICATION_ID NOT NULL NUMBER(15) Identifier of the application

with which the responsibilityis defined

RESPONSIBILITY_ID NOT NULL NUMBER(15) Responsibility identifierNUMBER_OF_ARGUMENTS NOT NULL NUMBER(3) Number of argumentsNUMBER_OF_COPIES NOT NULL NUMBER(15) Number of copies to printSAVE_OUTPUT_FLAG NOT NULL VARCHAR2(1) Flag to indicate whether to

save output to a fileNLS_COMPLIANT NOT NULL VARCHAR2(1) Indicates if program is NLS

compliantLAST_UPDATE_LOGIN NULL NUMBER(15) Standard Who columnNLS_LANGUAGE NULL VARCHAR2(30) LanguageNLS_TERRITORY NULL VARCHAR2(30) The territory using the

languagePRINTER NULL VARCHAR2(30) Name of printer to print outputPRINT_STYLE NULL VARCHAR2(30) Output print stylePRINT_GROUP NULL VARCHAR2(1) Flag to indicate whether to

print the request outputtogether with other reports orprograms in the report set

REQUEST_CLASS_APPLICATION_ID NULL NUMBER(15) Identifier of application withwhich request type is defined

CONCURRENT_REQUEST_CLASS_ID NULL NUMBER(15) Request type identifierPARENT_REQUEST_ID NULL NUMBER(15) Request identifier of the

request that submits thisrequest

CONC_LOGIN_ID NULL NUMBER(15) Login session identifierLANGUAGE_ID NULL NUMBER(15) Language identifierDESCRIPTION NULL VARCHAR2(240) DescriptionREQ_INFORMATION NULL VARCHAR2(240) Miscellaneous information for

the request to be used with theparent request of a report set

RESUBMIT_INTERVAL NULL NUMBER(15,10) The number of units to resubmita request

RESUBMIT_INTERVAL_UNIT_CODE NULL VARCHAR2(30) Code to indicate whetherresubmit interval unit is inDays, Hours, Minutes, or Months

RESUBMIT_INTERVAL_TYPE_CODE NULL VARCHAR2(30) Code indicating whether tostart interval count down fromthe requested start time or thecompletion of the request




RESUBMIT_TIME NULL VARCHAR2(8) The time of the day toregularly resubmit the request

RESUBMIT_END_DATE NULL DATE The end date for resubmittingthe request

RESUBMITTED NULL VARCHAR2(1) Flag to indicate whether therequest has been resubmitted

CONTROLLING_MANAGER NULL NUMBER(15) Identifier of concurrentmanager that processed thisrequest

ACTUAL_START_DATE NULL DATE The actual time and date whenthe request started running

ACTUAL_COMPLETION_DATE NULL DATE The time and date when therequest was completed

COMPLETION_TEXT NULL VARCHAR2(240) The text message about how therequest completed

OUTCOME_PRODUCT NULL VARCHAR2(20) Not currently usedOUTCOME_CODE NULL NUMBER(15) Not currently usedCPU_SECONDS NULL NUMBER(15,3) Not currently usedLOGICAL_IOS NULL NUMBER(15) Not currently usedPHYSICAL_IOS NULL NUMBER(15) Not currently usedLOGFILE_NAME NULL VARCHAR2(255) Logfile nameLOGFILE_NODE_NAME NULL VARCHAR2(30) The name of node or machine on

which to create the log fileOUTFILE_NAME NULL VARCHAR2(255) Name of output fileOUTFILE_NODE_NAME NULL VARCHAR2(30) The name of node or machine on

which to create the output fileARGUMENT_TEXT NULL VARCHAR2(240) Concurrent Request ArgumentARGUMENT1 NULL VARCHAR2(240) Concurrent Request ArgumentARGUMENT2 NULL VARCHAR2(240) Concurrent Request ArgumentARGUMENT3 NULL VARCHAR2(240) Concurrent Request ArgumentARGUMENT4 NULL VARCHAR2(240) Concurrent Request ArgumentARGUMENT5 NULL VARCHAR2(240) Concurrent Request ArgumentARGUMENT6 NULL VARCHAR2(240) Concurrent Request ArgumentARGUMENT7 NULL VARCHAR2(240) Concurrent Request ArgumentARGUMENT8 NULL VARCHAR2(240) Concurrent Request ArgumentARGUMENT9 NULL VARCHAR2(240) Concurrent Request ArgumentARGUMENT10 NULL VARCHAR2(240) Concurrent Request ArgumentARGUMENT11 NULL VARCHAR2(240) Concurrent Request ArgumentARGUMENT12 NULL VARCHAR2(240) Concurrent Request ArgumentARGUMENT13 NULL VARCHAR2(240) Concurrent Request ArgumentARGUMENT14 NULL VARCHAR2(240) Concurrent Request ArgumentARGUMENT15 NULL VARCHAR2(240) Concurrent Request ArgumentARGUMENT16 NULL VARCHAR2(240) Concurrent Request ArgumentARGUMENT17 NULL VARCHAR2(240) Concurrent Request ArgumentARGUMENT18 NULL VARCHAR2(240) Concurrent Request ArgumentARGUMENT19 NULL VARCHAR2(240) Concurrent Request ArgumentARGUMENT20 NULL VARCHAR2(240) Concurrent Request ArgumentARGUMENT21 NULL VARCHAR2(240) Concurrent Request ArgumentARGUMENT22 NULL VARCHAR2(240) Concurrent Request ArgumentARGUMENT23 NULL VARCHAR2(240) Concurrent Request ArgumentARGUMENT24 NULL VARCHAR2(240) Concurrent Request ArgumentARGUMENT25 NULL VARCHAR2(240) Concurrent Request ArgumentCRM_THRSHLD NULL NUMBER(15) Used internally by the conflict

resolution managerCRM_TSTMP NULL DATE Used internally by the conflict

resolution managerCRITICAL NULL VARCHAR2(1) Is this a critical storage




REQUEST_TYPE NULL VARCHAR2(1) Specialization typeORACLE_PROCESS_ID NULL VARCHAR2(30) Database process identifierORACLE_SESSION_ID NULL NUMBER(15) Database session identifierOS_PROCESS_ID NULL VARCHAR2(240) Operating system process

identifierPRINT_JOB_ID NULL VARCHAR2(240) Reserved for future useOUTPUT_FILE_TYPE NULL VARCHAR2(4) Format of output fileRELEASE_CLASS_APP_ID NULL NUMBER Application identifier of the

scheduleRELEASE_CLASS_ID NULL NUMBER Schedule identifierSTALE_DATE NULL DATE Used for advanced schedulesCANCEL_OR_HOLD NULL VARCHAR2(1) Used for advanced schedulesNOTIFY_ON_PP_ERROR NULL VARCHAR2(255) User to notify if post

processing steps failCD_ID NULL NUMBER Conflict domain identifierREQUEST_LIMIT NULL VARCHAR2(1) Indicates maximum number of

requests a user may submit atone time

CRM_RELEASE_DATE NULL DATE Date at which conflicts wereresolved

POST_REQUEST_STATUS NULL VARCHAR2(1) Reserved for future useCOMPLETION_CODE NULL VARCHAR2(30) Indicates the completion status

of the request, such as successINCREMENT_DATES NULL VARCHAR2(1) Flag to increment date

parameters on resubmissionRESTART NULL VARCHAR2(1) Indicates program may be

restartedENABLE_TRACE NULL VARCHAR2(1) Turns on tracing for requestsRESUB_COUNT NULL NUMBER Resubmission count (for

repeating requests)NLS_CODESET NULL VARCHAR2(30) Character setOFILE_SIZE NULL NUMBER(15) Filesize of request out in

bytesLFILE_SIZE NULL NUMBER(15) Filesize of request log in

bytesSTALE NULL VARCHAR2(1) Used with Scheduler to indicate

requests that could not be runwithin the specified/requiredperiod

SECURITY_GROUP_ID NULL NUMBER Security group identifierRESOURCE_CONSUMER_GROUP NULL VARCHAR2(30) Database Resource Manager group

under which this request shouldbe processed/run

EXP_DATE NULL DATE Expiration date for requestQUEUE_APP_ID NULL NUMBER(15) Not currently used (To

associate request with aspecific manager)

QUEUE_ID NULL NUMBER(15) Not currently used (Toassociate request with aspecific manager)

OPS_INSTANCE NOT NULL NUMBER Oracle Parallel System instanceidentifier

Indexes





FND_CONCURRENT_REQUESTS_N1 NOT UNIQUE 1 REQUESTED_BY3 ACTUAL_COMPLETION_DATEFND_CONCURRENT_REQUESTS_N2 NOT UNIQUE 1 STATUS_CODEFND_CONCURRENT_REQUESTS_N3 NOT UNIQUE 1 PARENT_REQUEST_IDFND_CONCURRENT_REQUESTS_N4 NOT UNIQUE 1 PRIORITY_REQUEST_IDFND_CONCURRENT_REQUESTS_N5 NOT UNIQUE 1 DESCRIPTIONFND_CONCURRENT_REQUESTS_N6 NOT UNIQUE 1 CONCURRENT_PROGRAM_ID2 PROGRAM_APPLICATION_IDFND_CONCURRENT_REQUESTS_N7 NOT UNIQUE 1 PHASE_CODE2 STATUS_CODEFND_CONCURRENT_REQUESTS_N8 NOT UNIQUE 1 RESPONSIBILITY_APPLICATION_ID2 RESPONSIBILITY_IDFND_CONCURRENT_REQUESTS_U1 UNIQUE 1 REQUEST_ID


FND_CONCURRENT_REQUESTS_S REQUEST_ID



FND_DATA_GROUPS

FND_DATA_GROUPS stores information about different datagroups.Each row includes a data group identifier, a data groupname,and a flag that indicates if the data group is created during installor upgrade. You need one row for each data group that you defineusing Oracle Application Object Library.


DEFAULT_GROUP_FLAG YES_NO FND_LOOKUPSN NoY Yes


DATA_GROUP_ID (PK) NOT NULL NUMBER(15) Data group identifierDATA_GROUP_NAME NOT NULL VARCHAR2(30) Data group nameLAST_UPDATE_DATE NOT NULL DATE Standard Who columnLAST_UPDATED_BY NOT NULL NUMBER(15) Standard Who columnCREATION_DATE NOT NULL DATE Standard Who columnCREATED_BY NOT NULL NUMBER(15) Standard Who columnLAST_UPDATE_LOGIN NOT NULL NUMBER(15) Standard Who columnDEFAULT_GROUP_FLAG NOT NULL VARCHAR2(1) Flag to indicate whether this

is an Oracle Applicationdefined data group

DESCRIPTION NULL VARCHAR2(240) Description

Indexes



FND_DATA_GROUPS_U1 UNIQUE 1 DATA_GROUP_IDFND_DATA_GROUPS_U2 UNIQUE 1 DATA_GROUP_NAME


FND_DATA_GROUPS_S DATA_GROUP_ID



FND_FORM

FND_FORM stores information about your registered application forms.Each row includes names (the actual SQL*Forms form name, and theEasyForm form title) and a description of the form. Each row alsoincludes a flag that indicates whether this form is included in theAuditTrail audit set. You need one row for each form in eachapplication. Oracle application Object Library uses this information forthe RegressionTester, on–line Help, EasyForm, Zoom, AuditTrail andother purposes.


FND_APPLICATION APPLICATION_ID APPLICATION_ID


AUDIT_ENABLED_FLAG YES_NO FND_LOOKUPSN NoY Yes


APPLICATION_ID (PK) NOT NULL NUMBER Application identifierFORM_ID (PK) NOT NULL NUMBER Form identifierFORM_NAME NOT NULL VARCHAR2(30) Form nameLAST_UPDATE_DATE NOT NULL DATE Standard Who columnLAST_UPDATED_BY NOT NULL NUMBER(15) Standard Who columnCREATION_DATE NOT NULL DATE Standard Who columnCREATED_BY NOT NULL NUMBER(15) Standard Who columnLAST_UPDATE_LOGIN NOT NULL NUMBER(15) Standard Who columnAUDIT_ENABLED_FLAG NOT NULL VARCHAR2(1) Flag to indicate if this form

is included in the AuditTrialaudit set

Indexes



FND_FORM_U1 UNIQUE 1 APPLICATION_ID2 FORM_IDFND_FORM_U2 UNIQUE 1 FORM_NAME2 APPLICATION_ID


FND_FORM_S FORM_ID



FND_LOOKUP_VALUES

FND_LOOKUP_VALUES stores Oracle Application Object LibraryQuickCodevalues. Each row includes the QuickCode lookup type, theQuickCodeitself, its meaning, and additional description, as well asvalues that indicate whether this QuickCode is currently valid. Eachrow also includes a language code that indicates what language theinformation is in. You need one row for each QuickCode in each of thelanguages installed at your site. Oracle Application ObjectLibrary usesthis information to display LOVs for OracleApplication Object Libraryforms and other forms.


FND_LOOKUP_TYPES LOOKUP_TYPE LOOKUP_TYPESECURITY_GROUP_ID SECURITY_GROUP_IDVIEW_APPLICATION_ID VIEW_APPLICATION_ID


LOOKUP_TYPE (PK) NOT NULL VARCHAR2(30) QuickCode lookup typeLANGUAGE (PK) NOT NULL VARCHAR2(30) LanguageLOOKUP_CODE (PK) NOT NULL VARCHAR2(30) QuickCode codeMEANING NOT NULL VARCHAR2(80) QuickCode meaningDESCRIPTION NULL VARCHAR2(240) DescriptionENABLED_FLAG NOT NULL VARCHAR2(1) Enabled flagSTART_DATE_ACTIVE NULL DATE The date when the QuickCode

becomes activeEND_DATE_ACTIVE NULL DATE The date when the QuickCode

becomes inactiveCREATED_BY NOT NULL NUMBER(15) Standard Who columnCREATION_DATE NOT NULL DATE Standard Who columnLAST_UPDATED_BY NOT NULL NUMBER(15) Standard Who columnLAST_UPDATE_LOGIN NULL NUMBER(15) Standard Who columnLAST_UPDATE_DATE NOT NULL DATE Standard Who columnSOURCE_LANG NOT NULL VARCHAR2(4) The Language the text will

mirror. If text is not yettranslated into LANGUAGE thenany changes to the text in thesource language row will bereflected here as well.

SECURITY_GROUP_ID (PK) NOT NULL NUMBER(15) Security group identifierVIEW_APPLICATION_ID (PK) NOT NULL NUMBER(15) Identifies which application’s

view will include the lookupvalues

TERRITORY_CODE NULL VARCHAR2(2) Territory code of territoryusing the language

ATTRIBUTE_CATEGORY NULL VARCHAR2(30) Attribute categoryATTRIBUTE1 NULL VARCHAR2(150) AttributeATTRIBUTE2 NULL VARCHAR2(150) AttributeATTRIBUTE3 NULL VARCHAR2(150) AttributeATTRIBUTE4 NULL VARCHAR2(150) AttributeATTRIBUTE5 NULL VARCHAR2(150) AttributeATTRIBUTE6 NULL VARCHAR2(150) AttributeATTRIBUTE7 NULL VARCHAR2(150) Attribute




ATTRIBUTE8 NULL VARCHAR2(150) AttributeATTRIBUTE9 NULL VARCHAR2(150) AttributeATTRIBUTE10 NULL VARCHAR2(150) AttributeATTRIBUTE11 NULL VARCHAR2(150) AttributeATTRIBUTE12 NULL VARCHAR2(150) AttributeATTRIBUTE13 NULL VARCHAR2(150) AttributeATTRIBUTE14 NULL VARCHAR2(150) AttributeATTRIBUTE15 NULL VARCHAR2(150) AttributeTAG NULL VARCHAR2(30) Optional additional category

for lookup values

Indexes



FND_LOOKUP_VALUES_U1 UNIQUE 1 LOOKUP_TYPE3 VIEW_APPLICATION_ID5 LOOKUP_CODE7 SECURITY_GROUP_ID9 LANGUAGEFND_LOOKUP_VALUES_U2 UNIQUE 1 LOOKUP_TYPE3 VIEW_APPLICATION_ID5 MEANING7 SECURITY_GROUP_ID9 LANGUAGE

Sequences




FND_ORACLE_USERID

FND_ORACLE_USERID stores information about ORACLE accountsthat contain application data. Each row includes the ORACLEusername and description, the logical database this ORACLE ID belongsto(for concurrent processing), whether this ORACLE ID is enabled, andwhether this ORACLE ID is restricted from changing OracleApplicationObject Library data such as menus (READ_ONLY_FLAG).OracleApplication Object Library does not useORACLE_PASSWORD,CONCURRENT_BATCH_QUEUE_ID orREAD_ONLY_ORACLE_ID. You need one row for each ORACLE IDyou register. Oracle Application ObjectLibrary uses this information toallow users access to application data on the basis of responsibility.



READ_ONLY_FLAG ORACLEID_PRIVILEGE_IS FND_LOOKUPSA EnabledB RestrictedD Disabled


ORACLE_ID (PK) NOT NULL NUMBER Identifier for ORACLE accountORACLE_USERNAME NOT NULL VARCHAR2(30) Username for the ORACLE accountLAST_UPDATE_DATE NOT NULL DATE Standard Who columnLAST_UPDATED_BY NOT NULL NUMBER(15) Standard Who columnCREATION_DATE NOT NULL DATE Standard Who columnCREATED_BY NOT NULL NUMBER(15) Standard Who columnLAST_UPDATE_LOGIN NOT NULL NUMBER(15) Standard Who columnDESCRIPTION NULL VARCHAR2(240) DescriptionENABLED_FLAG NULL VARCHAR2(1) Flag to indicate if the ORACLE

account is activeREAD_ONLY_FLAG NULL VARCHAR2(1) Flag to indicate if the ORACLE

account can update OracleApplication Object Library data

ENCRYPTED_ORACLE_PASSWORD NULL VARCHAR2(100) Password for the ORACLE accountin a encrypted format

CONCURRENT_BATCH_QUEUE_ID NULL NUMBER(15) Not currently usedINSTALL_GROUP_NUM NULL NUMBER Indicates set of books

Indexes



FND_ORACLE_USERID_U1 UNIQUE 1 ORACLE_IDFND_ORACLE_USERID_U2 UNIQUE 1 ORACLE_USERNAME




FND_ORACLE_USERID_S ORACLE_ID



FND_PRINTER

FND_PRINTER stores information about printers. Each row includes aname and description of the printer, as well as the printer type.You needone row for each printer installed at your site. Oracle application ObjectLibrary uses this information to printout put such as reports.


FND_PRINTER_TYPES PRINTER_TYPE PRINTER_TYPE


PRINTER_NAME (PK) NOT NULL VARCHAR2(30) Name of printerLAST_UPDATE_DATE NOT NULL DATE Standard Who columnLAST_UPDATED_BY NOT NULL NUMBER(15) Standard Who columnCREATION_DATE NOT NULL DATE Standard Who columnCREATED_BY NOT NULL NUMBER(15) Standard Who columnLAST_UPDATE_LOGIN NOT NULL NUMBER(15) Standard Who columnPRINTER_TYPE NOT NULL VARCHAR2(30) Printer type

Indexes



FND_PRINTER_U1 UNIQUE 1 PRINTER_NAME

Sequences




FND_PRODUCT_INSTALLATIONS

FND_PRODUCT_INSTALLATIONS stores information about OracleApplicationsproducts at your site. Each row includes a valueidentifying the application (APPLICATION_ID), a value identifying thedatabase account(ORACLE_ID), the product’s version number(PRODUCT_VERSION), the product’s status at your site (STATUS,where I means installed,L means custom, N means not installed, and Smeans installed as shared product), and the product’s industry(INDUSTRY, where C means for commercial or for–profit use, G meansfor educational or not–for–profit use, B means Project Billing, and Pmeans ProjectCosting). Each row also includes the names of thetablespace in which the application tables, indexes, and temporaryobjects reside(TABLESPACE, INDEX_TABLESPACE, andTEMPORARY_TABLESPACE), and the sizing factor for the product(SIZING_FACTOR).Oracle Applications uses this information to displayproduct version numbers when you choose \ Help Version, wheninstalling and upgrading your database, and for other purposes.


FND_APPLICATION APPLICATION_ID APPLICATION_IDFND_ORACLE_USERID ORACLE_ID ORACLE_ID


DB_STATUS FND_PRODUCT_STATUS FND_LOOKUPSI InstalledL CustomN Not installedS Shared

INDUSTRY FND_PRODUCT_INDUSTRY FND_LOOKUPSB Project BillingC CommercialG GovernmentN UnknownP Project CostingT Test purposes

STATUS FND_PRODUCT_STATUS FND_LOOKUPSI InstalledL CustomN Not installedS Shared


APPLICATION_ID (PK) NOT NULL NUMBER(15) Application identifierORACLE_ID (PK) NOT NULL NUMBER(15) ORACLE account in which the

application is installed




LAST_UPDATE_DATE NOT NULL DATE Standard Who columnLAST_UPDATED_BY NOT NULL NUMBER(15) Standard Who columnCREATION_DATE NOT NULL DATE Standard Who columnCREATED_BY NOT NULL NUMBER(15) Standard Who columnLAST_UPDATE_LOGIN NOT NULL NUMBER(15) Standard Who columnPRODUCT_VERSION NULL VARCHAR2(30) Version number for the

applicationSTATUS NULL VARCHAR2(1) The status of the applicationINDUSTRY NULL VARCHAR2(1) The industry of the applicationTABLESPACE NULL VARCHAR2(30) Name of tablespace for the

application’s tablesINDEX_TABLESPACE NULL VARCHAR2(30) Name of tablespace for the

application’s indexesTEMPORARY_TABLESPACE NULL VARCHAR2(30) Name of tablespace for

temporary objectsSIZING_FACTOR NULL NUMBER The sizing factor for the

applicationINSTALL_GROUP_NUM NULL NUMBER(15)DB_STATUS NULL VARCHAR2(1)PATCH_LEVEL NULL VARCHAR2(30)

Indexes



FND_PRODUCT_INSTALLATIONS_PK UNIQUE 1 APPLICATION_ID2 ORACLE_ID

Sequences




FND_RESPONSIBILITY

FND_RESPONSIBILITY stores information about responsibilities. Eachrow includes the name and description of the responsibility, theapplication it belongs to, and values that identify the main menu, andthe first form that it uses. Each row also includes values that identifythe data group and the data group application identifier. Oracleapplication Object Library uses GROUP_APPLICATION_ID Andrequest_GROUP_ID to identify report security group assigned to theresponsibilities. TERM_SECURITY_ENABLED_FLAG is if Security byTerminal is enabled for the responsibility. You need one row for eachresponsibility at your site. Oracle application Object Library uses thisinformation to determine which application data, forms, menus andreports a user can access.


FND_APPLICATION APPLICATION_ID APPLICATION_IDFND_DATA_GROUP_UNITS APPLICATION_ID DATA_GROUP_APPLICATION_IDDATA_GROUP_ID DATA_GROUP_IDFND_MENUS MENU_ID MENU_IDFND_REQUEST_GROUPS APPLICATION_ID GROUP_APPLICATION_IDREQUEST_GROUP_ID REQUEST_GROUP_ID


TERM_SECURITY_ENABLED_FLAG YES_NO FND_LOOKUPSN NoY Yes


APPLICATION_ID (PK) NOT NULL NUMBER(15) Application identifierRESPONSIBILITY_ID (PK) NOT NULL NUMBER(15) Responsibility identifierLAST_UPDATE_DATE NOT NULL DATE Standard Who columnLAST_UPDATED_BY NOT NULL NUMBER(15) Standard Who columnCREATION_DATE NOT NULL DATE Standard Who columnCREATED_BY NOT NULL NUMBER(15) Standard Who columnLAST_UPDATE_LOGIN NULL NUMBER(15) Standard Who columnDATA_GROUP_APPLICATION_ID NOT NULL NUMBER(15) Data group application

identifierDATA_GROUP_ID NOT NULL NUMBER(15) Data group identifierMENU_ID NOT NULL NUMBER(15) Menu identifierTERM_SECURITY_ENABLED_FLAG NULL VARCHAR2(1) Flag to indicate if Security by

Terminal is enabled for theresponsibility

START_DATE NOT NULL DATE The date the responsibilitybecomes active

END_DATE NULL DATE The date the responsibilityexpires

GROUP_APPLICATION_ID NULL NUMBER(15) Application identifier fromreport security groupdefinition




REQUEST_GROUP_ID NULL NUMBER(15) Identifier of report securitygroup assigned to theresponsibility

VERSION NULL VARCHAR2(1) Version of responsibility. Forexample, web (W) or AOL (4)

WEB_HOST_NAME NULL VARCHAR2(80) IP address or alias of machinewhere the Webserver is running.Defaults to the last agent

WEB_AGENT_NAME NULL VARCHAR2(80) Name of Oracle Web Agent.Defaults to the last agent

RESPONSIBILITY_KEY NOT NULL VARCHAR2(30) Internal developer name forresponsibility

Indexes



FND_RESPONSIBILITY_U1 UNIQUE 4 APPLICATION_ID6 RESPONSIBILITY_IDFND_RESPONSIBILITY_U2 UNIQUE 1 RESPONSIBILITY_KEY2 APPLICATION_ID


FND_RESPONSIBILITY_S RESPONSIBILITY_ID



FND_TABLES

FND_TABLES stores information about the registered tables in yourapplications. Each row includes the actual table name(TABLE_NAME)a more descriptive title (USER_TABLE_NAME), and adescription.Each row also contains information about the storageparameters fort he table, a flag (AUTO_SIZE) which indicates whetherthe install should automatically apply a sizing factor to the storageparameters,and the type of the table. You need one row for each table ineach application. Oracle Applications uses this information facilitator,when installing and upgrading your database, and for other purposes.


FND_APPLICATION APPLICATION_ID APPLICATION_ID


AUTO_SIZE YES_NO FND_LOOKUPSN NoY Yes

TABLE_TYPE TABLE_TYPE FND_LOOKUPSF Special Flexfield DataI InterimS Seed DataT Transaction Data


APPLICATION_ID (PK) NOT NULL NUMBER(15) Application identifierTABLE_ID (PK) NOT NULL NUMBER(15) Table identifierTABLE_NAME NOT NULL VARCHAR2(30) Table nameUSER_TABLE_NAME NOT NULL VARCHAR2(80) Table titleLAST_UPDATE_DATE NOT NULL DATE Standard Who columnLAST_UPDATED_BY NOT NULL NUMBER(15) Standard Who columnCREATION_DATE NOT NULL DATE Standard Who columnCREATED_BY NOT NULL NUMBER(15) Standard Who columnLAST_UPDATE_LOGIN NOT NULL NUMBER(15) Standard Who columnAUTO_SIZE NOT NULL VARCHAR2(1) Flag to indicate if this table

is automatically sized duringan install

TABLE_TYPE NOT NULL VARCHAR2(1) Type of the table (seed data,transaction data, interim)

INITIAL_EXTENT NOT NULL NUMBER(15) Initial extent storageparameter

NEXT_EXTENT NOT NULL NUMBER(15) Next extent storage parameterMIN_EXTENTS NOT NULL NUMBER(15) Minimum extents storage

parameterMAX_EXTENTS NOT NULL NUMBER(15) Maximum extents storage

parameter




PCT_INCREASE NOT NULL NUMBER(15) Percent increase storageparameter

INI_TRANS NOT NULL NUMBER(15) Initial transactions storageparameter

MAX_TRANS NOT NULL NUMBER(15) Maximum transactions storageparameter

PCT_FREE NOT NULL NUMBER(15) Percent free storage parameterPCT_USED NOT NULL NUMBER(15) Percent used storage parameterDESCRIPTION NULL VARCHAR2(240) Description

Indexes



FND_TABLES_U1 UNIQUE 1 APPLICATION_ID2 TABLE_ID

FND_TABLES_U2 UNIQUE 1 APPLICATION_ID2 TABLE_NAME

FND_TABLES_U3 UNIQUE 1 APPLICATION_ID2 USER_TABLE_NAME


FND_TABLES_S TABLE_ID



FND_USER

FND_USER stores information about application users. Each rowincludes the user’s username (what a user types in at the sign–onscreen), password, and information on when the user should change thepassword. Each row also contains information on when the user lastsigned on, start and end dates for when a username is valid and adescription of the user. Oracle Application Object Library does not usethe USER_PASSWORD and LOCAL_PRINTER columns. You need onerow for each application user at your site. Oracle Application ObjectLibrary uses this information to allow users to sign on to an application.


USER_ID (PK) NOT NULL NUMBER(15) Application user identifierUSER_NAME NOT NULL VARCHAR2(100) Application username (what a

user types in at the OracleApplications sign–on screen)

LAST_UPDATE_DATE NOT NULL DATE Standard Who columnLAST_UPDATED_BY NOT NULL NUMBER(15) Standard Who columnCREATION_DATE NOT NULL DATE Standard Who columnCREATED_BY NOT NULL NUMBER(15) Standard Who columnLAST_UPDATE_LOGIN NULL NUMBER(15) Standard Who columnENCRYPTED_FOUNDATION_PASSWORD NOT NULL VARCHAR2(100) The Oracle Application Object

Library encrypted password usedto connect to database

ENCRYPTED_USER_PASSWORD NOT NULL VARCHAR2(100) The encrypted password for theapplication user to sign on toOracle Applications

SESSION_NUMBER NOT NULL NUMBER The session number of theapplication user’s last sign–onsession

START_DATE NOT NULL DATE The date the password becomesactive

END_DATE NULL DATE The date the password expiresDESCRIPTION NULL VARCHAR2(240) DescriptionLAST_LOGON_DATE NULL DATE The date the application user

last signed onPASSWORD_DATE NULL DATE The date the current password

was setPASSWORD_ACCESSES_LEFT NULL NUMBER(15) The number of accesses left for

the passwordPASSWORD_LIFESPAN_ACCESSES NULL NUMBER(15) The number of accesses allowed

for the passwordPASSWORD_LIFESPAN_DAYS NULL NUMBER(15) Lifespan of the passwordEMPLOYEE_ID NULL NUMBER(15) Identifier of employee to whom

the application username isassigned

EMAIL_ADDRESS NULL VARCHAR2(240) The Electronic mail address forthe user

FAX NULL VARCHAR2(80) The fax number for the user




CUSTOMER_ID NULL NUMBER(15) Customer contact identifier. Ifthe AOL user is a customercontact, this value is aforeign key to thecorresponding customer contact.

SUPPLIER_ID NULL NUMBER(15) Supplier contact identifier. Ifthe AOL user is a suppliercontact, this value is aforeign key to thecorresponding supplier contact.

WEB_PASSWORD NULL VARCHAR2(240) Unused

Indexes



FND_USER_N1 NOT UNIQUE 1 EMPLOYEE_IDFND_USER_U1 UNIQUE 1 USER_IDFND_USER_U2 UNIQUE 1 USER_NAME


FND_USER_S USER_ID

Index – 1

Index

AApplication Building Block, 1 – 6

CColumn descriptions, 3 – 4Columns, Who, 3 – 4Concurrent Program List, 2 – 20

See also Concurrent Program Definitions

DDatabase Diagram, 1 – 6

Summary Database Diagram, 1 – 6database diagrams

conventions, 2 – 6summary, 2 – 5

Database triggers, 3 – 6

FForeign keys, 3 – 3Form, 1 – 7Form List, 2 – 20

See also Form DefinitionsForms and Table View List, 2 – 18

IIndexes, 3 – 6

important note about, 3 – 6Internal View List, 2 – 19

LLookup types. See QuickCodes

MModule List, 2 – 20

See also Module DefinitionsModules, 1 – 6

OOracle8 sequences. See Sequences

PPublic Table List, 2 – 15

QQuickCodes, 1 – 7

Columns that contain, 3 – 3

RRelationship, 1 – 6Report List. See Report Definitions

SSequences, 3 – 6

Index – 2 Oracle Alert Technical Reference Manual

summary database diagram. See databasediagrams

TTable and View Definitions

ALR_ACTION_DATA, 3 – 10ALR_ACTION_GROUP_MEMBERS, 3 – 14ALR_ACTION_GROUPS, 3 – 12ALR_ACTION_HISTORY, 3 – 16ALR_ACTION_OUTPUTS, 3 – 18ALR_ACTION_SET_CHECKS, 3 – 22ALR_ACTION_SET_INPUTS, 3 – 24ALR_ACTION_SET_MEMBERS, 3 – 26ALR_ACTION_SET_OUTPUTS, 3 – 28ALR_ACTION_SETS, 3 – 20ALR_ACTIONS, 3 – 7ALR_ACTIONS_V, 2 – 18ALR_ACTUAL_RESPONSES, 3 – 30ALR_ALERT_ACTIONS_VIEW, 2 – 19ALR_ALERT_CHECKS, 3 – 35ALR_ALERT_HISTORY_VIEW, 2 – 19ALR_ALERT_INPUTS, 3 – 37ALR_ALERT_INSTALLATIONS, 3 – 39ALR_ALERT_OUTPUTS, 3 – 40ALR_ALERTS, 3 – 32ALR_CHECK_ACTION_HIST ORY_VIEW, 2

– 19ALR_DISTRIBUTION_LISTS, 3 – 42ALR_GROUPS_AND_ACTIONS_VIEW, 2 –

18ALR_INSTALLATIONS_VIEW, 2 – 19ALR_LOOKUPS, 3 – 44ALR_MESSAGE_SYSTEMS, 3 – 45ALR_ORACLE_MAIL_ACCOUNTS, 3 – 46ALR_OUTPUT_HISTORY, 3 – 48ALR_PERIODIC_ALERTS_VIEW, 2 – 19ALR_PERIODIC_SET_MEMBERS, 3 – 51ALR_PERIODIC_SETS, 3 – 50ALR_PROFILE_OPTIONS, 3 – 53

ALR_RESPONSE_ACTION_HIST ORY, 3 –56

ALR_RESPONSE_ACTIONS, 3 – 55ALR_RESPONSE_ACTIONS_VIEW, 2 – 19ALR_RESPONSE_MESSAGES, 3 – 57ALR_RESPONSE_SETS, 3 – 59ALR_RESPONSE_VARIABLE_VALUES, 3 –

62ALR_RESPONSE_VARIABLES, 3 – 60ALR_SCHEDULED_PROGRAMS, 2 – 19ALR_VALID_RESPONSES, 3 – 64ALR_VARIABLES_AND_OUTPUTS, 2 – 19FND_APPLICATION, 3 – 66FND_CONCURRENT_PROGRAMS, 3 – 67FND_CONCURRENT_REQUESTS, 3 – 71FND_DATA_GROUPS, 3 – 78FND_FORM, 3 – 79FND_LOOKUP_VALUES, 3 – 80FND_ORACLE_USERID, 3 – 82FND_PRINTER, 3 – 84FND_PRODUCT_INSTALLATIONS, 3 – 85FND_RESPONSIBILITY, 3 – 87FND_TABLES, 3 – 89FND_USER, 3 – 91

TablesSee also Table and View DefinitionsColumn descriptions, 3 – 4Foreign keys, 3 – 3Indexes. See IndexesPrimary Keys, 3 – 4QuickCodes Columns, 3 – 3Who columns, 3 – 4, 3 – 5

VView Definitions. See Table and View

DefinitionsViews

See also Table and View Definitions; ViewList

Derivation, 3 – 6

CAUTION!This document contains proprietary,

If you are an Oracle customer, thisnumbered copy is registered in your site’s

name. Use, duplication, and disclosure areseverely restricted and subject to

restrictions stated in your contract withOracle Corporation.

If you are an Oracle employee, thisnumbered copy is registered in your name

and must be returned if you leave thecompany. It is your responsibility not to

disclose this information to anyone outsideof Oracle who is not licensed to use this

product. If you have a prospect whoneeds to see this information, contactmailid APPSAPP to obtain a special

nondisclosure agreement.

If you are neither an Oracle customer with avalid contract for the use of this document

nor an Oracle employee, then you receivedthis document in an unauthorized manner

and are not legally entitled to possessor read it. Please return it immediatelyto Oracle. You may call collect to theoffice of the Executive Vice President

Applications Division, to arrange its return.

confidential information that is the exclusiveproperty of Oracle Corporation.

Copy #

��

��

A80845–01

alrtrm

Documents

technical reference

programs software

oracle corporation agreement

oracle corporation products

restricted computer

printed matter

important information

safe use