!!!My Non-Predefined Matrix Time Cards
Project Objective
The overview should outline the business intent, purpose and scope of the project. (1-2 sentences)
 The project objective is to create a non-predefined "cost center matrix" timesheet. 
 
 
 
Project Iterations
An iteration is a deliverable outside of PD.  The goal of each iteration should be stated clearly.  This section should be updated to show the developer involved and the date completed.
1st Iteration - EC20100114 – initial version
2nd Iteration - ….
3rd Iteration - …
Related CCARE Cases/Defects
A list of the known CCARE Cases/Defects related to the project and any other background material that may be relevant and helpful.
Below is a list of the CCARE cases/defects related to this project:
Case	Defect	Cust	Pri	Status	Pgm	Problem / Enhancement
89050	43475					Q3692 Need customized Timesheet created
						

Requirements / Features
Outline the specific requirements and features that are being addressed, broken down by topic if the subject area is large.  These should be tied to the iterations using [2nd], [3rd], … at the beginning  if NOT in the initial iteration so that it is understood by all what will be done and when.

•	The EE needs ability to add / delete a matrix line.

Development Approach
This is an optional section to describe the steps the developer would go through in fulfilling the project goals.
1.	
Questions / Additional Notes
This section should contain questions that have been or need to be asked/answered so that the project can be completed.
1.	
Development Problems / Issues
Provide an outline of all problems, issues or challenges encountered while doing the development work (or anticipated up front).
•	For QA defect discovered working on this project that need to be fixed.
-	D#43599 -QA- Mandatory requirement for a column is not respected on a dialog -  WEPTTCM - Add Sundry Line(MPMSL)    
-	 D#43600  -QA-when you click on a matrix cell the amount is not highlighted 
-	D#43601 - QA- QA-Column Records Attributes are not respected on a matrix (EE should not be allowed to change a submitted TS)

Implementation
This section MUST be filled out by the developer.  It should provide an outline of any business or technical setup required, a list of all processing considerations, and a list of all functions involved in the setup and usage of the feature.
•	The screen has two tabs :
-	"Update May Time Card" where the EE will enter the time
-	"Totals" - that provides  different type of totals (time code, time code type, time code sets, and leave balance) 

•	On "Update May Time Card" are three major matrix areas :
-	Work Time  
All the time codes that has time type Regular, Excess, Overtime, and they are defined on assignment work rule
-	Leave Time
All the time codes that has leave policy type not null, and they are defined on assignment work rule
-	Sundries 
All the time codes that has time type Money, Meal Allowance, and they are defined on assignment work rule

       Note: 
If EE has, a holiday pay generated then at the end of leave area a non editable matrix shows when the holiday paid day is.
•	The matrix lines maybe added/deleted through dialogs, where EE needs to provide the combination for matrix line.
 When EE use Add dialog the system will create PTSE with that combination for each day on a time sheet period.
 When EE use Delete dialog the system will delete all the records in the time sheet for the combination provided.
•	After the lines are created, the EE can record the time / sundry as need it.
•	The dialogs that are used to add/delete  matrix line are:
-	MPMLL - Add/Delete Matrix Leave line
-	MPMSL - Add/Delete Matrix Sundry Line Dialog
-	MPMWL - Add/Delete Matrix Work Line Dialog

Notes: 
-	The time codes that are allowed to be choose in the dialog follow the same rules as describe earlier  for each matrix area
-	The cost centers allowed on a dialog are the one that are allow by assignment department. Please see on IDDP Allow Cost Centers tab
-	The dialogs are not configurable in IMFDH without changing the code in the ear, they contain special logic for adding/deleting PTSE records. 
•	For the EE that will use this screen  UEGTS should generated only the header and if need it the holiday paid
•	Since we do not generate details, auto balancing logic is not available for this type of time sheet.
•	This screen it designs for 7 days timesheet. If this need to support 14 timesheet  the form definition need to be changed as follow, on form layout tab for any group that has layout type "Matrix Columns"  need to changed "SS Rows Displayed" form 7 to 14 this number should be the same as timesheet time frame.
•	Excepting matrix cell, any information on matrix area should be display only.
•	The grid information alignment is depending on information display on each area they belong (work, leave, sundries) so their alignment in a form would be approximate. 
•	First column in a matrix area should have all the time value because in other away the info can be shifted so information will not display in a correct place.(e.g. Cost center cannot be the first column in the work area since this is not a mandatory information and can be null).

Resources Released
This does not need to include java classes but should include icons, style changes and documents.

Quality Assurance
Note the QA person, date, feature QA’d and any comments or set up notes along with the severity or urgency of the issue.  Please do not repeat the whole Requirements / Features section here.  Include where you were working, the test case and all steps required to reproduce the issue [if needed].

Document Revision History
Identifies each document version and who made the change and when.
Version	Author/Date	Description
1.00	EC20100114	Initial Version