why SAP can put break-point everywhere

[Former Member]

Hi everyone,

I have a question about break-point in transfer rule. There is a break-point in transfer rule for a long time and we never have a problem. Today we are having a system memory problem, basis think this break-point took all memory. My questions are

1) why only today the break-point took all memory not other days

2) why SAP can put break-point everywhere in extractors/updaterules/ transferrules for debugging purpose?

Can you please help me to understand and answer these questions?

Thanks alot, Jin

[former_member187400 · Accepted solution]

Hi Jin,,

Yes Jin ,,, in my experiences break-point will consume the memory. Due to, BW will give resource to handle & execute that statement.

Perhaps, you used to not feel it, since your application is not bigger like now. Then, today, your application has got bigger, then you just felt it ..

One thing, you can do, you need to remove the break-point statement from your routine.

How can you know what routine the break-points statement stay is ..

Steps:

1. go to tcode: se16

2. type for RSAABAP table, execute it.

3. for the line selection, type : break-point, then execute it.

4. get the code ID column.

5. open for RSUPDROUT table (tcode: se16)

6. Using the CODE ID, get the UPDID from that table.

7. open for RSUPDINFO table (tcode: se16)

8. Using the UPDID, you'll get the routine where the break-point stays.

9. Go to that routine, then remove break-points statement.

Hopefully it can help you a lot Jin..

Regards,

Niel

• thanks a lot for the points you choose to assign.

[Former Member]

Hi Niel

Thank you so much for your quick reply, great information and help. You deserv more than 10 point (it's on your way).

Thanks again, Jin

[former_member187400]

Okay no problem..

btw, tks for your appreciation ..

Regards,

Niel.