Break-point

[Former Member]

Hello senior ABAPers

i came across a situation where break- point is triggering in production system while its not triggering in development.i want to disable the break point for end users in production.

its a z program copied from standard program "stock on posting date ".

thanks.

[Former Member]

Hello senior ABAPers

i came across a situation where break- point is triggering in production system while its not triggering in development.i want to disable the break point for end users in production.

its a z program copied from standard program "stock on posting date ".

thanks.

[PeterJonker]

Well why is the break point there ?

Was it hardcoded in the z program ? Then it will be best to delete it again and move the changed program with a transport.

Unless you have assigned the break pint an ID (Checkpoint group) then you can disable the break point with transaction SAAB

[Former Member]

Thank you so much Peter.

i guess production is open. anyways i moving the change.

[Former Member]

hi faizur rahman,

well then it looks like its getting time to close the production again...

Because normaly you would not need to copy a z-report from production to development system as mentioned in your post Not able to delete text elements.

Did you already check if the different triggering is caused by different code in production and test-system.

Maybe you should rebuild your development system soon...

If not, you can never be sure that the code in production is the same as in development...

regards

Stefan Seeburger

[Former Member]

Elaborate on the technical details. SAP standard program name where copy was taken.

Is there any break point statement used in your Z program? How is it used? any checkpoint group active?

[Former Member]

1. Standard Tcode MB5B.

2. Yes, several break-points are used in z program with ID mmim_rep_mb5b. But those are not triggering. Break point without ID is triggering in production.

[SuhaSaha]

faizur rahman wrote:

several break-points are used in z program with ID mmim_rep_mb5b. But those are not triggering.

MMIM_REP_MB5B is a Checkpoint group. You can control the behaviour via SAAB (T-code). I use the statement BREAK-POINT ID in complex programs (and definitiely in an implicit enhancement), it eases my efforts during debugging.

Read the F1 documentation for BREAK-POINT statement.

Break point without ID is triggering in production.

Did you not perform the ATC,SCI checks on the code before moving it to production?

[former_member202771]

Hi Faizur,

Check the possibility of break-point in within IF condition.

thanks,
Anil

[Former Member]

hahaha! nice idea.

if 1 = 2.

break-point.

endif.

I suppose, this is what you meant.

But my primary concern is not removing break-point.I wanted to know,under what circumstances a  break-point trigger in Production system.

thanks

Faiz

[former_member202771]

I had a similar issue. reason was below if condition.

T331-USAUS :Stock removal strategy via user exit

this key can be maintained for a combination of Storage type and Storage type via view V_T301.

So was suggesting if there is similar kind of issue in your case.

Thanks,

Anil

[Former Member]

Just comment that line in source code!

Mario