Advise on Migration project

Hi,
I have recently completed BI 7.0 training and have the opportunity to move into a upgrade project (don't know whether it is R/3 or BW upgrade yet) to get my first BI project exposure. I am not sure what all should I check before joining the project so that I can better utlise my time in some other implementation project in case this is not an ideal choice.
Please can you advise in which case it is better - R/3 upgrade or BI upgrade in terms of getting more hands-on experience in BI and also whether a upgrade project is at all advisable as the first project. I checked some other posts and it appears that in case of R/3 upgrade there is not much work required at the BI end. Is it true ? I have lots of experience in ABAP and so want to get exposure in this new technology.
Tx,
R

Why not...this is going to be a great experience ( and since this is your first project, everything is an experience for you). Also, whether it R3 or BI, learning is going to be there for sure...
Read here:
A complete guide for Upgrading BW 3.X to SAP NetWeaver 2004s BI :
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/2e8e5288-0b01-0010-2ea8-bcd4df5084a7
A good presentation:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/8d1a0a3a-0b01-0010-eb82-99c4584c6db3
Migration strategies:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/6a19f233-0e01-0010-6593-c47af5a8df3b
Landscape planning and deployment
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/01b9395c-0e01-0010-6786-c4ee5e5d2154
Checklist for technical upgarde:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e0c9c8be-346f-2a10-2081-cd99177c1fb9
go through this thread;
Upgrade from BW 3.x to BI 7.0
BW upgrade from 3.x to BI 7.0
Support Project: BW 3.5 to BI 7 upgrade
BI 7.0 Initial Hurdles
Thanks...
Shambhu

Similar Messages

Access Migration Error Creating Migration Project - string literal too long

I get this error when attempting to create an MS Access Migration Project:
ORA-20001: GET_BLOCK Error. ORA-20001: GET_STMT error. ORA-20001: Execution of the statement was unsuccessful. ORA-06550: line 8, column 8: PLS-00172: string literal too long &lt;pre&gt;begin &amp;lt;br&amp;gt;declare &amp;lt;br&amp;gt; p varchar(32767) := null; &amp;lt;br&amp;gt; l_clob clob; &amp;lt;br&amp;gt;begin &amp;lt;br&amp;gt; dbms_lob.createtemporary(l_clob,FALSE, dbms_lob.session); &amp;lt;br&amp;gt; dbms_lob.open(l_clob,dbms_lob.lob_
I suspected the 'string literal too long' was due to a very long code section in the Exporter .sql file -
So I edited out that code except - essentially by cutting the macro code within the quotes, cutting down that code module.
Same error.
Any suggestions on what else may be causing this?
Thanks - Karen

I found it - two other big long ugly macros that I had to cut out as well. Then the migration project created just fine. Thanks for the moral support :)

What are the consultant roles in Upgradation or migration project

Hello ,
Would you please any dody help me to provide the role & responsibilities of consultant in SAP upgradation or migration project.Thanks.
Regards,
Sampally

Dear Sampally,
SAP defined a roadmap for upgrade.
1) Project Preparation
Analyze the actual situation
Define the objectives
Create the project plan
Carry out organizational preparation for example identify the project team
2)Upgrade Blueprint
The system and components affected
The mapped business processes
The requirements regarding business data
3)Upgrade Realization -- In this phase the solution described in the design phase is implemented in a test environment. This creates a pilot system landscape, in which the processes and all their interfaces can be mapped individually and tested on the functional basis.
4)Final Preparation for Cutover -- Testing, Training, Minimizing upgrade risks, Detailed upgrade planning
5)Production Cutover and Support
The production solution upgrade
Startup of the solutions in the new release
Post processing activities
Solving typical problems during the initial operation phase.
SAP expects at least 2 to 3 months for Upgrade and that again depends on project scope and complexity and various other factors.
STEPS IN TECHNICAL UPGRADE
Basis Team will do the prepare activities. (UNIX, BASIS, DBA).
Developer need to run the Transaction SPDD which provides the details of SAP Standard Dictionary objects that have been modified by the client. Users need to take a decision to keep the changes or revert back to the SAP Standard Structure. More often decision is to keep the change. This is mandatory activity in upgrade and avoids data loses in new system.
After completing SPDD transaction, we need to run SPAU Transaction to get the list of Standard SAP programs that have been modified. This activity can be done in phases even after the upgrade. Generally this will be done in same go so that your testing results are consistent and have more confident in upgrade.
Run SPUMG Transaction for Unicode Conversion in non-Unicode system. SPUM4 in 4.6c.
Then we need to move Z/Y Objects. Need to do Extended programming check, SQL trace, Unit testing, Integration testing, Final testing, Regression Testing, Acceptance Testing etc.,
The main Category of Objects that needs to be Upgraded is
Includes
Function Groups / Function Modules
Programs / Reports
OSS Notes
SAP Repository Objects
SAP Data Dictionary Objects
Domains, Data Elements
Tables, Structures and Views
Module Pools, Sub Routine pools
BDC Programs
Print Programs
SAP Scripts, Screens
User Exits
Also refer to the links -
http://service.sap.com
http://solutionbrowser.erp.sap.fmpmedia.com/
http://help.sap.com/saphelp_nw2004s/helpdata/en/60/d6ba7bceda11d1953a0000e82de14a/content.htm
http://www.id.unizh.ch/dl/sw/sap/upgrade/Master_Guide_Enh_Package_2005_1.pdf
Hope this helps you. Please let me know in case of any specific queries.
Regards,
Rakesh

