Stop Delaying Your System Copy Projects: Use BC-INS-MIG for Faster SAP Incident Resolution

Sara Kim breaks down what you need to know

Nothing kills my developer productivity faster than a test system that’s stalled because a system copy went sideways. I’ve sat in front of a half-refreshed sandbox, unable to deploy a new tool or validate a custom ABAP fix, simply because someone logged the issue under a generic component like BC-DB-ORA or—worse—just attached it to the support project without a clear application area. Those days taught me one thing: the support routing engine at SAP is like a transport directory—if you put the file in the wrong folder, nobody finds it. For any problem during an SAP system copy, the only component you need to remember is BC-INS-MIG. It’s not a magic wand, but it’s the closest thing to an express lane for migration support.

The Real Story

The SAP system copy procedure guide—that chunky PDF every Basis consultant has bookmarked—explicitly states that you should create a customer message under application area BC-INS-MIG for any problems arising during homogenous/heterogeneous copies, system refreshes, or conversion issues. I’ve seen the documentation, you’ve probably seen it, yet time and again I find teams filing under generic infrastructure or database components out of habit.

BC-INS-MIG routes your incident directly to the support team that specializes in system migration and copy topics. That matters because system copy problems are rarely pure database problems and almost never plain ABAP runtime glitches. They sit at a messy intersection of platform, operating system, R3load/R3szchk, and post-copy automation. The migration support engineers have debug scripts, internal tools, and a knowledge base specifically tailored to that mess. A generic component, on the other hand, might force your incident through three levels of reassignment before anyone even reads the attachment. I’ve traced incidents that spent 48 hours in limbo just because someone typed BC-INS instead of BC-INS-MIG.

Here’s what BC-INS-MIG officially covers: homogeneous and heterogeneous system copies, system refresh using backup/restore, SWPM, SUM-based system conversions, database-independent migration (DIM), and export/import issues. In short, if you’re moving data between systems, this is your box.

What This Means for You

For SAP Basis administrators, the implication is immediate. Stop treating the incident component as a formality it’s a routing instruction. When you open a message, use the exact text BC-INS-MIG in the “Component” field. I recommend setting up a template in your ticketing workflow that pre-fills this field whenever the subject matches a system copy activity. Automate the discipline—you already automate the copy itself.

For consultants and architects, this is a quality gate. If you’re overseeing a migration project, audit the first few incident messages from your team. I’ve had to tell a project lead, “Your go-live was delayed because the support ticket sat in the wrong queue for two days. That’s a process failure, not a technical one.” Add a checklist item: “All system copy incidents logged under BC-INS-MIG.” It sounds trivial, but it can mean the difference between meeting a weekend cutover window and explaining to the business why the test environment isn’t ready on Monday.

And for developers like me who rarely touch SWPM but suffer the consequences: if you’re the first to spot a botched copy (e.g., missing ABAP development objects, SAPscript forms broken), don’t just escalate to Basis. Ask whether the incident was properly filed. Sometimes the quickest fix is a correctly routed message that asks for a re-run of a post-copy step, not a full system restore.

Action Items

• Immediately update your incident creation process: In Solution Manager, SAP for Me, or your help desk tool, replace any generic BC-* components for system copy tickets with BC-INS-MIG. Document this as a standard operating procedure (SOP) and link the official SAP guide as the authority.
• Audit open incidents: Look at your current system copy-related messages. If any are stuck in “Processing” with multiple reassignments, check the component. I’ve seen a simple reassignment to BC-INS-MIG breathe life back into a stalled ticket.
• Include BC-INS-MIG in your migration plan checklist: Right next to “Verify backup availability” or “Run R3szchk,” add “Confirm support incident component set to BC-INS-MIG.” Make it just as mandatory as the technical steps.
• Educate your junior Basis team: I’ve had perfectly smart colleagues who didn’t know the difference between BC-INS-MIG and BC-INS-TCU (which is for transport control). Spend five minutes showing them the SAP guide screenshot. It will save days of frustration.

Community Perspective

In Basis forums and at SAP TechEd hallway conversations, I often hear the same frustration: “SAP support takes too long during system copies.” When I dig deeper, almost always the component was wrong. A fellow consultant once told me she spent a week on a heterogeneous copy failure because the incident got routed to the Linux support team (BC-OP-LNX) based purely on a kernel panic message. Actually, it was a Unicode conversion issue that should have landed in BC-INS-MIG. Once reassigned, the migration specialist identified a missing language supplement within hours. The community knows this; we just need to remind ourselves. I’ve contributed to open-source tools that parse SWPM logs, and trust me, the errors are specialized enough to warrant the specialist team. Don’t send them on a wild goose chase.

Bottom Line

Using the correct application area isn’t about being pedantic—it’s about respecting your own project timeline. SAP system copies are stressful enough without manually prolonging the support cycle. BC-INS-MIG is your direct line to the engineers who can actually fix a migration failure, not just close the message with “please check SAP Note 123456.” Next time you hit a roadblock during a system refresh, open the incident screen and type those nine characters. It’s the simplest quality improvement you can make in what is often the most chaotic phase of an SAP landscape project. And if I catch you still filing under BC-DB-ORA, I might just bring it up in my next TechEd talk.

Source: System Copy for SAP Systems Based on SAP NetWeaver 7.1x - ABAP

References

• SAP Community Hub
• SAP News Center

References

• System Copy for SAP Systems Based on the Application …
• SAP News Center
• SAP Community Hub