eTRM uses javascript that opens and focuses a separate window to display reports. Your browser does not appear to support javascript. This should not prevent you from using eTRM but it does mean the window focus feature will not work. Please check the contents of other windows on your desktop if you click on a link that does not appear to do anything.

APPS.OE_ORDER_BOOK_UTIL dependencies on WF_ENGINE

Line 1612: -- and needs to be done before calling the wf_engine as the workflow

1608:
1609:
1610: -- Lock the order: header, lines , sales credits and price adjustments
1611: -- This will prevent another user from working on the same order
1612: -- and needs to be done before calling the wf_engine as the workflow
1613: -- engine will hang if another user is trying to book the same order
1614:
1615: OE_ORDER_UTIL.Lock_Order_Object
1616: (p_header_id => p_header_id

Line 1625: -- Call WF_ENGINE to complete the BOOK_ELIGIBLE activity and proceed

1621: ELSIF x_return_status = FND_API.G_RET_STS_UNEXP_ERROR THEN
1622: RAISE FND_API.G_EXC_UNEXPECTED_ERROR;
1623: END IF;
1624:
1625: -- Call WF_ENGINE to complete the BOOK_ELIGIBLE activity and proceed
1626: -- to the next activity in the order workflow
1627:
1628: BEGIN
1629: WF_ENGINE.CompleteActivityInternalName

Line 1629: WF_ENGINE.CompleteActivityInternalName

1625: -- Call WF_ENGINE to complete the BOOK_ELIGIBLE activity and proceed
1626: -- to the next activity in the order workflow
1627:
1628: BEGIN
1629: WF_ENGINE.CompleteActivityInternalName
1630: ( itemtype => 'OEOH'
1631: , itemkey => l_itemkey
1632: , activity => 'BOOK_ELIGIBLE'
1633: , result => NULL

Line 1644: oe_debug_pub.add( 'AFTER CALLING WF_ENGINE' ) ;

1640: RAISE ;
1641: END ;
1642:
1643: IF l_debug_level > 0 THEN
1644: oe_debug_pub.add( 'AFTER CALLING WF_ENGINE' ) ;
1645: END IF;
1646:
1647: -- if order was booked, the flag on the order header would have
1648: -- been updated.