ABAP Test Cockpit(ATC) – Introduction and Steps

We take care of ABAP Test Cockpit Arrangement and Exception Proces is one of our HANA ABAP Instructional exercise. In this article and in coming series, we would jump profound into ATC process and further more investigate SCI and SCII. I’m certain, these subjects would come exceptionally convenient to all ABAPers who are sharp into the quality course of SAP ABAP and furthermore needs to prepare their code for HANA data set movement. ABAP Test Cockpit – Introduction and Steps.

Benefits of using ABAP Test Cockpit – Introduction and Steps:

ABAP Test Cockpit is SAP’s toolset for overseeing ABAP quality checks halfway.
ATC depends on the SAP Code Overseer motor, so all SCI checks and variations can be reused. ATC will consequently utilize SCI+ rather than standard SCI assuming SCI+ has been executed.
Required implementation of a quality passage.
Incorporated into the ABAP workbench.
All check results are accessible by means of a focal revealing system which has channels and collections
Has a powerful interaction for overseeing exclusions and special cases.

Functions available in the ATC tool are differentiated by roles:

Administrator
- Perform one-time setup tasks such as ATC check run schedules and jobs
Quality Assurance (QA) Lead
- Define check variants
- Monitor check runs
- Approve or reject exemptions
Developer
- Correct bugs or request exemptions

Roles needed

Admin Users need to have role SAP_SATC_ADMIN
QA Leads need to have role SAP_SATC_QE
Developers will be able to use the tool and apply for exemptions if they have S_DEVELOP, ACTVT 02 or 03
S_Q_ADM and S_Q_GOVERN are additional authorizations if required.

Initial Configuration – Maintain Check Variant (ADMIN)

Transaction Code : ABAP Test Cockpit – Introduction and Steps

The subsequent stage is to arrangement the essential design utilizing the Arrange ATC choice. Check Variation from the past screen is placed and framework ID is kept up with as own framework ID. Conduct on transport discharge is set to Obstruct on Mistake (can likewise be set to Caution on blunder).

Subsequent stage is to keep up with the rundown of Value Approvers. Just those clients can be added as approvers who have important QA Lead approval.

Run SE03 exchange and afterward go to Worldwide Modifying. Set “Really take a look at Items when Solicitation Delivered” choice to “Worldwide Enacted” (default esteem is “Set by Client”) and save.

TR release (Developer)

While endeavoring to deliver a vehicle which contains ATC/SCI blunders, the mistake message “Items contains blunders and in this manner can’t be delivered” is shown.
This gets set off just during the TR discharge. The singular errands can in any case be delivered however can be come by executing an exemplary BADI CTS_REQUEST_CHECK.
The accompanying connection shows something similar: CTS_REQUEST_CHECK

Setting Up Scheduled Runs / Central Results (ADMIN)

Framework wide booked runs of ATC can be arrangement by utilizing the “Timetable Runs” choice and tapping on “Make”. The name of the booked run can then be given. In the accompanying design screen, the SCI variation name and the extent of the Focal Outcomes can be confined (by bundle/transport later/programming part).

Triggering Central Results Run (ADMIN)

Select the Focal Outcomes run recently made and click on Time
Select really take a look at box to show this is the Focal Actually look at run (other booked runs may likewise be planned for a particular use which may not be the Focal run). Then, at that point, click on Execute to set off a one time promotion doc Focal Run.
A bunch occupation might be arrangement through SM37 for occasionally executing the above characterized ATC Focal Run by booking program SATC_CI_CFG_SERIES_SCHEDULE behind the scenes.

Monitoring Central Runs (QA Lead)

From the ATC principal screen picked the Screen and Control Runs choice
Enter choice rules as required and afterward execute to see current and past Booked Runs

Viewing results of Central Runs (QA Lead)

Select the Focal Outcomes run and afterward click on Outcome to raise the itemized SCI report
Utilizing channels and the Measurements View choices, the outcome rundown might be reduced as required

Viewing results of Central Runs (Developer)

Go to the SE80 exchange. Click on Utilities menu > Settings. Go to the Workbench (general) tab and empower ATC Result Program. This will empower ATC Result Program to show up in SE80’s left sheet.
By utilizing this choice, current and past focal runs might be perused.

Applying for exemption (Developer)

