Release Strategy trigger for Any changes in PO?

[Former Member]

Dear Experts,

1. I am using version management and I have activated some fields for versions, I have requirement to trigger the release strategy for any chagnes in PO, how to achieve that?

2. Second is related to version management...when I am making changes in Header Text (PO Text type) then it is creating a new version but when I am making changes in Header Note then the version is not triggered, I am not able to understand what table and field should be activated for all these text types (header text, header note, pricing types, vendor memo etc) because we have an requirement that the version should be triggered if there are any changes in any type of texts at Header level as well as item level, please advise me how to achieve it or what to be activated for that??

Thanks in advance for your valuable help and suggestions.

Regards,

Anoop Singh

[former_member450554]

Hi Anoop,

It can easily be achieved using workflow. You need to associate the changes by triggering an event ‘Changed’ of the relevant business object. Then link this event using transaction SWETYPV – Event Type linkages to any workflow task or function module. Take help of an abaper.  Also ask the abaper to put a check on the changes like release; else it will be an endless loop.

Regards,

Ashish Kale

[Former Member]

Dears,

I have configured version management and release strategy, in release strategy I have created a new characterstics as REVNO for version and I have entered versions 0 to 4 in strateg. But still the release is not triggering when a new version is triggered, release strategy only getting changed in case of value changes. My requirement is if the PO is approved and someone make changes then version is triggering and along with version the release strategy should also be re-triggered.

Please advise me if I am missing something. You valuable inputs are appreciated.

Regards,

Anoop

[Former Member]

Hi,

for header note...

Goto messages in SPRO & click the text for messages --> define text for messages --> header operation 2 & text id F01 delete if you don't want to generate version for changes made in header text, thru ME22n.

Regards,

[Former Member]

Hi,

Sorry I thought U don't want to generate version.

To generate version for all changes, you must add those fields as print relevant changes.

Version will be generated for change in address, master conditions, account assignments.

Regards,

[Former Member]

Hi Raju,

Thanks for quick reply.

What I should activate for all these text types in header (such as header text, header note, vendor memo) because I am not able to find any field name for these text types or the table because we need to enter the table name and field name in fields relevant to print out of changes.

Please advise me on that so I can activate it for all text types in PO header so if any changes done in any header text type will generate a version?

[Former Member]

Hi Anoop,

Whatever entries are there in operation 1, just add those as operation 2 with same details, because as you know 1 is new (create) and 2 is for change.

Regards,

[Former Member]

Hi Raju,

Please also advise me on if I make any changes in PO it should trigger for release. How to achieve it? Any changes in PO should trigger release procedure?

[Former Member]

Hi Anoop,

It depends on your final release indicator. If it is configured as new release strategy in case of changes/outputted", then automatically release strategy re-set/re-triggers. Also note the you have to complete the version to re-trigger the release strategy.

Regards,