I would like to thank all the visitors of this blog for there support and co-operation which gave me confidence to walk through the blog life with firm steps!!! Bundle of THANKS!!!
I can’t believe it’s been a year since I started this blog. It’s really quite amazing when I look back through all the entries. I realize what a collection of resources I’ve built upJ. It certainly has been an interesting journey, the collaborative aspects of blogging are certainly greater than I expected.
If you have some order lines in booked status and the ship line activity is in error instead of ‘Notified’ then use the following script (But check on Test Environment first). Pass the line_id for one of the line from problematic order and check if this will progress the line to ‘Awaiting Shipping’ and the work flow activity to Notified status.
set serveroutput on
Declare
l_line_id NUMBER := &line_id; /* Order Line Id*/
l_org_id NUMBER; /* Organization Id*/
l_count NUMBER;
l_activity_id NUMBER;
l_result VARCHAR2(30);
Begin
OE_Standard_WF.OEOL_SELECTOR
(p_itemtype => ‘OEOL’
,p_itemkey => to_char(l_line_id) /* Order Line Id*/
,p_actid => 12345
,p_funcmode => ‘SET_CTX’
,p_result => l_result
);
select activity_id
into l_activity_id
from wf_item_activity_statuses_v
where item_type = ‘OEOL’
and activity_name = ‘SHIP_LINE’
and item_key = to_char(l_line_id)
and activity_status_code = ‘ERROR’;
wf_item_activity_status.create_status(’OEOL’,to_char(l_line_id),l_activity_id,wf_engine.eng_notified,wf_engine.eng_null,SYSDATE,null);
commit;
End;
/
The following Notifications are available:”You can set up the application to automatically notify the service request owner and customer contacts associated with the service request whenever a certain event occurs, for example, whenever a service request is created, closed, or reassigned. Notifications can be sent via Oracle Workflow notifications or by e-mail.
Oracle TeleService includes a notification workflow and notification templates suitable for different types of events, but implementers must set up the rules that trigger the workflow. The rules make it possible to selectively notify users only about events of interest to the organization. This notification functionality enhances and replaces notifications through the Call Support Process workflow which can be associated with Service Request Types. The Call Support Process notifies users each and every time a service request is updated. This release includes one seeded notification rule: If service request status changes to closed, then notify the primary contacts of related service requests.
The following table describes the events that can trigger a notification message to be sent and the scope of the rule you can create.
1. Contact Added to Service Request
2. Published Solution Added to Service Request
3. Service Request Status Changed
4. Service Request Created
5. Service Request Owner Changed
6. Relationship Created
7. Relationship Removed
8. Service Request Updated
The Notifications that are available in Oracle Service can be set up via the Customer Support -> Setup -> Service Requests -> Notification Rules form.
Reference
Metalink
Oracle® TeleService Implementation Guide
1. Login to OAM
2. Navigate to Workflow
3. Click on Service Components you will find a new page with item name “Workflow Notification Mailer” and Container “Workflow Mailer Service”
4. Under column container click on Workflow Agent Listener Service
5. From drop down list at the end of the line , choose start then click on Go button
6. Once service container are activated , all service components with startup mode automatic will be up and running
