SAP GTS 2025: SPL screening status governance moves out of transaction BP

Transaction BP is powerful, which is not always a compliment. Some decisions belong in a dedicated compliance workbench, where evidence and responsibility are harder to misplace.

The 2025 governance change clarifies the boundary between master-data maintenance and screening outcome handling. That boundary is where auditability lives.

Here is the project version: SAP GTS 2025 restricts changes to SPL Screening Status data in transaction BP. That sounds simple, which is how SAP topics lure us into underestimating them.

The stated control idea is straightforward: unauthorized changes should not be possible, and a block on a business partner already released should be handled through the Manage Partners - SPL Screening app.

The SAP evidence trail is less romantic: This is a governance improvement, not only a UI change. Transaction BP is a powerful master-data transaction. If compliance status can be changed there too casually, it becomes difficult to prove that screening decisions followed the correct process. In a clean demo this takes minutes; in production it asks for ownership, variants and a little courage.

Moving status handling into dedicated screening apps creates a clearer operational boundary.

This is where the support ticket usually starts: For business teams, the message should be: BP remains important for master-data context, but SPL decisions belong in the screening workbench. That separation improves auditability and reduces the chance that master-data maintenance accidentally changes compliance status. The screen is only the stage. The process is the plot.

The control angle is the part worth underlining: For consultants, this requires role review. Users who maintain partners do not automatically need authority to change screening outcomes. Users who manage screening outcomes need training on audit trail, reason codes, comments and escalation. A consultant should be able to explain this without opening a thirty-slide apology deck.

For training, the useful lesson is this: A good support checklist asks where the status was changed, by whom, through which app, with which reason and with which audit evidence. The new governance model makes those questions easier to answer. That is the difference between technical navigation and knowledge people can reuse.

Not every user who can maintain a business partner should be allowed to bless one. SAP finally says the quiet part with a control design.