Professional Documents
Culture Documents
2.
3.
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 processedin SAP system only. After Go live, no transaction
should be performedin legacy system 3. Pre-requisite or Assumptions Scenario and Integration Testing are
completed. Cleansed and Validated Master Data made available. Authorization Matrix completed. Processeshave
been freezed. 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. TRANSACTIONDATA GL
Balances of account type S which are non open Item based LSMW/Direct Input 0000 RFBIBL00 D- Direct Input
VendorBalances LSMW/DirectInput 0000 RFBIBL00 D- Direct Input CustomerBalances LSMW/DirectInput 0000
RFBIBL00 D- Direct Input AssetBalances LSMW Regular Recording AS91 AS81 AUC Balances LSMW/DirectInput
0000 RFBIBL00 D- DirectInput
3. 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 6. Prerequisitesto Load
MasterData Client Setup and Number range maintenance. At least test once the LSMW recordings beforemoving
into productionabout the reliability and for errors. Load handful of assets in a Quality or in Pre-productionsystem
depending on your landscape to ensure that the system is calculating the depreciation,as expected and planned
depreciations to be posted are accurate. 7. 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. It is advised to load assetdata
along with values instead of loading master first and giving values next. 8.Procedure for Cut Over 1) Check again if
the documentsplitting is active and in case new GL accounts are added by the users, the assignments for
documentsplitting characteristics is made or not. If not do and transport before you start. 2) Delete costelements 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 costcenter balances after go live? Exceptionto the
above is AUC. 3) Assignthe 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 categoryand postwith out tax allowed before upload. 4) Remove Withholding
tax code assignments to vendors.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. 5) For Nonopen item managed accounts provide with the totals as on the cutover date profit center wise. 6) For openitem
managed accounts provide with the totals as on the cutover date profit center wise. 7) For reconciliation accounts,
line items of customer/vendorshould 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.2006need 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 depreciationarea. 11) Again you
need to keep in mind the configurations you made for the client with respectto 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 smoothupload 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.
4. 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 15) Before start of
uploading assetline 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 resetthe reconaccounts. 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 orderto AUC expenses accountand once upload
is through, settle the orders to the AUC asset via KO88 before the go-live 9. ProcedureAfter Cut Over data Upload
1) Resetthe filed status groups; postauto 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 blockthe accounts for
posting in future. 3) Get the next relevant posting periods openedin OB52,OKP1 & MMPV by the core team
member and close all the legacy periods. 4) Resetthe VendorFSG 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 settlementand not FULL. 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. 7) Revert all FSG changes for
CUSTOMER/VENDOR/GLto the requirement. 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.
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.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 documentsplitting
assignments. 11) If you are in Version4.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 documentor just pass a rectification entry. 13) It is the same case with stock uploads. Afteryour MM counterpart
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. 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. Theoretical Steps Declaration:This Project is a Live Hands on ImplementationProgramERP6.0 SAP
FICO, Startedafter taking inputs from my Project Manager.