APPS.PO_REQAPPROVAL_LAUNCH SQL Statements

The following lines contain the word 'select', 'insert', 'update' or 'delete':

Line: 92

     /* DEBUG */  PO_WF_DEBUG_PKG.insert_debug(itemtype,itemkey,x_progress);

Line: 151

  select WF_CREATEDOC_ITEMTYPE,WF_CREATEDOC_PROCESS
  from po_document_types
  where DOCUMENT_TYPE_CODE= 'REQUISITION'
  and   DOCUMENT_SUBTYPE  = 'PURCHASE';

Line: 200

     /* DEBUG */  PO_WF_DEBUG_PKG.insert_debug(itemtype,itemkey,x_progress);

Line: 204

  select to_char(PO_WF_ITEMKEY_S.nextval) into l_dummy from sys.dual;

Line: 226

     /* DEBUG */  PO_WF_DEBUG_PKG.insert_debug(itemtype,itemkey,x_progress);

Line: 304

PROCEDURE POREQ_SELECTOR ( -- Added as a part of bug 3540107
  p_itemtype   IN VARCHAR2,
  p_itemkey    IN VARCHAR2,
  p_actid      IN NUMBER,
  p_funcmode   IN VARCHAR2,
  p_x_result   IN OUT NOCOPY VARCHAR2
) IS

  -- Context setting revamp 
  l_session_user_id               NUMBER;

Line: 330

     PO_WF_DEBUG_PKG.insert_debug(
      			itemtype   => p_itemtype,
                        itemkey    => p_itemkey,
                        x_progress => 'POREQ_SELECTOR called with mode: '
			||p_funcmode||' itemtype: '||p_itemtype
			||' itemkey: '||p_itemkey);

Line: 370

       l_progress :='010 selector fn - sess_user_id:'||l_session_user_id
       		    ||' ses_resp_id '||l_session_resp_id||' responder id '
		    ||l_responder_id;

Line: 375

          /* DEBUG */  PO_WF_DEBUG_PKG.insert_debug(p_itemtype,p_itemkey,l_progress);

Line: 384

       PO_WF_DEBUG_PKG.insert_debug(itemtype   => p_itemtype,
                                    itemkey    => p_itemkey,
                                    x_progress => 'POREQ_SELECTOR: inside Test Ctx ');

Line: 387

       PO_WF_DEBUG_PKG.insert_debug(itemtype   => p_itemtype,
                                    itemkey    => p_itemkey,
                                    x_progress => 'l_is_supplier_context: ' || l_is_supplier_context);

Line: 416

	       -- bug 5333226 : if the selector fn is called from a background ps/
	       -- notif mailer then force the session to use preparer's or responder
	       -- context. This is required since the mailer/bckgrnd ps carries the
	       -- context from the last wf processed and hence even if the context values
	       -- are present, they might not be correct.

		  if (wf_engine.preserved_context = TRUE) then
	             p_x_result := 'TRUE';

Line: 457

      l_progress := '020 selection fn responder id not null';

Line: 459

          /* DEBUG */  PO_WF_DEBUG_PKG.insert_debug(p_itemtype,p_itemkey,l_progress);

Line: 464

       l_progress :='030 selector fn : setting user id :'||l_responder_id
       		    ||' resp id '||l_resp_id_to_set||' l_appl id '||l_appl_id_to_set;

Line: 467

          /* DEBUG */  PO_WF_DEBUG_PKG.insert_debug(p_itemtype,p_itemkey,l_progress);

Line: 485

      l_progress := '040 selector fn responder id null';

Line: 487

          /* DEBUG */  PO_WF_DEBUG_PKG.insert_debug(p_itemtype,p_itemkey,l_progress);

Line: 492

      l_progress := '050 selector fn : set user '||l_user_id_to_set||' resp id '
      		    ||l_resp_id_to_set||' appl id '||l_appl_id_to_set;

Line: 495

          /* DEBUG */  PO_WF_DEBUG_PKG.insert_debug(p_itemtype,p_itemkey,l_progress);

Line: 523

      PO_WF_DEBUG_PKG.insert_debug(itemtype   => p_itemtype,
                                   itemkey    => p_itemkey,
                                   x_progress => 'Exception in Selector');

Line: 529

                    'POREQ_SELECTOR',
                    p_itemtype,
                    p_itemkey,
                    p_actid,
                    p_funcmode);

Line: 536

END POREQ_SELECTOR;