<!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.2900.2963" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=643283812-25092006><FONT face=Arial
color=#0000ff size=2>Thank you - that one had slipped by me!
</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=643283812-25092006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=643283812-25092006><FONT face=Arial
color=#0000ff size=2>Actually we decided "go for the future", i.e. use ABAP
objects instead of BOR. We also changed our design a little so we don't have to
make as many calls across systems. The need for a cross-system call in the first
place is historic (legacy), the details needed are actually stored in the
ECC 6.0 system - I just need to get some information from the other system
first, to know which details to look up.</FONT></SPAN></DIV>
<DIV align=left><FONT face=Arial size=2>-- </FONT></DIV>
<DIV align=left><FONT face=Arial size=2>Kjetil Kilhavn, Statoil OFT GBS
BAS DEV SAP</FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2></FONT> </DIV><FONT face=Arial
size=2></FONT><FONT face=Arial size=2></FONT><BR>
<BLOCKQUOTE dir=ltr
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> sap-wug-bounces@mit.edu
[mailto:sap-wug-bounces@mit.edu] <B>On Behalf Of </B>Veit
Unger<BR><B>Sent:</B> 25. september 2006 14:26<BR><B>To:</B> SAP Workflow
Users' Group<BR><B>Subject:</B> Re: Cross-system method
call<BR></FONT><BR></DIV>
<DIV></DIV><BR><FONT face=sans-serif size=2>Hi Kjetil,</FONT> <BR><BR><FONT
face=sans-serif size=2>actually it is possible.</FONT> <BR><BR><FONT
face=sans-serif size=2>Using the macros you would need to do for example a
"swc_create_remote_object lref_object type key logsys".</FONT> <BR><FONT
face=sans-serif size=2>After that a normal "swc_call_method..." will do
fine.</FONT> <BR><BR><FONT face=sans-serif size=2>But there are some
prerequisites:</FONT> <BR><FONT face=sans-serif size=2>- you need to maintain
the logical systems (BD54)</FONT> <BR><FONT face=sans-serif size=2>- you need
to have a suitable RFC destination (SM59)</FONT> <BR><FONT face=sans-serif
size=2>- you need to link the logical system to the destination (BD97)</FONT>
<BR><BR><FONT face=sans-serif size=2>kind regards,</FONT> <BR><FONT
face=sans-serif size=2>Veit </FONT><BR><BR><FONT face=sans-serif
size=2>--</FONT> <BR><FONT face=sans-serif size=2>Dipl. WiInf. Veit
Unger<BR>IBM Global Business Services / SerCon<BR>Nahmitzer Damm 12 - 12277
Berlin - Germany<BR>Tel.: +49 (0)170-9147650 <BR>eMail:
veit.unger@de.ibm.com<BR></FONT><BR><BR><BR>
<TABLE width="100%">
<TBODY>
<TR vAlign=top>
<TD width="40%"><FONT face=sans-serif size=1><B>"Kjetil Kilhavn"
<KJETILK@statoil.com></B> </FONT><BR><FONT face=sans-serif
size=1>Sent by: sap-wug-bounces@mit.edu</FONT>
<P><FONT face=sans-serif size=1>25.09.2006 10:45</FONT>
<TABLE border=1>
<TBODY>
<TR vAlign=top>
<TD bgColor=white>
<DIV align=center><FONT face=sans-serif size=1>Please respond
to<BR>"SAP Workflow Users' Group"
<sap-wug@mit.edu></FONT></DIV></TR></TBODY></TABLE><BR></P>
<TD width="59%">
<TABLE width="100%">
<TBODY>
<TR vAlign=top>
<TD>
<DIV align=right><FONT face=sans-serif size=1>To</FONT></DIV>
<TD><FONT face=sans-serif size=1>"SAP Workflow User's Group"
<sap-wug@mit.edu></FONT>
<TR vAlign=top>
<TD>
<DIV align=right><FONT face=sans-serif size=1>cc</FONT></DIV>
<TD>
<TR vAlign=top>
<TD>
<DIV align=right><FONT face=sans-serif size=1>Subject</FONT></DIV>
<TD><FONT face=sans-serif size=1>Cross-system method
call</FONT></TR></TBODY></TABLE><BR>
<TABLE>
<TBODY>
<TR vAlign=top>
<TD>
<TD></TR></TBODY></TABLE><BR></TR></TBODY></TABLE><BR><BR><BR><FONT face=Arial
size=2>We are on version 4.6C in one of our systems, and version ECC 6.0
(basis and cross-app version 7.0) in another system. I have to create a report
which needs data from both of these systems. The report will be executed on
the ECC 6.0 system.</FONT> <BR><FONT size=3> </FONT> <BR><FONT face=Arial
size=2>In the spirit of OO the idea I had was to retrieve a table of (runtime
or persistent if I have to) object references from the 4.6C and then query
each object for its details. </FONT><BR><FONT face=Arial size=2>I've looked in
The Book (Practical Workflow for SAP) a bit, and it seems that this is not
possible. I can understand runtime objects not being possible since the
context is likely to be lost after the first call (so the handles wouldn't be
available), but from what I understand the other option is not possible
either, as it seems only RFC calls are possible between systems. So why do we
have the LOGSYS element in structure SWOTOBJID? Is there another possibility I
haven't discovered?</FONT> <BR><FONT face=Arial size=2>-- </FONT><BR><FONT
face=Arial size=2>Kjetil Kilhavn, Statoil OFT GBS BAS DEV SAP</FONT>
<P><FONT
size=1>-------------------------------------------------------------------<BR>The
information contained in this message may be CONFIDENTIAL and is<BR>intended
for the addressee only. Any unauthorised use, dissemination of
the<BR>information or copying of this message is prohibited. If you are not
the<BR>addressee, please notify the sender immediately by return e-mail and
delete<BR>this message.<BR>Thank you.</FONT><TT><FONT
size=2>_______________________________________________<BR>SAP-WUG mailing
list<BR>SAP-WUG@mit.edu<BR>http://mailman.mit.edu/mailman/listinfo/sap-wug<BR></FONT></TT>
<P></P></BLOCKQUOTE><p></p><p><font size=1>-------------------------------------------------------------------<br>The information contained in this message may be CONFIDENTIAL and is<br>intended for the addressee only. Any unauthorised use, dissemination of the<br>information or copying of this message is prohibited. If you are not the<br>addressee, please notify the sender immediately by return e-mail and delete<br>this message.<br>Thank you.</font size></BODY></HTML>