Is CL_PRC_RESULT_FACTORY released for ABAP Cloud?

Use the released successor I_SLSPRCGCONDITIONRECORD instead of CL_PRC_RESULT_FACTORY for ABAP Cloud / Clean Core compliant development.

CL_PRC_RESULT_FACTORY

Q: What replaces CL_PRC_RESULT_FACTORY in SAP S/4HANA Clean Core?

CL_PRC_RESULT_FACTORY maps to the released successor I_SLSPRCGCONDITIONRECORD (CDS View), per the SAP Cloudification Repository.

DClean core level D — ReplaceSAP state: notToBeReleasedATC expected: internal API · priority 2 (warning)

Two questions, two answers. The level D above answers the clean core target question — what this object is worth in an ABAP Cloud target. Whether classic ABAP may still call it is a separate property, and it is the right-hand column.

ABAP Cloud view

Not to be released

SAP will not release it for ABAP Cloud. There is no level A use of this object.

objectReleaseInfo

Classic view

Not listed

The classification file does not mention it, so it says nothing either way.

objectClassifications_SAP

SAP names as successor

I_SLSPRCGCONDITIONRECORD

From objectReleaseInfo — SAP names this as the released replacement.

Released S/4HANA Clean Core successor for CL_PRC_RESULT_FACTORY.

Released successor

I_SLSPRCGCONDITIONRECORDCDS View

Repository state: notToBeReleased

Source: SAP official (Cloudification Repository)

See how your code uses CL_PRC_RESULT_FACTORY

This is the object-level answer. To see, per object, whether your actual ABAP can move to the successor or needs an architect — with evidence — run a free ABAP static code analysis.

Analyze free at clean-core.io

→ ABAP static code analysis → Clean Core object classification (A–D)→ What is the Clean Core Score?→ SAP cloudification explained → Clean Core guide (RAP vs CAP)→ Browse the full catalog