SAP Knowledge Base Article - Preview

3677531 - System not creating new version in t-code me32k after contract changes in SAP S/4Hana

Symptom

  • When updating a contract in t-code ME32K, the system does not prompt for a new version creation after changes are made.
  • Changed values are being overwritten in the current version instead of creating a new version.
  • The release strategy is showing as completely released, but the processing status remains as "03" (In release/approval).


Read more...

Environment

  • SAP S/4HANA 1709 
  • SAP S/4HANA 1809
  • SAP S/4HANA 1909
  • SAP S/4HANA 2020
  • SAP S/4HANA 2021
  • SAP S/4HANA 2022
  • SAP S/4HANA 2023

Product

SAP S/4HANA 1709 ; SAP S/4HANA 1809 ; SAP S/4HANA 1909 ; SAP S/4HANA 2020 ; SAP S/4HANA 2021 ; SAP S/4HANA 2022 ; SAP S/4HANA 2023

Keywords

me32k, version management, contract changes, processing status 03, release strategy, po release status, new version creation, sap note 3585478, sap note 664928, t-code me32k troubleshooting. , KBA , MM-PUR-GF-VER , Version management , MM-PUR-OA-CON , Contract , MM-PUR-GF-REL , Release (Approval) , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.