Professional Documents
Culture Documents
Login / Sign-up
Former Member
March 14, 2016 5 minute read
Applies to:
ECC6.0 Version
Summary:
This article is helpful for Consultants in SAP MM specifically working in procurement Area. The document mainly deals with the
analysis of the behaviour of SAP system when three different configurations in SAP MM such as Version Management, Release
strategy and Output messages are in place.
Author: Prabhullachandran R
Author Bio:
Prabhullachandran R, a SAP Certified Materials Management Consultant has total 10 years of experience out of which 9 years in
SAP consulting in Procurement, Inventory Management and Country India Version. He has got expertise across various
industries such as Construction, Pharmaceutical & Manufacturing sectors. Throughout his career he has gained sound
knowledge by working in Companies like IBM, TCS, RP TECHSOFT, and COLLABERA.
Scholastically he has secured first class in Master of Technology in specialisation with Production & Industrial Engineering under
Mechanical Engineering Department of Mahatma Gandhi University, Kerala.
This Document depicts about the behaviour of the SAP system or how the integration works when a combination of three
different customisations with in SAP Materials Management such as Version Management, PO message settings and Release
strategy configuration are in place. The Document reveals how these different settings complement each other while Create or
Change or Release or Output a PO.
Process steps:
While creation Version Number = 0 and in Completed status. No need of activity in Version tab when the version = 0 as
subsequent versions meaningfully occurs only when the document is released.
Messages will be automatically generated as the condition records were maintained correctly in MN04 transaction code.
Triggering of new versions and Cancellation of releases will be applicable in PO based on the nature of changes and when the
changes are happened.
Case 1: Change in PO quantity to a higher value, after PO fully released and before the document gets
outputted.
Click on
Even though Quantity and subsequently value got raised, existing release will not get cancelled until the version completed
indicator is ticked manually for the latest version.
Case 3: Change in PO quantity to a lower value, after PO fully released and the document gets outputted.
Even though Version completed activated, Release strategy will not trigger, but new output will be activated.
As per standard SAP behaviour, Quantity/ price changes which are in to lower level which falls in the same release strategy
will not cancel the existing releases.
Case 4: Change in PO Delivery date, after PO fully released and the document gets outputted.
Case 5: Text creation or changing, after PO fully released and the document gets outputted.
Case 6: Material code change for the same quantity and same value, after PO fully released and the
document gets outputted.
Finally my analysis was on how system behaves when the whole material code itself got changed but the price and quantity
remains the same.
10000057 changed to 10000943 but quantity and effective price remains same.
By changing the Material code having same value and quantity in PO system triggers for version change
Releases will not reflect on this change even after checking version completion indicator.
Conclusion:
Version management, Release strategy and Output messages are different configurations in SAP MM but their behaviour in the
system has some dependencies.
Assigned tags
View more...
Related Blogs
Simple from the Source: Ariba Integration with SAP ERP now with SAP Best Practices for Sourcing and Collaborative Supply Chain
By Karsten Manske , Invalid Date
Simple from the Source: SAP Business Suite integration with SAP Ariba Solutions now with SAP Best Practices for Ariba’s Quote Automation and SAP SRM
extended classic integration
By Karsten Manske , Invalid Date
Related Questions
3 Comments
Former Member
Vikram Swain