EKKO/BUS2012 ( 3.1I -> 4.6C )

[Sheth, Neeraja]

Thank you, Thorsten.
 
I was initially confused about why I could not use perfect-looking generated
object BUS2012 (it would not appear as one of the objects when I tried to
link it through PO output generation, and I got a message at one point
saying something to the effect that it was not compatible with application
EF ). The reason - we have a custom workflow which uses a subtype ZBUS2012.
One of the custom methods had 'Report' selected in the ABAP tab even though
there was no ABAP report to run. This did not matter in 3.1I. But in 4.6C,
ZBUS2012 would not generate. The error said "ABAP program ' ' is not
defined". It took me half the day to figure out that I should check the ABAP
tabs of each of the custom methods.
 
Once ZBUS2012 could be generated, BUS2012 appeared as one of the objects I
could link PO output to. And so I went thru the event creation process you
described, and replaced my EKKO based event, linkage etc.
 
Now I am off to change ZBUS2032 - my method based on CREATEFROMDATA is
obsolete as of 4.0, and so is my custom workflow that uses it.
 
 
Regards
 
Neeraja Sheth
 
 
 
 
> -----Original Message-----
>> From: Susan R. Keohan [SMTP:skeohan at MIT.EDU]
> Sent: Tuesday, September 12, 2000 7:12 PM
> To:   SAP-WUG at MITVMA.MIT.EDU
> Subject:      AW: EKKO/BUS2012
>
> On behalf of wewers at ECENTA.COM...
>
> >Neeraja,
> >
> >the EKKO object type was originally intended by SAP for use with optical
> >archiving (ArchiveLink). I don't know much about 3.1, but already in 4.0,
> >the object type BUS2012 existed and it was (and is) the object type of
> >choice if you're dealing with release strategies on po's, for example.
> >
> >Now, what does this help with your problem? First of all, in 4.6C you
> need
> >to adapt your workflow(s) to the new object type. Since the BUS2012 and
> >underlying structures (tables, change documents, function modules) are
> >designed quite nicely, I don't expect this to be a hard problem.
> Secondly,
> >the event generation that in this moment seems to be your most urgent
> >problem can be implemented by some (again) rather simple workflow means:
> >change documents and a check function module. Let me explain:
> >
> >1. Define your event 'Created' in BUS2012.
> >
> >2. Couple this event with the change document type "EINKBELEG" (goto
> >Workflow Development -> Definition -> Event creation -> Change documents
> ->
> >Event coupling, 3rd menu item (the menu item labels might differ a bit,
> >because I don't have an R/3 here in this moment)
> >
> >3. On each event linkage you can define conditions. Try them. Maybe, they
> >offer you the filter mechanism (purchasing group as you say) that you
> need.
> >If so, you're done at this point. If not, you could define an attribute
> in
> >BUS2012 that evaluates the desired (complex) condition, and simply use
> this
> >attribute's value in the (then) simple change document condition. There
> is
> >also the option described in #4.
> >
> >4. If the simple conditions don't suffice and you find attributes too
> >strange in this context, you can use an ABAP exit that is available in
> every
> >event linkage between event and workflow. Goto (again: menu item labels
> >might differ) Utilities -> Events -> (Type) linkages. Double-click your
> >linkage item (between (Z)BUS2012.CREATED and WS...); in the following
> screen
> >you can specify a check function module. These modules have a certain
> >interface - you can look into other linkages, e.g. with DRAW.CHANGED,
> that
> >have check fm's in them, and learn from there how it works.
> >
> >What I described here is absolutely main-stream and endorsed by SAP (Alan
> -
> >did you make it all the way down here?). Don't hesitate to contact me if
> you
> >need any additional help on this or other workflow issues.
> >
> >Thorsten Wewers
> >BMT Consulting
> >
> >-----Urspr|ngliche Nachricht-----
> >Von: Sheth, Neeraja [mailto:Neeraja.Sheth at fnc.fujitsu.com]
> >Gesendet: Montag, 11. September 2000 19:18
> >An: SAP-WUG at MITVMA.MIT.EDU
> >Betreff:
> >
> >
> >We are in the process of upgrading from 3.1I to 4.6C.
> >
> >In 3.1I, I had created a custom workflow based on object EKKO -
> purchasing
> >document. The creation of a PO for a particular purchasing group raised
> an
> >event Z_EKKO.PO_CREATED through output generation, and this triggered the
> >workflow.
> >
> >With 4.6C, I find that EKKO is obsolete as of 4.0.
> >
> >I would like to know from someone what object I could use to link to PO
> >output. BUS2012 is not compatible with application 'EF' and does not show
> up
> >as one of the options when I try to link the output to an object and an
> >event.
> >
> >
> >Thanks in advance,
> >
> >Neeraja Sheth
> >Fujitsu Network Communications
> >