DBA Data[Home] [Help]

APPS.PO_REQ_DOCUMENT_CHECKS_PVT dependencies on DUAL

Line 43: -- The implementation of updatable_flag involves a fake "update dual" statement to

39: -- The number of messages put into FND Message Stack by this API
40: --x_msg_data
41: -- First message put into FND Message Stack by this API
42: --Notes:
43: -- The implementation of updatable_flag involves a fake "update dual" statement to
44: -- optimize performance.
45: --End of Comments
46: -------------------------------------------------------------------------------
47:

Line 74: --To obtimize performance, Execute a fake "update dual" in BULK. The WHERE clause

70: || l_progress, 'Entering Procedure '||l_api_name);
71: END IF;
72: END IF;
73:
74: --To obtimize performance, Execute a fake "update dual" in BULK. The WHERE clause
75: -- of the fake update statement checks if the current entity is updatable or not.
76: -- One dual row updated <==> where clause is true <==> current entity is updatable.
77: -- Later, Examine BULK_ROWCOUNT in a loop to determine updatable_flag
78: l_progress := '010';

Line 76: -- One dual row updated <==> where clause is true <==> current entity is updatable.

72: END IF;
73:
74: --To obtimize performance, Execute a fake "update dual" in BULK. The WHERE clause
75: -- of the fake update statement checks if the current entity is updatable or not.
76: -- One dual row updated <==> where clause is true <==> current entity is updatable.
77: -- Later, Examine BULK_ROWCOUNT in a loop to determine updatable_flag
78: l_progress := '010';
79:
80: -- bug3606853 START

Line 81: -- The original approach was to do a fake UPDATE on DUAL table. However, this

77: -- Later, Examine BULK_ROWCOUNT in a loop to determine updatable_flag
78: l_progress := '010';
79:
80: -- bug3606853 START
81: -- The original approach was to do a fake UPDATE on DUAL table. However, this
82: -- is causing locking issue (and priviledge). Therefore, BULK INSERT is used
83: -- instead of BULK UPDATE
84:
85: l_procedure_id := PO_CORE_S.get_session_gt_nextval;

Line 93: FROM DUAL

