Migration of On-Going Project

[mohammedrahman4]

Hi All, 

I need to migrate aroud 500 on going project & their associated WBS elements ( total WBS are 30000 ) together with budget to a new system . Can any one please suggest whether we can develop a program to do this activity ? Is there any BAPI to address this requirement as doing this activity is not feasible ?

Thanking you .

Best Regards 

Mohammed 

[VenkatesanAnnamalai]

Can you provide a few more details? What is your source system (Legacy) and what is your target system (On-Premises or Cloud)? Are you using only PS projects or PPM projects?

[RaquelSouza]

Automating Project and WBS Migration in SAP ABAP

Yes, it is absolutely feasible to develop an ABAP program to automate this migration. Since we are dealing with a large volume of projects (500) and WBS elements (30,000), the approach must be well-structured to ensure efficiency, data integrity, and error minimization.

🔹 Migration Approach

1️⃣ Data Assessment

📌 Before starting development, it is essential to identify:
✔️ Data sources: Where are the projects and WBS elements stored? (SAP tables, external systems, CSV files, etc.)
✔️ Data structure: What information needs to be migrated? (Project codes, authorization, budget, status, etc.)
✔️ Validation requirements: How can we prevent duplicates and inconsistencies?

👉 Key SAP tables involved:
📌 Projects: PRPS (WBS Elements) and PROJ (Projects)
📌 Budget/Costs: BPJA (WBS Budget) and COEP (Cost Line Items)

2️⃣ ABAP Program Development

✔️ Develop an ABAP report (SE38) to extract data from the old system.
✔️ Implement a data transformation process to match the new system format.
✔️ Use protected BAPIs to create/migrate projects and WBS elements.

👉 Recommended BAPIs:

• BAPI_PROJECTDEF_CREATE → Creates project definitions
• BAPI_BUS2054_CREATE_MULTI → Creates multiple WBS elements
• BAPI_COSTACTPLN_POSTPRIMCOST → Primary cost planning (budget update)

⚠️ If the company uses CJ20N for project management, verify whether project/WBS numbers should remain the same or need to be renamed in the new system.

3️⃣ Execution and Testing

✔️ Develop a test program to validate migration on a small batch of projects/WBS before full execution.
✔️ Implement logs and tracking to monitor errors and migration status.
✔️ Ensure reversibility, in case rollback measures are required.

📌 Suggested Automation

If the data volume is large, consider implementing a background process to avoid system performance issues:

📌 Use Jobs (SM37) to schedule and execute migrations in controlled batches.
📌 Split data into blocks of up to 5,000 WBS elements to optimize performance and reduce risks.

📌 Next Steps

1️⃣ Is the data format for migration already defined? (SAP → SAP, SAP → File, etc.)
2️⃣ Do we need to develop a data degradation report before migration to ensure data quality?
3️⃣ Is the new system ready to receive the data, or does it require structural adjustments?

My name is Raquel Souza - Brazil