Problem using table reference on event parameter.

Knott, Cheryl c-knott at ti.com
Thu Dec 19 15:08:03 EST 2002


Sky,
 
Thank you for your reply.
 
The structure you describe is exactly what is used in this workflow
(VBAPVB).  It works fine in production.  It is unclear to me how it was
defined in the past but cannot be defined that way now.  The method
parameters and workflow/task containers allow reference to the structure
without fields, but the event parameter gives an error message.
 
Perhaps the original release (3.1G) permitted this or perhaps the original
developer forced the definition.
 
Thank you again.
Cheryl Knott
 
-----Original Message-----
From: Kimball, Schuyler [mailto:schuyler.kimball at sap.com]
Sent: Thursday, December 19, 2002 11:25 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Problem using table reference on event parameter.
 
 
Hi again,
I just realized your question was a bit different than the one I answered.
To get the event parm to reference a table, you might try creating a data
dictionary structure identical to the table definition (Structure that
consists of an INCLUDE of component type VBAP), and reference the name of
the new structure in creating the event parm.
Not sure if this works or not, but it's worth a try.
 
Regards,
  Sky
 
Sky Kimball
Senior Technical Consultant
Professional Services Organization
SAP America, Inc.
 
950 Winter Street, Suite 3800
Waltham, MA 02451
T   1-781-684-6438
E   schuyler.kimball at sap.com
http://www.sap.com
 
-----Original Message-----
From: Kimball, Schuyler
Sent: Thursday, December 19, 2002 11:48 AM
To: 'SAP Workflow Users' Group'
Subject: RE: Problem using table reference on event parameter.
 
 
Hi Cheryl,
Since SAP has said that the multiline event parameter is not available on
your release, let's look at other ways that you could handle this (you'll
need to verify that these suggestions will work on your release and will
meet your needs).
 
By creating a new multiline virtual attribute on the business object
(instead of having the same information in a multiline element of the event
container), you could perform actions after the event occurs:
 
*  If the event is triggering a response within a workflow, you can begin
with a Wait For Event step, and then once the event occurs, use the virtual
attribute to retrieve the values you need, e.g. by using a Container
Operation step to set the value of a multiline element in the workflow
container.
 
*  If the event triggers a workflow, you could use the same virtual
attribute in a check function module (this would involve ABAP development).
 
I hope this covers the scenarios you need.
Regards,
  Sky
 
Sky Kimball
Senior Technical Consultant
Professional Services Organization
SAP America, Inc.
 
950 Winter Street, Suite 3800
Waltham, MA 02451
T   1-781-684-6438
E   schuyler.kimball at sap.com
http://www.sap.com
 
-----Original Message-----
From: Knott, Cheryl [mailto:c-knott at ti.com]
Sent: Thursday, December 19, 2002 11:05 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Problem using table reference on event parameter.
 
 
I am attempting to change an event parameter that has been in production for
> 4 years on release 4.0B.  The reference table is VBAPVB and there is no
reference field (the entire structure is passed).  I would like to change
the event parameter to multi-line.
 
I cannot save the multi-line change due to an error OL372 - 'Please enter
reference field'.
 
Here is the response I received from SAP:
" It is not possible to specify an event parameter as a table until later
releases. If you wish to specify a table you could use the services of
remote consulting, however, this is a billable service. See attached
notes."     (notes are 84044 and 48204 re:consulting services)
 
I had no problem changing the method or workflow task parameters to
multi-line.  They also specify only the reference table without the
reference field.
 
It seems that this must have been a capability at some point, since the
event parameter specifies only a reference table in the production system.
 
I appreciate your insight and suggestions.
 
Best Regards,
Cheryl Knott
 


More information about the SAP-WUG mailing list