Object FORM method HTMLPROCESS cannot be executed

Mon Feb 16 20:09:01 EST 2004

Thanks John,

that's what we did:

All employees and managers to have HR structural authorisation access to
TS and WS objects via authorisation profiles in table T77PR
All employees and managers to have authorisation S_TCODE to transaction
codes YY*
All employees and managers to have PLOG authorisation to display TS and WS
tasks
WF-BATCH to have super user HR structural authorisation authority in table
T77UA

I have a feeling that the problem really is the binding of the object
ABSENCE;  data displayed or changed by approval taks should be passed as
simple container elements, not as object attributes, including all data
displayed in work item texts and descriptions. We will change the binding
and hopefully it will work!

Cheers

Cristiana

John.Soden at newmont.com.au
Sent by: SAP Workflow <Owner-SAP-WUG at MITVMA.MIT.EDU>
17/02/2004 12:00 PM
Please respond to "SAP Workflow Users' Group"

        To:     SAP-WUG at MITVMA.MIT.EDU
        cc:
        Subject:        Re: Object FORM method HTMLPROCESS cannot be executed

just a thought - maybe the task ids need to be specified in the structural
auths before they can be executed (being PD objects). If your developer
has changed the delete leave workflow by creating a new task and that task
is not explicitly specified in the structural auths, maybe that is causing
the problem. To check this - go into OOSB and drill down on someone who
can approve leave and see if there are TS objects listed

We found structural auths gave us grief with the leave app workflow - we
eventually turned them off altogether.

cheers john

________________________________

From: SAP Workflow on behalf of Cristiana D'Agosto
Sent: Tue 17/02/2004 11:17 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Object FORM method HTMLPROCESS cannot be executed

Hi Jocelyn,

Well - it seems that the problem is related to structural authorisation.
We managed to get an example in ESQ to fail, at least now we know that it
is not necessarly the workflow itself.

Ok, so where do I go from here.  All other workflows do not require
additional structural authorisation to approve delegated workitems,
therefore this is obviously an isolated scenario.  The only difference
with leave deletions is the absence is not in a locked status whereas all
other workitems for approval are for infotypes that are locked - could
this make a difference?

I actually just noticed the object &ABSENCE& is being passed in the
binding for the Approval step; and I reckon that could be the problem. I
will modify it and see what happens.

Thanks and regards

Cristiana

"Dart, Jocelyn" <jocelyn.dart at sap.com>
Sent by: SAP Workflow <Owner-SAP-WUG at MITVMA.MIT.EDU>
16/02/2004 02:21 PM
Please respond to "SAP Workflow Users' Group"

To:     SAP-WUG at MITVMA.MIT.EDU
cc:
Subject:        Re: Object FORM method HTMLPROCESS cannot be executed

Hi Cristiana,
Perhaps the workflow is reading other details about the employee, e.g. to
build the work item text or pass as parameters, that the agent does not
have access to? Perhaps you have changed the work item text or long text
to include
other employee details that the agent does not have access to?

In which case, a "swap to background" step would be useful - idea is to
pull out all the information you need in the task to the workflow
container when you are using WF-BATCH, and then pass all that info to the
task, so that it doesn't need to be calculated dynamically when the agent
starts the work item.
Jocelyn

-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of
Cristiana D'Agosto
Sent: Friday,13 February 2004 5:10 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Object FORM method HTMLPROCESS cannot be executed

Hi Jocelyn,

the employee is already in table T77UA.

In Production we have several examples where a manager has 'delegated' the
workflow inbox to an employee.
We have several examples where the employee can then approve leave without
a problem but cannot approve the deletion of the leave request (message
"Object FORM method HTMLPROCESS cannot be executed" is displayed).
In QAS the employee can approve both scenarios without a problem, and
that's what is driving me insane!!

I still think it can be something related to authorization because of the
following:

1 - I logged on as myself (heaps of authorization)
2 - I selected one workflow that was in Error
3 - I re-started this workflow using SWPR
4 - I executed SWIA to execute the work item without agent checking

As a result, the form to approve the deletion was displayed with the
buttons Pass or Cancel; I pressed Pass and the 'Confirm Form' screen was
displayed with message "Form was transferred successfully" and the Confirm
button was displayed; pressed the Confirm button and Bob is your uncle!

I was told by the consultant that the way SAP designed the other workflows
was to allow a user without the correct authorisation to still be able to
approve the workitem using a new task TS95100088 - Swap to background.
This is supposed to overcome the authorisation issues and HR structural
authorisation issues.

