1. We need to compare the changes that Sri will do today in UAT and compare them .. 2.

The remove_strange_character code has to be put across all the procurement mo dules 3. Need to followup with Sukhada on the daily process chain/weekly process chain 4. On OTD.. need to add those restrictions characteristics that Belkis has reque sted. 5. All the WAD reports for OTD need to be reviewed and moved to quality. 6. All the OTD queries and BI objects and ECC objects need to reviewed and moved to quality. 7. The role for OTD has to be created and mapped to the iview and then .EPA file has to be created. 8. THe process chain for OTD has to be moved into Quality and we need to run the chain once..in Q. 9. The process chain for procurement has to be moved into quality. 10. For the WAD, the RRI has to be separately created by using template to templ ate option. 11.

Indira 1. On the line item query , there is a customer exit variable, rename it to " do cument date" and do it as mandatory. 1a. For the procurement wad's, the RRI has to be separately created by using tem plate to template interface option in tcode rsbbs. 2. On OTD all those characteristic restrictions to be applied on summary reports , I think we overlooked Belkis email. 3. The role for OTD has to be created and all the 10 WAD reports to be mapped t o the iview and then the .EPA file and role has to be transported to quality. - for any issues we wi ll ask Alpana to help. 4. Analyze/investigate on why the RRI jump is not popping for the variable input screen.

Kiran 1.The remove_strange_character code to be put across all the procurement and otd transformations and moved to Q, we need to be extra careful, I suggest take a copy of existing IObjects in BD1. 2. For the customer exit , copy the code from Q, comment it, include our new cod e and transport it to Q. Let the existing functionality break, I have a GO from Sri. 3. Lets review the tech specs of routines, i hope you have all the routines of p rocurement/otd inplace.

Archana 1. All the OTD ECC, BI, 10 queries, Process chains have to be moved to Quality a nd loaded with the data via the process chain. 2. According to Sri the OTD/OTS will run daily, so in that case will ask Sukhada to make the changes to her chain accordingly. 3. Continue to work on the OTD/OTS functional/technal specs.- Pls complete by EO D. Suhas 1. 2LIS_02_SCL enhancement - review the email sent by Sri.

2. The process chain for procurement has to be moved into quality and lets do a test run. 3. the fun/tech specs for procurement has to be completed. - Pls complete by EOD . 4. Similar to OTD, lets analyze the Inventory(03_BX,03_BF,03_UM) estimation in p roduction, compare the data with Quality. we need this by Thursday. 5. Reconcile the existing inventory reports in prod (BP1) with P03 (ecc). - take the inputs from Indira , she started a bit on this.

All, Let's review the attached draft rollout plan sometime in the afternoon. Regards, Prashant M J 03/08/11 Suhas 1. Continue to run the process chain for procurement , both in D and Q..(run sim ultaneously). Please note, we will not disturb the existing data, just we will test the deltas . 2. Similar to OTD, lets analyze the Inventory(03_BX,03_BF,03_UM) estimation in p roduction, compare the data with Quality. we need this by Thursday. 3. Reconcile the existing inventory reports in prod (BP1) with P03 (ecc). - take the inputs from Indira , she started a bit on this. Archana 1. The PC from D to Q hasnt gone fine, pls look into it.Once done, let Indira te st the process chain. 2. ECC transports for Procurement/OTD from Q to P03 . 3. Start bundling the transports of OTD BI objects in Q. get ready for Q to P03 . 4. Continue to work on the OTD/OTS functional/technical specs 5. Need to followup with Sukhada on the daily process chain/weekly process chain Indira1. for the template to template rri, try in RSBBS,with option from Query to a te mplate. 2. update the Bex User guide with the OTD/OTS screens.(I will send the attachmen t in a separate email). 3. Execute the process chain for OTD , both in D and Q. Please note, we will not disturb the existing data, just we will test the deltas. 4. Analyze/investigate on why the RRI jump is not popping for the variable inpu t screen. 5. Review the Iviews and Roles. Send a email to Basis to Transport the Iviews, R oles from BD1 to BQ1. Kiran 1. Work with Archana on the oTD/procurement transports to ECC. 2. Analyze the production environment (BP1),P03 to look out for any existing fun ction modules/customer exits.

3. Get the list of WAD's from Indira and transport them to Q.

04/08/11