cut over planning

[Former Member]

Dear Friends

What do you understand by stock transfer order

What is cut over planning..

With Regards

Sankalp singhai

[Former Member]

Hi Sankalp,

1. STO

Whenever you need to transfer a stock from one plant to other plant we use STO process. Supplying plant could be of other company code also.

For e.g. your company is operating world wide. Each company is having its own company code. If you need to transfer a material from Singapore to US you have to run STO.

Following are the step to set up STO scenario. Follow this step step you will never fail in STO.

<b>STO Process Steps</b>

1.Create a vendor for the company code of receiving plant, using account group :0007 via T-Code [XK01].

2 Assign this vendor to Delivering plant

Go to [XK02] >Purchasing view>Extras>Add. Purchasing data>Plant

3. Create internal customer with the sales area of the vendor. Go To [XD01 ]

4.In Pricing procedure determination relevant to STO, assign document Pricing Procedure and customer pricing procedure appropriate for STO to get the pricing in the invoice.

5.Maintain condition records for the relevant pricing condition.

6. Some more setting for STO: Go to MM> Purchasing > Purchase Order > Set up STO> define shipping data for plants > Go to Receiving plant >assign customer here & Supplying SA (for billing) to Receiving plant here

7. Go to MM> Purchasing > Purchase Order > Set up STO> define shipping data for plants > Go to Supplying plant and assign the sales area of receiving plant.

8. Go to MM> Purchasing > Purchase Order > Set up STO> assign delivery Type & Checking rule

Assign the delivery type to document type. In this case, Delivery type NLCC is assigned to Document type NB

9. Go to MM> Purchasing > Purchase Order > Set up STO>Assign document Type, One step Procedure, Under delivery tolerance

Assign the document type NB to supplying plant and receiving plant

10. After all settings , Create the STO using T-Code:[ME21n] and Save.

11. Create Delivery :[VL10G]

Click on the Background Button after selecting line item

A message is flashed : See log for information> next Click on Log for delivery creation Button >click on line item>click on document button to get Delivery document No

12. Picking, PGI:[VL02n

13. Billing:[VF01n]

Save the document and its done.

<b>Cut Over Planning.</b>

Whenever you shift from one ERP package to another you need to transfer your data as well.

Planning of transferring a data from one Package to another can be reffer as Cut over planning. In SAP terminology Cut over is

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.

Reward if it adds info

[Former Member]

Hi sankalp singhai,

sto is nothing but stock transport order,

there are 2 types of stock transport orders are there

1. intercompany sto

2.intra company sto

inter company sto means stock transfer between different plants belongs to different company codes

intra company sto means stock transfer between different plants belongs to one company code

2). cutover planning:

cut over activities are mainly in finel preparation before go live

i). legacy system shutdown and

ii). all finished goods uploaded from legacy system to sap

iii). and linking old number ranges to new number ranges

iv). uploading all transport requests

v). end user training

hope it helps u , if it is pls REWARD ME

Thanks & Regards

Venkat.Dhanemkula

[Former Member]

At the end of Phase 4, it is necessary to refine and validate the cutover plans generated in the Realization phase. Among other things, this includes tasks such as the reviewing of the runtime of test runs to estimate runtime for the complete data size. A conversion checklist for transporting all changes into the productive system is provided for all the configuration settings to be imported.

At this stage, it is important to verify that required tasks have been successfully completed, for example, that the technical environment is in place, the cutover programs are ready and the application data is verified. Approval is now sought from project management and company senior management to start the cutover process.

Here you can also refer to the Data Transfer Made Easy Guidebook created especially for this purpose. It is located in the Knowledge Corner of the ASAP CD.

The help desk is particularly important in the first weeks after going live, but you will require help desk support throughout the productive life of your R/3 System. An internal help desk should be staffed and supported mainly by employees of the enterprise. Setting up a help desk involves, among other things, installing office and technical equipment and defining OSS users. Problems which cannot be solved by this internal help desk are forwarded to SAP via the OSS system.

As soon as you know when you will go live with the R/3 System or with new R/3 applications you should inform SAP. Thus you can ensure that SAP can provide optimal support throughout your going-live phase. For the last weeks before and first weeks after the go-live date, SAP offers the R/3 GoingLive Customer Care Service, accessible via SAPNet and OSS.

