DBA Data[Home] [Help]

PACKAGE: APPS.GMS_AWARDS_BOUNDARY_DATES_CHK

Source


1 PACKAGE GMS_AWARDS_BOUNDARY_DATES_CHK AUTHID CURRENT_USER AS
2 -- $Header: gmsawvds.pls 120.1 2005/09/02 02:47:25 appldev ship $
3 
4   Procedure validate_start_date( P_AWARD_ID    	IN    NUMBER,
5                         	 P_START_DATE   IN    DATE ,
6 				 X_MESSAGE      OUT   NOCOPY VARCHAR2);
7 
8   Procedure validate_end_date	( P_AWARD_ID   	IN    NUMBER,
9                         	 P_END_DATE     IN    DATE ,
10 				 X_MESSAGE      OUT   NOCOPY VARCHAR2);
11 
12 -- Added for Bug: 2269791 (CHANGING INSTALLMENT DATE WHEN BASELINED BUDGET EXISTS)
13   Procedure validate_installment ( x_award_id IN NUMBER);
14 
15   -- The following procedure validates the change in project start date to see if any transactions
16   -- exist outside the modified date.
17 
18   Procedure validate_proj_start_date( P_PROJECT_ID    	IN    NUMBER,
19                         	      P_START_DATE      IN    DATE ,
20 				      X_MESSAGE         OUT   NOCOPY VARCHAR2,
21 				      P_TASK_ID         IN    PA_TASKS.TASK_ID%TYPE DEFAULT NULL);  /* Bug# 4138033 */
22 
23   Procedure validate_proj_completion_date( P_PROJECT_ID   	 IN    NUMBER,
24                         	           P_COMPLETION_DATE     IN    DATE ,
25 				           X_MESSAGE             OUT   NOCOPY VARCHAR2,
26 					   P_TASK_ID             IN    PA_TASKS.TASK_ID%TYPE DEFAULT NULL);  /* Bug# 4138033 */
27 
28 
29 END;