Inconsistent behavior between SAP Rule and underlying Agent Determination...

Thu Jul 29 16:47:37 EDT 2004

=20
=20
Hi Partha,
=20
Please post the entire source of your FM including the interface.
=20
=20
Regards,
Ramki Maley
Workflow Developer,  USCBP.
248-613-1287 (C)

=20
In a message dated 7/29/2004 2:58:23 PM Eastern Standard Time, =20
pchatterjee at DELOITTE.com writes:

Hi  Serge,

I have done various types of refreshes including what you  mentioned (I will=
=20
try changing the capitalization as you suggested).  I  am getting even=20
stranger behavior now believe it or not.  Everytime I  simulate, the popup j=
ust=20
disappears without telling me the role has  failed.

Very strange--thanks for your help though at least I am not  losing my mind,
Partha

-----Original  Message-----=20
From: SAP Workflow on behalf of  Serge Boulay=20
Sent: Thu 7/29/2004 2:51 PM =20
To: SAP-WUG at MITVMA.MIT.EDU=20
Cc:=20
Subject: Re: Inconsistent  behavior between SAP Rule and underlying Agent=20
Determination function  module

Hi Partha,

A stupid one but  have you leave the PFAC transaction? Maybe not logged out
but just went back to the main SAP menu... It is annoying but it  append to
me...

Serge

-----Message d'origine-----
De : SAP Workflow  [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] De la part de
Chatterjee, Partha (US - San Ramon)
Envoy=E9 : 29 juillet 2004 13:16
=C0 :  SAP-WUG at MITVMA.MIT.EDU
Objet : Re: Inconsistent  behavior between SAP Rule and underlying Agent
Determination function module

Hi Serge,

Yes those are the  macros I used.  My code in the funciton module is below:

INCLUDE <CNTAIN>.

DATA BEGIN OF ORG_OBJECT OCCURS 0.

INCLUDE STRUCTURE SWHACTOR.

DATA END OF ORG_OBJECT.

DATA: ORG_TYPE LIKE  SWHACTOR-OTYPE.

DATA: ORG_ID  LIKE SWHACTOR-OBJID.

DATA:  RESULT_TAB LIKE SWHACTOR OCCURS 0 WITH HEADER LINE.

REFRESH: ACTOR_TAB, RESULT_TAB,  ORG_OBJECT.

CLEAR: ACTOR_TAB,  RESULT_TAB, ORG_OBJECT.

* Get  the parameters under consideration.

SWC_GET_ELEMENT AC_CONTAINER 'plant' plant.

SWC_GET_ELEMENT AC_CONTAINER 'logentrytype'  logentrytype.

SWC_GET_ELEMENT  AC_CONTAINER 'eventdate' eventdate.

* Get the position ids from role resolution.

select * from ZSSE0017ROLETBL

into corresponding fields of  result_tab

where iaplant =3D  plant

and iatype =3D  logentrytype

and begda <=3D  eventdate

and endda >=3D  eventdate.

actor_tab-otype =3D  result_tab-otype.

actor_tab-objid =3D result_tab-objid.

append actor_tab.

endselect.

REFRESH:  AC_CONTAINER.

CLEAR:  AC_CONTAINER.

As you can see,  its pretty simple code.  I was playing around with containe=
r
refreshes thinking that that maybe the problem but I  don't think it is.

Best  regards,
Partha

-----Original  Message-----
From:  SAP Workflow on behalf of Serge Boulay
Sent: Thu 7/29/2004 2:09 PM
To: SAP-WUG at MITVMA.MIT.EDU
Cc:
Subject: Re: Inconsistent behavior between SAP  Rule and underlying
Agent Determination  function module

Hi  Partha,

Do you use SWC_GET_ELEMENT  AC_CONTAINER... statement in you function
module
in order to  get these container elements into you function module
variables?

Best  regards.

Serge

-----Message d'origine-----
De : SAP Workflow  [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] De la part
de
Chatterjee, Partha (US - San Ramon)
Envoy=E9 : 29 juillet 2004 12:37
=C0 : SAP-WUG at MITVMA.MIT.EDU
Objet : Re: Inconsistent behavior  between SAP Rule and underlying
Agent
Determination function  module

Hi Mike,

I am not sure I understand your  terminology.

On PFAC_DIS, I  click the simulate button (the abacus type symbol).
At this
point, I get a pop-up which allows me to enter my custom container
elements
(Plant, Event Date, and Incident Type which are from the  EH&S area).
After
enter the custom container elements, I  click the test button (wrench
symbol) and get the problem I am speaking about.  If I run  the same
test
with the underlying function module under se37 it  works fine and I
get the
Agents I am expecting in  ACTOR_TAB.

I am not sure what  the Org Management or the Extended Object ID have
to do
with  this?  So I guess answer to your question would be no as the
parameters
I am feeding the Rule do not have anything to with Org  Management.

Best  regards,
Partha

-----Original Message-----
From: SAP Workflow on behalf of Mike  Nickson
Sent: Thu 7/29/2004 11:53 AM
To:  SAP-WUG at MITVMA.MIT.EDU
Cc:
Subject: Re: Inconsistent  behavior between SAP Rule and
underlying
Agent  Determination function module

When you are simulating the rule  (presumably via PFAC) there
are 2
possible ways to supply the parameters.

Either via - Org  Management Object =3D USBLOGGSF

Or via - Extended Object ID =3D  BLOGGSF   &   Object Type =3D US

Are  these the parameters youa re using ?

Mike

"Chatterjee, Partha (US - San  Ramon)"
<pchatterjee at DELOITTE.com>
Sent by: SAP Workflow  <Owner-SAP-WUG at MITVMA.MIT.EDU>
29/07/2004 15:34
Please respond to SAP Workflow Users' Group

To:     SAP-WUG at MITVMA.MIT.EDU
cc:
Subject:        Inconsistent behavior between  SAP
Rule and
underlying Agent Determination
function  module

Hi All,

I have  developed a very simple rule that picks some agents
from a
custom
table.  When I execute the function module  underlying the
rule in
test/debug, the  function module always behaves as expected
returning
the
correct result to ACTOR_TAB.  However, if I simulate  the
rule I get
'No
Agent Found'.  I don't quite  understand what is happening
between
the
two  places.  We are on 4.7 extension set 2.

Has anyone run  into this type of problem before?  The only
relevant
note
I can find is 707767 but it is hard to know from the  minimal
problem
description whether  its appropriate.

Also, where is the place to search for  q&a's on this forum.

Best regards,

> Partha Chatterjee
>

This  message (including any attachments) contains
confidential
information
intended for a specific individual and purpose, and  is
protected by
law.
If you are not the intended  recipient, you should delete
this
message. Any
disclosure, copying, or distribution of this message, or the
taking
of any
action based on it, is strictly  prohibited.

This message (including any attachments) contains  confidential
information
intended for a specific individual  and purpose, and is protected by
law.   If
you are not the  intended recipient, you should delete this message.
Any
disclosure, copying, or distribution of this message, or the taking
of any
action based on it, is strictly prohibited.

This  message (including any attachments) contains confidential  information
intended for a specific individual  and purpose, and is protected by law.  I=
f
you are not the intended recipient, you should delete this message.   Any
disclosure, copying, or distribution of  this message, or the taking of any
action based  on it, is strictly prohibited.

This  message (including any attachments) contains confidential information=20
intended  for a specific individual and purpose, and is protected by law.  I=
f=20
you  are not the intended recipient, you should delete this message.  Any =20
disclosure, copying, or distribution of this message, or the taking of any =20=
action=20
based on it, is strictly prohibited.