"Item not covered by a release strategy"

[Sherman S. Wright]

Hi Neeraja -
 
I have checked the validity date, and it is still set to 12/31/9999.
 
I will let you know if we come up with a solution (we have opened an OSS issue also), because we expect to update the QA server on July 27.  I expect that PRs will stop getting release strategies there when that happens.  We will HAVE to find a solution before August 18, when PRD will be updated.
 
Regards,
Sherman
 
 
"Sheth, Neeraja" wrote:
 
> Sherman:
>
> Do let me know how you resolve this - it is intriguing.
>
> You must have looked, but I have to ask - has anyone played with the validity end date of your classification?
>
> Regards
>
> Neeraja
>
> > -----Original Message-----
> > From: Sherman S. Wright [SMTP:swright at lsil.com]
> > Sent: Thursday, July 12, 2001 12:45 PM
> > To:   SAP-WUG at MITVMA.MIT.EDU
> > Subject:      Re: "Item not covered by a release strategy"
> >
> > Hi Neeraja -
> >
> > Thank you for the idea, but authorizations don't seem to be the problem.  We have that authorization object and value in the requisitioner's profile already, and an SU53 after creating a PR line (which doesn't get covered by a release strategy) shows that "All authorization checks have so far been successful"...
> >
> > Any other ideas?  Anybody?
> >
> > Regards,
> > Sherman
> >
> >
> > "Sheth, Neeraja" wrote:
> >
> > > Sherman
> > >
> > > When we upgraded from 3.1I to 4.6C, no release strategy would get assigned to the new PRs. We found that we needed additional authorization : authorization for class type C_TCLA_BKA,  class type 32. We have added this authorization to the general SAP user profile so everyone has it. This resolved the issue for us.
> > >
> > > Try executing SU53 immediately after creating a new PR line item.
> > >
> > > Regards
> > >
> > > Neeraja
> > >
> > > > -----Original Message-----
> > > > From: Sherman S. Wright [SMTP:swright at lsil.com]
> > > > Sent: Tuesday, July 10, 2001 4:31 PM
> > > > To:   SAP-WUG at MITVMA.MIT.EDU
> > > > Subject:      "Item not covered by a release strategy"
> > > >
> > > > Hi All -
> > > >
> > > > I wonder if anyone's had a problem similar to this:
> > > >
> > > > We use release strategies for our Purchase Requisition lines, and all
> > > > has been working fine, across our complete landscape (DEV, QA, PRD),
> > > > which are all 4.6B.  However, a few weeks ago, our DEV box was
> > > > "upgraded" to Support Package 28 (it was at 25 prior to that), and now
> > > > all of our PR lines get the message "Item ##### not covered by a release
> > > > strategy".  Everything seems to be configured the same as the other
> > > > clients, workflow verification is correct, all classifications are
> > > > maintained, and "old" PRs will continue through workflow, but nothing
> > > > new is covered by a release strategy.
> > > >
> > > > Any ideas?
> > > >
> > > > Regards,
> > > > Sherman << File: Card for Sherman S. Wright >>
 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: swright.vcf
Type: text/x-vcard
Size: 0 bytes
Desc: Card for Sherman S. Wright
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20010712/8f7c3146/attachment.vcf