Event created with Transaction Code MR1M

Fri Oct 11 12:25:00 EDT 2002

Thank Mark

 -----Original Message-----
From:   Griffiths, Mark [mailto:mark.griffiths at sap.com]
Sent:   Friday, October 11, 2002 12:47 PM
To:     SAP-WUG at MITVMA.MIT.EDU
Subject:        Re: Event created with Transaction Code MR1M

If you read the documentation on BUS2081 you will see that the events are
all triggered automatically with no config (I think it is something like
Function Module MRM_INVOICE_PREPARE_AND_POST) - this definitely works in
4.6C if you use transcation MIRO.

If you are using an older system (as MR1M doesn't seem to work on the 46c
system I am looking at) then I think the object is BSEG_MMIV and the
triggering is done from customising in the IMG.

Cheers,

Mark

SAP UK

-----Original Message-----
From: Dart, Jocelyn
Sent: 11 October 2002 03:27
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Event created with Transaction Code MR1M

Hi Sosthene,
Yes exactly - you are missing the event creation configuration  -
events are not usually raised by the transactions unless whatever
appropriate configuration they require is configured, i.e. there is
no magic! Events do not turn on by themselves.

So if an event is there it usually means there is a matching configuration
option you can use - whether change documents, status management, or
whatever.

Try doing a search in OSS on BUS2081 - there are some explanatory notes
on what configuration should be used for particular objects. I noticed
there are a few there about event creation for BUS2081 such as 140060,
420230, etc.
You can also put a query in OSS to have SAP confirm what event configuration
needs
to be done for BUS2081.

Often the SAP Libary help description of the standard workflow scenario
which uses that object will also give details of how to configure that
event on. There's a fair bit in their on the MM-LIV scenarios.

Once you've turned it on, use SWELS/SWEL to check that your transaction
is raising the event. You may need to adjust your configuration.
If you still can't get it to start - then talk to OSS.

Regards,
Jocelyn

-----Original Message-----
From: ASSY, SOSTHENE [mailto:S.ASSY at AFDB.ORG]
Sent: Wednesday, 9 October 2002 11:00 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Event created with Transaction Code MR1M

Hi Jocelyn

When using transaction SWUE, the workflow is triggered. I want the workflow
to be triggered when the user has created the logistic invoice .
Then event used is CREATED with Object BUS2081.

Have you worked with this object .  I've read all OSS note. I wonder if the
event created is fine.

Please Advice

 -----Original Message-----
From:   Dart, Jocelyn [mailto:jocelyn.dart at sap.com]
Sent:   Tuesday, October 08, 2002 11:49 PM
To:     SAP-WUG at MITVMA.MIT.EDU
Subject:        Re: Event created with Transaction Code MR1M

Hi Sosthene,

Have you turned on the event log to check if MR1M raises that
event at all? You may be missing some event creation configuration.

Regards,
        Jocelyn Dart
Consultant (SRM, EBP, Workflow)
and co-author of the book
"Practical Workflow for SAP"
SAP Australia
email: jocelyn.dart at sap.com
phone: +61 412 390 267
fax:   +61 2 9935 4880

-----Original Message-----
From: ASSY, SOSTHENE [mailto:S.ASSY at AFDB.ORG]
Sent: Monday, 7 October 2002 7:30 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Event created with Transaction Code MR1M

Hi  all,

I want to use transaction Mr1M to create my logistic invoice (object
BUS2081).  Using event created as triggered event,  my workflow can't start.

Please Advice.

This e-mail and any attachment sent with it are confidential and intended
solely for the use of the individual to whom it is addressed. If you have
received this e-mail by error please delete it immediately. No reference
should be made of the information contained in this e-mail.  The views or
opinions expressed in this message, unless otherwise clearly indicated, are
solely those of its author and do not necessarily represent those of the
ADB.  Unauthorized publication, use, dissemination, forwarding, printing or
copying of this e-mail and its associated attachments is strictly
prohibited.  ADB believes but does not warrant that this e-mail and any
attachments are virus-free.  You must therefore take full responsibility for
checking for viruses therein. ADB disclaims any responsibility and liability
arising from your unauthorized use of the contents of this e-mail or your
failing to ensure that it is virus-free.