Page History

...

1. Unit Test Schedule? - SF3 Upgrade will not complete until this evening & SF2 by tomorrow evening or Wednesday morning. - Impact?
   •  Update to SF3 should be completed tonight by 10:00pm.
   • SPAU - generate tonight. 
   • Tomorrow am.  Rich K. will apply SAP notes. Should take 2hrs
     • When can SPAU & action log activities begin? - Other prep. activities? (interfaces, queued data files, etc.)
       • Mods and SPAU also will start Tuesday a.m. and complete by 3:00 pm 
     • How many days are required for UNIT test / from where in the plan do we subtract the time?
       • The project plan's schedule can not be changed. We must complete unit testing by Monday 11/9.
       • SF2 will be available for testing on Wednesday by aproximatly 11:00 am
2. Unit test execution SF2
   • SF3 was offered as an alternative environment to begin unit testing however the prep.(i.e. authorizations), results logging, and issue resolution were reasons to keep unit testing confined to one system.
   • SF2 update should be completed by late Tuesday or early Wednesday (8:00 a.m.)
   • A Check-in with the core team is scheduled for Tuesday at 3:00 to confirm we are on track.
   •  Wednesday a.m. activites for SF2:
     •  Transports from SPAU work, BSI transports ~1hr#* **{*}The action log will be executed (1 - 2hrs)*
     •  Unit test start - 11am Wednesday (original scheduled to start Tue 8am - planned duration was 5 days has now been cut to 3 days)
       • Consolidated list will be split up by teams.  Each team will update their spreadsheet with Pass/Fail Results
       • Daily updates required - If updated spreadsheets can not be posted to the Wiki daily, a percentage complete should be communicated to the PM and the end of each day. Core team check-in meetings are scheduled for 3:00 PM. on Wed., Thur., & Fri this week. The plan is to test on Saturday unless status for each group is on target to completed on time without weekend testing.
       • Issues/Errors must be logged in the SAP:: Test Issues queue, email = saptest@help.mit.edu.
       • The spreadsheets will be the official test log - Results (pass/fail) and testers name must be filled in for completion of this test phase
3. Time Sheets
   • There is a steering committee mtg this Wednesday
   • We need to stay current with our time allocated to this project
   • confirm that SAIS project team members have project related tasks assigned in Daptive
4. Testers
   • SAIS should have their same authorizations in SF2. Let, Ken know if there are additional authorizations needed.
   • We are looking for the complete list of business testers for UAT and the names of those who would need to be unlocked for SIT.
5. December 24th Institute holiday - was to be the 1st day for resuming normal transports. Can this change to the 23rd?
   •  Freeze will be lifted 12/29 due to institute closing on 12/24. Payroll pension 12/22, Weekly is 12/22 & Monthly 12/23 we will consider transports for the 22nd only if there is a pressing reason.

...

1. Unit Testing
   • Status?
   • Issues - Have all issues been logged? Count = 10? Can we catagorize and update status?
   • Transports? Are we okay to use zutreq?
2. SH2 Status - Updates should complete by 9pm tonight 11/9
   • Post upgrade steps (Application Server Updates, ABAP load generations, Database actions, etc.) scheduled for when? completed by?
   • Warehouse Extracts - Tuesday morning estimated schedule?
   • Evaluation of time requirements for scheduling production updates -
3. SIT - Schedule (was 11/10 - 11/22/09)
   • Preparation activitities Preparation activitities
   • Initial testing and environment set-up - What tasks should be scheduled for 11/10?
   • List of users to be unlocked unlocked
   • Test Case Catalogues and Results logging
4. Action Log Update - tasks required for refreshed system v. non-refreshed

November  12, 2009 SAPbiz

• Background
  • Why do we do this?  - Because we have need to!
  • Lessons learned
  • What's new?
• Progress to date:
  • SF2 Development Environment Support & Enhancement Packs were applied and pre-processing steps completed on 11/5/09
  • Unit Testing completed on 11/7/09
  •  
• Schedule

  November 2009
  Sunday	Monday	Tuesday	Wednesday	Thursday	Friday	Saturday
  1	2SF2 UNIT TEST	3SF2 UNIT TEST	4SF2 UNIT TEST	5SF2 UNIT TEST	6SF2 UNIT TEST	7SF2 UNIT TEST
  8	9SIT	10SH2 - Warehouse Extract - Trial balance	11HOLIDAY	12SH2 SIT	13SH2 SIT	14
  15	16 SH2 SIT	17SH2 SIT	18SH2 SIT	19SH2 SIT	20SH2 SIT	21
  22	23UAT	24UAT	25UAT	26HOLIDAY	27HOLIDAY	28
  29	30UAT
  December 2009
  Sunday	Monday	Tuesday	Wednesday	Thursday	Friday	Saturday
  		1UAT	2UAT	3UAT	4UAT	5
  6	7UAT	8UAT	9UAT	10Go / No Go	11PS1 DOWN AT 6PM	12
  13	14PS1 UP AT ???	15	16	17	18	19
  20	21	22	23	24HOLIDAY	25HOLIDAY	26
  27	28SH2 OPEN FOR GENERAL TESTING	29	30	31HOLIDAY

November  16, 2009 Core Team

...