APPS.PJI_PJP_SUM_CUST dependencies on PJI_FP_AGGR_PJP0

Line 62: * FP BASIS TABLE ( I.E. PJI_FP_AGGR_PJP0) *

58: * *
59: * Sample code with steps to customize custom measures for FP CUSTOM MEASURE TABLE(i.e.PJI_FP_CUST_PJP0) table*
60: * *
61: * *
62: * FP BASIS TABLE ( I.E. PJI_FP_AGGR_PJP0) *
63: * -------------------------------------- *
64: * This table is the first aggregation point after the transaction accum tables and provides a basis for *
65: * custom measures. This table has to be populated to store customized measures. It holds the mandatory *
66: * keys, which are being used, in custom table (i.e. PJI_FP_CUST_PJP0) to store customized measures. *

Line 71: * 1. Basis Table PJI_FP_AGGR_PJP0 should be populated *

67: * To see the definition of this table and its columns, please refer ETRM. *
68: * *
69: * MANDOTORY PREREQUISTE TO DEFINE CUSTOM MEASURE *
70: * --------------------------------------------- *
71: * 1. Basis Table PJI_FP_AGGR_PJP0 should be populated *
72: * WHAT IF FP BASIS TABLE IS NOT POPULATED *
73: * -------------------------------------- *
74: * If the basis table is not populated then the program will not use and store the customized measures *
75: * at all. *

Line 201: * PJI_FP_AGGR_PJP0 pjp0 -- FP basis table, *

197: * TO_NUMBER(NULL) CUSTOM13, *
198: * TO_NUMBER(NULL) CUSTOM14, *
199: * TO_NUMBER(NULL) CUSTOM15 *
200: * FROM *
201: * PJI_FP_AGGR_PJP0 pjp0 -- FP basis table, *
202: * PJI_FP_TXN_ACCUM_HEADER pjilookup -- PJI Lookup table *
203: * WHERE *
204: * pjp0.WORKER_ID = p_worker_id *
205: * AND pjp0.TXN_ACCUM_HEADER_ID = pjilookup.TXN_ACCUM_HEADER_ID; *

Line 289: PJI_FP_AGGR_PJP0 pjp0

285: TO_NUMBER(NULL) CUSTOM13,
286: TO_NUMBER(NULL) CUSTOM14,
287: TO_NUMBER(NULL) CUSTOM15
288: FROM
289: PJI_FP_AGGR_PJP0 pjp0
290: WHERE
291: pjp0.WORKER_ID = p_worker_id AND
292: 1 = 2;
293: