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

[Sheth, Neeraja]

Thanks for the input, Markus and Rob.
 
The release strategies for PR line items are defined correctly with =
OMGQ. It
is just that they get applied inconsistently. This is a random and
thankfully rare problem. It happened to a couple of PRs in the sandbox. =
 
 
In 3.1I,  to identify errors of omission early with newly created =
release
strategies, and to prevent workflow from being blamed for lines not =
showing
up in the approvers' inbox, I had created a background job that runs =
nightly
and sends an email notification to the MM analyst - a list of the PR =
line
items without release strategies. This would continue in 4.6C - so it =
will
catch the above inconsistencies as well.
 
Regards
 
Neeraja
 
> -----Original Message-----
>> From: Markus Brahm [SMTP:mbrahm at cscploenzke.de]
> Sent: Sunday, September 03, 2000 3:23 PM
> To:   SAP-WUG at MITVMA.MIT.EDU
> Subject:      Re: Release strategy not getting applied in standard SAP PR
> workf low in 4.6C
>=20
> Hello Neeraja,
>=20
> just to be sure. If those POs are old ones you can define by their =
release
> 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
> define
> this bey each status. This seems to be connected to the phenomen you =
had
> 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.
>=20
> Another aspect could be that the release strategy information is no =
longer
> updated online from release 4.0b on. As far as I remember there is a
> special
> menu item like "Get release streategy" or "Update release strategy
> information"
> which differs from the button concerning functionality.
>=20
> Cheers,
>=20
> Markus
>=20
>=20
>=20
>=20
>=20
> Rob Lake <Robert.Lake at uk.nestle.com> on 01.09.2000 09:58:29
>=20
> Please respond to SAP Workflow Users' Group <SAP-WUG at MITVMA.MIT.EDU>
>=20
> To:   SAP-WUG at MITVMA.MIT.EDU
> cc:    (bcc: Markus Brahm/PLZ/CSC)
>=20
> Subject:  Re: Release strategy not getting applied in standard SAP PR
> workf
>       low in 4.6C
>=20
>=20
>=20
> Neeraja,
>=20
> 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.
>=20
> There have also been some instances where this has happened with =
purchase
> orders.
>=20
> 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.
>=20
> Rob Lake
> Procurement and Supply Process Development, Nestl=E9 UK Ltd
> Tel: +44 (0)1904 604961, e-mail: Robert.Lake at uk.nestle.com
>=20
>=20
> -----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
>=20
>=20
> 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.
>=20
> 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'.
>=20
> 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.
>=20
> 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.
>=20
> I have looked up OSS notes but could not find one that applies to =
this
> situation.
>=20
> Has anyone come across this? Any idea on what I should be checking =
would
> help me a lot.
>=20
> Regards
>=20
> Neeraja Sheth
> Fujitsu Network Communications
>=20
>=20
>=20
>=20