on 11-24-2007 8:22 AM
I am trying to activate a workflow but getting error . The technical log details shows that the superior(manager) cannot be resolved in rule 168 . while testing the rule 168 I can get the superior of person by passing
Extended object id = Position
and
object type = S
but when I try to find the superior by passing
Extended object id = SAP log on name
and
object type as US
I am unable to get the superior ..
Please advice what could be the cause of it . do we need to change some HR setting ie saving relation in some info type or some thing can be done in workflow to resolve it .
Closing thsi thread
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
if it's only of standard then it will be using object type US and saplog on name ..
correct me if i am wrong ...
now i have tested the rule 168 it's not giving the results with object type US .. so some thing from HR side has to be done ? or it's from work flow side .. please advice
i am debugging the FM it seems to be some thing related to evaluation path ..
but hr team says need some more detail where they can make changes .. please advice
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
<b>can i make standard workflow and rule 168 to work with user number (P) .</b>
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi All,
it is all related to standard work flow 20000050 of travel request .so should the problem of binding should occur ? i have checked the binding's all are green and <b>workflow initiator is binded to org object properly</b> .
it seems that by default rule 168 communicates using sap user name . <b>can i make standard workflow and rule 168 to work with user number (P) .</b>
please advice what could be the various points i can check it out ..
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
It seems that you made mistake in binding. . You just bind Orgobject to the work object id.
Regards,
Surjith
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
while testing the rule 168 I can get the superior of person by passing
Extended object id = Position
and
object type = S
but when I try to find the superior by passing
Extended object id = SAP log on name
and
object type as US
I am unable to get the superior ..
<b>actally when we use position or empid whith respective id type the testing of rule seems to be working fine but when we use object type 'US' and provide sap id it does not find it superior .. the all cases are in testing of rule using pfac_dis and whith the same empids .</b>
as these all cases are in pfac_dis by default the rule uses type US ? or we have some setting for it
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
yes the employee id is maintained in 105 and i am able to get superior
Extended object id = personnel id (4000....)
and
object type = P
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
So, your rule is working perfectly while testing, but the problem appears when executing the workflow?
If it is so, then I would say that there are at least couple of possible reasons:
1) there is something wrong in the binding for the rule
2) authorization problem - your test user is not authorized to "search" its superior from the organization
Can you get the superior (while testing), if you use the object type P (=person)?
Have you assigned user IDs for the persons (infotype 105)?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
87 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.