Object does not exist : MESSAGE OL 826 - Production issue

[Former Member]

R/3 release 4.6C

Transaction: FB03

Custom WF: Triggering events: FIPP-CREATE and FIPP-COMPLETED

When we try to post a document (journal) the workflow gets triggered and reaches the approver. The approver approves it and then it gets posted.

Here in this case, after the approval the workflow running into error with u201Cmessage OL 826 Object does not existu201D

When I click on the message I get this information

Object does not exist : Message no. OL 826

Diagnosis : You tried to create an instance of the object type EMPLOYEET with the

key 1234520080603. No instance of this kind exists.

PERNR u2013 12345

Date - 03.06.2008

I checked this using the FM P_EMPLOYEE_CHECKEXISTENCE and it is working fine there. This FM is used in EMPLOYEET object for existence check.

Initially I thought the problem was with document and the buffer but after checking u201Cdiagnosisu201D message, it confirms me that this is related to Employee.

This is happening only to one employee and all other have NO issues.

I have checked with HR team and they reckon everything is fine from their side.

Since this is in Prod I am unable to debug and test.

I was looking into the previous forums to find the solution but couldnu2019t find RIGHT one. Could you please suggest any solution for this ?

Your help greatly appreciated.

Sreethan

Edited by: SAP User on Jun 12, 2008 12:13 PM

[pokrakam · Accepted solution]

Hello,

It sounds odd that this only happens for one employee. What I would suggest is to test the EMPLOYEET business object in SWO1. You will need some access for this, and if they won't give it to you then I guess it's not important enough to fix...

Cheers,

Mike

[Former Member · Accepted solution]

Mike,

Thank you for resp.

I got the access and tested it in SWO1 but didnt find any difference. Is there any specific way we can check this? I am going under test and giving pernr and date. its giving some values. as does for all.

Martin: If the lenght of PERNR is the problem then it should be for all. isnt it? I am not sure where the value is being checked. I checked the different steps and found this condition.

Parked Document.Personnel_Record.SAP User.Email in condition step.

Even is this is for all users then what could be the reason ? the reason i ask is we are not updating any user data here. The user is trying post the journal. Please help me.

Tcode should be : FB01/FB02. Sorry for that.

Regards,

Sreethan

[martin_nooteboom · Accepted solution]

Well if it is happening for only one pernr, it should be aproblem with that pernrn. Something must be different. Where is the pernr retreived from? It should be in a field somewhere, maybe they made a mistake when storing it.

Regards,

Martin

[pokrakam · Accepted solution]

Hello,

Please do an authorisation check after the user has approved. Most probably he is lacking an authorisation to view personnel numbers. Even though it is a background step, the actual step is created under the context of the approvers ID before it is executed by WF-BATCH.

Cheers,

Mike

[Former Member · Accepted solution]

Dear Mike/Martin,

Could you please explain a bit about the authorization problem?

PERNR A, B, C, and D do the posting the docs through FB01 and PERNR X usually do the approvals. the problem is happening onlyl with PERNR A ... if the approver has the auth problem then it could be same issue with other... please correct me if I am wrong.

As Martin suggested I have contacted HR team but they say .... they dont see anything different or changes for this EMP. The personal record is coming from the EVENT FIPP-CREATE or COMPLETED so there is no manual interaction.

Just guessing: if this is the problem for all the employees then what could be the reason ? guessing that in random it is happening to this emp. He has posted 6 docs....all of them have the same issue. I checked last 3 months records and I did see Couple of workflows in last 3 months with the same error.... so just thinking if this is the problem with all emp happens onlly ramdomly.

Thoughts ??

Thanks & Regards,

Sreethan

[martin_nooteboom · Accepted solution]

You can have an authorization expert take a look at the authorizations of person A and compare them to B for instance. Or let them do a trace to see if there is an issue.

Regards,

Martin

[pokrakam · Accepted solution]

No, you dind't understand. Read my last post again: do an auth check after the user has approved. If that doesn't show up then do an auth check after the posting.

If an approver doesn't have auth to view employees then it cannot generate the EMPLOYEET object instance required for the next step (posting). Or alternatively if the posting user is missing auth then there may be an EMPLOYEET but the system cannot instantiate it.

[Former Member · Accepted solution]

Mike/Martin,

I just checked with security team and they said that the approver doesnt have the authorization to view the initiator's personal record. Based on your information it assumed to be this is the problem and right authorization to the approver is the solution.

We have to wait and see how its going to work as they only post the journal during the month end process.

if everything goes fine then thats the issue.

*Thank You so much for your on time help. Its really great to have you in SDN *

Mike - Congrates for M (Moderator).

Regards,

Sreethan

[martin_nooteboom]

It is strange it is only happening for one pernr. I don't know how the key is build up, but pernr is 8 long so it should have preceding zero's.

Regards,

Martin