[Home] [Help]
1914: Implemented the same using caching logic.
1915: */
1916: CURSOR c_period_dtl(cp_sob_id IN NUMBER, cp_accounting_date IN DATE) IS
1917: SELECT period_name, start_date, end_date, closing_status
1918: FROM gl_period_statuses
1919: WHERE application_id = jai_constants.gl_application_id
1920: AND set_of_books_id = cp_sob_id
1921: AND closing_status IN ('O','F') -- added for bug#7010029
1922: AND cp_accounting_date BETWEEN start_date AND end_date
1932: l_func_curr_det jai_plsql_cache_pkg.func_curr_details;
1933: BEGIN
1934:
1935: -- CHK we need to see whether the accounting date that is being used belong to a open period or not
1936: -- GL_PERIOD_STATUSES has CLOSING_STATUS column that tells whether the the period is closed or not for each APPLICATION
1937:
1938: -- Validation of whether the accounting date falls under an open period or not, if not, then we populate the first date of period
1939: /* Bug 5243532. Added by Lakshmi Gopalsami
1940: Removed the logic which is referring to hr_operating_units
1956: p_period_name := r_period_dtl.period_name;
1957: ELSE
1958:
1959: FOR period IN ( SELECT period_name, start_date, end_date, closing_status
1960: FROM gl_period_statuses
1961: WHERE application_id = jai_constants.gl_application_id
1962: AND set_of_books_id = ln_sob_id
1963: AND start_date > p_accounting_date
1964: ORDER BY period_year, period_num