The designer might demand to apply for an exclusion on the off chance that any SCI finding is a bogus positive or not legitimate in a specific setting. Exceptions ought to be applied for just when any remaining legitimate SCI discoveries have been shut by the engineer.
Select the mistake message for which exclusion is mentioned and click In plain view subtleties.
This will raise a Subtleties sheet on which the “Apply for an Exclusion” interface must be clicked.

In the principal screen, notice the extent of the exclusion.
Kindly note that the accompanying exclusion will apply to all events of the actually look at message in the Sub Item/Article. It is absurd to expect to apply for explicit events of the message thus all substantial events of the check message should be shut prior to applying for an exclusion
In the following screen pick Approver, Reason (Misleading Positive or Others) and give avocation text. Click Total.

Approving Exemptions (QA Lead)

Goto ATC exchange and utilize the Exception Program choice.
Enter proper determination measures and execute.

Select fitting Exclusion and snap on Cycle. It is firmly prescribed not to straightforwardly tap on Support button since Legitimacy Date won’t get set.
Click on Switch Alter Mode in the base sheet.

Significant: Enter a Legitimate Until date (generally task delivery date) and tap on Support.
On endeavoring to deliver the assignment once more, it will be seen that the ATC Results list has lesser number of mistakes.

Frequently Asked Questions

Is ATC supplanting SAP Code Reviewer?
No, ATC is a system or toolset that implements code quality control utilizing the SAP Code Examiner (SCI) motor as it were. It guarantees the utilization of SCI and can be designed to quit shipping a program with blunders that are not endorsed by undertaking’s quality lead/commentator. The checks are performed utilizing the Check Variation made in SCI.
Is ATC accessible and can be utilized additionally in non-ECC frameworks?
Totally, all SAP frameworks that have SCI will likewise have ATC beginning from some adaptation post-Sep 2012. ATC will work in this large number of frameworks utilizing the SCI motor.
Assuming that code blunders found by SCI are smothered utilizing pseudo remarks (“#EC Remarks), will it appear in ATC Exemption list?
No, since they additionally won’t appear in the SCI device by the same token.
In the case of during the survey, one specific Mistake is Absolved by the analyst, then will it consequently Excluded all event of a similar Blunder?
Indeed, it will exclude all events of the very blunder that are right now present or may happen later on in a similar sub-object. This is a SAP constraint (SCN post). So as a workaround, it is basic to utilize the Legitimacy Date highlight while giving exclusions.
When Commentators endorse a specific example of an Exemption, then, at that point, does that should be re-supported each time during delivering transport for the code?
Indeed, assuming Legitimacy Date highlight has been utilized, all past exceptions should be re-endorsed. The commentators might sort by on the “first Found” section in the ATC Results Rundown for rapidly figuring out which blunders might have been recently presented.
Might ATC at any point be arranged to set off during Errand Delivery rather than CTS Delivery?
Indeed, a particular BADI must be carried out to enact ATC check while delivering an undertaking.
Might we at any point avoid In-Progress Improvements or remember For Progress Advancements just in the Focal Run?
No, all improvements protests that fulfill the Focal Run results channel will get gotten. In any case, in-progress can be sifted through in the ATC result list by determining the program names, client name or some other channel can be considered.
Could the Quality Lead/Commentator switch exception/dismissal choice taken prior on an exclusion solicitation, or change Legitimacy Date?
Indeed, Commentators might return to the Exclusion out of the blue and alter the solicitation to change status or Legitimacy Date.
When the designer has adjusted a current code, could we at any point request that ATC feature the Mistakes in the Delta code as it were?
No, ATC will continuously take a look at the full program/object/sub-object.
Could we at any point give Mass Exclusion for all ATC Blunders in a specific rendition of existing code and afterward command ATC for any progressions to the program?
No, giving exceptions to explicit occurrences is unimaginable. Once conceded, exclusions apply to all events of the blunder message in the whole sub-object.

Trust this article helped you in explaining a portion of the questions in ABAP Test Cockpit – Introduction and Steps Cycle. It is an extremely successful and valuable instrument for ABAPers and each designer ought to do the ATC really looks at himself/herself, prior to conveying the improvement object to the quality commentator and moved to the quality framework. All things considered, to give quality expectations to our client is one of the main objectives of any Execution Accomplice.

YOU MAY LIKE THIS

SAP ABAP HANA: Revolutionizing Enterprise Application

Introduction to SAP ABAP for HANA

Overcoming Common Challenges in SAP Implementations

5 Steps to a Smooth SAP S4HANA Migration