T-Code SAAB for SAP ABAP Checkpoint Group
Let’s go on SAP ABAP Checkpoint Group. On the off chance that changes are made to the code, there is no assurance that past suppositions are fulfilled. SAP ABAP designated spots can be utilized for ensuring that program rightness is kept up with. Under designated spots, we think about Declarations, Breakpoint, and Log focuses.
Attestations can be utilized for working on the nature of programming. Breakpoint and Log point are utilized for exploring program conduct if there should arise an occurrence of issues. They help in understanding and keeping up with the code.
The exchange SAAP has been there for a long while however it is a pity very few ABAPers know about it. Subsequently we figured relatives ought to be aware of this helpful apparatus. Slow on the uptake, but still good enough. It is a particularly helpful device, which could try and be valuable in the genuine creation climate. SAP ABAP Checkpoint Group.
Designated spot Gathering
The enactment condition of all designated spots which can be actuated is constrained by the designated spot bunch.
Affirmation
Allow us to consider a situation where cash is moved starting with one record then onto the next. Here, the amount of the two adjusts should be equivalent when move. Straightforward Money. Isn’t that so? With the assistance of statement, we can actually take a look at this condition. It is an explanation which we can place in the program portraying a particular condition.
language structure 1 – State legitimate articulation.
During program execution, on the off chance that articulation falls flat, execution can be halted. Program execution can be come by raising ASSERTION_FAILED.
punctuation 2 – Declare ID designated spot bunch CONDITION intelligent articulation.
In the event that ID articulation is utilized, declaration enactment and its way of behaving is controlled from outside the program by designated spot bunch in any case it is consistently dynamic.
How to create Checkpoint group?
Checkpoint group can be created using SAAB transaction.
Enter Name and tap on make. Save it.
If it’s not too much trouble, note – Naturally Declaration is Dormant as displayed underneath in the Attestations outline.
Let us write a very basic program and execute it in SE38.
REPORT ElearningCheckPoint. DATA : lv1 TYPE c VALUE 'A'. DATA : lv2 TYPE c VALUE 'B'. INITIALIZATION. LOG-POINT ID zcheck_pt FIELDS: lv1,lv2. START-OF-SELECTION . lv1 = 'X'. lv2 = 'Y'. LOG-POINT ID zcheck_pt FIELDS: lv1,lv2. WRITE 'Run.. Done'. ASSERT ID zcheck_pt CONDITION lv1 EQ lv2. BREAK-POINT ID zcheck_pt.
Execute the program. It would run successfully and write the output “Run.. Done”.
Case 1 – Abort
Presently, go to exchange SAAB. Select radio button Cut short in Affirmations casing and save the Designated spot Gathering.
Presently, execute the program once more. You will get a dump depicting the position where Declaration is disregarded.
You can most likely see the landfill in the ordinary t-code ST22. In any case, our point in this article is to see the Sign in SAAB T-code where we made the Designated spot.
Case 2 – Log
To begin logging, we want let the SAAB T-Code know about our aim. We want to pick the Log radio button (as displayed beneath) in the Statements (Forefront) segment.
You can see the log subtleties with Variable qualities, which would be extremely helpful in situations where we can’t repeat the situations in Quality or Improvement box – to pursue the strange missing qualities.
PS: If you do not see the above log, choose the Log radio button in Assertions frame and re-run your program.
Case 3 – Break
At the point when you select Break choice you will get following spring up which is only a data.
What does the above information mean?
Ans: In the typical case, the program is intruded on and the debugger is begun. In the event of foundation handling, there are two decisions. It will act like Log mode or Cut short mode relying upon what is chosen in the above spring up. Of course it is Log, so in Foundation handling mode, the program wouldn’t go into troubleshoot mode, however designated spot gathering would log the issues.
Very much like Declarations; Breakpoints and Logpoints can be initiated by choosing Break and Log individually.
BREAK-POINT:
Break Point can be actuated by composing following code in your program.
BREAK-POINT ID <Checkpoingroup>.
Dynamic breakpoint acts same as a Consistently Dynamic breakpoint. If there should arise an occurrence of foundation handling, activatable breakpoints are essentially overlooked. Run the Program in the frontal area, you can see the program drop by at line 30.
LOG-POINTS:
Log Point can be made dynamic by composing following code in your program.
LOG-POINT ID <Checkpoingroup>
Logs can be utilized to distinguish or examine the framework conduct. Variable qualities can be logged with the goal that the designers can dissect those qualities.
You can include your program explanation LOG-POINT ID ZCHEECK_PT. You can likewise utilize the accompanying linguistic structure.
Run the program and go to exchange SAAB. Go to tab ‘LOG’. You will see following subtleties which will assist you with investigating project’s way of behaving.
Above articulation log the worth of field ‘log’. We can log up to 32 fields.
You can utilize SUBKEY expansion to forestall the development of a gigantic measure of information in the log. All log events will deliver one record for a similar SUBKEY. Just last event should be visible however the counter will be increased.
LOG_POINT ID ZTRY SUBKEY ‘TEST’ FIELDS log.
Checkpoint group activation can be done with three levels
- Personal Activation – Designated spot gathering will be dynamic for current client as it were.
2. User Level activation – Designated spot gathering will be dynamic for all characterized clients.
3. Server level Activation – The Same way we can characterize servers for which it will be dynamic.
This was my unassuming work to carry your notification to this straightforward yet exceptionally incredible asset which each ABAPer ought to utilize. I know, this exchange SAAB ought to have been presented quite a while back. In any case, consistently you find a genuinely new thing in SAP. Kindly beginning utilizing it and let me know as to whether you face any issue. I would attempt to answer your questions.
YOU MAY BE INTERESTED IN
ABAP on SAP HANA: ATC – ABAP Test Cockpit Setup & Exemption Process