🚀 ABAP Performance Tip: LOOP...INTO vs LOOP...ASSIGNING

 If you're working on real-time SAP projects or processing large internal tables, performance isn't just a nice-to-have—it's essential. A report that executes in 5 seconds instead of 5 minutes can dramatically improve the user experience.

One of the simplest yet most impactful optimizations in ABAP is choosing the right way to loop through internal tables.

🖼️ Understanding the Diagram: LOOP...INTO vs LOOP...ASSIGNING

At first glance, both loops appear to do the same thing—they process every row of an internal table. However, what happens behind the scenes is completely different, and that's where the performance difference comes from.

❌ Top Diagram: LOOP AT ... INTO wa

LOOP AT lt_data INTO ls_data.
  ...
ENDLOOP.

🔍 What is happening?

1️⃣ ABAP reads a row from the internal table.

2️⃣ It creates a copy of that row inside the Work Area (WA).

3️⃣ Your program works on the copied data.

4️⃣ If you modify anything, you must write it back using:

MODIFY lt_data FROM ls_data.

📦 Memory Flow

Internal Table
       │
       │ Copy Data
       ▼
 Work Area (WA)

Every iteration creates another copy of the row.

For 100,000 records, that's 100,000 copy operations before your actual business logic even begins.

✅ Bottom Diagram: LOOP AT ... ASSIGNING <fs>

FIELD-SYMBOLS <fs> TYPE ty_data.

LOOP AT lt_data ASSIGNING <fs>.
  ...
ENDLOOP.

🔍 What is happening?

Instead of copying the row...

ABAP simply creates a Field Symbol (<fs>) that points directly to the existing row inside the internal table.

There is no copy at all.

📍 Memory Flow

Internal Table
      ▲
      │
 Field Symbol <fs>

The field symbol acts like a pointer or reference to the original data.

🚀 Biggest Advantage

If you update a field:

<fs>-status = 'Completed'.

The internal table is updated immediately.

No extra statement is required.

❌ No

MODIFY lt_data FROM ls_data.

✅ Because you're already working on the original row.

📖 Real-Life Analogy

❌ LOOP...INTO

Imagine reading a book.

Every time you want to edit one sentence:

• Photocopy the page 📄
• Write on the photocopy ✏️
• Replace the original page

Lots of unnecessary work.

✅ LOOP...ASSIGNING

Open the original book.

Write directly on the page.

Done. ✔️

No copying.
No replacing.
Much faster.

📊 Visual Comparison

LOOP...INTO	LOOP...ASSIGNING
📋 Copies each row into a Work Area	🎯 Points directly to the original row
Uses additional memory	Uses almost no extra memory
Requires MODIFY after changes	Changes happen automatically
Slower for large datasets	Faster and more efficient
Better for read-only or small tables	Best for updating large internal tables

💡 Interview Tip

A common interview question is:

Why is LOOP AT ... ASSIGNING faster than LOOP AT ... INTO?

✅ Answer:

Because ASSIGNING does not copy data into a work area. Instead, it uses a field symbol as a reference to the original table row, eliminating copy overhead and allowing direct updates without a MODIFY statement.

🎯 Easy Way to Remember

📝 INTO = Copy

Internal Table
      ↓ Copy
 Work Area

📝 ASSIGNING = Pointer

Field Symbol
      ↓
Internal Table

👉 Copy = More Memory + More Time ⏳

👉 Pointer = Less Memory + Better Performance ⚡

This is why LOOP AT ... ASSIGNING is considered the modern ABAP best practice, especially when processing or updating large internal tables in SAP S/4HANA projects.