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.JAI_CMN_RGM_RECORDING_PKG dependencies on GL_PERIOD_STATUSES

Line 1468: FROM gl_period_statuses

1464: Implemented the same using caching logic.
1465: */
1466: CURSOR c_period_dtl(cp_sob_id IN NUMBER, cp_accounting_date IN DATE) IS
1467: SELECT period_name, start_date, end_date, closing_status
1468: FROM gl_period_statuses
1469: WHERE application_id = jai_constants.gl_application_id
1470: AND set_of_books_id = cp_sob_id
1471: AND cp_accounting_date BETWEEN start_date AND end_date;
1472:

Line 1484: -- GL_PERIOD_STATUSES has CLOSING_STATUS column that tells whether the the period is closed or not for each APPLICATION

1480: l_func_curr_det jai_plsql_cache_pkg.func_curr_details;
1481: BEGIN
1482:
1483: -- CHK we need to see whether the accounting date that is being used belong to a open period or not
1484: -- GL_PERIOD_STATUSES has CLOSING_STATUS column that tells whether the the period is closed or not for each APPLICATION
1485:
1486: -- Validation of whether the accounting date falls under an open period or not, if not, then we populate the first date of period
1487: /* Bug 5243532. Added by Lakshmi Gopalsami
1488: Removed the logic which is referring to hr_operating_units

Line 1508: FROM gl_period_statuses

1504: p_period_name := r_period_dtl.period_name;
1505: ELSE
1506:
1507: FOR period IN ( SELECT period_name, start_date, end_date, closing_status
1508: FROM gl_period_statuses
1509: WHERE application_id = jai_constants.gl_application_id
1510: AND set_of_books_id = ln_sob_id
1511: AND start_date > p_accounting_date
1512: ORDER BY period_year, period_num