Release strategy not getting applied in standard SAP PR workf low in 4.6C
Markus Brahm
mbrahm at cscploenzke.de
Sun Sep 3 16:23:02 EDT 2000
Hello Neeraja,
just to be sure. If those POs are old ones you can define by their rele=
ase
status whether a new strategy should be worked out or not. You can for =
example
define that a new release strategy should never be worked out after the=
PO is
saved once or you can make it dependant on value changes etc. You can d=
efine
this bey each status. This seems to be connected to the phenomen you ha=
d with
copying the items. For Purchase requisitions the transaction to define =
this is
OMGQ, I don=B4t have the PO transaction at hand in the moment.
Another aspect could be that the release strategy information is no lon=
ger
updated online from release 4.0b on. As far as I remember there is a sp=
ecial
menu item like "Get release streategy" or "Update release strategy info=
rmation"
which differs from the button concerning functionality.
Cheers,
Markus
Rob Lake <Robert.Lake at uk.nestle.com> on 01.09.2000 09:58:29
Please respond to SAP Workflow Users' Group <SAP-WUG at MITVMA.MIT.EDU>
To: SAP-WUG at MITVMA.MIT.EDU
cc: (bcc: Markus Brahm/PLZ/CSC)
Subject: Re: Release strategy not getting applied in standard SAP PR w=
orkf
low in 4.6C
=
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 inconsis=
tency
in the way strategies are applied - different behaviour for different u=
sers,
creating a requisition item gives a different result to changing an exi=
sting
item to the same values.
There have also been some instances where this has happened with purcha=
se
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 fi=
ne,
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 line=
s 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 al=
l 11
lines.
If I change the purchase req so that a release strategy has to be reapp=
lied,
the correct release strategy gets applied to lines 20 - 50.
The problem is not consistent - If I copy the purchase req, the new pur=
chase
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 woul=
d
help me a lot.
Regards
Neeraja Sheth
Fujitsu Network Communications
=
More information about the SAP-WUG
mailing list