Variants:
1. BREAK-POINT.
2. BREAK-POINT f.
1. BREAK-POINT.
2. BREAK-POINT f.
Variant 1
BREAK-POINT.
Effect
The BREAK-POINT statement interrupts the processing and diverts the system to debugging mode. You can then display the contents of all the fields at run time and also control the subsequent program flow.
If the system is unable to branch to debugging for some reason (due to a background job or update), it generates a system log message.
If the system is unable to branch to debugging for some reason (due to a background job or update), it generates a system log message.
- After the BREAK-POINT , the system automatically performs any restart in the database, if no COMMIT WORK was executed. Since debugging sometimes switches off COMMIT WORK , you should not place a BREAK-POINT statement in a SELECT loop.
- In the editor, you can also set a breakpoint dynamically without making any changes to the ABAP/4 program. These dynamic breakpoints are valid only for the current user in the current session.
Variant 2
BREAK-POINT f.
Effect
Behaves like variation 1, except that the field contents of f remain in the event of any system log messages.
RELATED POST
SAP architecture,its full form of working and enjoy sap products
SAP journey from R/3 towards MySAP.com
RELATED POST
SAP architecture,its full form of working and enjoy sap products
SAP journey from R/3 towards MySAP.com
No comments :
Post a Comment