Does version management for purchase contract require flexible workflow setup?

[Roumi]

Hello, I would like to set up version management for purchase contract which will be created via Manage Purchase Contract F1600A app (SAP S/4HANA 2023, On-premise). I am going through the menu below to set it up, but versioning is not triggered.

If I do the setup via the 'old' menu, i.e. Set Up Version Management for External Purchasing Documents, I get the versions generated (for changes via the app and also GUI), but Manage Purchase Contract app is still not showing the Version history tab.

I am wondering what is the right way to set up versioning for documents using the app. Do I have to set up a workflow?

I saw in SAP documentation that I have to 'Ensure the flexible workflow is activated before enabling versioning for purchase contracts.'

On the other hand, SAP note 3252885 says: 'Version management is not integrated completely with flexible workflow in MM Purchasing Business Objects such as PO, PR, Contracts, etc. It has not been considered in the integration as many MM Purchasing Fiori apps such as ‘Manage Purchase Orders’ does not support the classic version management..' 

So, I am a bit confused which one is the right way...

Regards,

Roumi

[Lakshmipathi]

SAP Note 3252885 clarifies that version management is not fully integrated with flexible workflow or Fiori apps like F1600A. Even if versions are created in the backend, the Fiori UI does not display them. This is not a configuration error — it’s a functional gap in the app.

SAP documentation says: “Ensure flexible workflow is activated before enabling versioning.”  Version Management in Purchase Contracts  This means you must activate flexible workflow for contracts. But even with workflow active, version history may not appear in the app UI.

Go to ME33K or ME3N to view version history. Backend versioning works reliably here.

With CDS view I_PurchaseContractVersion, build a Fiori Elements app or embedded analytics report to expose version data.

[Roumi]

Thanks for taking the time to suggest a solution! However, seems that the backend versioning works (should be activated, of course) independently of the workflow activation. And as you have guessed, no version history appears in the app. So, not really clear why the workflow is a prerequisite. I’m asking those questions, because I read the SAP training for Public Cloud, where Version tab was available in Manage Purchase Contract app. The user is also able to compare the versions within the app. I was hoping that this could be the case in On-premise/Private Cloud as well.