cancel
Showing results forĀ 
Search instead forĀ 
Did you mean:Ā 

Large Technical Tables /AIF/PERS_XML

03-31-2026 3:33 PM
EUM_BASIS_TSMX Newcomer
776 views 2 comments
0 Likes
SAP Managed Tags
Subscribe

HI Team 

As part of RISE program SAP suggested the below recommendations

1.Transactions /AIF/MSG_DEL, /AIF/XML_COMPRESS , /AIF/PERS_DEL and report /AIF/MESSAGE_DELETION
2.Need to implement this SAP notes 2274361,2279909,3275559 to enable the required transactions-programs for compressing and deleting the XML messages
3.Only 3275559 note is revelent in our QAL system and can be implemented and the other 2 notes 2274361,2279909 are not applicable or not revelent
4.After applying the notes the given Tcodes, reports will be enabled.

Sine the given notes are not applicable could you please suggest the possible option or the correction notes to complet the recommendations

0 Likes

Accepted Solutions (0)

Answers (2)

Answers (2)

simon25
Product and Topic Expert
Product and Topic Expert

Hi,

HANA Database Support maintains the tools and reports for as many of these tables as possible in KBA 2388483 - How-To: Data Management for Technical Tables

With SAP standard technical table cleanup, this is still is under the expertise of the SAP product owner and support team.
In this case for "/AIF/PERS_XML" that would be these teams for "Application Interface Framework"

  • CA-GTF-AIF (Application Interface Framework)
  • BC-SRV-AIF (Application Interface Framework)

So you should open a support case with them if you need assistance on the application process for data archiving of this table.

Kind Regards
Simon

LPhilip
Product and Topic Expert
Product and Topic Expert
0 Likes

/AIF/PERS_XML stores the raw XML payload of AIF messages.

The notes "Not applicable" usually just means the fix is already included in your current SP level. You can verify in your system whether transactions /AIF/MSG_DEL, /AIF/PERS_DEL, /AIF/XML_COMPRESS or report /AIF/MESSAGE_DELETION exist or not.

You can go to SE16 → /AIF/PERS_XML and check which Namespace/Interface owns the most rows, and how old the oldest records are.

Then choose to archive or delete the relevant interfaces' messages.

Better to archive (instead of delete), which reduce the table size while keeping data accessible for audit purposes if needed.