cancel
Showing results for 
Search instead for 
Did you mean: 

Handling SKA1 Warnings in Custom Code Post S/4 Migration

ruxixon
Discoverer
0 Kudos
124

Dear SAP Community Members,

I am seeking advice on an issue encountered after migrating our systems to SAP S/4HANA and analyzing the code with the ABAP Test Cockpit (ATC). After the migration, numerous warnings have appeared regarding the use of SKA1 in the custom code developed for our client, which was adopted from an ECC machine. I have reviewed the SAP notes 2431747 and 2389136 related to these warnings. While I understand the impact of now having secondary cost elements within SKA1, I am unsure how to resolve these warnings.

A new field, GLACCOUNT_TYPE, has been added, which I believe should be neccesary to exclude the secondary cost elements that now appears in SKA1. Despite modifying the code, the same warnings persist when re-running the ATC.

An example of basic consult with errors in ATC:

  SELECT ska1~ktoplska1~saknrska1~vbund
    FROM ska1
    INTO TABLE lt_ska1
  WHERE  ska1~ktopl IN lr_ktopl AND
         ska1~saknr IN lr_saknr AND
         ska1~vbund   NE space
    ORDER BY PRIMARY KEY.

Has anyone experienced this issue and found a way to resolve it without resorting to pseudocomments? Any insights or advice would be greatly appreciated. At this moment, the use of CDS entities is not contemplated at this stage of the project.

Thank you very much in advance for your time and assistance.

Kind regards,

Ruxixon.

Accepted Solutions (0)

Answers (1)

Answers (1)

raymond_giuseppi
Active Contributor
0 Kudos

To get same result than in ECC, exclude secondary cost account (SKA1-GLACCOUNT_TYPE 'S')