SAP_WAPI_CREATE_EVENT and input_contianer (limits?)... 4.6c
Dart, Jocelyn
jocelyn.dart at sap.com
Mon Sep 10 20:12:29 EDT 2007
Hi Manish,
No those ones probably won't change - it's more in terms of creating
your own extensions or creating brand new business objects you should do
it in ABAP OO.
Apart from system BOR objects such as workitem, selfitem - I have found
it useful to create equivalent ABAP OO classes for common BO objects
such as USR01 and EMPLOYEET - you can link the ABAP OO to the bor object
type so that you can still take advantage of existing BOR attributes,
methods and events.
Please see my blogs on SDN re ABAP OO and workflow.
Regards,
Jocelyn Dart
Senior Consultant
SAP Australia Pty Ltd.
Level 1/168 Walker St.
North Sydney
NSW, 2060
Australia
T +61 412 390 267
M + 61 412 390 267
E jocelyn.dart at sap.com
http://www.sap.com
The information contained in or attached to this electronic transmission
is confidential and may be legally privileged. It is intended only for
the person or entity to which it is addressed. If you are not the
intended recipient, you are hereby notified that any distribution,
copying, review, retransmission, dissemination or other use of this
electronic transmission or the information contained in it is strictly
prohibited. If you have received this electronic transmission in error,
please immediately contact the sender to arrange for the return of the
original documents.
Electronic transmission cannot be guaranteed to be secure and
accordingly, the sender does not accept liability for any such data
corruption, interception, unauthorized amendment, viruses, delays or the
consequences thereof.
Any views expressed in this electronic transmission are those of the
individual sender, except where the message states otherwise and the
sender is authorized to state them to be the views of SAP AG or any of
its subsidiaries. SAP AG, its subsidiaries, and their directors,
officers and employees make no representation nor accept any liability
for the accuracy or completeness of the views or information contained
herein. Please be aware that the furnishing of any pricing information/
business proposal herein is indicative only, is subject to change and
shall not be construed as an offer or as constituting a binding
agreement on the part of SAP AG or any of its subsidiaries to enter into
any relationship, unless otherwise expressly stated.
-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Manish Khanna, Noida
Sent: Friday, 07 September 2007 5:46 PM
To: SAP Workflow Users' Group
Subject: RE: SAP_WAPI_CREATE_EVENT and input_contianer (limits?)... 4.6c
Jocelyn,
As you mention that SAP is moving away from BOR to bring ABAP OO on the
front wheel; Is somewhere mentioned the classes that could (or rather
should as we move to newer systems) alternatively be used for some
commonly used BOs (like workitem, selfitem and so on)
Thanks
Manish
-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Dart, Jocelyn
Sent: Thursday, September 06, 2007 3:16 PM
To: SAP Workflow Users' Group
Subject: RE: SAP_WAPI_CREATE_EVENT and input_contianer (limits?)... 4.6c
Hi Rick,
SAP is moving away from the macros - not the WAPIs.
The WAPIs were defined with a simpler interface that should not require
the use of macros, e.g. for tables you just put in each line with same
element name and different index number.
For objects there's a specific structure to use - but can't remember
what it is off the top of my head - have a look at the
SAP_WAPI_READ_OBJECTS (something like that)... and you should see it.
Actually we are moving away from BOR - existing stuff is still supported
but why oh why develop the old way when ABAP OO is soooooo much easier.
There are also some classes you can use instead of WAPIs if you are
using ABAP OO e.g. CL_SWF_EVT_EVENT=>RAISE_EVENT.
Regards,
Jocelyn Dart
Senior Consultant
SAP Australia Pty Ltd.
Level 1/168 Walker St.
North Sydney
NSW, 2060
Australia
T +61 412 390 267
M + 61 412 390 267
E jocelyn.dart at sap.com
http://www.sap.com
The information contained in or attached to this electronic transmission
is confidential and may be legally privileged. It is intended only for
the person or entity to which it is addressed. If you are not the
intended recipient, you are hereby notified that any distribution,
copying, review, retransmission, dissemination or other use of this
electronic transmission or the information contained in it is strictly
prohibited. If you have received this electronic transmission in error,
please immediately contact the sender to arrange for the return of the
original documents.
Electronic transmission cannot be guaranteed to be secure and
accordingly, the sender does not accept liability for any such data
corruption, interception, unauthorized amendment, viruses, delays or the
consequences thereof.
Any views expressed in this electronic transmission are those of the
individual sender, except where the message states otherwise and the
sender is authorized to state them to be the views of SAP AG or any of
its subsidiaries. SAP AG, its subsidiaries, and their directors,
officers and employees make no representation nor accept any liability
for the accuracy or completeness of the views or information contained
herein. Please be aware that the furnishing of any pricing information/
business proposal herein is indicative only, is subject to change and
shall not be construed as an offer or as constituting a binding
agreement on the part of SAP AG or any of its subsidiaries to enter into
any relationship, unless otherwise expressly stated.
-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Sample, Rick
Sent: Thursday, 06 September 2007 12:29 AM
To: SAP Workflow Users' Group
Subject: RE: SAP_WAPI_CREATE_EVENT and input_contianer (limits?)... 4.6c
Jocelyn ,
I was looking for a confirmation of design. Thanks!
I know the WAPIs are to replace FMs like SWE_CREATE_EVENT and I see a
lot more of them in ECC6. (NW) I also see that the SWC_SET_TABLE macro
from <CNTN01> does not work with the SWR_CONT and no replacement.
I can only come to the conclusion that SAP is breaking away from passing
in tables around and to use object ref.
Besides my own list of issues below, what is the future as you know it
with regard to these WAPIs and the old FM like SWE_CREATE_EVENT?
I ask these questions because I know others can benefit from the chat.
Rick
====================
Besides those issues I am fairly sure of the following.
Inflexible design:
Any table changes could cause rework at every point in process. (Who has
time for that!)
Passing data by value from IDOC to Event to WF:
I am sure that a few records would not be a big issue because I have one
working that was created years ago and working fine.
(Beginners luck!) But using SWE_CREATE_EVENT. Not WAPI.
Hundreds or thousands? Besides event queue, a lot of overhead I would
think. Setup / breakdown of data at every point.
A bigger load on system.
Unit testing would be more difficult.
Debugging:
If it WF failed to execute for any reason, where / how would I pass it
into a FM or Method to do postmortem. Gone with the wind!
-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Dart, Jocelyn
Sent: Wednesday, September 05, 2007 1:23 AM
To: SAP Workflow Users' Group
Subject: RE: SAP_WAPI_CREATE_EVENT and input_contianer (limits?)... 4.6c
Hi Rick,
Sorry not much help to give... except that complex types are not
generally easy to handle via the WAPIs - they like you to keep it
simple. But so long as the table is single level and not complex you
should be ok. But I'd be doing some prototyping if you can.
Only other thing I can think is you increase the risk of failure during
event creation - you would definitely need to use the event queue to
make sure you can redeliver the event. If the same piece of data can
be sent twice in two different IDOCs you could have guaranteed delivery
sequence problems - e.g. 2nd update processed before 1st update.
Regards,
Jocelyn Dart
Senior Consultant
SAP Australia Pty Ltd.
Level 1/168 Walker St.
North Sydney
NSW, 2060
Australia
T +61 412 390 267
M + 61 412 390 267
E jocelyn.dart at sap.com
http://www.sap.com
The information contained in or attached to this electronic transmission
is confidential and may be legally privileged. It is intended only for
the person or entity to which it is addressed. If you are not the
intended recipient, you are hereby notified that any distribution,
copying, review, retransmission, dissemination or other use of this
electronic transmission or the information contained in it is strictly
prohibited. If you have received this electronic transmission in error,
please immediately contact the sender to arrange for the return of the
original documents.
Electronic transmission cannot be guaranteed to be secure and
accordingly, the sender does not accept liability for any such data
corruption, interception, unauthorized amendment, viruses, delays or the
consequences thereof.
Any views expressed in this electronic transmission are those of the
individual sender, except where the message states otherwise and the
sender is authorized to state them to be the views of SAP AG or any of
its subsidiaries. SAP AG, its subsidiaries, and their directors,
officers and employees make no representation nor accept any liability
for the accuracy or completeness of the views or information contained
herein. Please be aware that the furnishing of any pricing information/
business proposal herein is indicative only, is subject to change and
shall not be construed as an offer or as constituting a binding
agreement on the part of SAP AG or any of its subsidiaries to enter into
any relationship, unless otherwise expressly stated.
-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Sample, Rick
Sent: Saturday, 01 September 2007 4:38 AM
To: Sample, Rick; SAP Workflow Users' Group
Subject: RE: SAP_WAPI_CREATE_EVENT and input_contianer (limits?)... 4.6c
One more thing, when I stated Multi line, I was not referring to a
simple container with multilines, I was referring to passing in a Table
via the imput_containter.
i.e.
create a table type, input the data, add the table to the
input_container.
-----Original Message-----
From: Sample, Rick
Sent: Friday, August 31, 2007 12:51 PM
To: 'SAP Workflow Users' Group'
Subject: RE: SAP_WAPI_CREATE_EVENT and input_contianer (limits?)... 4.6c
Jocelyn,
I really value your opinion. No sarcasm! You are a very experienced and
valuable resource.
Other than being a crappy design (which I admit. I never like passing
around data), what are the perils of passing in data via the event
container?
I looked and we do have one other WF that is passing in data via event
container tables.
And it is using SWE_EVENT_CREATE. I know this is to not be used. Replace
with WAPI.
What are the issues down the road with newer releases?
When I go to management and tell them I need to change the design I
would like to have "expert opinions" to back me up.
Thanks much,
Rick Sample
SAP Business Workflow Developer
Graybar, Inc.
-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Sample, Rick
Sent: Friday, August 31, 2007 8:35 AM
To: SAP Workflow Users' Group
Subject: RE: SAP_WAPI_CREATE_EVENT and input_contianer (limits?)... 4.6c
>>crappy process.
Yea, I know. Not mine. Inherited it from contractors to finish. Don't
ask!
Data coming from EDI, calling an RFC bapi, and no saved data anywhere.
Will probably just create a BOR (or ABAP Object), have a BAPI wrapper
create these tables, and pass into the WF just the object ref when we
raise event for WF.
I hate passing around data, never did it, and would never design that
way. That is why I am unsure the issues. ;
Rick Sample
SAP Business Workflow Developer
Graybar, Inc.
-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Dart, Jocelyn
Sent: Thursday, August 30, 2007 6:53 PM
To: SAP Workflow Users' Group
Subject: RE: SAP_WAPI_CREATE_EVENT and input_contianer (limits?)... 4.6c
Don't know of a limitation but sounds like a bit of a crappy process to
pass that much information around dynamically and likely to have
problems. Might be safer to stick the rows in a custom table with a
unique reference and just pass the reference.
Regards,
Jocelyn Dart
Senior Consultant
SAP Australia Pty Ltd.
Level 1/168 Walker St.
North Sydney
NSW, 2060
Australia
T +61 412 390 267
M + 61 412 390 267
E jocelyn.dart at sap.com
http://www.sap.com
The information contained in or attached to this electronic transmission
is confidential and may be legally privileged. It is intended only for
the person or entity to which it is addressed. If you are not the
intended recipient, you are hereby notified that any distribution,
copying, review, retransmission, dissemination or other use of this
electronic transmission or the information contained in it is strictly
prohibited. If you have received this electronic transmission in error,
please immediately contact the sender to arrange for the return of the
original documents.
Electronic transmission cannot be guaranteed to be secure and
accordingly, the sender does not accept liability for any such data
corruption, interception, unauthorized amendment, viruses, delays or the
consequences thereof.
Any views expressed in this electronic transmission are those of the
individual sender, except where the message states otherwise and the
sender is authorized to state them to be the views of SAP AG or any of
its subsidiaries. SAP AG, its subsidiaries, and their directors,
officers and employees make no representation nor accept any liability
for the accuracy or completeness of the views or information contained
herein. Please be aware that the furnishing of any pricing information/
business proposal herein is indicative only, is subject to change and
shall not be construed as an offer or as constituting a binding
agreement on the part of SAP AG or any of its subsidiaries to enter into
any relationship, unless otherwise expressly stated.
-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Sample, Rick
Sent: Friday, 31 August 2007 3:23 AM
To: SAP Workflow Users' Group
Subject: SAP_WAPI_CREATE_EVENT and input_contianer (limits?)... 4.6c
Anyone know of issues / limits with passing multilines via
SAP_WAPI_CREATE_EVENT?
100 - 200 lines (worse case) passed in via INPUT_CONTAINER into flow and
issue?
If so, I will need to make changes on calling program which I would like
to avoid right now.
Rick Sample
SAP Business Workflow Developer
Graybar, Inc.
_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug
_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug
DISCLAIMER:
------------------------------------------------------------------------
-----------------------------------------------
The contents of this e-mail and any attachment(s) are confidential and
intended for the named recipient(s) only.
It shall not attach any liability on the originator or HCL or its
affiliates. Any views or opinions presented in
this email are solely those of the author and may not necessarily
reflect the opinions of HCL or its affiliates.
Any form of reproduction, dissemination, copying, disclosure,
modification, distribution and / or publication of
this message without the prior written consent of the author of this
e-mail is strictly prohibited. If you have
received this email in error please delete it and notify the sender
immediately. Before opening any mail and
attachments please check them for viruses and defect.
------------------------------------------------------------------------
-----------------------------------------------
_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug
More information about the SAP-WUG
mailing list