Sap Fico -- Go Live Detailed Cutover Activities

1.SAP FICO -- GO LIVE DETAILED CUTOVER ACTIVITIES 2015 Overview. Create or identify a separate document type for initial balances upload and maintain a different number range for the same and use the same document type for uploads. This will be usefull for identifying the transactions posted before go live and after go live. Create two new GL accounts in Production for the Purpose of initial balances upload. One for Initial Stock Upload and another for the GL balance. Open only the current period of posting or the legacy date period in which you are posting in OB52 and close all other periods. Similarly use OKP1 for CO period lock. Do not open MM period after the legacy period at the time if initial stock uploads and get the same be opened by the core team member responsible for opening after completion of your upload activities. This will prevent erroneous posting to the next period due to the wrong dates given in the upload file. Create a New Field Status group with mostof organizations elements selected as optional. Make sure that if profit center is mandatory it needs to be mandatory only and do not change it to optional, as the LSMW screendoesn’t popup the profit center filed if the same is optional. FI G L master data will be uploaded via LSMW.(Recording for LSMW FS00 & also keep the changing master data recording handy) FI VendorMaster Data will be uploaded without purchasing organization Views (Recording forLSMW FK01 & also keep the changing master data recording handy. Your field status group settings configured for your client). If you are having EWT codes thenyour recording cannot take more than 6 line items. If you need to have more than 6 line items in tax type/tax code areas look for other alternatives. If vendors are relevant to EWT then advised to create a separate group making the tax fields mandatory. At the time of uploading the vendor master data into productionmake sure you change the FSG to optional on tax items and do not give any tax codes. FI CustomerMaster Data will be uploaded without sales Views Recording forLSMW FD01 & also keep the changing the master data recording handy. Keep in mind your filed status group settings configured for your client. All legacy asset master Data (AS91)along with the values will be uploaded with Cost Center/Location (Again keep in mind the master data screenfiled settings before recording and your client’s requirement). Write differentrecordings forSLM keys and WDV keys). For legacy assetdata transfer record transaction types for the assets acquired during the financial year in a separate recording.For the assets acquired before the start of the fiscalyear you need to ask the client accumulated depreciationas on start of the fiscal year and depreciationposted during the period or after the start of the fiscal year (Again depends on the configuration on how you are posting the depreciationto GL) All the G L balances of account type “S” and are non-open item managed need to be uploaded G L wise-Profitcenter wise Via LSMW as on the cutover date. Make sure that no two profitcenters were uploaded in the same documentbecause,if you have activated document splitting the number of line items generated at the time of saving the documentdue to split may exceed 950 line items and the system will throw you out of uploading. Even if it is not the case advised to upload data related to a profit center per document. All the G L balances of account type “S” and are open item managed need to be uploaded G L Wise- Item Wise -Profitcenter wise Via LSMW.Make sure that no two profit centers were uploaded in the same documentbecause,if you have activated document splitting the number of line items generated at the time of saving the documentmay exceed 950 line items and the system will throw you out of uploading. All the Customeropen items need to be uploaded Profit center wise. Make sure that no two profit centers were uploaded in the same documentbecause,if you have activated documentsplitting the number of line items generated at the time of saving the documentmay exceed 950 line items and the system will throw you out of uploading. All the Vendor openitems need to be uploaded Profitcenter wise. Make sure that no two profitcenters were uploaded in the same document because,if you have activated documentsplitting the number of line items generated at the time of saving the documentmay exceed 950 line items and the system will throw you out of uploading. 1. 2. SAP FICO -- GO LIVE DETAILED CUTOVER ACTIVITIES 2015 Copy Rights © SourceOne Management Services Pvt. Ltd & DoctorSAP Bangalore Pramila Nagaraj MBA FIN-2010 VTU SAP FI Associate Certified FreshOff Campus Candidate @ Source One Management Services Pvt. LtdBangalore You need to use direct input program in LSMW for transaction data upload and selectfinancial documents as object. All the Assetdata need to be identified depreciationarea wise with Assetclass and Depreciationkeys. For tax balance sheet Assetclass wise Gross block, accumulated depreciationand net block need to be uploaded (AS81). For Customers/Vendorsrelevant to Sales/Purchasing views take care to give properrecon accounts keeping in view of the alternate recon accounts if any applicable. Make sure you only extend customers/vendorsto other company codes.Other wise creation of vendors/customers will create a duplicate data. Educate the core user to tally the data before giving the same to you via Excel. Make sure that the Basis guy is available to you at the time of upload to handle transports, which were created during the upload for the purpose of upload or for any error in configuration. 2. Time Lines Depending on the amount of data, take sufficienttime for upload activities. In case the assetmasters/data is not ready still you SequenceOf Data Conversion • G L master Data • Vendor Master Data • Customer Master Data • Group AssetData • GL balances without open Item managed • GL balances with open Item managed • Customer Balances • Vendor Balances • Customer Balances with SpecialGLs • Vendor Balances with Special GLs • AssetMasters with Values for the assets existing at the start of the fiscal year • AssetMasters with Values for the assets acquired during the fiscal year with transaction type. 11) Again you need to keep in mind the configurations you made for the client with respectto account types. line items of customer/vendorshould be profit center wise.as expected and planned depreciations to be posted are accurate.This is necessarybecause if your upload items contain any balances and the tax codes are assigned the system will calculate EWT and tries to postthe same. which is not the case. All transactions starting after go live will be processedin SAP system only. no transaction should be performedin legacy system 3.GO LIVE DETAILED CUTOVER ACTIVITIES 2015 Copy Rights © SourceOne Management Services Pvt. This is because if you have large amounts of data.2007 need to be entered through AS91 via Transaction type 100 assuming your clients financial year is Apr-Mar and the cutover date is 31. Load handful of assets in a Quality or in Pre-productionsystem depending on your landscape to ensure that the system is calculating the depreciation.04.then the system will prompt you to press enter every time a GL account is encountered as the filed values payment terms is not relevant for account type S.Direct Input CustomerBalances LSMW/DirectInput 0000 RFBIBL00 D.Posting. TRANSACTIONDATA GL Balances of account type S which are non open Item based LSMW/Direct Input 0000 RFBIBL00 D.GO LIVE DETAILED CUTOVER ACTIVITIES 2015 Copy Rights © SourceOne Management Services Pvt. compare data and reset recon accounts.01. 3.2. D & K. 12) If the client’s need is to have the old balances also on age wise for Payables & Receivables.2006 and before 31. You need to revert the settings of master data for accounts with Auto posting. After Go live.Direct Input VendorBalances LSMW/DirectInput 0000 RFBIBL00 D. Processeshave been freezed.04.2006need to entered through AS91 and Assets acquired after 01. 7) For reconciliation accounts.Direct Input AssetBalances LSMW Regular Recording AS91 AS81 AUC Balances LSMW/DirectInput 0000 RFBIBL00 D.you need to play with. Authorization Matrix completed. 9) Assets acquired before 01. SAP FICO -. LtdBangalore 15) Before start of . 2) Delete costelements if created already in production. Prerequisitesto Load MasterData Client Setup and Number range maintenance. Ltd & DoctorSAP Bangalore Pramila Nagaraj MBA FIN-2010 VTU SAP FI Associate Certified FreshOff Campus Candidate @ Source One Management Services Pvt. 13) Make sure that the discount base column is given value for a smoothupload for Receivables and Payables.Procedure for Cut Over 1) Check again if the documentsplitting is active and in case new GL accounts are added by the users. as the legacy data is not relevant for cost centers. SAP FICO -. End user training and documentationis completed G L Master LSMW Regular Recording FS00 FI VendorMaster Data LSMW Regular Recording FK01 FI CustomerMaster Data LSMW Regular Recording FD01 Assetmaster Data LSMW Regular Recording AS91 together with values AS81 Group AssetMaster Data LSMW Regular Recording AS21 Cost Elements LSMW Regular Recording KA01 You can also create by batch input session VIA SPRO Cost Centers LSMW Regular Recording KS01 Profit centers LSMW Regular Recording KE51 Internal Orders LSMW Regular Recording KO01 Characteristics Manual Creation 5. If not do and transport before you start. via LSMW or T-code MASS. In such case the system will take great amount of time for uploading. you should convince the client saying where he wants to settle the costcenter balances after go live? Exceptionto the above is AUC.Accounts with relevance to tax categoryand postwith out tax allowed before upload. 4. For Example Payment terms. then if you club all the account types into one recording. Pre-requisite or Assumptions Scenario and Integration Testing are completed. the assignments for documentsplitting characteristics is made or not.01. • It is advised to load assetdata along with values instead of loading master first and giving values next.DirectInput 3. Cleansed and Validated Master Data made available. 7. 4) Remove Withholding tax code assignments to vendors. D&K. 6) For openitem managed accounts provide with the totals as on the cutover date profit center wise. and base line dates to achieve this via upload. 5) For Nonopen item managed accounts provide with the totals as on the cutover date profit center wise. 14) You need to use separate Direct Input recordings with object 100 and method 0000 (RFBIBL00) for account types S. Go-live date will be (Give the Go live date). At least test once the LSMW recordings beforemoving into productionabout the reliability and for errors. LtdBangalore 6. can go ahead with GL balance upload and assets can be done at a later date.2007. 8. 3) Assignthe field status group to all the G L accounts created for the purpose of upload of initial balances. Ltd & DoctorSAP Bangalore Pramila Nagaraj MBA FIN-2010 VTU SAP FI Associate Certified FreshOff Campus Candidate @ Source One Management Services Pvt. Even of the client insists. document. 10) Make sure you have created group assets via AS21 if you are using Group assets in tax depreciationarea. 8) For assets reset the reconciliation accounts load assets. 13) It is the same case with stock uploads. take the signoff and blockthe accounts for posting in future.OKP1 & MMPV by the core team member and close all the legacy periods. Theoretical Steps Declaration:This Project is a Live Hands on ImplementationProgramERP6.7EE or ERP 2004 without New GL getting activated. 17) For loading AUC values VIA Internal orders.Other wise the system will throw an error. . The sequence of steps may change slightly depending on your customization and modules implemented and hence this can be taken as a guide line only and not as a comprehensive document. ProcedureAfter Cut Over data Upload 1) Resetthe filed status groups. postauto settings. 16) After uploading the same again resetthe reconaccounts. 5) Settle the AUC balances and make the Internal order values to zero. create cost elements. 11) If you are in Version4. 7) Revert all FSG changes for CUSTOMER/VENDOR/GLto the requirement.Keep in mind that the non-leading ledgers are not relevant for account types. 6) Assignvendors with the relevant tax codes and post processthe open items as per the warning given by system for making the tax lines consistent. 8) Delete the number range assignments to the documenttype created for initial balance upload and transport so that to minimize the core user transactions in the legacy period. the reason could only be the Qty mismatch or the system has taken the MAP defined in the material master. Use in both the cases T-code OAMK to reset the recon accounts.uploading assetline items at GL level make sure is client is open for change and reset the recon accounts for assets. This document is for New Implementations ON New GL only and not for upgrades. F. as the recon accounts are not directly posted to. Reverse the documentor just pass a rectification entry. 12) After all of the above precautions still you find that there is a mistake whether small or big don’t be panic. 4) Resetthe VendorFSG settings and other relevant settings changed for the initial balances upload.create Internal orders.think what should have been went wrong. 1KEK. go back to your domain experience. settle the orders to the AUC asset via KO88 before the go-live 9.5D. 10) Any new master records created between Cutover and Go live dates are to be tracked and checked for documentsplitting assignments. 2) Once the initial balance accounts balances are zero.5E. Make sure you use periodic settlementand not FULL. Startedafter taking inputs from my Project Manager.after the above uploads are through. Afteryour MM counterpart loading the stocks and you verify and stocks are not getting matched. keep in mind you need to run F.0 SAP FICO.Tax settings to the original file given by the core user via MASS or LSMW. 3) Get the next relevant posting periods openedin OB52.upload values through the internal orderto AUC expenses accountand once upload is through. 9) If you are using the parallel ledgers as of ERP 2004 or ERP 2005 make sure you load the balances of nonleading ledgers first.