2 Problems after migration Project Server 2007 to 2010

Hi Everyone!!
I have 2 issues after migrate MS Project Server 2007 to Project Server 2010, in fact i had a lot issues, but i can solve almost all, so after solve all issues, just is pendings 2 issues very rare:
Backgrounds:
Migrated from: Windows Server 2008R2 - SQL Server 2008 R2 - Proejct Server 2007 with WSS 3.0 - All updates are up to date (CU is up to date) and all platform is ok
To: Windows Server 2008R2 - SQL Server 2008 R2 - Project Server 2010 SP2 - SharePoint Server 2010 SP2 - All updates are up to date (CU is up to date) and all platform is ok
3 Servers in the Farm, ----> 1WFE-1WAPP-1DB
Issues:
In the Project Center, some migrate Project don't show the icon with image about project documents, risk and issues although that project effectively have documents , risk and issues
In "Server Settings" , in section "Operational Policies" in "Project Sites" almost all projects don't show the URL with Project Site
For the issues 1 and 2, i tried some things:
Re publish all projects (approx 700 projects) with a script via PowerShell available in technet
Run the Wizard Again
Rebuild Solution
Restart the all Servers in the Farm
Restart Services ----> IIS - Project EventService - ProjectQueue - SharePoint Timer
and i can't solve it yet!!!
Please Any Ideas?
Erick Gutiérrez PMI Membership #ID 2089740 MTCS - Microsoft Project Server Managing Projects

Have you restored content DB successfully?
for point 2 have you performed:
have you synchronized project site under server setting --> operational policies --> Bulk Update Project
Sites
http://pwmather.wordpress.com/2012/10/08/projectserver-2010-bulk-update-project-site-issue-ps2010-msproject-sp2010-sharepoint/
after doing this publish all the project which are having issue it may solve your 1st issue.
You can check if below condition is applies to you (PWA 2007)
You may need to use the WSS site re-linker tool –
now built in to Server Settings in PWA as “Bulk Update Project Sites”. If you have changed URL die to a different port then re-linking should get your sites in order. In upgrade scenarios the “Previous Site Path” Web application might show as a GUID
in the drop down – however it still works and will re-link the sites.
http://technet.microsoft.com/en-us/library/cc197498(v=office.12).aspx
kirtesh

How to migrate projects from another (external) system into PS

Hi,
Which technique to use in your opinion is the best practice to migrate projects in PS?
Batch input or ABAP program and use BAPIS? or is ther other alternative?
Best regards
Jose Marin

Hello Jose,
Open PS is the best option, If your external system is MSP. There is no standard LSMW prog available for uploading the Projects. Howvever there are certain BAPIs available
1.BAPI_PS_INITIALIZATION
2.BAPI_BUS2001_CREATE
3.BAPI_BUS2054_CREATE_MULTI
4.BAPI_BUS2001_SET_STATUS (To set the status at project level)
OR
BAPI_BUS2054_SET_STATUS (To set the status at WBS element level)
5.BAPI_PS_PRECOMMIT.
I guess you don't have to code again for this. Whatever structures and internal tables in BAPI_PROJECT_MAINTAIN can be used to populate the above BAPIs.I have checked on BAPI_PROJECT_MAINTAIN and this creates a Project definition too.
Good option is to create a custom program and load data using the BAPIu2019s.The program should perform couple of pre-validations and should have error handling capability as well.
Thanks
Sarang

SAP PS Data Migration Project

