Skip to Content
avatar image
Former Member

Promotion Manager Best Practices

Hi,

I have only recently started looking at using Version Management in tandem with Promotion Management. I don't think this feature is widely known. Basic workflow:

- Create your promotion job

- Add the job to VM. This automatically checks in all the objects in the job in to VM

- Do a 'Get Latest Version' on the job. The source of that job now changes to 'From VMS' and indeed objects will be moved from the VMS rather than the CMS when the job is run.

In this way your source objects are static. You can run the job once in to Test say and then at a later date run the same job in to Production knowing that no one can possibly have made changes to any of the objects in between.

The only shortcoming of this is that the check-in of the objects happens from the local system in to the same VM system as the job. As a result, to use this functionality, you have to run your Promotion Management from your Development environment.

This appears to go against other SAP best practice which recommends having a separate system for Promotion Management or running it in Production, or Test, with Development being the last resort.

So I guess what I'm looking for is confirmation that I have got this right and that use of this rather neat feature is mutually exclusive with running your Promotion Management from a separate system or in Production.

Many thanks,

Mike

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

0 Answers