<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=US-ASCII">
<META content="MSHTML 6.00.2800.1479" name=GENERATOR></HEAD>
<BODY id=role_body style="FONT-SIZE: 10pt; COLOR: #000000; FONT-FAMILY: Arial"
bottomMargin=7 leftMargin=7 topMargin=7 rightMargin=7><FONT id=role_document
face=Arial color=#000000 size=2>
<DIV>
<DIV>
<DIV>Mikko,</DIV>
<DIV> </DIV>
<DIV>Please see the following from Alan reg. the future of WIS.</DIV>
<DIV><A
href="http://mailman.mit.edu/pipermail/sap-wug/2005-June/018025.html">http://mailman.mit.edu/pipermail/sap-wug/2005-June/018025.html</A></DIV>
<DIV> </DIV>
<DIV>
<DIV><FONT lang=0 face=Arial size=2 FAMILY="SANSSERIF"
PTSIZE="10">Regards,<BR>Ramki Maley<BR>Workflow Developer,
USCBP.<BR>248-613-1287 (C)</FONT></DIV></DIV>
<DIV> </DIV>
<DIV>In a message dated 8/16/2005 8:40:36 AM Eastern Standard Time,
mikko.maki-rahkola@accenture.com writes:</DIV>
<BLOCKQUOTE style="PADDING-LEFT: 0px; MARGIN-LEFT: 0px"><FONT
style="BACKGROUND-COLOR: transparent" face=Arial color=#000000 size=2>Hi wug
members,<BR><BR>we're planning to do some more serious reporting on process
statistics and we have selected BW as the reporting engine & frontend. The
statistical information contains both workflow-specific container element info
such as company codes and general workflow header statistics such as
completion times. The backend system is R/3 4.6c.<BR><BR>My problem is how to
determine the best approach for extracting the information. The following are
my initial options and thoughts about them. Please let me know if you have had
a similar decision to make and which way did you go, if you have can tell
which is the most convenient option or if you can just comment on some of
them.<BR><BR>Thanks!<BR>-Mikko<BR><BR>1. Direct extraction from standard
tables SWWIOBJCT, SWWWIHEAD and SWW_CONT<BR>- either build a function module
which picks up the information from all the tables and works as a BW data
source or<BR>- do the table joins in BW<BR>- pros: no development needed in
R/3, data to be kept in a single location, easy use in BW if fm is built<BR>-
cons: custom functionality build effort in R/3, problems with table joins
(especially linking workflows to objects and workflows to container elements),
extraction performance, amount of future support (changing a container element
name results in fm changes)<BR>- my preferred option currently if it's
possible<BR><BR>2. Extract first to WIS, then extract to BW<BR>- with the user
exit and steps in help.sap.com, the stats can be extracted first to a new WIS
table/structure and<BR>- BW can then be used to extract the information from
workflow-specific WIS structures/tables<BR>- I have tested the WIS update
procedure with the user exit codings and all, but it felt a bit awkward and I
remember having some problems with it<BR>- pros: less custom coding in R/3,
WIS quick to be filled<BR>- cons: duplicate information in standard tables and
WIS, possible BW extraction problems, extra configuration for future
workflows<BR>- not too keen about this, wis used just as a middleman<BR><BR>3.
Extract to BW from process-specific custom tables<BR>- quick and dirty
approach, a custom log table to be created for all workflows<BR>- a single
table line contains all the information needed for that process for a single
process instance<BR>- pros: easy to build reports on, easy to extract to
BW,<BR>- cons: duplicate information with standard tables, new tables for all
new future workflows<BR>- not too eager to do this either, too much work in
the long run<BR><BR><BR>This message is for the designated recipient only and
may contain privileged, proprietary, or otherwise private information.
If you have received it in error, please notify the sender immediately and
delete the original. Any other use of the email by you is
prohibited.<BR><BR><BR>_______________________________________________<BR>SAP-WUG
mailing
list<BR>SAP-WUG@mit.edu<BR>http://mailman.mit.edu/mailman/listinfo/sap-wug<BR></FONT></BLOCKQUOTE></DIV>
<DIV></DIV></DIV>
<DIV> </DIV></FONT></BODY></HTML>