Hi,
This is my first data migration project. We have to migrate SAP PS transactional data from SAP 4.7 to SAP 6.0. My task is to migrate WBS element data to the new system. To do that I need to do field and Value mapping also. Please suggest how do we go about completing the task at hand and also suggest what else do we migrate in SAP PS.

Hi,
If it is a new system, you can use BDC/LSMW/BAPI for uploading the data to PS.
Also topic have been already discussed in the forum. You can refer below threads for more info:
http://scn.sap.com/thread/912834
http://scn.sap.com/thread/3236416
Regards
Shishir

Steps to migrate Project Server 2007 from SQL Server 2005 to SQL Server 2008?

We need to migrate Project server 2007 from SQL Server 2005 to SQL Server 2008.
1. Is it as simple as doing backup and restore of databases and pointing Project Server to the new DB server? Or there are some specific steps that should be followed?
2. Article at
http://technet.microsoft.com/en-us/library/dd207290(office.12).aspx is about moving databases from one DB server to another (same versions). At one place, it mentions to
backup all databases but at another place it mentions that
You should only back up the Draft and Published databases from the source database server.
What should be done when moving from 2005 to 2008?
Regards,
Amit
Gupta

High Level step you can get this form Tech net or MSDN too
Shut down the SharePoint servers (App / Web)
backup all of the SharePoint and Project
Server databases from the SQL 2005 server
copy these over to the new SQL 2008 server and restore all of
the databases with the same names
script out all of the logins used by SharePoint/PS from the SQL 2005 server and create these on the SQL 2008 server
script out the Delete expired sessions SQL job from the SQL 2005 server and create this on the SQL 2008 server - or create them manually on the SQL 2008 server
repoint the SQL server DNS Alias from the SQL 2005 server to the SQL 2008 server, if SharePoint and Project Server was installed using the actual SQL server name and no alias, you can create a DNS alias for the old SQL 2005 server name that points to the SQL
2008 server. This is so that the SharePoint servers can still connect to the same SQL server name
Start up the SharePoint servers
kirtesh

Reg: Universe Designing (Migration Project)

Hi Gurus,
I need Informtion related to the migration project.
Migrating BO 5.1.7 to BO XI R 3.1.
the old universe with old database is structured as.
Eg: PTKEN as table name and objects as PTKEN.WASId
the new ( migrated universe ) has the database structure as
Eg: KEM_LKP_PTKEN as table anem and objects as WASId
What the process has to be done to change all the tables in the universe with the new database...
Regards
L K Vepuri
Edited by: L K Vepuri on Feb 28, 2011 3:56 PM

Hi Mr. Vepuri,
If the table name is changed at the universe level then follow the below steps.
1. Open the universe in the designer
2. Right click on the table which has been modified and rename it with the changed name.
3. Click on the View>> Refresh Structure.
4. and check whether it throws any error message or not.
For Object PTKEN.WASId--- what does it mean?
Is it column name or object name at universe level.
Object definition of each object is visible as Table_Name.Column_Name.
If you want to change the object name then you can rename it.
In order to propagate the changes made at a database level to universe level always click on the View >>refresh structure
Hope it helps.
Thanks,
Sands

How to modify developers' access to limit the ability to migrate projects?

In PeopleTools 8.48 how to modify the developers’ access to limit the ability to migrate projects ?
Thanks in advance for your help.

Yes you can do this through Permission lists.
Create a new permission, on Peopletools tab, click Tools Permissions
Set Upgrade to No Access
All these settings are defined in Peoplebooks - PeopleTools 8.49 PeopleBook: SEcurity administration, Setting up Permission lists
There is a section called Tools Permissions.
Note: PeopleSoft Administrator Role overrides this value.
Example:
Permission DEVELOP - has the settings above, to No Access for Upgrade.
This Permission list is in 90DEVL, 90QA, 90PROD.
If you give Develoers - PeopleSoft Administrator role in 90DEVL, 90QA .. They could copy projects between 90DEVL and 90QA, but could never copy to 90PROD.
It depends on how much control between development instances you want in regards to copying projects.
Pam

How to migrate Project Server 2003 to Project Online?

Hi Guys,
Is it possible to migrate Project Server 2003 to Project Online directly? I heard we normally have to take 3 hops for this;
1. Project Server 2003 - Project Server 2007 migration.
2. Project Server 2007 - Project Server 2010 migration.
3. Finally, Project Server 2010 - Project Online migration.
Is there a migration tool we can use to simply jump from Project Server 2003 to Project Online?
Thank You,
Arnel

