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.PA_DISPLAY_PERIOD_MASKS dependencies on PA_BUDGET_VERSIONS

Line 36: FUNCTION get_current_period_start_date ( p_current_planning_period IN pa_budget_versions.current_planning_period%TYPE

32: -- OR pa_period_type set for 'PA'
33: -- it is called by get_periods()
34: */
35:
36: FUNCTION get_current_period_start_date ( p_current_planning_period IN pa_budget_versions.current_planning_period%TYPE
37: ,p_period_set_name IN gl_sets_of_books.period_set_name%TYPE
38: ,p_time_phase_code IN pa_proj_fp_options.cost_time_phased_code%TYPE
39: ,p_accounted_period_type IN gl_sets_of_books.accounted_period_type%TYPE
40: ,p_pa_period_type IN pa_implementations_all.pa_period_type%TYPE)

Line 259: FUNCTION get_periods ( p_budget_version_id IN pa_budget_versions.budget_version_id%TYPE,

255: -- it will also set the global variables g_preceeding_end and g_suceeding_start
256: -- these will be used for the proceeding buckets end period and suceeding buckets start period
257: -- get_periods will return 1 if it populates periods_tab pl/sql table successfully
258: */
259: FUNCTION get_periods ( p_budget_version_id IN pa_budget_versions.budget_version_id%TYPE,
260: p_resource_assignment_id IN pa_resource_assignments.resource_assignment_id%TYPE DEFAULT -1) RETURN NUMBER
261: IS
262: l_return NUMBER := 0; --RETURN value
263: l_current_planning_period pa_budget_versions.current_planning_period%TYPE;

Line 263: l_current_planning_period pa_budget_versions.current_planning_period%TYPE;

259: FUNCTION get_periods ( p_budget_version_id IN pa_budget_versions.budget_version_id%TYPE,
260: p_resource_assignment_id IN pa_resource_assignments.resource_assignment_id%TYPE DEFAULT -1) RETURN NUMBER
261: IS
262: l_return NUMBER := 0; --RETURN value
263: l_current_planning_period pa_budget_versions.current_planning_period%TYPE;
264: l_period_set_name gl_sets_of_books.period_set_name%TYPE;
265: l_accounted_period_type gl_sets_of_books.accounted_period_type%TYPE;
266: l_pa_period_type pa_implementations_all.pa_period_type%TYPE;
267: l_time_phase_code pa_proj_fp_options.cost_time_phased_code%TYPE;

Line 281: -- current_planning_period and period_mask_id exist in table pa_budget_versions

277: -- get_current_period_start_date(),get_gl_periods_before_csr,get_gl_periods_after_csr
278: -- get_current_period_start_date() must return a start date for get_gl_periods_before_csr
279: -- and get_gl_periods_after_csr to run
280: -- period_set_name and accounted_period_type exist in table gl_set_of_books
281: -- current_planning_period and period_mask_id exist in table pa_budget_versions
282: -- pa_period_type exists in pa_implementations_all
283: -- to find the time phase code decode is used
284: -- IF pbv.version_type = COST the time phase code = ppfo.cost_time_phased_code
285: -- IF pbv.version_type = REVENUE the time phase code = ppfo.revenue_time_phased_code

Line 305: ,pa_budget_versions pbv

301: ppfo.all_time_phased_code) time_phase_code
302: FROM gl_sets_of_books gsb
303: ,pa_implementations_all pia
304: ,pa_projects_all ppa
305: ,pa_budget_versions pbv
306: ,pa_proj_fp_options ppfo
307: WHERE ppa.project_id = pbv.project_id
308: AND pbv.budget_version_id = ppfo.fin_plan_version_id
309: AND ppa.org_id = pia.org_id

Line 1062: the current planning period in the pa_budget_versions table and pa_proj_fp_options

1058:
1059: END end_date;
1060:
1061: /* The update_current_pp is called from the Edit Plan Lines Page to update
1062: the current planning period in the pa_budget_versions table and pa_proj_fp_options
1063: table.
1064: */
1065: -- Bug Fix 3975683
1066: -- Added record version numbers which will be used

Line 1070: PROCEDURE update_current_pp (p_budget_version_id IN pa_budget_versions.budget_version_id%TYPE,

1066: -- Added record version numbers which will be used
1067: -- to see if the record is already is updates or not
1068: -- and update the version number as well.
1069:
1070: PROCEDURE update_current_pp (p_budget_version_id IN pa_budget_versions.budget_version_id%TYPE,
1071: p_current_planning_period IN pa_budget_versions.current_planning_period%TYPE,
1072: p_commit IN VARCHAR2 := FND_API.G_FALSE,
1073: p_bud_rec_ver_num IN pa_budget_versions.record_version_number%TYPE,
1074: p_fp_rec_ver_num IN pa_proj_fp_options.record_version_number%TYPE,

Line 1071: p_current_planning_period IN pa_budget_versions.current_planning_period%TYPE,

1067: -- to see if the record is already is updates or not
1068: -- and update the version number as well.
1069:
1070: PROCEDURE update_current_pp (p_budget_version_id IN pa_budget_versions.budget_version_id%TYPE,
1071: p_current_planning_period IN pa_budget_versions.current_planning_period%TYPE,
1072: p_commit IN VARCHAR2 := FND_API.G_FALSE,
1073: p_bud_rec_ver_num IN pa_budget_versions.record_version_number%TYPE,
1074: p_fp_rec_ver_num IN pa_proj_fp_options.record_version_number%TYPE,
1075: X_Return_Status OUT NOCOPY Varchar2,

Line 1073: p_bud_rec_ver_num IN pa_budget_versions.record_version_number%TYPE,

1069:
1070: PROCEDURE update_current_pp (p_budget_version_id IN pa_budget_versions.budget_version_id%TYPE,
1071: p_current_planning_period IN pa_budget_versions.current_planning_period%TYPE,
1072: p_commit IN VARCHAR2 := FND_API.G_FALSE,
1073: p_bud_rec_ver_num IN pa_budget_versions.record_version_number%TYPE,
1074: p_fp_rec_ver_num IN pa_proj_fp_options.record_version_number%TYPE,
1075: X_Return_Status OUT NOCOPY Varchar2,
1076: X_Msg_Count OUT NOCOPY Number,
1077: X_Msg_Data OUT NOCOPY Varchar2) IS

Line 1081: FROM pa_budget_versions

1077: X_Msg_Data OUT NOCOPY Varchar2) IS
1078:
1079: CURSOR get_version_type_csr(p_budget_version_id NUMBER) IS
1080: SELECT version_type
1081: FROM pa_budget_versions
1082: WHERE budget_version_id = p_budget_version_id;
1083:
1084: l_version_type PA_BUDGET_VERSIONS.version_type%TYPE;
1085: l_curr_plan_period PA_BUDGET_VERSIONS.current_planning_period%type;

Line 1084: l_version_type PA_BUDGET_VERSIONS.version_type%TYPE;

1080: SELECT version_type
1081: FROM pa_budget_versions
1082: WHERE budget_version_id = p_budget_version_id;
1083:
1084: l_version_type PA_BUDGET_VERSIONS.version_type%TYPE;
1085: l_curr_plan_period PA_BUDGET_VERSIONS.current_planning_period%type;
1086: BEGIN
1087: -- Initialize values
1088: X_Return_Status := Fnd_Api.G_Ret_Sts_Success;

Line 1085: l_curr_plan_period PA_BUDGET_VERSIONS.current_planning_period%type;

1081: FROM pa_budget_versions
1082: WHERE budget_version_id = p_budget_version_id;
1083:
1084: l_version_type PA_BUDGET_VERSIONS.version_type%TYPE;
1085: l_curr_plan_period PA_BUDGET_VERSIONS.current_planning_period%type;
1086: BEGIN
1087: -- Initialize values
1088: X_Return_Status := Fnd_Api.G_Ret_Sts_Success;
1089: X_Msg_Count := 0;

Line 1125: UPDATE pa_budget_versions

1121:
1122: -- Bug Fix 3975683
1123: -- Started updating the record_version_number
1124:
1125: UPDATE pa_budget_versions
1126: SET current_planning_period = p_current_planning_period,
1127: record_version_number = record_version_number + 1
1128: WHERE budget_version_id = p_budget_version_id
1129: AND record_version_number = p_bud_rec_ver_num;