Oracle Alerts

Basic Definition of Oracle Alert is :

1. To Monitor Activity of Business Needs. e.g Sending Email ,calling Concurrent Program,SQL Scripts and Operating System Scripts.
Types of Oracle Alerts

Periodic Alert: Periodic Alert Fires at pre defined set of Time.e.g suppose you want to Email all Order Booked today We can Use Periodic Alerts. Event Alerts: Event Alerts Fires when particular database activity occurs e.g inserting record and updating record of tables.
How to Design Periodic Alerts:

Design of Periodic Alert is explained from scratch with the help of Test Alert Items with zero weight . We have to design periodic alert Items with zero weight for our Client.Basic Business need of this alerts is for Email to MIS User for List of item having Zero Weight saved in Oracle Inventory.

STEP1: Navigate To Alert Manager Form ..

N Alert Manager Alerts Define

Application Field: Name of Application e.g Oracle Payable Name : User defined Name of Alerts. Choose Period tab Frequency :Choose Frequency Accordingly. Days: Choose days according to Frequency. Suppose you Chosse Frequency Every N Business Days Then Enter Value 1 in Day Field. Start Time: Time You want to Fire periodic alerts suppose you want to fire at 6:30 A.M Write 06:30:00 in Start Time Field. Keep: How many days You Want to Mainitain History. Select Statement: Write Query in select Statement . Here is an Exapmle of Select Statement for Test Periodic Alert Items with zero weight. Select statement must include an INTO clause that contains one output for each column selected by your Select statement.In Example all input Column like Orgaization_code,tem_number(segment1),Description,Creation_date have Output Variable ORG,ITEM,DESCR,Create_date preceded by Amperstand(&). Query is: Test Query for Items with zero weight Alert is

SELECT distinct p.organization_code , substr(i.segment1,1,20) , substr(i.description,1,50), i.creation_date, INTO &org , &item , &descr , &create_date FROM mtl_system_items i, mtl_parameters p where i.organization_id = p.organization_id and p.organization_code in ('INF','ENF') and i.INVENTORY_ITEM_STATUS_CODE||'' = 'Active' and i.unit_weight is null and I.ITEM_TYPE = 'P' order by 1,2

Verify: Click on Verify Button to Verify your Query. This message will populate if Query is Right.

Run: To Check Record Count of Your Query Click on Run Button. Suppose Your Query Written Zero Rows This Message will populate.

STEP2 : Define Action:

Click on Action Button(Marked With Circle). This Form (Action Window 1.0) Will Poulate.. Explaination of Field on this Form :

Action Name:Specify Name of your Action. For Example Our Alert Items with zero weight. is for Email.we specify name EMAIL in Action Name. Action Level: Action level should be Summary.

Three are three Action Level

Detail - action is performed for each exception returned. Summary - action performed once for each exception. No Exception - action performed when no exceptions returned.

(Action Window 1.0)

Action Detail: By Click on Action Detail Button this Window (Action Detail Window 1.1)

Action Detail Window 1.1

Action Type: Four Action type.

Message - send message Concurrent Program Request - submit concurrent program SQL script - execute a SQL script OS script - execute an OS script

We Choose Action Type Message because Items with zero weight Alert is for Email Purpose.

Enter Email Addrees in To Field.

Text : In Text field design Layout of your Periodic Alerts. Items with zero weight Alert Layout is this: Important thing is that Output Variable &org,&item etc should be placed with in template like this

=**= Enter summary template below this line =**= **&org &item &descr &create_date =**= Enter summary template above this line =**=

Layout Sample of Test Periodic Alert Items with zero weight:

The following items currently have no weight maintained against them in the system.

Org Item Description Creation Date === ==================== ============================== ============= =**= Enter summary template below this line =**= **&org &item &descr &create_date =**= Enter summary template above this line =**= Column OverFlow: Wrap Max Width: Choose According to Requirments.

80 Characters 132 Characters

180 Characters

STEP3 : Define Action Sets:

Enter the groups of action to be run. Click on Action Sets Button. Action Set Window (Shown in Pictiure Action set Window 1.2) will populate.

Action set Name: Enter Action Set Name. In our Test Alert we enter Action set Name EMAIL.

Note : Action set Name should be same as in Action Name. Otherwise Periodic Alert will not Fire.

Action Set Window 1.2

Action set Name: Enter Action Set Name. In our Test Alert we enter Action set Name EMAIl. Output Tab: Output tab Contain List of Output Variable defoen in select Statement as shown in Window 1.4.Note that if you Output tab is Blank Requery the Alert then it will show output Variable. This problem we generally faced when designing periodic Alerts.

(Window 1.4)

Member Tab: Enter Name of Action .

How to Design Event Alerts:

Procedure of design of Event Alert is same as Periodic Alert.Just you Have to choose Event Tab and give Event Details. Application Name and Table Name and Click on Check box After Insert and After Update according to Requirment and rest of Procedure is same.

Practical Probem and Solution During Design Event Alerts:

We have to Design Item Attribute Update in Toshiba, Sydney Projects.Requirment of Alert is that if any item Comes in Inventory Email should sent to MIS USER. We developed Event Alerts. But when we are inserting new record in MTL_SYSTEM_ITEMS_B our Alert is Not Fired.

Solution: Solution

of Problem is :

GO TO Alert Details and in Alert Details Forms Click on Installation Tab and give the name of Operating Units for which You Want to Design Alerts.

