cut over strategy with example

[Former Member]

Dear friends

What is cut over strategy explain with an example

What is FTXP

In which master data we are not configuring tax?

With regards

Sankalp singhai

singhai.sankalp78@gmail.com

[Former Member · Accepted solution]

Cut over strategy:

This is one of the actvity in implementation project of final preparation phase,this is nothing but all the open items(vendor,customer&G/L) balances to be ready to upload from the legacy ssystem to R/3(SAP).So that the system is ready for golive and then business can run through R/3.

FTXP:

This is transaction code used by FI team to set up tax codes against each country.Through this you can see automatic tax accounts whaich they configured in OBYC for input and output tax.

Before doing this tax procedure must set up in the config.

Hope you are clear on this part.

Let me know if you need any clarifications on this.

Reward if it helpful.

Regards,

Chandra

[former_member227476]

dear snakalp

Cutover Activities

Communication to Vendor, Customer and Excise etc

User Training by Core Team

Cost Roll ups and Validations – Test

Upload of Master Data in Sequence on Test

Start entry of Open Sales Orders, Quotation, Enquiries, Purchase Orders in Prod

Stock Taking Activity at Plant

Stock Upload with SAP Material Code, Qty, Value and Storage Location as on xx.xx.xxxx on Prod

Enter Cash Balances as of xx.xx.xxxx

Enter Excise balances as of xx.xx.xxx with monthly duty payment for March

Configure Cut off Excise Number Range (Excise Invoice, RG registers) as on xx.xx.xxxx

Back up of Loaded Production Server

Go Live

Availability of all balances

FI Balance uploads (For both ledgers/ sub ledgers/ assets/ customers/ vendors)

If Sales Order is Open, we require foreclosing the Sales Order & also ensuring that there is no open delivery. Incase if there is any open deliveries, they should either complete the process up to Billing & creating accounting Document or the Deliveries should be cancelled. Similarly if there is any Billing document not passed to accounting, it should be ensured that they are passed to accounting.

In the New System, if transaction are small in number then sales order should be created manually & if the volume is high through LSMW.

The Duration of Cut-Over is around 15 - 20 days ideally

Cutover strategy is used for uploading the master data in the production system from the legacy system before Go live of the project.

Master data includes Customer master, Material master, Condition master.

Existing transaction which is present in the legacy system which needs to be processed in SAP system needs to be maintained in SAP.

Material stock needs to be uploaded.

Here we basically fixed the date up to which the data has to be uploaded. After cutover date no data will be updated in SAP till Go live.

Cutover strategy depends upon how the organizations design their data load strategies. Normally, you decide the sequence of Data loads for Configuration settings, Master data, Transaction data which follows whom and then you make a copy of the system as a Production system a day before and after checking the successful data loads, you go-live 100% or partial again depending upon organizational setup and policies.

Cutover planning is highly site specific. There's no thumb rule. The stock data as on the date of going live should be correctly entered. But stock being a highly dynamic quantity, the strategy for loading should be crystal clear. Then you have to load all the back dated transaction on the stock. Some stock comes into your plant/storage location as return and some stock is actually delivered to your customer through sales orders of various kinds.

Cutover strategy depends upon how the organizations design their data load strategies. Normally, you decide the sequence of Data loads for Configuration settings, Master data, Transaction data which follows whom and then you make a copy of the system as a Production system a day before and after checking the successful data loads, you go-live 100% or partial again depending upon organizational setup and policies.

Cutover planning is highly site specific. There's no thumb rule. The stock data as on the date of going live should be correctly entered. But stock being a highly dynamic quantity, the strategy for loading should be crystal clear. Then you have to load all the back dated transaction on the stock. Some stock comes into your plant/storage location as return and some stock is actually delivered to your customer through sales orders of various kinds.

Cutover Strategy is the plan of action of updating all the process transactions into SAP before GOLIVE.

Let me explain you in this way... suppose the GOLIVE date of an SAP project is August 1st. And the Company might be using some legacy system prior to this implementation. So all the transactions, master dates, G/L account information, material stock uploading etc should be updated into sap so that there will be smooth GOLIVE on August 1st. And there is also a gap between the SAP implementation and stop using of Legacy system. So all the transactions done in this gap also should be updated into SAP system.

So they come in backward process (Like August 1st to back dates) and chalk out a plan of action for updating all the necessary information into the SAP system so that by August 1st Go live is done.

rewards pls

siva