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.PA_PURGE_ICIP dependencies on PA_PURGE

Line 1: package body pa_purge_icip as

1: package body pa_purge_icip as
2: /*$Header: PAICIPPB.pls 120.6.12010000.2 2009/06/23 14:25:58 atshukla ship $*/
3:
4:
5: l_commit_size NUMBER ;

Line 587: -- Pa_Purge_Project_details which will show the no. of records

583:
584: else
585: -- After "deleting" or "deleting and inserting" a set of records
586: -- the transaction is commited. This also creates a record in the
587: -- Pa_Purge_Project_details which will show the no. of records
588: -- that are purged from each table.
589:
590: pa_debug.debug( ' ->Calling pa_purge.CommitProcess ') ;
591: pa_purge.CommitProcess

Line 590: pa_debug.debug( ' ->Calling pa_purge.CommitProcess ') ;

586: -- the transaction is commited. This also creates a record in the
587: -- Pa_Purge_Project_details which will show the no. of records
588: -- that are purged from each table.
589:
590: pa_debug.debug( ' ->Calling pa_purge.CommitProcess ') ;
591: pa_purge.CommitProcess
592: (p_purge_batch_id => p_purge_batch_id,
593: p_project_id => p_project_id,
594: p_table_name => 'PA_DRAFT_INVOICE_DETAILS_ALL',

Line 591: pa_purge.CommitProcess

587: -- Pa_Purge_Project_details which will show the no. of records
588: -- that are purged from each table.
589:
590: pa_debug.debug( ' ->Calling pa_purge.CommitProcess ') ;
591: pa_purge.CommitProcess
592: (p_purge_batch_id => p_purge_batch_id,
593: p_project_id => p_project_id,
594: p_table_name => 'PA_DRAFT_INVOICE_DETAILS_ALL',
595: p_NoOfRecordsIns => l_NoOfRecordsIns,

Line 653: pa_purge.CommitProcess

649:
650: IF NVL(l_NoOfRecordsDel,0) = 0 THEN
651: exit ;
652: ELSE
653: pa_purge.CommitProcess
654: (p_purge_batch_id => p_purge_batch_id,
655: p_project_id => p_project_id,
656: p_table_name => 'PA_DRAFT_INVOICE_DETAILS_ALL',
657: p_NoOfRecordsIns => l_NoOfRecordsIns,

Line 671: pa_debug.debug('Error Procedure Name := PA_PURGE_ICIP.PA_DraftInvDetails' );

667: WHEN PA_PROJECT_UTILS2.PA_Arch_Pur_Subroutine_Error then
668: RAISE PA_PROJECT_UTILS2.PA_Arch_Pur_Subroutine_Error ;
669:
670: WHEN OTHERS THEN
671: pa_debug.debug('Error Procedure Name := PA_PURGE_ICIP.PA_DraftInvDetails' );
672: pa_debug.debug('Error stage is '||x_err_stage );
673: pa_debug.debug('Error stack is '||x_err_stack );
674: pa_debug.debug(SQLERRM);
675:

Line 771: pa_debug.debug('Error Procedure Name := PA_PURGE_ICIP.PA_MC_DraftInvoiceDetails' );

767: WHEN PA_PROJECT_UTILS2.PA_Arch_Pur_Subroutine_Error then
768: RAISE PA_PROJECT_UTILS2.PA_Arch_Pur_Subroutine_Error ;
769:
770: WHEN OTHERS THEN
771: pa_debug.debug('Error Procedure Name := PA_PURGE_ICIP.PA_MC_DraftInvoiceDetails' );
772: pa_debug.debug('Error stage is '||x_err_stage );
773: pa_debug.debug('Error stack is '||x_err_stack );
774: pa_debug.debug(SQLERRM);
775: PA_PROJECT_UTILS2.g_sqlerrm := SQLERRM ;

Line 785: END pa_purge_icip;

781: RAISE PA_PROJECT_UTILS2.PA_Arch_Pur_Subroutine_Error ;
782:
783: end PA_MC_DraftInvoiceDetails;
784:
785: END pa_purge_icip;