Scribd
Upload
22 views3 pages

Migration

The document discusses different approaches for migrating data from an existing SAP system to a new SAP PS (Project System) module. It identifies five categories of data - master data, transaction data, configuration data, costing data, and user/organizational data - and standard methods for migrating each using tools like LSMW and data templates. While these tools can migrate some data automatically, careful planning, mapping, validation and testing is needed to ensure an accurate and complete migration.

Uploaded by

mohammedraulmadrid
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
22 views3 pages

Migration

The document discusses different approaches for migrating data from an existing SAP system to a new SAP PS (Project System) module. It identifies five categories of data - master data, transaction data, configuration data, costing data, and user/organizational data - and standard methods for migrating each using tools like LSMW and data templates. While these tools can migrate some data automatically, careful planning, mapping, validation and testing is needed to ensure an accurate and complete migration.

Uploaded by

mohammedraulmadrid
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

SAP PS Migration

When migrating data from a SAP system to a newly implemented SAP PS (Project
System) module, the specific data and how it's migrated can vary based on the
organization's requirements and the implementation approach. While there is no one-
size-fits-all answer as data migration strategies can differ, here's a general overview of
what data might be migrated and how it could be migrated using standard methods:

1. Master Data:

 Work Breakdown Structures (WBS)


 Network Activities
 Cost Centers
 Projects
 Project Templates
 Networks
 Milestones
 Work Centers

Migration Approach:

 Master data can be migrated using data templates provided by SAP. Data
templates are Excel-based spreadsheets where you can specify the data to be
migrated. These templates can then be uploaded into SAP using standard data
migration tools such as the LSMW (Legacy System Migration Workbench).

2. Transaction Data:

 Actual Costs
 Planned Costs
 Budgets
 Confirmations
 Procurement Data (Purchase Orders, Purchase Requisitions)
 Material Reservations

Migration Approach:
 For transactional data, historical data can be extracted from the existing system
and then mapped to the relevant SAP PS data structures. Standard data
migration tools like LSMW can be used to migrate transactional data.

3. Configuration Data:

 Control Keys
 Settlement Profiles
 Budget Profiles
 Network Profiles
 Project Profiles
 Status Profiles

Migration Approach:

 Configuration data can be manually set up in the new system as per the
organization's requirements. This might involve recreating profiles and settings
based on existing documentation or configurations.

4. Costing Data:

 Overhead Rates
 Cost Elements
 Costing Variants

Migration Approach:

 Configuration and costing data can be set up manually in the new system based
on existing records and documents.

5. User and Organizational Data:

 User Assignments
 Organizational Units

Migration Approach:

 User assignments and organizational units can be configured manually in the


new system based on existing roles and responsibilities.
It's important to note that while standard SAP tools like LSMW and data templates can
be used, the data migration process requires careful planning, mapping, and validation
to ensure accuracy and completeness. The migration strategy should be tailored to your
organization's specific needs, and it's often recommended to involve experienced
consultants who are familiar with SAP data migration best practices. Additionally, testing
the migrated data in a controlled environment before going live is crucial to identify and
address any discrepancies or errors.

You might also like