+ All Categories
Home > Documents > Committed to building Qatar - Qatari · PDF fileCommitted to building Qatar ... The capacity...

Committed to building Qatar - Qatari · PDF fileCommitted to building Qatar ... The capacity...

Date post: 10-Mar-2018
Category:
Upload: trinhhanh
View: 223 times
Download: 0 times
Share this document with a friend
2
Committed to building Qatar Issue 5 June–2012 1– End User Trainings: 1.1 Role based EU Trainings were conducted from 11th June to 21st June for all funcons: FICO Module :for Users at HO; PP,QM,PM Modules :for users at plant ; MM Module : for users at QSS/ITT office and plant ; SD Module: for users at Toyota tower, plant (logiscs) And QSS/ITT . 1.2. User IDs were created for users , Roles have been created in SAP for users to pracce as per their authorizaons in SAP . 1.3 . Hands on sessions were also held for all users to prepare for Go-Live 2– Go Live Cut-Over Strategy/Planning 2.1 Cutover is an acvity where in a date line is drawn where the transacons in the legacy system are stopped and the values are uploaded into SAP system. 2.2 All the transaconal data is moved in to SAP like open purchase orders, open sales orders, customer and vendor invoice items and stock balance. 2.3 It helps the business to cleanse the data and ensure the correct and accurate data is moved to SAP. 2.4 Cut-over involves following three steps: Data Extracon from legacy system. Conversion of Data in SAP Format/template . Key dates for Cut-Over A.Cut over to the SAP system will be 30-June-2012 I. Closing Balances as of 30st June 2012 (i.e Opening as of 1st July 2012) will be considered as the Cut-Over Balances of SAP system. II.Cut-over Balances includes physical inventory as of 30th June 2012 and all “open Items” like AR, AP III. “Switch Over” will happen aſter Cut– Over Balances (of 30th June 2012) are uploaded and verified in SAP. B. It is expected that the complete verified Cut-over Balances will be available on 9 July 2012 for upload in SAP System I. Transions for the period July 1st-9th will be entered in SAP System from 10th July onwards. II. To ensure quick clearing of the backlog (of transacons data From July 1st-9th ), it is imperave that : Suitable strategies are adopted to reduce the number of Transacons In the period; for example : make issues for a week In advance ; Raise PRs/POs in advance or defer the same aſter 10 July ; SAP Project Update 3– SAP Support Desk The support services model comprises for the following levels in QIG: 3.1 Level-1 support: will be provided by QIG Power users who will be the first point of contract for the End users; this may Involve training End User . 3.2 Level-2 support: Issues unresolved by power Users will be handled by AH IT Team. 3.3 Level-3 Support : QIG IT will escalate crical issues to Fujitsu support Team 3.4 Level-4 Support : all complex issues , including enhancement etc. , will be escalated to the Regional SAP Support Desk via Soluon Manager 3– Master Data Verificaon Master Data which was compiled earlier was uploaded in SAP test system. This data, in turn , has been downloaded from SAP test system (‘dump’) and provided to business for verificaon. Monthly steering commiee meeng Page 1
Transcript

Committed to building Qatar

Issue 5 June–2012

1– End User Trainings: 1.1 Role based EU Trainings were conducted from 11th June to 21st June for all functions: FICO Module :for Users at HO; PP,QM,PM Modules :for users at plant ; MM Module : for users at QSS/ITT office and plant ; SD Module: for users at Toyota tower, plant (logistics) And QSS/ITT . 1.2. User IDs were created for users , Roles have been created in SAP for users to practice as per their authorizations in SAP . 1.3 . Hands on sessions were also held for all users to prepare for Go-Live

2– Go Live Cut-Over Strategy/Planning 2.1 Cutover is an activity where in a date line is drawn where the transactions in the legacy system are stopped and the values are uploaded into SAP system. 2.2 All the transactional data is moved in to SAP like open purchase orders, open sales orders, customer and vendor invoice items and stock balance. 2.3 It helps the business to cleanse the data and ensure the correct and accurate data is moved to SAP. 2.4 Cut-over involves following three steps: Data Extraction from legacy system. Conversion of Data in SAP Format/template .

Key dates for Cut-Over A.Cut over to the SAP system will be 30-June-2012 I. Closing Balances as of 30st June 2012 (i.e Opening as of 1st July 2012) will be considered as the Cut-Over Balances of SAP system. II.Cut-over Balances includes physical inventory as of 30th June 2012 and all “open Items” like AR, AP III. “Switch Over” will happen after Cut– Over Balances (of 30th June 2012) are uploaded and verified in SAP. B. It is expected that the complete verified Cut-over Balances will be available on 9 July 2012 for upload in SAP System I. Transitions for the period July 1st-9th will be entered in SAP System from 10th July onwards. II. To ensure quick clearing of the backlog (of transactions data From July 1st-9th ), it is imperative that : Suitable strategies are adopted to reduce the number of Transactions In the period; for example : make issues for a week In advance ; Raise PRs/POs in advance or defer the same after 10 July ;

SAP Project Update

3– SAP Support Desk The support services model comprises for the following levels in QIG: 3.1 Level-1 support: will be provided by QIG Power users who will be the first point of contract for the End users; this may Involve training End User . 3.2 Level-2 support: Issues unresolved by power Users will be handled by AH IT Team. 3.3 Level-3 Support : QIG IT will escalate critical issues to Fujitsu support Team 3.4 Level-4 Support : all complex issues , including enhancement etc. , will be escalated to the Regional SAP Support Desk via Solution Manager 3– Master Data Verification Master Data which was compiled earlier was uploaded in SAP test system. This data, in turn , has been downloaded from SAP test system (‘dump’) and provided to business for verification.

Monthly steering committee meeting

Page 1

Committed to building Qatar

Issue 5 June–2012

Learning SAPanese – Lesson 4 SAP MM is the materials management module that is used for Procurement Handling and Inventory Management. Materials management is integrated with other modules such as SD, PP and QM. Materials management is used for procurement and inventory management. The module has two important master data - material and vendor. Broadly, the various levels that can be defined for a SAP MM implementation are: Client, Company Code, Plant, Storage Location and Purchase Organization. SAP Materials management covers all tasks within the supply chain, including consumption-based planning, planning, vendor evaluation and invoice verification. It also includes inventory and warehouse management to manage stock until usage dictates the cycle should begin again. SAP MM is all about managing the materials i.e the resources of an organization. These resources include man, manpower and materials. The main functionality within MM includes purchasing, Inventory management, valuation and assignment, batch management and classification Learning SAPanese – Lesson 5 The Production Planning module of SAP takes care of Master data needed like Bill Of Materials, Routings and Work Centers and stores it in one separate component. Various stages of the planning system can be planned by using components like Sales and Operation Planning Long Term Planning Demand Management Materials Requirement Planning

SAP PP module can also plan Capacity. The capacity Planning sub-module takes into account various capacities like pooled capacity etc. Production Orders reporting has flexibility of confirming orders The material can be staged to production site from the Warehouse after releasing the order. Costing can be triggered automatically by integrating the module with the Cost Accounting Module. Learning SAPanese – Lesson 6 Plant Maintenance operates the overall maintenance business processes and functions. The Plant Maintenance module allows a maintenance organization to: Identify, document, and correct failures and degradations of any assets for which they have responsibility.

Plan and schedule activities to prevent or predict failures and keep assets and processes operating within design specifications

Page 2


Recommended