This page (revision-11) was last changed on 26-Nov-2021 10:22 by jmyers

This page was created on 26-Nov-2021 10:22 by jmyers

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
11 26-Nov-2021 10:22 2 KB jmyers to previous
10 26-Nov-2021 10:22 3 KB jmyers to previous | to last
9 26-Nov-2021 10:22 3 KB jmyers to previous | to last
8 26-Nov-2021 10:22 4 KB jmyers to previous | to last
7 26-Nov-2021 10:22 4 KB jmyers to previous | to last
6 26-Nov-2021 10:22 4 KB jmyers to previous | to last
5 26-Nov-2021 10:22 4 KB jmyers to previous | to last
4 26-Nov-2021 10:22 6 KB jmyers to previous | to last
3 26-Nov-2021 10:22 6 KB jmyers to previous | to last
2 26-Nov-2021 10:22 7 KB jmyers to previous | to last
1 26-Nov-2021 10:22 1 KB jmyers to last

Page References

Incoming links Outgoing links
RTTEP
RTTEP

Version management

Difference between version and

At line 8 added 121 lines
Project Objective
The overview should outline the business intent, purpose and scope of the project. (1-2 sentences)
The scope is to create a new report to report the scheduled time. Starting point is oracle RTTE report that will be adapted to eP evolution on this area. It will report shift pattern scheduled time.
Shift Calendar and Event Scheduling scheduled time report will be develop later on, if they are needed.
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 - EC20110628 – initial version the report for shift pattern scheduling
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
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 scope is to create a new report to report the scheduled time. Starting point is oracle RTTE report that will be adapted to eP evolution on this area. It will report shift pattern scheduled time.
Shift Calendar and Event Scheduling scheduled time report will be develop later on, if they are needed.
• Parameters
 Entity
- Entity for the report
 Starting Date
- Start Date of the time frame for report
 Ending Date
- End Date of the time frame for the report
 Print Off Days
- current version
o if it is the parameter set to yes will not make any difference on the scheduled time printed by the report
o if it is set to yes in addition "Print Only Exception" then the report will show only time entries that are not work time
- new version - Print only time entries associate with a leave line
Note: We added the Leave Type information in the main area. Please see new report layout example
 Print Only Exceptions
- Print only the time entries that are not work time type(05 on X_TIME_ENTRY_TYPE)
 Print Extra Clock Punches - to be renamed as Unprocessed Clock Punches for better reflection of what is printing
Note:
The information it will be printed only when the parameter is set to yes, and looks like green rounded area on new report layout example
 Print Missing Clock Punches -to be renamed as Print Clock Punches to reflect what is doing on RTTE
- new version layout to be changed to show in addition information Expected Punches Prediction like on W%TMCP
Note:
The information it will be printed only when the parameter is set to yes, and looks like blue rounded area on new report layout example
 New parameter Print Missing Punches to report the schedule/ unscheduled missing punches
- add new areas where o show summary by date of schedule/unscheduled missing punches similar W%MPTC
Scheduled
Unscheduled
Note:
The information it will be printed only when the parameter is set to yes and looks like red rounded area on new report layout example
The missing punch information it will be reported only for EE team post assignment
The job is displayed for unscheduled punches since this is the information that is driving the assignment
 Sort People By - removed
• Filters
 Print only Time Code - removed
 Work Division - only on shift pattern version
 Work Area - only on shift pattern version
 Work Station - only on shift pattern version
 Work Team - only on shift pattern version
• Layout change
 Current version
 New version
- Main area
• Move the date as the first column
• Sort by Start Time (IN)
• Add a non schedule time indicator( the time entries are not associated with a scheduled shift)
• Add a Leave Type on a main area
• After the EE name and assignment, the report will display the information about the rand, job and department of the station where EE is schedule to work
• Added Expected Punches prediction like on W%TMCP
• Exception column should not print Clock Punch exception
- Added an additional two areas to summarize by day Missing Punches Scheduled/Unscheduled like on W%TMCP screen
- For Shift Pattern the report to be group by Work Division, Area, Station, Team
 Example of the new report
Example
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).
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.
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 EC20110628 Initial Version
This page (revision-11) was last changed on 26-Nov-2021 10:22 by jmyersTop