FI Cutover ActivitiesThis question has beenAnswered.

Reena LambaSep 2, 2008 5:27 AMHello Experts,Can someone give me the steps/sequence of FI cutover activities. We will be going live soon. I just want to be prepared for the turnaround.I know its a big topic but just outline should be helpful.Thanks,Reena.

Correct AnswerbyANONYMOUS ANONYMOUSonSep 2, 2008 7:07 AMHii Reema..Some of the cutover activities are..1. G/L Master Upload Thru BDC or LSMW (TC-Fs00 and extended one co code to another company code Fs01)2. Vendor Master Upload Thru BDC Or LSMW (Will be Taken Care By MM)3. Customer Master Upload Thru BDC or LSMW (Will be Taken Care By SD)4. Asset Master Upload(Thru As90)5. Cost Element Master Upload6. Cost Center Master Upload7. Profit Center Master Upload8. G/L Balances Thru F-0210. Vendor Balances thru F-4311. Customer Balances thru F-2212. Customer Advances thru f-2913. Vendor Advances thryu F-48Before uploading Vendor Balances you have to take care of WHT(TDS) Information.Regards,AakashSee the answer in context 5267Views Average User Rating(0 ratings) Re: FI Cutover Activities

ramakrishna raoSep 2, 2008 5:57 AM(in response to Reena Lamba)Hi Reena, FI Cutovers activites are uploading master data through LSMW or BDC, Transport the configuration settings using T.Code: SE09 or SE10 and the uploading the Transaction data by bring to closing balances.By!R.K Alert Moderator Like(0) Re: FI Cutover Activities

