What Notification Types are available in Oracle Service

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

CRM and Order Management Integration

Order Entry had a separate entity: SO_LINE_SERVICE_DETAILS to store install base information associated with product sales order lines. You had to run the Service Interface concurrent program to then communicate the install base information to Oracle Service. This program is now obsolete. Order Management integrates with the various CRM products (IStore, Telesales, Quotes etc) via Order Capture. Any changes to the Order Object are communicated on line to Order Capture via the ASO_ORDER_FEEDBACK_PUB.UPDATE_NOTICE API. Order Capture in turn publishes the information to a queue that all the interested CRM products poll.

An Oracle White Paper

How to Exract Service Activity LOV Detail

SELECT cs_txn_billing_oetxn_all.org_id, cs_transaction_types_vl.NAME,
cs_transaction_types_vl.description,
cs_txn_billing_types.billing_type,
cs_transaction_types_vl.revision_flag,
cs_transaction_types_vl.new_cp_return_required,
cs_transaction_types_vl.new_cp_status_code,
cs_transaction_types_vl.installed_cp_return_required,
cs_transaction_types_vl.installed_status_code,
cs_txn_billing_types.txn_billing_type_id,
cs_transaction_types_vl.no_charge_flag,
cs_txn_billing_oetxn_all.order_type_id, csd_repairs.repair_line_id,
cs_txn_billing_oetxn_all.line_type_id,
cs_transaction_types_vl.line_order_category_code line_category_code,
cs_bus_process_txns.transaction_type_id
FROM csd_repairs,
csd_repair_types_b,
cs_bus_process_txns,
cs_transaction_types_vl,
cs_txn_billing_types,
cs_txn_billing_oetxn_all
WHERE csd_repair_types_b.repair_type_id = csd_repairs.repair_type_id
AND cs_bus_process_txns.business_process_id =
csd_repair_types_b.business_process_id
AND cs_transaction_types_vl.transaction_type_id =
cs_bus_process_txns.transaction_type_id
AND (TO_DATE (SYSDATE) BETWEEN NVL
(cs_bus_process_txns.start_date_active,
TO_DATE (SYSDATE)
)
AND NVL (cs_bus_process_txns.end_date_active,
TO_DATE (SYSDATE)
)
)
AND cs_transaction_types_vl.transaction_type_id =
cs_txn_billing_types.transaction_type_id
AND cs_txn_billing_types.billing_type = ‘M’
AND cs_txn_billing_oetxn_all.txn_billing_type_id =
cs_txn_billing_types.txn_billing_type_id
– AND cs_transaction_types_vl.line_order_category_code = ‘RETURN’
AND NVL (cs_transaction_types_vl.depot_repair_flag, ‘N’) = ‘Y’
ORDER BY cs_transaction_types_vl.NAME

Supply Chain Footprint in Oracle Application

1. Supply Chain Planning

MRP/Supply Chain Planning

Demand Planning

Advanced Supply Chain Planning

Constraint and Inventory Optimization

Global Order Promising

Manufacturing Scheduling

Inventory Optimization

Collaborative Planning

Transportation Planning

Supply Chain Intelligence as an independent module

2. Order Management

Order Management

Configurator

iStore

TeleSales

Receivables

Advanced Pricing

Quoting & Proposals

Trade Management

Release Management

Sales Contracts

3. Procurement

Purchasing

Payables

iProcurement

Sourcing

iSupplier Portal

Procurement Contracts

  1. Manufacturing

Discrete Manufacturing

- Project Manufacturing

- Flow Manufacturing

- Project Contracts

- Shop Floor Management

Process Manufacturing

  1. Logistics

Inventory Management

Mobile Supply Chain Apps

Warehouse Management

Transportation Execution

6. Service

Tele Service

Depot Repair

Field Service

- Spares Management

- Advanced Scheduler

- Mobile Field Service

iSupport

Service Contracts

7. Maintenance Management

Enterprise Asset Management

Property Manager

Service Request Flow in Oracle CRM

1. Customer Contact Center

a. Build Customer Contact

2. Service Request

a. Service Request Creation

b. Task Creation

c. Knowledge Management

3. Task Dispatch

a. Dispatch Scheduling

b. Parts Request

4. Task Debrief

a. Material

b. Labor

c. Overheads

5. Charges

a. Warranty

b. Revenue

will post screen shots with some Mandatory setup steps

Posted in CRM. 1 Comment »

Field Service Debrief Features

Reports on parts, expenses, and labor for a task assignment and ultimately results in updates to Inventory, Installed Base, and Charges. Reports on Counters.

From Field Service Debrief you can easily access the Capture Counter Reading functionality from Oracle Service to capture counter readings.

Offers direct access to specific Spares Management functionality such as Parts Requirements and View On hand Quantity.

Offers direct access to Notes, Calendar, or Service Request and a Pro Forma invoice

Technical Aspects of CRM

Technical Aspects of CRM
While it must be emphasized that CRM is not a technology, there are a number of technical issues that need to be considered when a company decides to implement a CRM system. The first technical issue that needs to be analyzed is scalability. In a nutshell, the CRM system must be very scalable, and the volue of information within the system should never reach an end. It must be able to grow over time as the company collects more information.
The CRM systems which are the most scalable are also the most valuable. Another thing that the company must look at is communication. The goal of Customer relationship management is to build a powerful bond with your customers.

A company cannot be successful with this if they cannot effectively communicate with those they serve. It is not enough to use one method of communication. Instead, multiple forms of communication must be used. This includes the telephone, Internet, television, radio, magazine, and any other form of communication available. When a company is able to effectively communicate with their customers, this will give them the necessary resources to succeed. It is also important for companies to look at “workflow.” In this context the term workflow is used to describe the business processes the company will use to track and maintain information.

It is not enough for a company to get information. If they want to become successful and maintain a presence in the market, the company must be able to properly process and analyze the information they receive. In addition to workflow, it is also important for organizations to consider the “assignment.” The term “assignment” can be used to provide specific requests to an individual or group. By giving the correct assignments to the proper entities, a company will be capable of reaching their goals once these assignments have been carried out. One thing that all CRM systems have in common is a database. The database is the place where customer information will be stored.

The database may also be referred to as being a data warehouse. Because the company will be storing information that is related to their customers, it is important for them to look at privacy issues. Data encryption should be used at all times, and the company must make sure they are functioning within the boundaries of the law. Customer relationship management is a powerful tool because it will allow a company to track the buying habits of their clients. This information can be analyzed on an individual level, and this can allow a company to market specific products to specific customers. In addition to tracking the purchases, the company can also track the product itself, and they can store a great deal of information on it.

In order for a purchase to be repeated, the customer must be satisfied. In order for this to occur, the customer must understand the needs of the customers they serve. It could be said that CRM is just the opposite of “one size fits all.” It will deal with customers on an individual level. Privacy is an important issue that companies must consider when implementing a CRM system. If a company violates the privacy of their customers, this can damage the relationship that they’ve worked hard to build up. In order to avoid this problem, companies must be careful when implementing and utilizing a CRM system. They must know how to get the information they need without violating the privacy of their customers.

To deal with the privacy issue, it is important for companies to understand the concerns of the customers. In most cases, customers are wary of having their information stored in a database that can fall into the hands of third party companies. To handle these concerns, the company must create a policy of making sure this information is never shared under any circumstances. The customers must be informed of this policy, and the company must make sure it is followed. The only time the information should be shared is if the customer allows it. Many customers will not mind providing companies with information as long as they have asked for it. When a company uses clandestine methods to get data on their customers, this will destroy their reputation of the customers should discover it.

With Thanks to exforsys.com