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.PO_ENCUMBRANCE_POSTPROCESSING dependencies on XLA_DISTRIBUTION_LINKS

Line 699: --between po_bc_distributions and xla_distribution_links. A 1-1 mapping

695: l_progress := '100';
696: --
697: --We need to set the value of APPLIED_TO_DIST_ID_2 this would be passed
698: --onto the allocation attributes so that a 1-1 mapping can be created
699: --between po_bc_distributions and xla_distribution_links. A 1-1 mapping
700: --already exists between xla_distribution_links and gl_bc_packets. This
701: --is the route to be followed to establish a 1-1 mapping between
702: --po_bc_distributions and xla_distribution_links
703: l_num_of_rows_inserted :=sql%rowcount;

Line 700: --already exists between xla_distribution_links and gl_bc_packets. This

696: --
697: --We need to set the value of APPLIED_TO_DIST_ID_2 this would be passed
698: --onto the allocation attributes so that a 1-1 mapping can be created
699: --between po_bc_distributions and xla_distribution_links. A 1-1 mapping
700: --already exists between xla_distribution_links and gl_bc_packets. This
701: --is the route to be followed to establish a 1-1 mapping between
702: --po_bc_distributions and xla_distribution_links
703: l_num_of_rows_inserted :=sql%rowcount;
704: IF g_debug_stmt THEN

Line 702: --po_bc_distributions and xla_distribution_links

698: --onto the allocation attributes so that a 1-1 mapping can be created
699: --between po_bc_distributions and xla_distribution_links. A 1-1 mapping
700: --already exists between xla_distribution_links and gl_bc_packets. This
701: --is the route to be followed to establish a 1-1 mapping between
702: --po_bc_distributions and xla_distribution_links
703: l_num_of_rows_inserted :=sql%rowcount;
704: IF g_debug_stmt THEN
705: PO_DEBUG.debug_var(l_log_head,l_progress,'l_num_of_rows_inserted',l_num_of_rows_inserted);
706: END IF;

Line 1359: --We have to join with xla_distribution_links to get a mapping between

1355: --Modified the query below to join with gl_bc_packets_hists
1356: --This is so that the error rows are always found. GL moves
1357: --all errored rows to gl_bc_packets_hist for performance reasons.
1358: --
1359: --We have to join with xla_distribution_links to get a mapping between
1360: --po_bc_distributions and gl_bc_packets. We need a distinct to ensure that
1361: --for federal /customization cases where there could be multiple rows in
1362: --gl_bc_packets for the same distribution po_bc_distributions we are returned
1363: --just one row.

Line 1403: FROM XLA_DISTRIBUTION_LINKS XLD,

1399: pbd.adjustment_status,
1400: pbd.distribution_type) *
1401: PBD.accounted_amt TRANSACTION_AMOUNT,
1402: PBD.reference15 REFERENCE15
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 ,

Line 1438: FROM XLA_DISTRIBUTION_LINKS XLD,

1434: pbd.adjustment_status,
1435: pbd.distribution_type) *
1436: PBD.accounted_amt TRANSACTION_AMOUNT,
1437: PBD.reference15 REFERENCE15
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 ,