PO Release after support packs 51 for 4.6C - Resolved!

[Susan R. Keohan]

Thanks Jocelyn!

It was OSS note 797775, and I would suggest an addition to anyone else 
with an issue like this... Since we are not using Forecasting and 
Replenishment, I would also suggest that the event FREBUS2012 CREATED be 
deleted via SWEC.  In our case, it raises an unnecessary event.

Dart, Jocelyn wrote:
> Sue, 
> 
> There's an SAP note for this that talks about the problem - basically
> there's an alternative workflow that doesn't use release code for some
> specialist part of ECC. 
>  
> The note was supposed to delete the offending entry in transaction SWEC,
> but I just had the same problem in another system and noticed that the
> entry was still there. 
> 
> Just kill the entry in SWEC that creates the RELEASESTEPCREATED event
> and your problems are solved.  
> 
> 
> Regards,
> Jocelyn Dart
> Senior Consultant
> SAP Australia Pty Ltd.
> Level 1/168 Walker St.
> North Sydney 
> NSW, 2060
> Australia
> T   +61 412 390 267
> M   + 61 412 390 267
> E   jocelyn.dart at sap.com
> http://www.sap.com
> 
> The information contained in or attached to this electronic transmission
> is confidential and may be legally privileged. It is intended only for
> the person or entity to which it is addressed. If you are not the
> intended recipient, you are hereby notified that any distribution,
> copying, review, retransmission, dissemination or other use of this
> electronic transmission or the information contained in it is strictly
> prohibited. If you have received this electronic transmission in error,
> please immediately contact the sender to arrange for the return of the
> original documents. 
> Electronic transmission cannot be guaranteed to be secure and
> accordingly, the sender does not accept liability for any such data
> corruption, interception, unauthorized amendment, viruses, delays or the
> consequences thereof.
> Any views expressed in this electronic transmission are those of the
> individual sender, except where the message states otherwise and the
> sender is authorized to state them to be the views of SAP AG or any of
> its subsidiaries. SAP AG, its subsidiaries, and their directors,
> officers and employees make no representation nor accept any liability
> for the accuracy or completeness of the views or information contained
> herein. Please be aware that the furnishing of any pricing information/
> business proposal herein is indicative only, is subject to change and
> shall not be construed as an offer or as constituting a binding
> agreement on the part of SAP AG or any of its subsidiaries to enter into
> any relationship, unless otherwise expressly stated. 
> 
> 
> -----Original Message-----
> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
> Of Susan R. Keohan
> Sent: Thursday, 26 October 2006 4:10 AM
> To: SAP Workflow Users' Group
> Subject: PO Release after support packs 51 for 4.6C
> 
> Hello Friends,
> 
> We recently applied about 3 years of support packs to our R/3 4.6c 
> environment.  Previously we have several PO release codes which needed 
> to be manually released, and several others that were configured via 
> OMGS to be released via workflow.
> 
> The manual release codes are now raising an event, RELEASESTEPCREATED, 
> (or was it always raising the event, and I just never noticed ?) which 
> then causes a failure, because a mandatory import element is missing 
> (the release code), and subsequently, events get logged in the event 
> queue.  Entries are being generated in SM58, and Basis is having some 
> heartburn.
> 
> Our users can still manually release the PO where they should be able 
> to, and workflow still processes the 'automated' routing for approval, 
> but I am concerned about the event getting raised for the manual
> steps...
> 
> For example...
> 02    AD    9     Administration
> 02    BC          Buyer Commodities
> 02    BS          Buyer Subcontract
> 02    CA    9     Campus Approval
> 02    CH          Change order
> 02    CS    9     Commodities Suprv
> 02    MA    9     Monetary Approval
> 
> In the release strategies above, I would not expect workflow to be 
> triggered for BC, BS, or CH, nor would I expect an event to be raised 
> for these events.
> 
> Have I spent too long in the SRM world ?  Can anyone enlighten me ?  I 
> know I could write a check function to kill off the ones that only need 
> manual release...
> 
> Any help would be greatly appreciated.

-- 
Susan R. Keohan
SAP Workflow Developer
MIT Lincoln Laboratory
244 Wood Street
LI-200
Lexington, MA. 02420
781-981-3561
keohan at ll.mit.edu