The users that have experienced these problems with the Deletion of Leave
can approve other workflows with no errors and I have also tested this in
ESQ for Deletion of Leave with the same scenario as Production and it
works as expected.

I was told that the only authorisation change made at the time SAP changed
the workflows was to assign transaction YY* to the employee role to allow
authorisation to the approval transactions via ESS.

There is any specific/tricky authorization required for using the form to
approve the deletion of a leave request?

Losing sleep over this one!!

Much thanks and regards

Cristiana

"Dart, Jocelyn" <jocelyn.dart at sap.com>
Sent by: SAP Workflow <Owner-SAP-WUG at MITVMA.MIT.EDU>
13/02/2004 03:24 PM
Please respond to "SAP Workflow Users' Group"

To:     SAP-WUG at MITVMA.MIT.EDU
cc:
Subject:        Re: Object FORM method HTMLPROCESS cannot be
executed

Hi Cristiana,
Could be user starting the workflow doesn't have sufficient HR struc
authorisation to access the data, therefore the bindings are empty.
Try setting the users involved with HR struc auth to everything by adding
them to table T77UA.
If it works with full HR struc auth at least you know the problem is
somewhere in those settings and
not in your workfflow itself.
Jocelyn

-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of
Cristiana D'Agosto
Sent: Thursday,12 February 2004 4:19 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Object FORM method HTMLPROCESS cannot be executed

Hi Jocelyn,

still not sure what is going on!

It does work in the QAS client, but it doesn't work in Production.

Structural Authorization is switched on (table T77S0 - AUTSW / ORGPD = 1)
in both clients (QAS and PROD).

The modification was made to the workflow to support the solution for
'delegation of the workflow inbox' (similar to what was done at DoH,
remember?).

The modification was made to all workflows but one; just recently the
consultant made the modification for the Approval for Leave Delete Request
workflow. The only difference between the Leave Delete Request workflow
and the Approval of Leave workflow is in the binding of the approval task;
in the Leave Delete Request workflow the object type ABSENCE is being
passed to the task as well as the container elements (e.g.
&ABSENCE.EMPLOYEENUMBER&, &ABSENCE.AGGREGATE.NAME&, ect); in the Approval
of Leave workflow, only the container elements are being passed. But that
still wouldn't explain why it does work in QAS and it doesn't work in
Production - driving me crazy!!

In Production, the worklfow goes into error for the scenario where a
manager delegates the inbox to an employee - I do smell some authorization
problem, but I can't figure out where or what is wrong.

I wish it wasn't working in any of the clients!!!

Any further ideas?

Thanks and regards

Cristiana

"Dart, Jocelyn" <jocelyn.dart at sap.com>
Sent by: SAP Workflow <Owner-SAP-WUG at MITVMA.MIT.EDU>
10/02/2004 05:44 PM
Please respond to "SAP Workflow Users' Group"

To:     SAP-WUG at MITVMA.MIT.EDU
cc:
Subject:        Re: Object FORM method HTMLPROCESS cannot be
executed

Cristiana,
Check that the work item is still active.
Check the user's security in SU01 and for HR structural authorisations.
Refresh buffer using SWU_OBUF - should do this if you introduce changes
and then use them on the same day.
Regards,
Jocelyn

-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of
Cristiana D'Agosto
Sent: Tuesday,10 February 2004 4:43 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Object FORM method HTMLPROCESS cannot be executed

G'day all,

we are in version 4.6C and using ESS.

An employee is allowed to Delete their own leave; when that happens, the
Approval for Leave Delete Request workflow starts.

Everything was working fine; one of the consultants made a modification in
this workflow and now when the approver attempts to executes the work item
, the message Work item 000003646541: Object FORM method HTMLPROCESS
cannot be executed".

The Task for approval executes FORM.HTMLPROCESS

All the other workflows we have are working fine and are using
FORM.HTMLPROCESS

Any ideas? I am sure it is something small but I can't see it!

Many thanks and regards

Cristiana

Scanned by Newmont Australia Ltd. Anti Virus gateway

IMPORTANT NOTICE - By storing, copying, relying upon or otherwise using
this e-mail, you agree to be bound by our Terms Governing Electronic
Communications. A copy of these terms can be reviewed at
www.newmont.com.au/eComm-terms.htm or obtained by phoning us on +61 8 8303
1700. If you do not accept these terms or suspect that you may have
received this e-mail message in error, please notify the sender and
promptly delete this e-mail.

#### disclaimer.txt has been removed from this note on February 17 2004 by
Cristiana D'Agosto