topic Re: Transaction SAAB: ECC 5.0 / How does Assert ID works? in Application Development and Automation Discussions

Transaction SAAB: ECC 5.0 / How does Assert ID works?

Former Member — Tue, 02 Dec 2008 21:57:32 GMT

Hello,

Please advice what is difference between BREAK, LOG and ABORT in assertion activation tab?

Thanks,

Anand

Re: Transaction SAAB: ECC 5.0 / How does Assert ID works?

MarcinPciak — Tue, 02 Dec 2008 22:16:31 GMT

This is how the system will behave when reaching ASSERTION point.

If the condtion is not fulfiled (in ASSERT)

BREAK - will stop at this point, switching to Debugging mode

LOG - will create a log entry with an error and proceed with next statement in the program

ABORT - the executed program reaches runtime error ASSERTION_FAILED, causing dump of a program.

Re: Transaction SAAB: ECC 5.0 / How does Assert ID works?

Former Member — Tue, 02 Dec 2008 22:29:08 GMT

Please read the SAP online documentation from SAAB transaction itself.

There is well defined documentation is there.Just run the tcode and click on BLUE i button.in SAP manual there is all link available for all functionality.

Re: Transaction SAAB: ECC 5.0 / How does Assert ID works?

Former Member — Tue, 02 Dec 2008 22:40:29 GMT

Hi,

Even if I set to Break or LOG mode, it is still giving me a short dump. So I thought of asking this question.

Thanks and rgds,

Anand

Re: Transaction SAAB: ECC 5.0 / How does Assert ID works?

MarcinPciak — Wed, 03 Dec 2008 07:28:14 GMT

Hi Anand,

Make sure you have activated your checkpoint. You can do this in SAAB t-code or in directly in Debugger.

Regards

Marcin

Re: Transaction SAAB: ECC 5.0 / How does Assert ID works?

hassan_nia — Wed, 16 May 2012 05:56:00 GMT

REPORT zhan_test_log_point1 .
TABLES: vbak.
DATA: gi_vbak TYPE TABLE OF vbak.
DATA: wa_vbak TYPE vbak.
*
SELECT-OPTIONS s_vbeln FOR vbak-vbeln OBLIGATORY.
START-OF-SELECTION.
SELECT * FROM vbak INTO TABLE gi_vbak WHERE vbeln IN s_vbeln.
*
WRITE: / 'Here is the Start step'.
*                                            Log hole table:
* LOG-POINT ID zhan_log2 FIELDS gi_vbak.
LOOP AT gi_vbak INTO wa_vbak.
*                                            Log structure:
*    LOG-POINT ID zhan_log2 SUBKEY wa_vbak-vbeln FIELDS wa_vbak.
*                                            Log field:
    LOG-POINT ID zhan_log2 FIELDS wa_vbak-auart wa_vbak-ernam wa_vbak-erdat.
* You can't check Sy-subrc here
    WRITE:/ wa_vbak-vbeln.
ENDLOOP.
WRITE: / 'Here is the end of Log.'.

*---------------------------------------------------*

*Here is e.g. for an assert:

ASSERT id zhan_assert1 CONDITION sy-subrc IS not INITIAL. " Dump if SY-SUBRC is NOT initial.

* Here is e.g. for a break-point.

BREAK-POINT ID zhan_break1.