Community

Ask a Question Write a Blog Post Login

Search Questions and Answers

Former Member
Oct 11, 2008 at 07:28 AM

go-live preparation
242 Views
0

Follow RSS Feed

Hi,all,

This is my first implementation project.Our project is now final preparation phase.In my PM module,I have uploaded
all relevant master data in production server.Our go-live date is on 15th oct'08.What are the other activities I need to
do? Like other module is uploading cut-over data like initial stock,open PO,etc.?In PM module is there any cut-over
data concept. and also on 15th or from 15th Oct,08, is it required to manually enter some transactional data for 1st
oct'08 to 15th oct'08??Please,suugest me in details what are precautionary measures I need to take or what the
activities I need to do???Your valuable input is solicited.Thanks in advance.

rgds

rajib

Add a Comment | Alert moderator

Assigned Tags

PLM Enterprise Asset Management (EAM)/Plant Maintenance (PM)

Similar Questions

Impact of not going live of CS module in Pilot go-live
Former Member Nov 23, 2019

Client preparation
Former Member Nov 22, 2019

5 Answers

Sort by: Votes | Newest | Oldest

Best Answer

Kaushal Rai
Oct 11, 2008 at 07:54 AM

Dear,
2
In PM you have to take care of those transaction which are related to external services, like material
procurement, service procurement, material sent to outside for repairing. Here billing documnet
should be cleared or it should be noted.

Regards,

Kaushal Rai

Add a Comment | Alert moderator | Share

Former Member
Oct 11, 2008 at 08:18 AM

dear rajib
0
As you have uploaded master data in production server...now follow all these steps before go-live :

1. prduction system readiness

A. indentify transport requests & approvals

B. all requests transport to production

2. data conversion
 perform data conversion to production system

3. cut over

perform cut over to production system

then go -live

regards

vineet

Add a Comment | Alert moderator | Share

Former Member
Oct 11, 2008 at 06:07 PM

Dear Rajib,
0
All planned maintenance has to be carried out and completed before mm-dd-yyyy as far as
practicable. All stores and spares required for these activities be issued for maintenance before mm-
dd-yyyy and treated as consumed in Financial Accounting.

No unplanned maintenance activities that cannot be completed before mm-dd-yyyy be commenced

after mm-dd-yyyy, except in case of emergencies.

However all stores and spares required for the purpose also be requisitioned and issued in advance by
mm-dd-yyyy.

There shall be no Maintenance Orders in SAP for consideration in respect of incomplete maintenance
activities as on mm-dd-yyyy. After Go-live maintenance orders will be created for all work getting
done.

N.B.: mm-dd-yyy = Go-live date

Rajesh

Add a Comment | Alert moderator | Share

Former Member
Oct 13, 2008 at 09:40 AM

hi
0
 0
1.check all PM number ranges are created.

2.Sapres stock uplaod

3.PM activity types assgined to all cost centre in KP26

4.Maintenance plans - you need to be carefull on start up dates in plans.

5.External service POs and orders to be created on GOKLIVE

-ashok

Add a Comment | Alert moderator | Share

Former Member
Oct 13, 2008 at 01:45 PM

thanks dudes for your valuable input.

0
rgds

rajib

Add a Comment | Alert moderator | Share

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want
the poster to clarify the question or provide more information, please leave a comment instead, requesting
additional details. When answering, please include specifics, such as step-by-step instructions, context for
the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules
of Engagement.

Rules of Engagement 

Know someone who can answer? Share a link to this question.

You must be Logged in to submit an answer.

Please provide a distinct answer and use the comment option for clarifying purposes.
10 characters required.

Submit your Answer

Find us on

Privacy Terms of Use

Legal Disclosure Copyright

Trademark Cookie Preferences

Newsletter Support