[Home] [Help]
369: x_packet_id => x_packet_id
370: );
371:
372: l_progress := '200';
373: -- Populate eventids in psa_bc_xla_events_gt for these events
374: -- to be considered by Budgetary Control API
375: IF g_debug_stmt THEN
376: PO_DEBUG.debug_var(l_log_head,l_progress,'x_packet_id',x_packet_id);
377: END IF;
385: -- in one transaction boundary, PSA is getting the event id of previous lines
386: -- also which it has allready processed in this tranaction.
387: -- So clearing the event GT table before we insert any new event.
388:
389: DELETE FROM psa_bc_xla_events_gt
390: WHERE event_id IN ( SELECT distinct ae_event_id
391: FROM po_bc_distributions
392: WHERE packet_id <> x_packet_id
393: );
392: WHERE packet_id <> x_packet_id
393: );
394:
395:
396: INSERT into psa_bc_xla_events_gt
397: (
398: event_id,
399: result_code -- Bug #4637958
400: )
1362: --gl_bc_packets for the same distribution po_bc_distributions we are returned
1363: --just one row.
1364: --
1365: -- We will get all the packets id from gl_bc_packets for the events which we have populated in
1366: -- psa_bc_xla_events_gt table for the current packet Id. We won't use the packet id returned by
1367: -- Execute GL call as there can be mutiple packet id from which we need to take the result from
1368: -- GL BC PACKETS. In case of Cancel action with recreate demand we create two events, which belong
1369: -- to different entity. So two packets will be created by PSA.
1370: --
1367: -- Execute GL call as there can be mutiple packet id from which we need to take the result from
1368: -- GL BC PACKETS. In case of Cancel action with recreate demand we create two events, which belong
1369: -- to different entity. So two packets will be created by PSA.
1370: --
1371: -- Performance Fix : Changed in Inner query based on psa_bc_xla_events_gt to
1372: -- change the Plan of the Overall SQL.
1373: SELECT
1374: DISTINCT
1375: STATUS_CODE,
1403: FROM XLA_DISTRIBUTION_LINKS XLD,
1404: PO_BC_DISTRIBUTIONS PBD,
1405: GL_BC_PACKETS GLBC
1406: WHERE GLBC.PACKET_ID IN (SELECT DISTINCT glbc1.packet_id
1407: FROM psa_bc_xla_events_gt ps_ev_Gt ,
1408: GL_BC_PACKETS glbc1
1409: WHERE ps_ev_Gt.event_id = glbc1.event_id)
1410: AND XLD.AE_HEADER_ID = GLBC.ae_header_id
1411: AND xld.ae_line_num = GLBC.ae_line_num
1438: FROM XLA_DISTRIBUTION_LINKS XLD,
1439: PO_BC_DISTRIBUTIONS PBD,
1440: GL_BC_PACKETS_HISTS GLBCH
1441: WHERE GLBCH.PACKET_ID IN (SELECT DISTINCT glbch1.packet_id
1442: FROM psa_bc_xla_events_gt ps_ev_Gt ,
1443: GL_BC_PACKETS_HISTS glbch1
1444: WHERE ps_ev_Gt.event_id = glbch1.event_id)
1445: AND XLD.AE_HEADER_ID = GLBCH.ae_header_id
1446: AND xld.ae_line_num = GLBCH.ae_line_num
3998: l_proc_name CONSTANT VARCHAR2(30) := 'DELETE_PACKET_AUTONOMOUS';
3999: l_log_head CONSTANT VARCHAR2(100) := g_log_head || l_proc_name;
4000: l_progress VARCHAR2(3) := '000';
4001: --
4002: -- SQL What: Querying for events currently in PSA_BC_XLA_EVENTS_GT
4003: -- SQL Why : Need to delete all data related to these events from PSA tables
4004: -- SQL Join: None
4005: CURSOR cur_events IS
4006: SELECT event_id
4003: -- SQL Why : Need to delete all data related to these events from PSA tables
4004: -- SQL Join: None
4005: CURSOR cur_events IS
4006: SELECT event_id
4007: FROM PSA_BC_XLA_EVENTS_GT;
4008:
4009: BEGIN
4010:
4011: IF g_debug_stmt THEN