Skip to Content
author's profile photo Former Member
Former Member

Version management and release startegy

Dear friends,

I have implimented version mgt for purchase orders recently.My observations are:


--On saving the document first time –version “o” is created

--Version is created automatically

---Release strategy is triggered.

---Before release of release strategy, if any body is changed, changes are recorded on his user id and no new version is creating,all the changes before release are saved on version “o”.

--Till release of release strategy no new versions are creating but release strategy is triggering based on the value changes.


---Once the document is released, after that any changes are made in the document, then new version is creating, but version is not closing automatically.On saving the document, version is not closing.

That means on this same version other user can make changes.

When version is ticked(closed) manually, then only version is closing.

Once the release strategy is released, release strategy is triggered only on closing of the version check box manually, other wise release strategy is not triggering even on value changes.

Where as before implementing release strategy was triggering for every changes in value of the purchase order.

Now on implementation of Version management,before release of document,document is triggered to higher or lower levels for every changes in the value of the document,but after release of the document,release strategy is not triggering on value changes.If we are in the same version,

even though we change value,release strategy is not triggering.only after closing the version,then only release strategy is triggering.

We need to manually close the version on every changes after version “o” is created automatically.There is no problem with release strategy,already using for the alst 5years.

The above process described on release strategy after implementing the version management is the standard process/or any problem with this behaviour

Please suggest,



Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • author's profile photo Former Member
    Former Member
    Posted on Nov 30, 2007 at 01:47 PM


    Release procedure is working fine, there will not be any problem,



    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi Srinivas,

      Please suggest, after the version "O" is created we need to close the version manualy?.

      If the value is changed by any user and he does close the version,then release strategy will not be triggered,it is a business concern,is it a standard process.

      please suggest.

      And In IMG--Set up cahnge dispalys node, we need to enter all the field names of the purchase order?

      ---Ex: there are 30 fields are there including Header and item details,

      We have got 10 document types. That means every docuemnt type same 30 fileds are to be entered.


      Currently i have not entered any fields and testing but it is working fine,is it correct.

      ---If i want to enter,do i need to enter EKPO table and related fields of item details,

      and EKKO table and related fields for Header fields,under SET UP CHANGE DISPALY NODE in IMG.

      Please suggest.



Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.