Types of Siebel User Interfaces

What are types of Siebel User Interfaces?
Following two Types of Siebel User Interfaces are available
– High Interactivity Mode (HI)
– Standard Interactivity Mode (SI)
HI and SI user interfaces are designed to serve two different group of user.
High Interactivity Mode (HI)
HI is available for employee applications like Siebel Sales. It is supporting highly interactive users. It requires Internet Explorer 5 +. It provides additional functionality (using additional code such as Active X controls). It has drag-and-drop for setting column width etc. It reduces number of page refreshes (So Decrease load on Server). It has menu bar and tool bars and has implicit save (automatically save record by stepping out). It reduces the number of page refreshes.
Standard Interactivity Mode (SI)
SI is available for customer Application and behaves like traditional web applications; requiring frequent page refreshes. It behaves like typical HTML based Web Application. It is available on a wide variety of browsers.
Major Plus Points in High Interactivity Mode (HI)
The following features are supported only by high interactivity rest almost everything is same
• HI Required Internet Explorer 5 + to Run application
• Client-side scripting is available with access to Siebel objects on the client side
• Hi have Interactive controls. Like calculator, calendar date/time selector
• Implicit save. saves the record without having to press the save button
• Supports High interactive graphical UI Elements such as Flowcharts, Organization charts

Advertisements

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

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