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 1526: -- and needs to be done before calling the wf_engine as the workflow

1522:
1523:
1524: -- Lock the order: header, lines , sales credits and price adjustments
1525: -- This will prevent another user from working on the same order
1526: -- and needs to be done before calling the wf_engine as the workflow
1527: -- engine will hang if another user is trying to book the same order
1528:
1529: OE_ORDER_UTIL.Lock_Order_Object
1530: (p_header_id => p_header_id

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

1535: ELSIF x_return_status = FND_API.G_RET_STS_UNEXP_ERROR THEN
1536: RAISE FND_API.G_EXC_UNEXPECTED_ERROR;
1537: END IF;
1538:
1539: -- Call WF_ENGINE to complete the BOOK_ELIGIBLE activity and proceed
1540: -- to the next activity in the order workflow
1541:
1542: WF_ENGINE.CompleteActivityInternalName
1543: ( itemtype => 'OEOH'

Line 1542: WF_ENGINE.CompleteActivityInternalName

1538:
1539: -- Call WF_ENGINE to complete the BOOK_ELIGIBLE activity and proceed
1540: -- to the next activity in the order workflow
1541:
1542: WF_ENGINE.CompleteActivityInternalName
1543: ( itemtype => 'OEOH'
1544: , itemkey => l_itemkey
1545: , activity => 'BOOK_ELIGIBLE'
1546: , result => NULL

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

1547: );
1548:
1549:
1550: IF l_debug_level > 0 THEN
1551: oe_debug_pub.add( 'AFTER CALLING WF_ENGINE' ) ;
1552: END IF;
1553:
1554: -- if order was booked, the flag on the order header would have
1555: -- been updated.