PR Release Strategy

[Harmon Dan-rrfs20]

We ran into a similar situation where the event SIGNIFICANTLYCHANGED for BUS2009 (Purchase Req Item) was not being raised when the req was rejected after it had completed the approval process (I know this sounds strange, but that is how the business wants to run the process...)
 
We could not determine what fields were used or how R/3 was determining if a significant change had occured.  We could not find a change document for this object.
 
Our solution was to use BUS2105 (Purchase Requisition) and change document BANF.  Change document BANF includes table EBAN and we were able to set up a custom event that is raised when a certain field in EBAN is changed.  This required creating our own Z business object and delegating it to BUS2105.  While this solution may not help you out directly, you might want to take a look at change document BANF.
 
Keep in mind that the difference between BUS2009 and BUS2105 is that BUS2009 is the purchase req line item and BUS2105 is kind of like the purchase req header.
 
Regards,
Dan
|--------------------------------------------------------------------|
| Dan Harmon                    |             Phone:    480-634-3090 |
| R/3 Workflow Group Leader     |               Fax:    480-634-3761 |
| Information Technology        |             Pager:    888-782-2030 |
| Motorola SPS                  |            dan.harmon at motorola.com |
|--------------------------------------------------------------------|
| A balanced diet is a cookie in each hand.                          |
|--------------------------------------------------------------------|
 
> -----Original Message-----
>> From: Flavio Oliveira [mailto:oliveiraflavio at hotmail.com]
> Sent: Wednesday, July 10, 2002 5:38 AM
> To: SAP-WUG at MITVMA.MIT.EDU
> Subject: Re: PR Release Strategy
>
>
> It is not a field, but a "situation". A significant change is
> when somebody
> has to be notified about the modification. For example, if
> the requision
> release strategy is "R1" and, after the change it becames
> "R2". This is a
> significant change. But, if the requisition is changed and the release
> strategy is not affected, nobody has to be informed and it is not a
> significant change.
>
> Flavio.
>
> >From: "Boland, Anita" <Anita.Boland at SPR.DOE.GOV>
> >Reply-To: SAP Workflow Users' Group <SAP-WUG at MITVMA.MIT.EDU>
> >To: SAP-WUG at MITVMA.MIT.EDU
> >Subject: PR Release Strategy
> >Date: Mon, 8 Jul 2002 11:18:19 -0500
> >
> >On the PR Release Strategy Workflow does anyone know how to tell what
> >fields in the EBAN table are considered "Significant Event"
> to restart the
> >workflow?
> >
> >Thanks,
> >
> >Anita
>
>
>
>
> _________________________________________________________________
> MSN Photos is the easiest way to share and print your photos:
> http://photos.msn.com/support/worldwide.aspx
>