alerts - full features

7/22/2019 Alerts - Full features

1/69


2/69

Defining a periodic alert:

Enter application and Name. Name the alert (up to 50 characters), and give it a meaningful

description (up to 240 characters).

Enter a name for the alert that is unique within the application. Warning: Use characters other than the pound sign (#), the colon (:),

or the percent sign (%) for your initial letter; as these characters arereserved for use in Enter Query mode.

Select Periodic in the Type field. Check Enabled to enable your periodic alert.

To set the frequency for a periodic alert:


3/69

Select a frequency for your periodic alert. You can choose from nine frequency

options:

On Demand--Oracle Alert checks your periodic alert only when youspecify. You do not have to fill in any other field in the PeriodicDetails block. You check on demand alerts by using the Request

Periodic Alert Check window.

On Day of the Month--If you choose this frequency, Oracle Alertchecks your alert on a monthly basis on the day number you enter inthe Day field.

On Day of the Week--If you choose this frequency, Oracle Alertchecks your alert on the day of the week you enter in the Day field.

Every N Calendar Days--If you choose this frequency, enter a valuein the Days field. Oracle Alert considers every day a calendar day, and

does not skip holidays.

Every Day--Choosing this frequency is the same as choosing Every NCalendar Days and entering a value of 1 in the Days field.

Every Other Day--Choosing this frequency is the same as choosingEvery N Calendar Days and entering a value of 2 in the Days field.

Every N Business Days--If you choose this frequency, enter a valuein the Days field. Oracle Alert lets you choose your business days, but

does not skip any holidays.

Every Business Day--Choosing this frequency is the same aschoosing Every N Business Days and entering a value of 1 in the

Days field.


4/69

Every Other Business Day--Choosing this frequency is the same aschoosing Every N Business Days and entering a value of 2 in theDays field.

Every N-business days will only count monday to friday. If you choose 3 days, andstart on monday. It will run Monday, Thursday, the next Tuesday, Friday.

Note:

The business days above are determined based on the Business Day systemselected in the below screen.

Alert Manager Responsibility -> System -> Options -> More Option tab

The American system starts with Sunday and defines Monday throughFriday as business days.

The European system starts with Monday and defines Monday throughFriday asbusiness days.

The Middle Eastern System starts with Monday and defines Mondaythrough Saturday as business days.

Every N-calendar days will count all days of the weeks. If you choose 3, and starton monday. It will run Monday, Thursday, Sunday, Wednesday, etc.


5/69

Keep Days Field:

Number of days of exceptions, actions, and response actions history you want to

keep for this alert.

End Date Field:

To disable your alert by a certain date. Note that you can enter a date in this fieldonly if the alert is enabled.

Last Checked field:

In the Last Checked field, Oracle Alert displays the last date that this exception

condition was checked, if it has been checked.

To enter a SQL Select statement for your periodic alert:

Enter a SQL Select statement that retrieves all the data your alert needs to performthe actions you plan to define.

Must include INTO clause Inputs are identified by colon before the name. :INPUT_NAME Outputs are identified by ampersand (&) before the name.

&OUTPUT_NAME


6/69

you can format your number outputs as real numbers by specifying aSQL*Plus format mask in your Select statement. &PRICE#9999.99

PL/SQL functions can be used. SQL Select statement must be less than 64K. SQL query can be imported from external sources and it also has to beless than 64K. If the Select statement in the file does not contain an Into clause,

Oracle Alert automatically inserts an Into clause into the alert Selectstatement. This default Into clause contains three outputs:

&OUTPUT1, &OUTPUT2, and &OUTPUT3. You may want to givethese outputs meaningful names.

Verify the SQL statement:

You can verify the accuracy and effectiveness of your Selectstatement. Choose Verify to parse your Select statement and display

the result in a Note window.

Choose Run to execute the Select statement in one of yourapplication's Oracle IDs, and display the number of rows returned in aNote window.


7/69

EVENT ALERTS

To create an event alert, you perform the following tasks in the order listed:

Define the database events that will trigger your alert Specify the details for your alert Define actions for your alert Create action sets containing the actions you want your alert to perform

DEFINING EVENT ALERTS

Responsibility: Alert Manager

Navigation: Alert -> Define
http://docs.oracle.com/cd/A60725_05/html/comnls/us/alr/alrdet.htm#t_alrdethttp://docs.oracle.com/cd/A60725_05/html/comnls/us/alr/actions.htm#e_acthttp://docs.oracle.com/cd/A60725_05/html/comnls/us/alr/actset.htm#e_ashttp://docs.oracle.com/cd/A60725_05/html/comnls/us/alr/actset.htm#e_ashttp://docs.oracle.com/cd/A60725_05/html/comnls/us/alr/actions.htm#e_acthttp://docs.oracle.com/cd/A60725_05/html/comnls/us/alr/alrdet.htm#t_alrdet


8/69

EVENT DETAILS:

Application: The application of the table the alert has to monitor.

Table: The table name

Note: You cannot use a view as the event table for your alert.

Do not define an event alert on the table FND_CONCURRENT_REQUESTS.Oracle Alert submits a concurrent request to the concurrent manager when an

event alert is triggered by an insert or update to an event table.

After Insert/ After Update: The trigger event when the alert has to be triggered

ALERT DETAILS WINDOW

Note: From this section the process is the same for Event and Periodic Alerts

The Alert Details window includes information such as which Application

installations you want the alert to run against, what default values you want yourinputs variables to use, and what additional characteristics you want your output

variables to have.


9/69

INPUTS TAB:

Input Name: Oracle Alert automatically displays the inputs used in your Select

statement.

There are 4 implicit inputs provided by oracle

ROWID--Contains the ID number of the row where the insert or update thattriggers an event alert occurs.

MAILID--Contains the email username of the person who enters an insert orupdate that triggers an event alert.

DATE_LAST_CHECKED--Contains the date and time that the alert wasmost recently checked

ORG_IDcontains the current org ID.Description: Optionally add a description for each input.

Data type: Oracle Alert uses the data type to validate the default values for inputsyou enter in the Default Values field

Default Values: You can enter up to 240 characters.

OUTPUTS TAB:


10/69

Output Name:In the Outputs alternative region, Oracle Alert automatically

displays the outputs used in your alert Select statement without the ampersand (&)and any numbering format.

Description: Optionally add a description for each input.

Max LengthDetail Summary

You can specify the maximum number of output characters you want to display inyour detail or summary message actions.

Number Format: If your output value is numeric, enter the SQL*Plus format

mask in the Number Format field.

Check for Duplicates: Checks the previous combination of outputs for duplicates.Note: You must save history for your alert to use duplicate checking.

INSTALLATIONS TAB:


11/69

Oracle ID:specify an Oracle ID if you want Oracle Alert to check your alertagainst that specific Oracle ID.

Operating Unit:Not mandatory for Periodic Alerts.

ALERT ACTIONS WINDOW


12/69

Action Name: User defined name.

Description:Optional

Action Level:

DETAIL: Action is being performed for each individual exception. SUMMARY: Once for all exceptions found. NO EXCEPTION: Action performs when no exception is found.

ACTION DETAILS: (for Action Level DETAIL and NO EXCEPTION)

There are four types of actions you can create:

message actions concurrent program actions operating script actions SQL statement script actions

Action Type: MESSAGE


13/69

List: The distribution List

Note: Below fields are disabled if this field is entered.

ReplyTo: Reply to mail ID

To, Subject, CC,BCC :Similar to conventional mail options.

Print for user: the names, or alert outputs or response variables that represent thenames of the recipients for whom you want to print a copy of the message

Note:You can enter as many recipients as you want, up to 240 characters.

Response Set/Response Days (explained in later sections in this document)

Text:The message that has to be sent. Ouput variables referred using &.

Note: For detail or no exception message actions, the message text that you specify

in Oracle Alert must be less than 2000 characters, while the message file that youspecify must be less than 64K.


14/69

Action Type: CONCURRENT PROGRAM

Application: The application name in which the concurrent program is registered.

Program Name: User Concurrent program name.

Arguments: Parameters for the program separated by space. Dynamic outputsfrom alert SQL query are passed using &VARIABLE_NAME.

Action Type: OPERATING SYSTEM SCRIPT


15/69

Application: If the operating system script you want to execute is in a file located

in an Application's base path bin directory, specify that Application name in theApplication field.

Arguments: Parameters to the program.

File: Enter the full path of the operating system script. Application name shouldnot be entered in this case.

Note: Oracle Alert cannot substitute values into output variables located in anoperating system script file. Script should be less than 64K.

Text:The script is entered here. It should be less than 2000 characters. Outputvariables can be passed here.

Action Type: SQL STATEMENT SCRIPT

Application: If the operating system script you want to execute is in a file located

in an Application's base path bin directory, specify that Application name in theApplication field.


16/69

Arguments: Parameters to the program.

File: Path of the file.

Note: Script should be less than 64K.

Text: The SQL script. PL/SQL procedures and Functions can be used here.

Note: The SQL script you enter must have less than 2000 characters.

ACTION DETAILS: (for Action Level SUMMARY)

Action Type: SQL STATEMENT SCRIPT / CONCURRENT PROGRAM/

OPERATING SYSTEM SCRIPT

Defining the action details remains the same for all these action types except thatfor summary, Oracle Alert performs the actions once for each unique combinationof critical output values. Outputs used as arguments are considered critical outputs.

Action Type:MESSAGE


17/69

For MESSAGE action type the Text filed changes to a standard template type.

This action sends one mail consolidating all the outputs from the exceptions.

Example:

=**= Enter summary template below this line =**=

** PO Number: &PO Vendor: &VENDOR

Description: &DESC

Line: &LINE Item: &ITEM

Quantity: &QTY Price: $&PRICE

=**= Enter summary template above this line =**=

You specify the format of a summary message in two Oracle Alert windows:

In the Outputs alternative region of the Alert Details window in the Alertsform

In the Action Details block of the Actions window in the Alerts formReference Link:

http://docs.oracle.com/cd/A60725_05/html/comnls/us/alr/summary.htm#e_fsum

ACTION SET WINDOW

Seq: The sequence in which the actions has to be performed.

ActionSet Name: User defined name.
http://docs.oracle.com/cd/A60725_05/html/comnls/us/alr/summary.htm#e_fsumhttp://docs.oracle.com/cd/A60725_05/html/comnls/us/alr/summary.htm#e_fsumhttp://docs.oracle.com/cd/A60725_05/html/comnls/us/alr/summary.htm#e_fsum


18/69

Description: Optional (up to 240 characters).

SuppressDuplicates: suppress the actions in this action set if the exception foundis a duplicate that occurred during the last alert check.

Note: Must save History to use this action.

Enabled: To enable action set.

End Date: Disable action set after that date.

ACTION SET DETAILS

Inputs/ Outputs Tab: The variables in alert SQL are displayed here.

Can change default input values which are action set specific.

Seq: The sequence in which the action set has to be performed.

Action: LOV which contains actions defined in the actions window.

Type: Populates based on the action selected. Not user enterable.


19/69

On error: The action that has to take place if the current action fails.

o Action: AbortAborts the alert SetThe action set that has to trigger if current action set fails MemberThe action within the same action set.

o Seq: Enabled only for Action set and memberEnabled: To enable action set.

End Date: Disable action set member after that date.

ALERTS RESPONSE PROCESSING

Oracle Alert can process responses to your alert messages. When Oracle Alertreceives a response to a specific alert message, it automatically performs theactions you define.

When Oracle Alert sends out your message, it automatically appends two pieces oftext:

Response Text--tells the recipient exactly how to reply to the alert message.This text originates from the Message Elements alternative region of theOracle Alert Options form. Your Oracle Alert installation is supplied withthe following default text, which you can customize to your needs:

Your response to this mail note will be processed

electronically. For successful processing, you must:

- Include this note in your reply by using your mail

system's Reply With Original feature.

- Make your actual response EXACTLY like ONE of the

following; however, you should replace the question mark

(?) with the value you want to specify.

Choose one of the following responses:

Valid Response Text--lists the possible responses that the recipient mustreply with. You define these possible responses in the Valid Responses

block of the Response Sets window. Oracle Alert appends this ValidResponse Text to your message, so the recipient knows the exact text he orshe must respond with.


20/69

The steps followed are.

1. Define Response set which contains

Define variables for use in responses if needed. Define a set of possible responses to a particular alert message Define one or more actions for Oracle Alert to take when it receives a

particular response

Define actions for responses that are not valid. Define actions for no response condition

2. Attach the response set to the appropriate message action in DEFINE ALERTSwindow

STEP 1: Defining Response set

RESPONSE SET WINDOW

Response Set Name: User defined name.

Description: Optional

Enabled: Checkbox must be checked.

End Date: Date until which it is valid.


21/69

RESPONSE VARIABLES

Note: Response variable and output variables should not have the same name

Variable Name: Valid name (up to 30 characters)

Description: (up to 240 characters).

Type: Data type of the variable.

Max Length: Maximum length of the variable.

If the value to the variable exceeds the max length filed then oracle alert

Truncates character and date data Displays a row of pound signs (######) for numeric data

RESPONSE ACTIONS: VALID

A valid response is a response that you expect from an alert message recipient, andone that initiates the alert actions you specify. You can define any number of validresponses.


22/69

Response Name: User defined name.

Text: The text which has to be displayed in the alert message sent in mail.

Note: Your response must not include a blank line, so limit your response to oneparagraph. Oracle Alert interprets a blank line as the end of the response.

If you want the respondent to specify a particular value for a response variable inher/his response, enter the response variable in the Text field, followed by an equalsign and a question mark between a set of quotation marks (="?").

Example:

If a response variable QUANTITY is used, while soliciting response from user inmessage use it as

Reorder QUANTITY="?"

Actions Block:

Seq: The sequence in which the action has to be performed.

Action: LOV which lists the set of actions defined in the ACTIONS window.


23/69

Description/ Type: Populates once action is selected.

Enabled: Checkbox must be checked

End Date: Date till which the response is valid.

RESPONSE ACTIONS: INVALID

Define here the set of actions that has to be performed if the response provided bythe responder is no valid or is not understood






RESPONSE ACTIONS: NONE


24/69

Define here the set of actions that has to be performed if there is no response fromthe responder within the number of days mentioned in the alert message.






STEP 2: Attaching response set to Alert Message action

Navigate to

Alert -> Define -> Actions -> the message action


25/69

Response Set: The response set defined in previous step.

Response Days: The number of days within which the user is expected to respond.

TRIGGERING ORACLE ALERTS FOR TESTING

EVENT ALERTS:

Since they are similar to database triggers they can be triggered by updating orinserting a row into the corresponding table.

Whenever event alerts are created 2 database triggers (insert & Update) get createdin backend for the table. This can be verified using

SELECTdba_triggers.table_name,dba_triggers.trigger_name,dba_triggers.status,user_objects.status,dba_triggers.trigger_body

FROMuser_objects,dba_triggers


26/69

WHERE dba_triggers.trigger_name =user_objects.object_name

ANDuser_objects.object_type ='TRIGGER'ANDuser_objects.object_name LIKE'%%'

Whenever event alerts are triggered a program Check Event Alert'gets

submitted. Hence it can be verified in back end by the following querySELECTREQUEST_ID,

REQUEST_DATE,PHASE_CODE,

STATUS_CODE,ORACLE_ID,PROGRAM_APPLICATION_ID,

CONCURRENT_PROGRAM_IDFROMAPPLSYS.FND_CONCURRENT_REQUESTS

WHEREConcurrent_program_id =(SELECTConcurrent_program_id

FROMfnd_concurrent_programs_tl

WHEREUSER_CONCURRENT_PROGRAM_NAME ='Check Event Alert')ORDERBYrequest_date DESC;

PERIODIC ALERTS:

Set the Frequency in Periodic alert toOn Demand

Navigate to

Alert Manager Responsibility -> Request -> Check

Application: The application in which the alert is defined.


27/69

Alert: The name of the periodic alert to be checked.

Start Date:Gets populated automatically based on frequency set while definingalert.

Once the Submit Request button is clicked the periodic alert is triggered andrequest ID gets generated.

ORACLE ALERT HISTORY

Once periodic or event alerts are triggered they can be verified using the alert

history.

Navigate to

Alert Manager Responsibility -> History

Application: The application in which the alert is defined.

Alert Name: The name of the alert to be checked.

Type/ Keep Days/ Last checked: Populated automatically based on alertdefinition

View History Dates:

From/ To: Dates on which the alert history has to be viewed.


28/69

FIND CHECKS:

Requestor: User who started the concurrent manager if periodic alert else the userwho caused the event in case of event alert.

Date/ Time:When the alert was triggered.

Request ID:The request ID generated.

Status: The possible statuses are:

Completed--The alert check is complete Running--Oracle Alert is currently checking the alert Pending--The alert is in the concurrent queue waiting to run


29/69

Error--The alert check did not complete successfullyThe log can also be viewed for each chevk in the Tools -> Request Log

FIND EXCEPTIONS:

This is to review the output variable values for each exception triggered in theoutput.

The Review Alert Exceptions window displays the name of the action set run foreach exception, when the action set ran and completed and the Oracle ID


30/69

FIND ACTIONS

The action details of the triggered alert are displayed here.


31/69

DUPLICATES CHECKING AND ESCALATION GROUP

Duplicates for the output variable values during exceptions can be tracked at alertlevel or action set level.

This checks the previous exception output and suppresses the action if duplicatesare found.

Saving history by entering Keep Days is mandatory for duplicate checking.

Alert level:

Alerts -> Define -> Alert Details -> Outputs Tab -> Check box Check For

Duplicates enabled


32/69

Action Set Level:

Alerts -> Define -> Action sets -> Action Set Details -> Outputs Tab -> Check boxCheck For Duplicates enabled

Note: Action set duplication takes precedence over the alert duplication.

ESCALATION ACTION

Escalation group are set of actions defined for Oracle Alert, to perform when itfinds the same exceptions during consecutive alert checks.

Creating Escalation Groups:

Alerts -> define -> create new alert and save

Tool special menu -> Escalation Groups


33/69

Group Name: User defined name.

Description: Optional

Type: Message/ SQL Statement/ Concurrent program/ Operating System script

Note: Actions within an escalation group must be of the same action type.

Escalation Group Member Block

Action Name: Predefined actions from the Actions Window

Level: The hierarchy level when it has to be triggered. Each time Oracle Alertchecks the alert and finds the same exception, it performs the next higher level ofaction in the escalation group

Note: Once escalation reaches the highest enabled action level


34/69

Suppress Duplicates check box checkedin Action set: Oracle Alert no

longer performs any action within that escalation group, even if the exceptionremains in your database.

Suppress Duplicates check box uncheckedin Action set: Oracle Alert

continues to perform the highest action until the exception is removed from yourdatabase.

******************************************************************

SUMMARY THRESHOLD

Oracle Alert can automatically determine whether to perform a detail or summary

action, depending upon the number of exceptions found by the alert Selectstatement.

If you define a summary threshold, Oracle Alert performs a detail action for each

exception found by the Select statement, but if the number of exceptions foundexceeds the summary threshold, Oracle Alert performs a summary action.

Note:

A threshold group is composed of one detail action and one summary action of thesame action type.

Defining summary thresholds

1. Create an alert

Alert Manager Responsibility -> Define

2. Define a detail and summary action of same type in the alert.3.Navigate to

Tools menu -> Threshold Groups

4. Define the threshold group.


35/69

Name/Description: User enterable fields.

Note:

Name upto 80 characters and description upto 240 characters.

Type: the type of action of the group

Threshold Group Member Block

Action: The detail and summary action names

Level: Populated automatically based on the action defined

5. Define an action set in the alerts action sets window


36/69

Action Set Name: User defined name

Enabled Checkbox: Enable

6. Define the action detailsSeq: The sequence of the actionAction: The summary threshold name

Summary Threshold: The maximum number of exceptions that the alert Select

statement can find before Oracle Alert switches from performing the detail actionin the threshold group to performing the summary action.


37/69

******************************************************************

CREATING DISTRIBUTION LISTS

Distribution lists let you predefine a set of message recipients for use on manyactions.

Application: Name of application

Name: User defined name (upto 30 characters)Description: User defined (upto 240 characters)

Mail Recipients Block

To/CC/BCC: The mail IDs

Note:Best practise is not to use alert output variables here.


38/69

******************************************************************

DEFINING PERIODIC SETS

Periodic sets are created for alerts that need to be checked simultaneously.

Application: The application Name

Note:Only periodic alerts defiend under this application can be added in this periodic

set.

Name: User Defined name

Description: (upto 240 characters)

Periodic Set Memebers Block

Seq: The sequence in which the alerts should fire.

Application: Application of the alertName: Periodic alerts defined earlier.


39/69

******************************************************************

TRANSFER ALERT

An alert definition can be transferred to another database, or we can make a copyof an existing alert.

Source Alert Block

Application: Name of application of the alert.

Alert: The name of alert we want to transferDatabase: The user name and password of the database

username/password

Destination Alert BlockApplication: Name of application of the alert we want to transfer to.Alert: The new name for the alert.Database: The user name and password of the database where it has to be stored

username/password


40/69

******************************************************************

REGISTERING CUSTOM APPLICATION

Alerts can be defined for custom applications. The registered custom applicationhas to be installed in alert manager responsibility to define alerts in it.

They can be registered using below form.

Application: The application that has to be registered,

Oracle Username: Oracle ID associated with the custom applicationStatus: Since this is not installed during auto upgrade it displays as custom for all

the applications we register.


41/69

******************************************************************

ORACLE ALERT OPTIONS WINDOW

Options window is used to define the options oracle alerts uses when checkingalerts.

Mail systems, Mail server optionsand Response Processingtabbed regions areno longer used.

Message Elements Tab: Information such as Response Text, Message Actionheader and Footer are defined here.

More options Tab: The details such as Business Day System, summary messagewidht, concurrent manager name are mentioned here.


42/69

******************************************************************

DEMO

CREATING EVENT ALERTS

Scenario: Create Event alerts to notify the DBA whenever an User is created orupdated in the application

STEP 1:


Navigation: Alert -> DefineApplication: Application Object LibraryName: EVENT_ALERT_TESTDescription:

Select EVENT tab.

EVENT DETAILS BLOCK

Application: Application Object LibraryTable: FND_USER

After Insert/ After Update Check box:Checked

Keep Days: 1End Date:


43/69

Last Day Checked: Populates automaticallySelect Statement:

SELECTUSER_NAME INTO&UNAME FROMFND_USER WHEREROWID=:ROWID

STEP 2:

Click Actions Button

ACTION TYPE: SQL Statement Script

Action Name: Update Table

Description: Action Level: Detail

Click Action Details Button

Action Type: SQL Statement Script

Application: required if script is present in server pathArguments: For passing parameters dynamicallyText:


44/69

INSERTINTOXX_ALERT_MSGVALUES(&UNSAME);

COMMIT;

ACTION TYPE: Submit Program

Action Name: Submit ProgramDescription:

Action Level: Detail



45/69


Application: Application Object LibraryProgram Name: Active Users

Arguments: For passing parameters dynamically

ACTION TYPE: Message

Action Name: Send Mail

Description: Action Level: Detail



46/69

List: Reply To: If response needed default mail ID

To:[email protected]

Subject: User AlteredCC:[email protected]

BCC:[email protected]

Text:

The Following User has been created or Updated.

User Name: &UNAME
mailto:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]


47/69

STEP 3:

Creating action sets for the alert.

Click Action sets button

Seq: 1Action Set Name: SQL Action Set

Enabled: Checked

Click Action Set Details buttonMembers Tab

Seq: 1Action: Update Table

Type: Action: SQL StatementOn Error

Action: Set

Seq: 2

Enabled: Checked


48/69

Seq: 2Action Set Name: Submit Prog SetEnabled: Checked


Seq: 1Action: Submit Program

Type: Action: Concurrent Program

On Error

Action: AbortEnabled: Checked

Seq: 3Action Set Name: Send Mail SetEnabled: Checked



49/69

Seq: 1

Action: Send MailType: Action: Message

On Error

Action: Abort

Enabled: Checked

STEP 4:

Save the alert and verify in back end if the triggers have been created for the table.

ALR_FND_USER_0_108_UAR

ALR_FND_USER_0_108_IAR

Are the 2 triggers created for after insert and after update.


50/69

STEP 5:

Trigger the alert by updating or creating a new user.

Navigation: System Administrator -> Security ->Define

Altered existing User.


51/69

STEP 6:

Verify in backend if alert is triggered


52/69

STEP 7:

Check alert history.

Navigation:Alert Manager Responsibility->History

Application:Application Object LibraryAlert Name:EVENT_ALERT_TEST

Click Find Actions Button


53/69

Click Find Exceptions Button


54/69

Click Find Checks Button

STEP 8:

Verify if the actions have been performed.

Action: Submit Program


55/69

Action: Update table

Event alert successfully defined and tested.

*****************************************************************

CREATING PERIODIC ALERTS

Scenario: Create periodic alert to check the sales orders created for every 30 days.

STEP 1:


Navigation: Alert -> Define


56/69

Application: Application Object LibraryName: PERIODIC_ALERT_DEMODescription:

Select PERIODIC tab

PERIODIC DETAILS BLOCK

Frequyency: Eery N Calendar DaysDays: 30

Start Time:09:00:00

Keep Days: 1End Date:

Last Day Checked: Populates automaticallySelect Statement:

SELECTorder_number,header_id,

ordered_date,cust_po_number,(SELECTMESSAGE_TEXT

FROMFND_NEW_MESSAGESWHEREMESSAGE_NAME ='XX_ALERT_DEMO'ANDROWNUM=1)

xx_msgINTO&p_order_number,

&p_headre_id,&p_ordered_date,&p_cust_po_number,&p_xx_msg

FROMoe_order_headers_allWHERE(ordered_date >(SYSDATE-30)ANDordered_date


57/69

Note:

In the above select statement you can find a message text referred from

FND_NEW_MESSAGES table.

This is used because there are limitations on the number of characters that can beentered in the text field for action sets.

Hence hard coded text can be defiend as Application Messages and added as

variable.

Definin g Message

Responsibility: Application DeveloperNavigation: Application->Messages

Name: XX_ALERT_DEMO

Language: USApplication: Application Pbject Library


58/69

Current Message Text:

The above orders have been created since the past 30 days.

Kindly verify from your end and send us the consolidated report for the same.

Further steps are similar to the ones cretaed for EVENT alerts.

STEP 2:

Click Actions Button

ACTION TYPE: Message

Action Name: Send Mail

Description: Action Level: Summary


59/69


Action Type: MessageTo:[email protected]

Subject: Orders CreatedText:

=**= Enter summary template below this line =**=

** Order Number: &P_ORDER_NUMBER

Ordered Date: &P_ORDERED_DATE

Customer PO Number: &P_CUST_PO_NUMBER

=**= Enter summary template above this line =**=

&p_xx_msg

Note:The action level selected above is SUMMARYthus the action is beingperformed once for all the exceptions detected.

Hence a predefined template occurs for the text type and we need to place theouput variables that has to be printed for each exception inside the template and the

ones that need to be printed once in the message outside the template.

&p_xx_msg is the message variable which stores content of the application

message and gets printed at the end of the mail.
mailto:[email protected]:[email protected]:[email protected]:[email protected]


60/69

ACTION TYPE: SQL Statement Script

Action Name: SQL Mail

Description:

Action Level: Detail



Text:EXECXX_send_mail;


61/69

Note:

Reference Link

http://www.oracle-base.com/articles/misc/email-from-oracle-plsql.php

STEP 3:

Creating action sets for the alert.

Click Action sets button
http://www.oracle-base.com/articles/misc/email-from-oracle-plsql.phphttp://www.oracle-base.com/articles/misc/email-from-oracle-plsql.phphttp://www.oracle-base.com/articles/misc/email-from-oracle-plsql.php


62/69

Seq: 1Action Set Name: Summary MailEnabled: Checked


Seq: 1

Action: Send MailType: Action: Message

On Error

Action: AbortEnabled: Checked

Seq: 2

Action Set Name: SQL Set

Enabled: Checked



63/69

Seq: 1

Action: sql MailsType: Action: SQL Statement script

On Error

Action: Abort

Enabled: Checked

STEP 4:

Verify if the periodic alert is working fine.

Set Frequency to On Demandor change the Start Date to sysdate in CheckWindow


64/69

Navigate to

Alert Manager Responsibility->Request-> Check

Application: Application Object LibraryAlert: PERIODIC_ALERT_DEMO

Start Date:Sysdate gets populated

Click Submit Request button

A program gets submitted in back end.

View->Requests->Find


65/69

STEP 5:

Check alert history.

Navigation:Alert Manager Responsibility->History

Application:Application Object Library

Alert Name:PERIODIC_ALERT_DEMO

Click Find Actions Button


66/69

Click Find Exception Button

Note:

The application message text has been fetched into the variable P_XX_MSG


67/69

Click Find Checks Button

Note:

In the below screen shot you can see that in Summary mail action for the 25

Exceptionsfor the alert 1 Actionhas been performed.This is because we have defined the action level as SUMMARY.

But for action SQL mails we have 20 actions since there it is DETAILlevel.


68/69

Mails sent to mail box from SQL mails Action


69/69

Periodic alert created successfully and tested.

******************************************************************

ESCALATION ACTION DEMO

Defining EscalatingActions.docx

******************************************************************

SUMMARY THRESHOLD DEMO

Summary ThresholdDemo.docx

******************************************************************

alerts - full features

Documents