DBA Data[Home] [Help]

APPS.PO_REQ_DOCUMENT_CHECKS_PVT dependencies on PO_CORE_S

Line 85: l_procedure_id := PO_CORE_S.get_session_gt_nextval;

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;
86:
87: FORALL i IN 1..p_count
88: -- SQL What: Checks if current PO Header/Line/Shipment is in updateable status
89: INSERT INTO PO_SESSION_GT

Line 235: l_procedure_id := PO_CORE_S.get_session_gt_nextval;

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;
236:
237: FORALL i IN 1..p_count
238: -- SQL What: Checks if current PO Header/Line/Shipment is in reservable status
239: INSERT INTO PO_SESSION_GT

Line 367: l_procedure_id := PO_CORE_S.get_session_gt_nextval;

363: -- The original approach was to do a fake UPDATE on DUAL table. However, this
364: -- is causing locking issue (and priviledge). Therefore, BULK INSERT is used
365: -- instead of BULK UPDATE
366:
367: l_procedure_id := PO_CORE_S.get_session_gt_nextval;
368:
369: FORALL i IN 1..p_count
370: -- SQL What: Checks if current PO Header/Line/Shipment is in unreservable status
371: INSERT INTO PO_SESSION_GT