Venkat KrishnaSep 2, 2008 6:35 AM(in response to Reena Lamba)Hello Reena,Cutover activities the name itself tells you cut the business data ex: legacy transactions are stopped from today onwards means today is cut date and will take all balances as on todays date and upload into sap system by using LSMW, BDC, Ecatt etc., It is part of final preparation at 4th phase in the ASAP methodology. That includes upload the balances, sign off from end user, user acceptance test etc.,Financial Accounting:The following account numbers will be used for the takeover of the opening data:Open balance assets Initial stock uploadsOpen balance GLOpen balance of ReceivablesOpen balance of PayablesTrial Balance:-1.The certified trial balance as on will be taken over in the SAP system.2.It may be noted that this trial balance needs to be broken down profit center wise for the balance sheet accounts and cost center & profit center wise for the revenue accounts (Profit & Loss Accounts)3.The Balance sheet items excluding AR/AP/FA will be taken as the closing balance, whereas, open line item will be taken for AR/AP/FA u2013 respective sub-ledger wise. AR/AP line items will compulsory have payment terms. CWIP will be uploaded asset wise. So CWIP accounts will be broken up accordingly.Accounting Entries while data upload:1.Inventory Takeover:When inventory will be uploaded, following entry will be generated by the system depending upon the valuation class specified in the material master.Inventory Accountu2026u2026u2026u2026.DrTo Initial stock upload account2.Receivable Takeover:Account Receivables will be uploaded customer wise and only the open items will be taken over to new system. At the time of upload following entry will be generated.Customer Account (with actual reconciliation account DrTo Opening balance u2013 account receivables3.Payable Takeover:Account Payables will be uploaded vendor wise and only the open items will be taken over to new system. At the time of upload following entry will be generated.Vendor Account DrTo Open Balance u2013 Account payables4.Asset Takeover:The asset balances will be uploaded asset wise. This will not create any accounting entries initially and asset balances will be loaded.In case of Accounts Receivable, Accounts Payable, and Assets, it should be ensured that the sub ledger balances are tallying with the general ledger.5.Other GL Takeover:All the GL Accounts (other than above) will be taken over by debiting / crediting to the account code (open balance GL)The closing balance of balance sheet accounts will be taken over and the profit and loss accounts will be taken cost center wise.At the end of the data takeover exercise, all takeover accounts together shall show a u2018zerou2019 balance. These accounts shall be blocked for posting after the data take on activity.GR/IR account:It would be ideal to ensure that all invoices relating to goods received be booked in the legacy system before the cut off date. Alternatively, all provisions made in the legacy system relating to goods received but invoices not received will have to be adjusted against corresponding vendor invoices received after the go-live date. In case of invoices relating to goods that have been received before the go-live date, the following entry shall be passed in the production system:Corresponding Provision Accountu2026u2026u2026u2026u2026u2026..DrTo Vendor AccountThe invoice for such receipts shall be passed using the FI invoice booking transaction and not through Materials Management. The verification of the invoice shall be manual.Apart from the above-mentioned data, the budget data for Cost center and Profit center also needs to be uploaded into the SAP system.ThanksPara Alert Moderator Like(0) Correct AnswerRe: FI Cutover Activities

GuestSep 2, 2008 7:07 AM(in response to Reena Lamba)Hii Reema..Some of the cutover activities are..1. G/L Master Upload Thru BDC or LSMW (TC-Fs00 and extended one co code to another company code Fs01)2. Vendor Master Upload Thru BDC Or LSMW (Will be Taken Care By MM)3. Customer Master Upload Thru BDC or LSMW (Will be Taken Care By SD)4. Asset Master Upload(Thru As90)5. Cost Element Master Upload6. Cost Center Master Upload7. Profit Center Master Upload8. G/L Balances Thru F-0210. Vendor Balances thru F-4311. Customer Balances thru F-2212. Customer Advances thru f-2913. Vendor Advances thryu F-48Before uploading Vendor Balances you have to take care of WHT(TDS) Information.Regards,Aakash Like(0) Re: FI Cutover Activities

NateshKumar ValmikiSep 2, 2008 7:58 AM(in response to Reena Lamba)Cutover Activities or strategirs are used transfered from legacy system to sap system at this point of time billing wil stoped all open orders contract pricing data wil transefer as per the cut over plan which is provided by implementation partnerFICO go-live detailed cutover activitiesThis question isAssumed Answered.

Sunny BMay 11, 2008 1:48 AMHi Gurus,Would appreciate if someone can send me a detailed list of go-live cutover activities that a FICO consultant has to do.For example: How do we handle the G/L accounts? Do I just create them in production or transport them?How do I get the end of books entry from the legacy system to the production system? Do I pass a manual journal entry?Please advise 6626Views Average User Rating(0 ratings) Re: FICO go-live detailed cutover activities

Sridhar MuthekepalliMay 11, 2008 4:48 AM(in response to Sunny B)Hi:Please refer to this document for Cutover Activities/Strategies in SAP FI.http://www.sap-img.com/sap-implementation.htmFor Opening balances, you can use the T.code FB01.It is team effort when you are doing cutover activities.Please let me know if you need more information.Assign points if useful.RegardsMSReddy Alert Moderator Like(0) Re: FICO go-live detailed cutover activities

Sarma tadikondaMay 11, 2008 6:10 AM(in response to Sunny B)1.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 use full 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 balances.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 upload 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 Filed Status group with most of 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 screen doesnt 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 Vendor Master Data will be uploaded without purchasing organization Views (Recording for LSMW FK01 & also keep the changing master data recording handy. Keep in mind your filed status group settings configured for your client). If you are having EWT codes then your 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 production make sure you change the FSG to optional on tax items and do not give any tax codes.FI Customer Master data will be uploaded without sales Views Recording for LSMW 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 screen filed settings before recording and your clients requirement). Write different recordings for SLM keys and WDV keys). For legacy asset data 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 fiscal year you need to ask the client accumulated depreciation as on start of the fiscal year and depreciation posted during the period or after the start of the fiscal year (Again depends on the configuration on how you are posting the depreciation to GL)All the G L balances of account type S and are non-open item managed need to be uploaded G L wise-Profit center wise Via LSMW as on the cutover date. Make sure that no two profit centers were uploaded in the same document because, if you have activated document splitting the number of line items generated at the time of saving the document due 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 -Profit center wise Via LSMW. Make sure that no two profit centers were uploaded in the same document because, if you have activated document splitting the number of line items generated at the time of saving the document may exceed 950 line items and the system will throw you out of uploading.All the Customer open items need to be uploaded Profit center wise. Make sure that no two profit centers were uploaded in the same document because, if you have activated document splitting the number of line items generated at the time of saving the document may exceed 950 line items and the system will throw you out of uploading.All the Vendor open items need to be uploaded Profit center wise. Make sure that no two profit centers were uploaded in the same document because, if you have activated document splitting the number of line items generated at the time of saving the document may exceed 950 line items and the system will throw you out of uploading.You need to use direct input program in LSMW for transaction data upload and select financial documents as object.All the Asset data need to be identified depreciation area wise with Asset class and Depreciation keys.For tax balance sheet Asset class wise Gross block, accumulated depreciation and net block need to be uploaded (AS81).For Customers/Vendors relevant to Sales/Purchasing views take care to give proper recon accounts keeping in view of the alternate recon accounts if any applicable.Make sure you only extend customers/vendors to 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 LInesDepending on the amount of data, take sufficient time for upload activities.In case the asset masters/data is not ready still you can go ahead with GL balance upload and assets can be done at a later date.Go-live date will be (Give the Go live date).All transactions starting after go live will be processed in SAP system only.After Go live, no transaction should be performed in legacy system3.Pre-requisite or AssumptionsScenario and Integration Testing are completed.Cleansed and Validated Master Data made available.Authorization Matrix completed.Processes have been freezed.End user training and documentation is completedG L MasterLSMWRegular RecordingFS00FI Vendor Master DataLSMWRegular RecordingFK01FI Customer Master DataLSMWRegular RecordingFD01Asset master DataLSMWRegular RecordingAS91 together with valuesAS81Group Asset Master DataLSMWRegular RecordingAS21 Cost ElementsLSMWRegular RecordingKA01You can also create by batch input session VIA SPROCost CentersLSMWRegular RecordingKS01Profit centersLSMWRegular RecordingKE51Internal OrdersLSMWRegular RecordingKO01CharacteristicsManual Creation5.TRANSACTION DATAGl Balances of account type S which are non open Item basedLSMW/Direct Input0000RFBIBL00D- Direct InputVendor BalancesLSMW/Direct Input0000RFBIBL00D- Direct InputCustomer BalancesLSMW/Direct Input0000RFBIBL00D- Direct InputAsset BalancesLSMWRegular RecordingAS91AS81AUC BalancesLSMW/Direct Input0000RFBIBL00D- Direct Input6.Prerequisites to Load Master DataClient Setup and Number range maintenance.At least test once the LSMW recordings before moving into production about the reliability and for errors.Load handful of assets in a Quality or in Pre-production system depending on your landscape to ensure that the system is calculating the depreciation, as expected and planned depreciations to be posted are accurate.7.Sequence Of Data ConversionG L master DataVendor Master DataCustomer Master DataGroup Asset DataGL balances without open Item managedGL balances with open Item managedCustomer BalancesVendor BalancesCustomer Balances with Special GLsVendor Balances with Special GLsAsset Masters with Values for the assets existing at the start of the fiscal yearAsset Masters with Values for the assets acquired during the fiscal year with transaction type.It is advised to load asset data along with values instead of loading master first and giving values next.*8.Procedure for Cut Over *1)Check again if the document splitting is active and in case new GL accounts are added by the users, the assignments for document splitting characteristics is made or not. If not do and transport before you start.2)Delete cost elements if created already in production, as the legacy data is not relevant for cost centers. Even of the client insists, you should convince the client saying where he wants to settle the cost center balances after go live? Exception to the above is AUC.3)Assign the field status group to all the G L accounts created for the purpose of upload of initial balances, via LSMW or T-code MASS. You need to revert the settings of master data for accounts with Auto posting, Accounts with relevance to tax category and post with out tax allowed before upload.4)Remove Withholding tax code assignments to vendors. This is necessary because if your upload items contain any balances and the tax codes are assigned the system will calculate EWT and tries to post the same, which is not the case.5)For Non-open item managed accounts provide with the totals as on the cutover date profit center wise.6)For open item managed accounts provide with the totals as on the cutover date profit center wise.7)For reconciliation accounts, line items of customer/vendor should be profit center wise.8)For assets reset the reconciliation accounts load assets, compare data and reset recon accounts.9)Assets acquired before 01.04.2006 need to entered through AS91 and Assets acquired after 01.04.2006 and before 31.01.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.01.2007.10)Make sure you have created group assets via AS21 if you are using Group assets in tax depreciation area.11)Again you need to keep in mind the configurations you made for the client with respect to account types, D & K. For Example Payment terms.12)If the clients need is to have the old balances also on age wise for Payables & Receivables, you need to play with, document, Posting, and base line dates to achieve this via upload.13)Make sure that the discount base column is given value for a smooth upload for Receivables and Payables.14)You need to use separate Direct Input recordings with object 100 and method 0000 (RFBIBL00) for account types S, D&K. This is because if you have large amounts of data, then if you club all the account types into one recording, 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. In such case the system will take great amount of time for uploading.15)Before start of uploading asset line items at GL level make sure is client is open for change and reset the recon accounts for assets. Other wise the system will throw an error, as the recon accounts are not directly posted to.16)After uploading the same again reset the recon accounts. Use in both the cases T-code OAMK to reset the recon accounts.17)For loading AUC values VIA Internal orders, after the above uploads are through, create cost elements, create Internal orders, upload values through the internal order to AUC expenses account and once upload is through, settle the orders to the AUC asset via KO88 before the go-live9.Procedure After Cut Over data Upload1)Reset the filed status groups; post auto settings, Tax settings to the original file given by the core user via MASS or LSMW.2)Once the initial balance accounts balances are zero, take the signoff and block the accounts for posting in future.3)Get the next relevant posting periods opened in OB52, OKP1 & MMPV by the core team member and close all the legacy periods.4)Reset the Vendor FSG settings and other relevant settings changed for the initial balances upload.5)Settle the AUC balances and make the Internal order values to zero. Make sure you use periodic settlement and not FULL.6)Assign vendors with the relevant tax codes and post process the open items as per the warning given by system for making the tax lines consistent.7)Revert all FSG changes for CUSTOMER/VENDOR/GL to the requirement.8)Delete the number range assignments to the document type created for initial balance upload and transport so that to minimize the core user transactions in the legacy period.9)If you are using the parallel ledgers as of ERP 2004 or ERP 2005 make sure you load the balances of non-leading ledgers first. Keep in mind that the non-leading ledgers are not relevant for account types.10)Any new master records created between Cutover and Go live dates are to be tracked and checked for document splitting assignments.11)If you are in Version 4.7EE or ERP 2004 without New GL getting activated, keep in mind you need to run F.5D, F.5E, 1KEK.12)After all of the above precautions still you find that there is a mistake whether small or big dont be panic, go back to your domain experience, think what should have been went wrong, Reverse the document or just pass a rectification entry.13)It is the same case with stock uploads. After your MM counter part loading the stocks and you verify and stocks are not getting matched, the reason could only be the Qty mismatch or the system has taken the MAP defined in the material master.Please keep in mind that this document is for new implementations ON New GL only and not for upgrades.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.Hoep this is Useful to you.Reward points if useful.Sarma