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.FII_AR_TPDUE_TBL_REFRESH dependencies on FII_CUSTOMER_HIERARCHIES

Line 173: -- to fii_time_structures, fii_customer_hierarchies, hz_parties

169:
170:
171: --------------------------------------------------------------------------
172: --Insert data FROM fii_ar_net_rec_base_mv by joining
173: -- to fii_time_structures, fii_customer_hierarchies, hz_parties
174: --Here we calculate ITD amounts for date on which the job is run
175: --fii_customer_hierarchies and hz_parties is used to avoid
176: --costly GT table population while running the report
177: --------------------------------------------------------------------------

Line 175: --fii_customer_hierarchies and hz_parties is used to avoid

171: --------------------------------------------------------------------------
172: --Insert data FROM fii_ar_net_rec_base_mv by joining
173: -- to fii_time_structures, fii_customer_hierarchies, hz_parties
174: --Here we calculate ITD amounts for date on which the job is run
175: --fii_customer_hierarchies and hz_parties is used to avoid
176: --costly GT table population while running the report
177: --------------------------------------------------------------------------
178:
179: insert /*+ append */ INTO FII_AR_TPDUE_BASE_F

Line 268: FII_CUSTOMER_HIERARCHIES cust,

264: current_open_amount_prim,
265: current_open_amount_sec
266: FROM fii_time_structures cal,
267: fii_ar_net_rec_base_mv b,
268: FII_CUSTOMER_HIERARCHIES cust,
269: HZ_PARTIES hz
270: WHERE cal.report_date = l_this_date
271: AND cal.time_id = b.time_id
272: AND cal.period_type_id = b.period_type_id

Line 303: -- to fii_time_structures, fii_customer_hierarchies, hz_parties

299: END IF;
300: commit;
301: --------------------------------------------------------------------------
302: --Insert data FROM fii_ar_disputes_base_mv by joining
303: -- to fii_time_structures, fii_customer_hierarchies, hz_parties
304: --Here we calculate ITD amounts for date on which the job is run
305: --fii_customer_hierarchies and hz_parties is used to avoid
306: --costly GT table population while running the report
307: --------------------------------------------------------------------------

Line 305: --fii_customer_hierarchies and hz_parties is used to avoid

301: --------------------------------------------------------------------------
302: --Insert data FROM fii_ar_disputes_base_mv by joining
303: -- to fii_time_structures, fii_customer_hierarchies, hz_parties
304: --Here we calculate ITD amounts for date on which the job is run
305: --fii_customer_hierarchies and hz_parties is used to avoid
306: --costly GT table population while running the report
307: --------------------------------------------------------------------------
308:
309:

Line 371: FII_CUSTOMER_HIERARCHIES cust,

367: past_due_dispute_amount_prim,
368: past_due_dispute_amount_sec
369: FROM fii_time_structures cal,
370: fii_ar_disputes_base_mv b,
371: FII_CUSTOMER_HIERARCHIES cust,
372: HZ_PARTIES hz
373: WHERE cal.report_date = l_this_date
374: AND cal.time_id = b.time_id
375: AND cal.period_type_id = b.period_type_id

Line 504: -- to fii_time_structures, fii_customer_hierarchies, hz_parties

500:
501:
502: --------------------------------------------------------------------------
503: --Insert data FROM fii_ar_net_rec_base_mv by joining
504: -- to fii_time_structures, fii_customer_hierarchies, hz_parties
505: --Here we calculate ITD amounts for date on which the job is run
506: --fii_customer_hierarchies and hz_parties is used to avoid
507: --costly GT table population while running the report
508: --------------------------------------------------------------------------

Line 506: --fii_customer_hierarchies and hz_parties is used to avoid

502: --------------------------------------------------------------------------
503: --Insert data FROM fii_ar_net_rec_base_mv by joining
504: -- to fii_time_structures, fii_customer_hierarchies, hz_parties
505: --Here we calculate ITD amounts for date on which the job is run
506: --fii_customer_hierarchies and hz_parties is used to avoid
507: --costly GT table population while running the report
508: --------------------------------------------------------------------------
509:
510: insert /*+ append */ INTO FII_AR_TPDUE_AGRT_F

Line 599: FII_CUSTOMER_HIERARCHIES cust,

595: current_open_amount_prim,
596: current_open_amount_sec
597: FROM fii_time_structures cal,
598: fii_ar_net_rec_agrt_mv b,
599: FII_CUSTOMER_HIERARCHIES cust,
600: HZ_PARTIES hz
601: WHERE cal.report_date = l_this_date
602: AND cal.time_id = b.time_id
603: AND cal.period_type_id = b.period_type_id

Line 608: FROM fii_customer_hierarchies cust1

604: AND bitand(cal.record_type_id, 512) = 512
605: AND cust.child_party_id = b.party_id
606: AND b.parent_party_id in (SELECT decode (cust1.next_level_is_leaf_flag,
607: 'Y', cust1.parent_party_id, cust.child_party_id)
608: FROM fii_customer_hierarchies cust1
609: WHERE cust1.next_level_party_id = cust.child_party_id
610: AND cust1.child_party_id = cust.child_party_id
611: AND cust1.child_party_id <> cust1.parent_party_id)
612: AND cust.next_level_party_id = hz.party_id

Line 638: -- to fii_time_structures, fii_customer_hierarchies, hz_parties

634: END IF;
635: commit;
636: --------------------------------------------------------------------------
637: --Insert data FROM fii_ar_disputes_agrt_mv by joining
638: -- to fii_time_structures, fii_customer_hierarchies, hz_parties
639: --Here we calculate ITD amounts for date on which the job is run
640: --fii_customer_hierarchies and hz_parties is used to avoid
641: --costly GT table population while running the report
642: --------------------------------------------------------------------------

Line 640: --fii_customer_hierarchies and hz_parties is used to avoid

636: --------------------------------------------------------------------------
637: --Insert data FROM fii_ar_disputes_agrt_mv by joining
638: -- to fii_time_structures, fii_customer_hierarchies, hz_parties
639: --Here we calculate ITD amounts for date on which the job is run
640: --fii_customer_hierarchies and hz_parties is used to avoid
641: --costly GT table population while running the report
642: --------------------------------------------------------------------------
643:
644:

Line 707: FII_CUSTOMER_HIERARCHIES cust,

703: past_due_dispute_amount_prim past_due_dispute_amount_prim,
704: past_due_dispute_amount_sec past_due_dispute_amount_sec
705: FROM fii_time_structures cal,
706: fii_ar_disputes_agrt_mv b,
707: FII_CUSTOMER_HIERARCHIES cust,
708: HZ_PARTIES hz
709: WHERE cal.report_date = l_this_date
710: AND cal.time_id = b.time_id
711: AND cal.period_type_id = b.period_type_id

Line 716: FROM fii_customer_hierarchies cust1

712: AND bitand(cal.record_type_id, 512) = 512
713: AND cust.child_party_id = b.party_id
714: AND b.parent_party_id in (SELECT decode (cust1.next_level_is_leaf_flag,
715: 'Y', cust1.parent_party_id, cust.child_party_id)
716: FROM fii_customer_hierarchies cust1
717: WHERE cust1.next_level_party_id = cust.child_party_id
718: AND cust1.child_party_id = cust.child_party_id
719: AND cust1.child_party_id <> cust1.parent_party_id)
720: AND cust.next_level_party_id = hz.party_id)