[Former Member]

hi,

Cutover planning 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.

STO : it is basically movment of stock from one storage location to a different may be within a plant or between different plants of a company code. It can also take place between plants of two diff company codes. In this case billing takes place.

The following are the steps.

- Configure using transaction OMGN.

- Depending upon the sending and receiving plants, maintain sales organization and customer data in customizing.

- Maintain the supplying plant as a vendor and attach the plant to the vendor in the Vendor Master.

- Material type has to be HALB or HAWA.

- Ensure that the company with sales Organization has a plant to take care of stocking.

- The PO used is NB and not Stock Transfer PO.

Configure SD for inter-company billing to enable picking up the pricing procedure for billing.

- Carry Out delivery through process delivery due list and billing through process billing due list.

Otherwise, You need to configure your Stock Transport Order settings for your Cross-Company:

Business Transaction to work.

1. Customer No. for the Goods Receiving Plant - OMGN

2. Availability Check- Checking Rule (if necessary) - OMGN

3. Assign a Delivery Type for the Delivering Plant - OMGN (for Stock Transport Orders, NLCC)

4. PO type (which i belive you have done) - OMGN

5. Assign Vendor No. to the Supplying Plant (done) - VK02

6. Assign Customer No. to the Purchasing Plant for the Inter-Compnay Invoice (but you need to assign this to the Sales Organization pre-assigned to the Purchasing Plant),

IMG-SD-Billing-InterCompany Billing-Define Internal Customer No. by Sales Org

***and by the way for the Invoice to work between Cross-Compnay Plants, you need also to have a Sales Org for the Supplying Plant and a Pricing Determination Procedure.

Pl reward if helpful.

Thanks

Sadhu Kishore

[Former Member]

Hi Sankalp,

STO Process:

Stock Transfer Orders comes into picture when the stock is moving / Transferring between two diffrent plants with two Different Company Codes or Stock Transfer between two plants with One Company Code the Difference are given below:

P.O Order types and Delivery Types

STO: - Stock Transfer Order

Stock Transfer between Two Plants with One Company code.

The Purchase Order Type is Used in this case is "UB",

And the Delivery Type Used here is "NL"

STPO:- Stock Transfer Purchase Order

Stock Transfer Purchase Orders Between Two Plants with Two Different Company Codes.

The Purchase Order Type is Used in this case is "NB",

And the Delivery Type Used here is "NLCC".

Configure Intercompany Stock Transport Order

Material should exist in both the plants (Delivering & Ordering),

Internal customer should be assigned to the ordering plant ( MM -> Purchasing -> Purchase Order -> Setup stock transport order -> assign the internal customer to the ordering plant and assign the Sales area of the internal customer.

Assign its Sales area to the delivering plant

Assign the document type and Delivery type NB and NLCC

Assign the Supplying plant --> Receiving Plant --> NB

Take the delivering plant and assign the sales area.

Vendor master has to be created and assign the supply source (Delivering Plant).

Create a purchase order ME21N ---> Save

Delivery VL10 G ---> Calculation rule (appropriate) --> Assign the purchase order number here and execute.

Select the Delivery creation line and do the back ground process.

Start the log display and see the delivery document number by the documents button

Goto VL02N --> do picking and PGI --> Then do the MIGO with respect to the delivery document.

Billing (Intercompany pricing conditions should be set).

CUT OVER PLANNING:

Detailed plans need to be developed for cutting over from the old system(s) to the new. Parallel runs of what will happen over the conversion period using test data, convert and watch for a period after wards to ensure nothing unexpected happens.

Train Users

Well trained users will support and defend the system on site. Unsupportive users will continually undermine the system and eventually it will be replaced. Therefore the more effort you put into helping the users master the system early the better. Fit gap means, before implementing the SAP all the business data is in the form of documents, we cannot keep this data as is in the SAP. There should be a gap. So by filling this gap, we make configuration with the help of these documents. This is called as fit gap analysis.

Please Reward If Really Helpful,

Thanks and Regards,

Sateesh.Kandula