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_PROJ_FP_OPTIONS

Line 38: ,p_time_phase_code IN pa_proj_fp_options.cost_time_phased_code%TYPE

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)
41: RETURN DATE IS
42:

Line 91: ,p_time_phase_code IN pa_proj_fp_options.cost_time_phased_code%TYPE

87:
88:
89: PROCEDURE get_plan_period_end ( p_planning_end_date IN pa_resource_assignments.planning_end_date%TYPE
90: ,p_period_set_name IN gl_sets_of_books.period_set_name%TYPE
91: ,p_time_phase_code IN pa_proj_fp_options.cost_time_phased_code%TYPE
92: ,p_accounted_period_type IN gl_sets_of_books.accounted_period_type%TYPE
93: ,p_pa_period_type IN pa_implementations_all.pa_period_type%TYPE
94: )
95: IS

Line 132: ,p_time_phase_code IN pa_proj_fp_options.cost_time_phased_code%TYPE

128:
129:
130: PROCEDURE get_plan_period_start ( p_planning_start_date IN pa_resource_assignments.planning_start_date%TYPE
131: ,p_period_set_name IN gl_sets_of_books.period_set_name%TYPE
132: ,p_time_phase_code IN pa_proj_fp_options.cost_time_phased_code%TYPE
133: ,p_accounted_period_type IN gl_sets_of_books.accounted_period_type%TYPE
134: ,p_pa_period_type IN pa_implementations_all.pa_period_type%TYPE
135: )
136: IS

Line 267: l_time_phase_code pa_proj_fp_options.cost_time_phased_code%TYPE;

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;
268: l_period_mask_id pa_period_mask_details.period_mask_id%TYPE;
269: l_cpp_start_date DATE;
270: l_count NUMBER := 0 ; --counter variable
271: l_plan_start_date pa_resource_assignments.planning_start_date%TYPE;

Line 306: ,pa_proj_fp_options ppfo

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
310: AND gsb.set_of_books_id = pia.set_of_books_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 1074: p_fp_rec_ver_num IN pa_proj_fp_options.record_version_number%TYPE,

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
1078:

Line 1142: UPDATE pa_proj_fp_options

1138: RAISE FND_API.G_EXC_ERROR;
1139: END if;
1140:
1141: IF l_version_type = 'COST' THEN
1142: UPDATE pa_proj_fp_options
1143: SET COST_CURRENT_PLANNING_PERIOD = p_current_planning_period,
1144: record_version_number = record_version_number + 1
1145: WHERE FIN_PLAN_VERSION_ID = p_budget_version_id
1146: AND record_version_number = p_fp_rec_ver_num;

Line 1148: UPDATE pa_proj_fp_options

1144: record_version_number = record_version_number + 1
1145: WHERE FIN_PLAN_VERSION_ID = p_budget_version_id
1146: AND record_version_number = p_fp_rec_ver_num;
1147: ELSIF l_version_type = 'REVENUE' THEN
1148: UPDATE pa_proj_fp_options
1149: SET REV_CURRENT_PLANNING_PERIOD = p_current_planning_period,
1150: record_version_number = record_version_number + 1
1151: WHERE FIN_PLAN_VERSION_ID = p_budget_version_id
1152: AND record_version_number = p_fp_rec_ver_num;

Line 1154: UPDATE pa_proj_fp_options

1150: record_version_number = record_version_number + 1
1151: WHERE FIN_PLAN_VERSION_ID = p_budget_version_id
1152: AND record_version_number = p_fp_rec_ver_num;
1153: ELSIF l_version_type = 'ALL' THEN
1154: UPDATE pa_proj_fp_options
1155: SET ALL_CURRENT_PLANNING_PERIOD = p_current_planning_period,
1156: record_version_number = record_version_number + 1
1157: WHERE FIN_PLAN_VERSION_ID = p_budget_version_id
1158: AND record_version_number = p_fp_rec_ver_num;