Oracle Sale Quote is another system that offers excellent opportunity for the sales guys to create/follow up and play with the Sales Quotes as per the customer requirement and needs. Once Quote is approved it can be converted into Sales Order(in Order management) with Single click of mouse.
In this blog I will explain some of important features available in Oracle Sale Quote.
Note – Please Note that there is no workflow associated with Oracle Sales Quote, off course we do have Approval workflow for Quotes (Integrated with AME)
Open the Sales Quote,
1. Enter Header
2. Enter lines.
In this blog I will explain in brief about Quotes Functionality Offered by Oracle Order Management Suite. Topics that I will cover here are
Defaulting Rule & Generation of Defaulting Rule (When Required).
Data Flow from Quotes to OM Order.
Oracle Quotes offers limited capability to create Quotes and Progress it through the Negotiation phase and finally creates Sales Order.In case your Organization has complex / advance quoting needs you should Implement Oracle Sales Quoting.
Select Line_Id, flow_status_code,ordered_quantity,shipped_quantity, fulfilled_flag, invoice_interface_status_code
From Oe_Order_Lines_All l
where open_flag = 'Y'
And not Exists
(Select 1 From Wf_Items W
and w.item_key = to_char(l.line_id));
In this video Presentation I will talk about the Manual Scheduling Workflow Sub-Process available in Oracle Order Management.
In Order Management Order line workflow we have 3 type of Scheduling Sub-Process.
Schedule – Line
Schedule - Line, Manual
Schedule - Line, Deferred
today I will talk about Ist and 2nd.
In Schedule – Line, Scheduling is Online- that means as soon as we Book the Order Scheduling happens, but in Schedule – Line Manual Scheduling , scheduling is Manual , as soon as we book the Sales Order Scheduling workflow activity will not be Trigger,
Please Refer the Below YouTube demo for
How to Modify the Oracle Order line workflow to Add Manual Scheduling Sub-Process.
How to Progress line with the Manual Schedule -Subprocess with "Schedule Order" concurrent Program
User Hooks are a feature that allows customizing the application in a way that is less invasive and that can be easily disabled for diagnosing problems with the customization. Hooks are code that is conditionally executed by some application packages. The condition is that the hook has to be enabled.
Hook calls are interleaved in some of ASO APIs, mostly on public APIs. There are two types of Hooks: Pre-processing Hooks: Are hooks that execute (if enabled) before the API does any actual processing. These are good for modifying/adding information so the API can proceed with that change in place. These hooks are of type B (from Before) Post-processing Hooks: Are hooks that execute (if enabled) after the API did all processing. Post hooks are usually good for cleanup of a pre-hook or for further processing after the vanilla API has finished work. These hooks are of type A (from After). Below are the Steps to Implement Custom Hooks in ASO .
Requirement for Implementation in my Case - In my example I want to use Freight Terms at the iStore to be used as Qualifier to derive the item price in Shopping Cart in iStore, but Freight Terms is not supported as Qualifier for iStore ,and to fulfilfill this requirement , I have implemented custom hook to used Freight Terms as Qualifier from the iStore. Implementation Steps
One or both of the following values is invalid so it's not possible to query workflow information: Item Type (OEOH) / Item Key (xxxxx). Try selecting the "Status Monitor" tab to search for a different workflow.
Oracle Order management raised above error if you try to view the workflow status for a particular item type(says OEOH) and item key(Order Header ID) combination and no such records exists for item_key in wf_items table.