NO, directly you can not migrate. You have to follow the sequence
1. Project Server 2003 to project server 2007
2. Project Server 2007 to project server 2010
3. Project Server 2010 to project server 2013 online.
Unfortunately we dont have nay tool which will help us to do this .
Microsoft has a virtual machine (2007) that you can use to jump to 2007. Basically the databases of 2003 must be converted to 2007. Once this is done (database at 2007) you can use this database as start point to be converted to 2010.
Microsoft has virtual machine for 2010 too if you want you can use it rather than creating your own environment.
Don't use 2007 backward compatibility mode in 2010, we experienced some issues with it.
kirtesh

Document statuses of migrated project not gettign displayed

Hi Gurus,
We migrated the project using 'Solar_Project_Admin'. All documents get populated correctly. But the problem is staus of documents are not getting migrated. Where as the status scemas were traported before project. So, all the status scemas for dcouemnt types are available in migrated server. Even the migrated project shows attached statuse scemas to document type.
Eventhough the status is not getting displayed.
Please guide me if I missed out any step.
Thanks & Regards,
Vrushali

Hi Gurus.
I am transporting project with SOLAR_PROJECT_ADMIN and all documents that are in status RELEASED are transported, but documents in status IN PROCESS are not.
Any idea?
thx

Approach to migration project

Hello Gurus
Am on a migration project,can anyone please suggest me the approach of how to do migration. To be clear, how to do migration based on modules or objects or dataflows. Please help

I'd start with the basic elements: InfoObjects and Master Data. Once those are covered, it will be easier to migrate the other structures.
Follow the approach by Business Area/Module, that way you work following the logic/flow of that area and get to double check any impact in the related data/structures.
And, of course, follow the "natural" data flow... Datasources, Infosources, Transfer Rules, Update Rules, Transformations, DTPs, ODS, InfoCube, Queries (if needed).
Also pay special attention to user security settings just to make sure you don't have problems on that aspect.
Good luck...

EMIGALL: migration project

Hi,
I am looking for some documentation regarding migration projects. In particular:
Roadmap of a migration project.
Main aspects when planning a migration project.
Best practices.
Which are the parameters to consider in order to estimate time, resources, and so on.
As you see, the query is more related to the plannig point of view than technical point of view(how to use the tool).
Thanks, in advance for your help.

Sorry guys, I haven't had any time lately.
Obviously, I can't write down all my experience, because it would take way too long. I also don't know what you don't know.
Anyway, I can answer specific questions, so here we go:
Order of migration objects
The order, the migration objects have to be imported, is defined by the Key and Status Management (table TEMKSV). For each object field with processing type 5 there's a dependecy to another object, that has to be imported beforehand. So after identifying all fields of an object you want to populate, there's a list of objects that have to be imported beforehand. You can see the list under EMIGALL menu item Migration Object: Display, then go to Relationship Data.
You can see a relationship diagram when pushing Object Hierarchy.
EMIGALL import runs
For testing purpose a single file can easily be imported via EMIGALL menu item Migration object: Data import. The load program has to be generated beforehand (see EMIGALL Menu item: Generate Report).
For end-to-end testing and the productive load there's a job scheduler. Everything can be set-up and run under EMIGALL menu item Utilities: Schedule import jobs. I have to admit, that I didn't use it myself, because at my last major migration project, which went over 5 years, I've developed a framework around the IS-U migration tool to meet the clients requirements (I'm not going into details because Fritz Keller wouldn't be happy with everyone doing something like that).
I hope that helps
Jürgen

Export Migration Project

Hello,
is there a possibility to export a migration project?
Best regards
Tareq

Hi Tareq,
Unfortunately there is no option to export a Migration project currently. In the meantime, once you've got access to your migrated Database schema objects (preferably as a DDL script) and also all the necessary Migration files e.g. for an MS Access Migration, that would be a SQL script e.g. Northwind.sql and for an Oracle Forms conversion, that would be XML files for Form Modules/Menus/Object Libraries and Oracle Reports, and PLD files for converted PLLs, then you can very easily re-create the Migration Project in a different workspace. I appreciate that the selections you may have made in the Migration Project cannot be exported, so we could possibly look at addressing this in a future release.
Regards,
Hilary

Process to Migrate Projects

Hi Folks,
What's the best approach to migrate projects to e sourcing system and what are the templates used .
Thank you,
HM

Hello,
I never got such requirement in the past. But when I was going through the system, I found a template for Projects.
I didn't get any option to attach an excel in SCN, hence I converted it to notepad and attaching.
Hope this helps!!
Regards,
Vignesh

Advise on Migration project

Similar Messages

Maybe you are looking for