Release strategy not getting applied in standard SAP PR workf low in 4.6C

[Rob Lake]

Neeraja,
 
I can't offer a solution but we have noticed similar behaviour in 4.6B. =
 One
of my colleagues has been investigating it and has found total =
inconsistency
in the way strategies are applied - different behaviour for different =
users,
creating a requisition item gives a different result to changing an =
existing
item to the same values.
 
There have also been some instances where this has happened with =
purchase
orders.
 
Can anyone shed any light on this?  I know that strictly speaking this =
isn't
a workflow problem as if the strategy is applied, the workflow works =
fine,
but users don't always see the distinction.
 
Rob Lake
Procurement and Supply Process Development, Nestl=E9 UK Ltd
Tel: +44 (0)1904 604961, e-mail: Robert.Lake at uk.nestle.com
 
 
-----Original Message-----
From: Sheth, Neeraja [mailto:Neeraja.Sheth at fnc.fujitsu.com]
Sent: 31 August 2000 17:01
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Release strategy not getting applied in standard SAP PR
workflow in 4.6C
 
 
We are in the process of upgrading to 4.6C. One of the users has raised =
a
critical issue in the 4.6 sandbox : Release strategies are not getting
applied to purchase requisition line items.
 
Example:
A purchase req with 11 line items with exactly the same characteristic
values was assigned a release strategy to lines 10, 60-110 whereas =
lines 20,
30, 40 and 50 were not assigned any strategy. If I try to get release
strategy information, I get the pop-up saying 'Item xx not covered by a
release strategy'.
 
Our release strategies depend upon document type/purchasing group/MRP
controller/material group/value - the same strategy is applicable to =
all 11
lines.
 
If I change the purchase req so that a release strategy has to be =
reapplied,
the correct release strategy gets applied to lines 20 - 50.
 
The problem is not consistent - If I copy the purchase req, the new =
purchase
req has all 11 line items with the release strategy applied.
 
I have looked up OSS notes but could not find one that applies to this
situation.
 
Has anyone come across this? Any idea on what I should be checking =
would
help me a lot.
 
Regards
 
Neeraja Sheth
Fujitsu Network Communications