AW: BUS2013/BUS2014 change event not triggered.

Fri Sep 30 04:40:29 EDT 2005

In my release-WF's I missed sometimes Events too. 

I use BADI ME_PURCHDOC_POSTED.POSTED to fire additional Events for
constellations I need.

Maybe it helps.

Regards

Heinz

  _____  

Von: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] Im Auftrag von
Khanna, Manish
Gesendet: Donnerstag, 29. September 2005 20:16
An: SAP Workflow Users' Group
Betreff: RE: BUS2013/BUS2014 change event not triggered.

This is what is happening.

For a recent development I had to change the workflows for PO/SA/Contracts.

I made changes to 
1. The WF templates
2. Created a custom task with logic.
3. Created a FM
4. Created a custom object to for the method in 2.

Now while testing we found that

1. When we change a SA/Contract , ME32L and ME33K do not reset the release
and put it back in blocked status. This is why the event ReleaseStepCreated
did not trigger. I checked with the functional team and they said nothing
changed in release strategy.

2. I checked in our quality system and found that ME32L and ME33K work fine
in case of change.

3. Assuming that my development is independent of these transactions we
moved the transport to Quality system.

4. unfortunately ME32L and ME33K started behaving in same manner as in
development box.

Now I'm confused as 
1. I did not move the customization
2. No change in the BUS2013 and BUS2014 was moved
3. Even the standard transactions were not moved ( assuming some change due
to application of SAP patches)

Still it is not working :(

  _____  

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of
Hill, Anna
Sent: Thursday, September 29, 2005 6:02 AM
To: SAP Workflow Users' Group
Subject: RE: BUS2013/BUS2014 change event not triggered.

The other thing you need to check is that when you make the change, that the
contract/SA is changed such that is it subject new a release strategy. If
the change is not significant to push the value up or down enough (or to
change any of the other fields that the characteristics are based on in the
release strategy) so that a new release code is applied, the event will not
be raised. 

Good luck, keep me posted. 

Cheers

Anna

  _____  

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of
Khanna, Manish
Sent: Wednesday, September 28, 2005 4:34 PM
To: SAP Workflow Users' Group
Subject: RE: BUS2013/BUS2014 change event not triggered.

Hi Anna,

Thanks a lot. I needed to solve this urgently.

What was happening is 

1. When a PO approval was in process and somebody changed the value or added
a new line, event CHANGED gets fired (SWEC, BUS2012 , Changed, On change)

2. However when a PO was already approved and then changed, event
'ReleaseStepCreated' was fired, along with change. Here I was unable to
establish a link. 

We need the SA and the contracts to  behave in the same manner as 2. I'll
give it a try and let u know if it works.

Thanks for your help

Manish

  _____  

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of
Hill, Anna
Sent: Wednesday, September 28, 2005 7:39 AM
To: SAP Workflow Users' Group
Subject: RE: BUS2013/BUS2014 change event not triggered.

Hi Manish

There is some application configuration required to get the
ReleaseStepCreated events raised which must already be in place in your
system for PO,s but not for contracts or scheduling agreements. To get the
event raised, you need to tell the application that you want to use workflow
for particular release codes, and then the application raises the event when
a contract or scheduling agreement is raised subject to those release codes.

To set up the config, go into the IMG: Materials Management - purchasing -
contract - release procedure for contracts - define release procedure for
contracts. Go into Release Codes (note NOT workflow!) and enter either a 1
or a 9 in the workflow column for the release codes you want to use with
workflow. Follow a similar procedure to set up for SA's. You will then find
that the events are raised when the contracts/SA's are created/changed
subject to the release codes. 

You may also want to read the associated documentation.

Have fun!!

Anna

SAP UK

  _____  

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of
Khanna, Manish
Sent: Tuesday, September 27, 2005 11:03 PM
To: sap-wug at mit.edu
Subject: BUS2013/BUS2014 change event not triggered.

Hi,

We have approval workflows for PO(BUS2012), Consignment Scheduling
Agreements(BUS2013) and Contracts(BUS2014).

Whenever a PO is changed "when its in the released state(after at least 1
approval)" event 'ReleasedStepCreated' is fired, which triggers another
workflow for the PO. 

However similar thing is not happening for SA and contracts. Please note
that event 'changed' gets fired when PO is changed in Blocked state. However
I need SA and Contracts to behave in the same fashion as PO, when they are
changed in 'Released state'.

Any ideas what I'm missing. 

Regards

Manish

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20050930/a7c32410/attachment.htm