E-Recruitment (300) WF in ECC5.0 (640)

[Alexis Collins]

Hi Mark,

 

I'm not sure what you mean when you say the req is created "and Forward
is selected".  The WF is triggered when a status change is requested. 

 

The recruiter creates the requisition in "Draft" status, and then
requests the status be changed to "Released".  The system then prompts
the recruiter to enter an approver since they don't have authority to
make this change themselves (based on the role you noted below).

 

I hope this helps.

Alexis

________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Mark Pyc
Sent: Tuesday, March 28, 2006 9:51 AM
To: WUG
Subject: E-Recruitment (300) WF in ECC5.0 (640)

 

G'day all,

 

Can anyone provide advice around the set up required to get the standard
WFs for Processing an E-Rec Requisition working (WS51800008)?

 

My E-Rec consultant believes they have set up everything necessary. The
basis boys believe they have maintained the technical internet settings
and activated the BSPs. I've ensured that all the Workflows linkages are
activated and tasks are general. However when a Requistion is created
and 'Forward' is selected (apparently the trigger for the process)
nothing happens. 

 

The events ERC_OBJECT.CREATED and ERC_OBJECT.STATUSCHANGED both get
raised and trigger WS51900008 and WS51900005 respectively. Both of these
flows are for object types other than NB (requisition) and as such do
nothing (really should be a start condition preventing their start, but
that's another story). 

 

The desired event  ERC_REQUI.APPROVALREQUESTED is not raised and
WS51800008 is not triggered.

 

There is nothing in SM58. Nothing in ST22. Nothing in SM13. Nothing in
SM21. 

 

SLG1 (Application Logs) do show some entries (mostly relating to User
links to Candidates) although not sufficiently in sync for me to believe
they are very meaningful. There were issues with WF-BATCH not being
linked to a Candidate although this has been resolved (as crazy as the
requirement seems to me). 

 

All OSS notes that we can find which offer the steps necessary to set up
E-Rec have been followed.

 

Reading the help again prior to sending this message I noted that the WF
will only start if the raising user does not have sufficient access to
perform the action without approval. I've checked that the user being
tested with is associated with the recommended Role
SAP_RCF_REQUISITION_REQUESTER which according to the doco I've seen
exists for this purpose. 

 

Does anyone know what might be needed to get this thing to fire off?

 

Many thanks for reading this far!

Mark

----------------------------------------------------------------------
This e-mail, including any attached files, may contain confidential and privileged information for the sole use of the intended recipient.  Any review, use, distribution, or disclosure by others is strictly prohibited.  If you are not the intended recipient (or authorized to receive information for the intended recipient), please contact the sender by reply e-mail and delete all copies of this message.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20060328/fa144b0c/attachment.htm