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.PJI_PJP_SUM_CUST dependencies on PJI_AC_CUST_PJP0

Line 319: -- 3. Only populate PJI_AC_CUST_PJP0.

315: -- Activities Reporting Lines fact: PJI_AC_XBS_ACCUM_F.
316: --
317: -- 1. Only modify code in the indicated area.
318: -- 2. Do not issue any statements that result in a "commit" or a "rollback"
319: -- 3. Only populate PJI_AC_CUST_PJP0.
320: --
321: -- History
322: -- 19-MAR-2004 SVERMETT Created
323: --

Line 364: * Sample code with steps to customize custom measures for AC CUSTOM MEASURE TABLE(i.e.PJI_AC_CUST_PJP0) table*

360: **************************************************************/
361:
362:
363: /**************************************************************************************************************
364: * Sample code with steps to customize custom measures for AC CUSTOM MEASURE TABLE(i.e.PJI_AC_CUST_PJP0) table*
365: * *
366: * *
367: * AC BASIS TABLE ( I.E. PJI_AC_AGGR_PJP0) *
368: * -------------------------------------- *

Line 371: * keys, which are being used, in custom table (i.e. PJI_AC_CUST_PJP0) to store customized measures. *

367: * AC BASIS TABLE ( I.E. PJI_AC_AGGR_PJP0) *
368: * -------------------------------------- *
369: * This table is the first aggregation point after the transaction accum tables and provides a basis for *
370: * custom measures. This table has to be populated to store customized measures. It holds the mandatory *
371: * keys, which are being used, in custom table (i.e. PJI_AC_CUST_PJP0) to store customized measures. *
372: * To see the definition of this table and its columns, please refer ETRM. *
373: * *
374: * MANDOTORY PREREQUISTE TO DEFINE CUSTOM MEASURE *
375: * --------------------------------------------- *

Line 382: * AC CUSTOM MEASURES TABLE ( I.E. PJI_AC_CUST_PJP0) *

378: * -------------------------------------- *
379: * If the basis table is not populated then the program will not use and store the customized measures *
380: * at all.
381: * *
382: * AC CUSTOM MEASURES TABLE ( I.E. PJI_AC_CUST_PJP0) *
383: * ------------------------------------------------- *
384: * This table is used to derive PJP custom measures only if derived measures are available in context *
385: * of TASK. After customizing the custom measures, they are stored in this table. *
386: * Following is the list of custom measure available: *

Line 421: * INSERT INTO PJI_AC_CUST_PJP0 cust_i *

417: * ------------------------------------ *
418: * - Customizing a measure using CALENDAR_TYPE,CURRENCY_CODE,REVENUE *
419: * - Define computation logic for custom measure 1 *
420: * - Remove 1=2 from the SELECT part *
421: * INSERT INTO PJI_AC_CUST_PJP0 cust_i *
422: * ( *
423: * WORKER_ID, *
424: * PROJECT_ID, *
425: * PROJECT_ORG_ID, *

Line 499: INSERT INTO PJI_AC_CUST_PJP0 cust_i

495: * pl/sql logic has to ensure that it derives incremental amounts (ie., change since the last time *
496: * summarization has been run).
497: **************************************************************************************************************/
498:
499: INSERT INTO PJI_AC_CUST_PJP0 cust_i
500: (
501: WORKER_ID,
502: PROJECT_ID,
503: PROJECT_ORG_ID,