If there is change in PO header text after Releasing PO,version Management is not deactivating & release Stratergy is not reset again. can u guide me how version & release strategy will work .
While maintaining Release indicator "6" in PO release strategy . PO release strategy is reset only when changes in Qty & price.
Please give me customization setting for version management & release stratgy.... if there is small changes in po heder text
version management & release strategy should be reset.
If i will change in PO header condition then also version is not activated. i have to add that manually. mine client requirement is like that if there is any small chnge in PO, version should active automaticallly not manually. what is the customizing for version management.
first update the verion management path is mm-purchase-version mngt
this updation with based on the purchase organization.
when ever you make the po, if release strategy is activated , once you release the po version management is updated.
if any chages in po version status will be updated. both is linked with purchase organization.
Version management & release strategy is activated for the PO but the problem is, when qty & price is changed for the PO then only New version is activated & relese PO get cancelled but I want small change in PO new version should be activate automatically.
Ex- If i chage header condition or Header text new version should be activate but its not possble.
Please give proper way if change in po,new version should be activate.
Thanks for your reply,
Mine problem is solved. In customizing Purchasing /Messages/ Text For messages / Define Text for Purchase Order
was not maintained for PO Document type thats the reason after change in PO header text ,PO was not getting trigger for next version
Now i am facing problem for release strategy, after change it is not getting cancelled & rereleased.
Please suggest me any proper solution.
Release strategy change is not possible if header text is edited. You may have to use your own user exit for the same. You may build a logic by stating that whenever if the version number changes, reset the existing release strategy.
Use ehancement M06E0004 for deriving your own logic.
If header text changes we cannot capture in std version management setting.
If they wanted to capture the text field changes there are two ways are there.
1. ask your abaper to display for other user and give any one user to edit it.
2. If changes are done in the text level ask your abaper to trigger a mail to the higher levels through enhancement.
Standard setting its very tough to capture
If both the Version management and the release strategy is maintained in the PO then the Preference is given to the releasing the final version before the release of the PO.
In case the version is not set for release manually the PO can not be printed/mailed/faxed. Once the user sets the version complete indicator then the PO will get printed.
The PO mail/fax/print will not go even if the release from the release strategy is complete and Version is not released.
This may solve your problem as you can ask the client to release the version only after all the changes are done in it and then ask for the complete release.