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 add new Attachment Category to a Form (Sale Order)

How to add new Attachment Category to a Form (Sale Order)

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

How to Check Order In Workflow Error and Not Bookable

By Using Following Query you can extract Order Number and Other Details which are in Work flow Error

SELECT h.order_number, h.org_id “Operating Unit ID”, h.ordered_date,
h.header_id, h.cancelled_flag, h.open_flag, h.flow_status_code,
h.creation_date, h.last_update_date,
(SELECT COUNT (1)
FROM oe_order_lines_all l
WHERE l.header_id = h.header_id AND open_flag = ‘Y’) “Order Open”
FROM oe_order_headers_all h, wf_items wi
WHERE wi.item_type = ‘OEOH’
AND wi.item_key = TO_CHAR (h.header_id)
AND h.open_flag = ‘Y’
AND NOT EXISTS (
SELECT ‘WF is pending’
FROM wf_item_activity_statuses wias
WHERE wias.item_key = TO_CHAR (h.header_id)
AND wias.item_type = ‘OEOH’)

How to Change LOV Using Forms Personalization

Good Article worth Reading as During Implementation its Common Requirement