89: INSERT INTO PO_SESSION_GT
90: ( key
91: )
92: SELECT l_procedure_id
93: FROM DUAL
94: WHERE
95: EXISTS (select null from po_requisition_headers h
96: WHERE h.requisition_header_id = p_req_header_id(i)
97: AND (h.authorization_status is NULL

Line 122: -- Updateable Header/Line found in the fake "update dual" stmt

118: l_progress := '030';
119: FOR i IN 1..p_count LOOP
120:
121: IF SQL%BULK_ROWCOUNT(i) > 0 THEN
122: -- Updateable Header/Line found in the fake "update dual" stmt
123: x_req_status_rec.updatable_flag(i) := 'Y';
124:
125: -- This document is updatable, lock the document if p_lock_flag=Y
126: l_progress := '040';

Line 194: -- The implementation of reservable_flag involves a fake "update dual" statement to

190: -- The number of messages put into FND Message Stack by this API
191: --x_msg_data
192: -- First message put into FND Message Stack by this API
193: --Notes:
194: -- The implementation of reservable_flag involves a fake "update dual" statement to
195: -- optimize performance.
196: --End of Comments
197: -------------------------------------------------------------------------------
198:

Line 224: --To obtimize performance, Execute a fake "update dual" in BULK. The WHERE clause

220: || l_progress, 'Entering Procedure '||l_api_name);
221: END IF;
222: END IF;
223:
224: --To obtimize performance, Execute a fake "update dual" in BULK. The WHERE clause
225: -- of the fake update statement checks if the current entity is reservable or not.
226: -- One dual row updated <==> where clause is true <==> current entity is reservable.
227: -- Later, Examine BULK_ROWCOUNT in a loop to determine reservable_flag
228: l_progress := '010';

Line 226: -- One dual row updated <==> where clause is true <==> current entity is reservable.

222: END IF;
223:
224: --To obtimize performance, Execute a fake "update dual" in BULK. The WHERE clause
225: -- of the fake update statement checks if the current entity is reservable or not.
226: -- One dual row updated <==> where clause is true <==> current entity is reservable.
227: -- Later, Examine BULK_ROWCOUNT in a loop to determine reservable_flag
228: l_progress := '010';
229:
230: -- bug3606853 START

Line 231: -- The original approach was to do a fake UPDATE on DUAL table. However, this

227: -- Later, Examine BULK_ROWCOUNT in a loop to determine reservable_flag
228: l_progress := '010';
229:
230: -- bug3606853 START
231: -- The original approach was to do a fake UPDATE on DUAL table. However, this
232: -- is causing locking issue (and priviledge). Therefore, BULK INSERT is used
233: -- instead of BULK UPDATE
234:
235: l_procedure_id := PO_CORE_S.get_session_gt_nextval;

Line 243: FROM DUAL

239: INSERT INTO PO_SESSION_GT
240: ( key
241: )
242: SELECT l_procedure_id
243: FROM DUAL
244: WHERE
245: EXISTS (select null from po_requisition_headers h
246: WHERE h.requisition_header_id = p_req_header_id(i)
247: AND (h.authorization_status is NULL

Line 272: -- Reservable Header/Line found in the fake "update dual" stmt

268: l_progress := '030';
269: FOR i IN 1..p_count LOOP
270:
271: IF SQL%BULK_ROWCOUNT(i) > 0 THEN
272: -- Reservable Header/Line found in the fake "update dual" stmt
273: x_req_status_rec.reservable_flag(i) := 'Y';
274: ELSE
275: x_req_status_rec.reservable_flag(i) := 'N';
276: END IF; --END of IF SQL%BULK_ROWCOUNT(i) > 0

Line 330: -- The implementation of unreservable_flag involves a fake "update dual" statement to

326: -- The number of messages put into FND Message Stack by this API
327: --x_msg_data
328: -- First message put into FND Message Stack by this API
329: --Notes:
330: -- The implementation of unreservable_flag involves a fake "update dual" statement to
331: -- optimize performance.
332: --End of Comments
333: -------------------------------------------------------------------------------
334:

Line 361: --To obtimize performance, Execute a fake "update dual" in BULK. The WHERE clause

357: || l_progress, 'Entering Procedure '||l_api_name);
358: END IF;
359: END IF;
360:
361: --To obtimize performance, Execute a fake "update dual" in BULK. The WHERE clause
362: -- of the fake update statement checks if the current entity is unreservable or not.
363: -- One dual row updated <==> where clause is true <==> current entity is unreservable.
364: -- Later, Examine BULK_ROWCOUNT in a loop to determine unreservable_flag
365: l_progress := '010';

Line 363: -- One dual row updated <==> where clause is true <==> current entity is unreservable.

359: END IF;
360:
361: --To obtimize performance, Execute a fake "update dual" in BULK. The WHERE clause
362: -- of the fake update statement checks if the current entity is unreservable or not.
363: -- One dual row updated <==> where clause is true <==> current entity is unreservable.
364: -- Later, Examine BULK_ROWCOUNT in a loop to determine unreservable_flag
365: l_progress := '010';
366:
367: -- bug3606853 START

Line 368: -- The original approach was to do a fake UPDATE on DUAL table. However, this

364: -- Later, Examine BULK_ROWCOUNT in a loop to determine unreservable_flag
365: l_progress := '010';
366:
367: -- bug3606853 START
368: -- The original approach was to do a fake UPDATE on DUAL table. However, this
369: -- is causing locking issue (and priviledge). Therefore, BULK INSERT is used
370: -- instead of BULK UPDATE
371:
372: l_procedure_id := PO_CORE_S.get_session_gt_nextval;

Line 380: FROM DUAL

376: INSERT INTO PO_SESSION_GT
377: ( key
378: )
379: SELECT l_procedure_id
380: FROM DUAL
381: WHERE
382: EXISTS (select null from po_requisition_headers h
383: WHERE h.requisition_header_id = p_req_header_id(i)
384: AND (h.closed_code is NULL or h.closed_code IN ('OPEN', 'CLOSED')))

Line 402: -- unreservable Header/Line found in the fake "update dual" stmt

398: l_progress := '030';
399: FOR i IN 1..p_count LOOP
400:
401: IF SQL%BULK_ROWCOUNT(i) > 0 THEN
402: -- unreservable Header/Line found in the fake "update dual" stmt
403: x_req_status_rec.unreservable_flag(i) := 'Y';
404: ELSE
405: x_req_status_rec.unreservable_flag(i) := 'N';
406: END IF; --END of IF SQL%BULK_ROWCOUNT(i) > 0