Output determination and event triggering [FinanzIT: Viruscheck]

Thu Jul 15 06:49:21 EDT 2004

Koenraad,

I had a similar issue a few years ago when I tried to create an event via
output determination for my object type ZBUS2031 (delegation type of
BUS2031) in SD. That didn't work either although everything looked just
fine. Then, after creating an OSS call someone from SAP told me that each
transaction for a certain object type is bound to their own object type. It
turned out that I should have used BUS2031 instead of ZBUS2031. That was it
!
So if you're dealing with the same issue please make sure that you use the
standard object type.

Best regards,

Ronald

                      Koenraad Janssens
                      <koenraad.janssens at sidmar.a        An:       SAP-WUG at MITVMA.MIT.EDU
                      rcelor.com>                        Kopie:
                      Gesendet von: SAP Workflow         Thema:    Re: Output determination and event triggering [FinanzIT: Viruscheck]
                      <Owner-SAP-WUG at MITVMA.MIT.E
                      DU>

                      15.07.2004 11:12
                      Bitte antworten an "SAP
                      Workflow Users' Group"

David,

I'm afraid it still doesn't work....  will have a look (again) at OSS...
too see if something turns up there...

Kind regards

Koenraad

david.bibby at Linklaters.com
Sent by: Owner-SAP-WUG at MITVMA.MIT.EDU
14/07/2004 11:41
Please respond to SAP-WUG

        To:     SAP-WUG at MITVMA.MIT.EDU
        cc:
        Subject:        Re: Output determination and event triggering

Koenraad,
For your output type under the General tab, check if you have the
following tick boxes checked:
"Access to conditions", "CannotBeChanged" and "Partner-indep. output"
Also under the Default Values tab, see if the Dispatch time is "Send
immediately" and the Transmission medium "Events".

I don't recognise the error but this may help.

Regards
David

-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU]On Behalf Of
Koenraad Janssens
Sent: 14 July 2004 10:19
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Output determination and event triggering

Hi David

Thank you.. but now we get the error
No object categoreis transferred (no check of event YYY possible)
The object type transferred to output determination is empty.
The system cannot check the existence of the event determined YYY

I mean it is filled in in the output condition... so I don't understand
why we get this error.

Kind regards.
Koenraad

david.bibby at Linklaters.com
Sent by: Owner-SAP-WUG at MITVMA.MIT.EDU
14/07/2004 10:56
Please respond to SAP-WUG

        To:     SAP-WUG at MITVMA.MIT.EDU
        cc:
        Subject:        Re: Output determination and event triggering

Koenraad
Have you tried RVNSWE01 as the program and CREATE_EVENT for the form
routine ?
Rgds
David

-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU]On Behalf Of
Koenraad Janssens
Sent: 14 July 2004 09:47
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Output determination and event triggering

Hi all

In SD we're trying to use an output procedure to trigger an event. However
we just don't seem to get this right.
The output condition record itself is in place but probably the
customizing isn't correct.
In maintenance output types we have defined a processing routine entry for
medium 9 (events) however we do not know which program and form routine to
use.
For instance for ALE you have medium A program RSNASTED and form routine
ALE_PROCESSING.

Anyone got a clue?

Kind regards

Koenraad

***********************************************************************************

This message should only be read by those persons to whom it is
addressed, and may contain confidential information, the disclosure
of which is prohibited. This message is not intended to create rights
or obligations without subsequent written confirmation of its contents.
If you have received this message in error, please notify us immediately
***********************************************************************************

________________________________________________
This message is confidential. It may also be privileged or
otherwise protected by work product immunity or other legal
rules. If you have received it by mistake please let us know
by reply and then delete it from your system; you should not
copy it or disclose its contents to anyone. All messages
sent to and from Linklaters may be monitored to ensure compliance
with internal policies and to protect our business. Emails are not
secure and cannot be guaranteed to be error free as they can be
intercepted, amended, lost or destroyed, or contain viruses. Anyone
who communicates with us by email is taken to accept these risks.

The contents of any email addressed to our clients are subject to
our usual terms of business; anything which does not relate to the
official business of the firm is neither given nor endorsed by it.

The registered address of the UK partnership of Linklaters is One
Silk Street, London, EC2Y 8HQ. Please refer to
http://www.linklaters.com/regulation for
important information on the regulatory position of the firm.