SAP Knowledge Base Article - Preview

3563946 - SCI/ATC uses class moniker "O" instead of "X" when self-scanning

Symptom

You are using central ATC with remote analysis to scan various systems. Your central ATC system scans itself via destination NONE. You have noticed that the ABAP Naming Convention check does not handle Exception Classes correctly. You have noticed that class CL_CI_TEST_ABAP_NAMING_NEW - executed via SCI or ATC - should report as correct. Yet the check wants to use "O" (general class moniker) instead of "X".


Read more...

Product

SAP NetWeaver Application Server for ABAP innovation package all versions

Keywords

ATC, Remote, Analysis, NONE, ABAP Naming Convention, CLASS-DATA AX_AUTH_ERROR, CL_CI_TEST_ABAP_NAMING_NEW, Class Moniker , KBA , BC-ABA-LA , Syntax, Compiler, Runtime , BC-DWB-TOO-ATF , ABAP Check Frameworks - ABAP Test Cockpit, Code Inspector , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.