Below are some of the scenarios where the approval path will have to be routed differently when compared to the standard path.
1. Requisitions created on certain items.
2. When a base line is set on Approval limit.
3. Information displayed in Notifications.

Steps to create the custom workflow:
1. In the workflow builder, copy and paste the standard workflow Requisition (REQAPPRV) to the DB. It will ask for a new ITEM_TYPE. Provide a name for the custom workflow.
2. Add the required attributes, functions and nodes to the Process. Make necessary changes to the Process.
3. For Notifications, messages need to be provided appropriately. Pl/SQL messages may not work properly in 11.5.10 version. For those cases, JRAD notification messages can be used.
4. Save the workflow in the database.
5. In Oracle Applications system, navigate to
SETUP->PURCHASING->DOCUMENT TYPES and select 'Purchase Requisition'.
6. Select the custom approval workflow and the starting process in the Requisition approval LOV.
7. Save the record.
8. Schedule a periodic concurrent request 'Workflow Background Process' for this new custom item type.

Above steps are provided at high level only. Mail me if you need any help.


----------------------------------------------------------------------------------------------------------
This query can be used to determine which approval path a Requisition or a Purchase Order has taken:
– For Requisition
select pos.name
from po_requisition_headers_all rh, wf_item_attribute_values av, per_position_structures pos
where av.item_type = rh.wf_item_type
and av.item_key = rh.wf_item_key
and av.name = ‘APPROVAL_PATH_ID’
and to_number(av.NUMBER_VALUE) = pos.position_structure_id
and rh.segment1 = ‘&1′ ;
–and rh.org_id = 172; — You can use your org_id if necessary
– For Purchase Order
select pos.name
from po_headers_all poh, wf_item_attribute_values av, per_position_structures pos
where av.item_type = poh.wf_item_type
and av.item_key = poh.wf_item_key
and av.name = ‘APPROVAL_PATH_ID’
and to_number(av.NUMBER_VALUE) = pos.position_structure_id
and poh.org_id = 103
and poh.po_header_id = 1324; –You need to retrieve your PO_HEADER_ID