03-18-2024 6:35 PM - edited 03-19-2024 12:47 PM
Hey there!
we are facing the following issue when executing the ATC checks for S/4HANA readiness:
Object not checkable, due to inconsistent configuration: (3 Check Failures)
Check failures: (3 Check Failures)
Object Name:RSNAST00 Object Type: PROG
The SAP-owned namespace /0SJ1G/ is in scope. SAP objects cannot be checked in this case.
Object Name:V60A Object Type: FUGR
The SAP-owned namespace /0SJ1G/ is in scope. SAP objects cannot be checked in this case.
Object Name:V61B Object Type: FUGR
The SAP-owned namespace /0SJ1G/ is in scope. SAP objects cannot be checked in this case.
At least the 1st failure come from an enhancement.
We have not figured out where the other two check failures come from.
Additionally the mentioned namespace /0SJ1G/ seems weird, because none of the objects belong to this namespace.
The reason why we cannot ignore these check failures is, that it prevents us from selecting the check run with "Analyze result in ATC problems view". If we do, no findings will be displayed.
From our point of view there are not SAP-notes that fit to the problem.
System information:
SAP_BASIS 758
SAP_ABA 75I
Does anyone have a clue, what we could check?
The system says: the SAP-owned namespace is in scope. But how can this namespace be in scope if we explicitely select a different package in the check run and mark "Include Objects from checkable namespaces"?
Thanks for any hint!
/edit:
I know put the enhancements in a new package and excluded this package from the search run. Now there are no more errors. But: The findings cannot be displayed. I found out that the following error in eclipse ATC problems view occurred:
An internal error occurred during: "Displaying result in ATC Problems View".
System failure: "SQL error SQL code: 4 occurred while accessing table SATC_CI_CF_E_BASE_NAC." (For detailed information, check the generated short dump in transaction ST22 of system "F4S")
/edit2
it seems as if the error ocurred only once. there is still "Findings: None", but no error anymore.
I applied the following work around:
I put the enhancements in a new package and excluded this package in the check run settings.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Namespaces and enhancements in ATC - always fun! This is admittedly one of the most complicated parts of running ATC in a customer system, but let's see:
As for the error in ADT: I don't know what "SQL error code 4" for your database is, but the dump should tell you a bit more - it might just be a (temporary) problem with your database instead of anything wrong with the ATC. In any case, this is completely unrelated to the namespace problem, the table mentioned in the error message is for the storage of customized ATC priorities.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for your detailed comment, @BjörnJüliger ! at least your explanations fit to my expectations... 🙂 In my opinion it is an error of the check run which
Concerning the eclipse error: I aggree that this probably was a one time error due to some temporarily system incosistencies.
Review Object Dependencies: Since you've identified that at least one failure comes from an enhancement, review the dependencies of this enhancement. It's possible that there are other dependencies or related objects causing the additional failures.
Check Namespace Scope: Double-check the scope settings for the ATC check run. Ensure that the correct package or namespace is selected and that the "Include Objects from checkable namespaces" option is appropriately configured. It's possible that despite your selection, the SAP-owned namespace is somehow included due to misconfiguration.
Review SAP Notes: While you mentioned there are no SAP Notes directly addressing your issue, it's always worth reviewing the latest SAP Notes related to ATC, ABAP development, or your specific SAP modules. Sometimes, new notes addressing similar issues are released after your last search.
ATC Configuration: Verify the ATC configuration settings, especially those related to namespaces and object types. Ensure that there are no conflicting configurations that might inadvertently include SAP-owned namespaces.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
78 | |
9 | |
8 | |
7 | |
6 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.