Query Event Alert: SELECT :ROWID, segment1, organization_id, inventory_item_id into &rowid, &segment1, &organization_id, &inventory_item_id from mtl_system_items_b where rowid= :ROWID

Query Periodic Alert with time interval: select rsh.receipt_num, msi.segment1, rsl.quantity_shipped, sum(rcv.QUANTITY), decode(msi.organization_id,184, '[email protected] [email protected] [email protected] [email protected]', 195,'[email protected] [email protected] [email protected] [email protected]') INTO &RECEIPT_NUM, &SEGMENT1, &QUANTITY_SHIPPED, &QUANTITY_RECEIVED, &TO_RCP from mtl_system_items msi, rcv_shipment_lines rsl, RCV_TRANSACTIONS rcv, rcv_shipment_headers rsh where trunc(rsh.creation_date) > '01-jan-90' and rsh.SHIPMENT_HEADER_ID =rcv.SHIPMENT_HEADER_ID and rsl.shipment_header_id = rsh.shipment_header_id and rsl.SHIPMENT_LINE_ID =rcv.SHIPMENT_LINE_ID and rcv.TRANSACTION_TYPE ='DELIVER' and msi.organization_id = rsl.to_organization_id and msi.inventory_item_id = rsl.item_id and msi.organization_id in(184,195)

and rcv.quantity >0 and rcv.last_update_date >= to_date(:DATE_LAST_CHECKED, 'DD-MON-YYYY HH24:MI:SS') - (30/(24*60*60)) group by rsh.receipt_num, msi.segment1, rsl.quantity_shipped,msi.organization_id

CREATE OR REPLACE PACKAGE BODY cinv_update_msib AS PROCEDURE update_row( errbuf OUT VARCHAR2, retcode OUT NUMBER, p_organization_id NUMBER, p_inventory_item_id NUMBER) AS l_serial_control_code NUMBER:=NULL; BEGIN IF p_organization_id IN (195, 200, 184, 192) THEN SELECT msib.serial_number_control_code INTO l_serial_control_code FROM mtl_system_items_b msib, mtl_parameters mp WHERE msib.inventory_item_id = p_inventory_item_id AND msib.organization_id = mp.master_organization_id AND mp.organization_id = p_organization_id; IF l_serial_control_code <> 1 THEN UPDATE mtl_system_items_b SET serial_number_control_code = 6 WHERE organization_id = p_organization_id AND inventory_item_id = p_inventory_item_id; END IF; ELSE NULL; END IF;

IF p_organization_id IN (195, 200, 184, 187, 189, 188, 190, 192) THEN UPDATE mtl_system_items_b msib SET msib.atp_flag = 'Y' WHERE msib.organization_id = p_organization_id AND msib.inventory_item_id = p_inventory_item_id; ELSE NULL; END IF; EXCEPTION WHEN OTHERS THEN fnd_file.put_line(fnd_file.log,'Process Failed:'); --NULL; END update_row; END; /

Q: Can one create event alerts on custom tables, triggered by custom applications? A: For a customer to use event alerts on a custom application, they will need to register the application, the application's ORACLE ID, the event table and the form with AOL. In Release 9, additional user-exit calls need to be added to the custom form. See the R9 Alert Reference Manual. In Release 10, the above requirement is due to the event alert database trigger needing the correct application context that is derived from signing-on to AOL (with some username, responsibility). When triggered by custom apps not registered with and accessible by AOL, event alerts can't properly function. Although it's technically feasible to default the username/responsibility for this case, we haven't implemented it for competitive reasons (ie. we still need to weigh the pros/cons.)

Q: Can one create event alerts triggered by applications built using tools other than Oracle Forms or registered concurrent programs? A: No. Q: Which electronic mail facilities does Alert use/support? A: Oracle Alert is shipped with e-mail capabilities integrated with Oracle Office and Oracle Inter Office. VMS mail and UNIX send mail technologies are also supported. A single-user license of Oracle Office is bundled with the Oracle Alert kit. For Oracle Alert Release 10.7 or later, a single-user license of Oracle Inter Office Messaging Options is bundled instead. Other mail facilities can be linked to Alert using Oracle Office/ Inter Office server and gateways that support various mail standards and platforms. For some mail facilities that provide SMTP gateways (such as cc:Mail),Oracle Office/Inter Office server and gateways are not required as Alert has the capability to send mail by calling any command-line executable that understands SMTP. To use Response Processing (receiving and parsing user mail replies),Oracle Office/Inter Office is REQUIRED. The single-user license bundled with Alert satisfies this requirement. Currently there are no other supported configurations to support this feature. Q: My Alert concurrent programs cannot connect to the Oracle Office (or Oracle Inter Office) account, displaying "Cannot login to Oracle*Mail". A: Verify that your server environment is correct. Particularly, make sure that $ORACLE_HOME/office subdirectory exists, containing two sub directories: mesg/ and oacore/. Verify that$ORACLE_HOME/office/mesg/OAE message file exists. Verify that your mail database has been registered correctly withAlert. Ensure that database name, account names and passwords are entered correctly.

Q: How often should the Alert tables be purged? A: There is no recommended purge frequency. It all depends on how many alerts have been enabled and their frequency. The site's dba may wish to monitor the ALR tables to determine the purge frequency. Also note bug 451137, in which the "Purge Alert and Action Set Checks" alert has a poor performance. The customer may choose to run the SQL statements supplied in the bug text instead.