Skip to Content
Former Member
Jun 16, 2009 at 03:06 PM

Transporting Purchase Requisition Release Strategies



I was previously updating purchase requisition release strategy data (release codes, prerequisites and release statuses) manually by opening clients. However, I have recently started transporting these updates automatically between DEV, QAT and PRD environments. The classification data for each strategy is being updated via ALE.

This all seemed to be working welI until I yesterday when I created a new strategy with only one release (approver) code. The strategy was functioning properly in our DEV environment. But when I transported and tested it in our QAT environment, it pulled in four additional release codes that are not configured.

Where are these addtional approvers coming from, how can I omit them from this strategy and prevent this from happening in the future?