Skip to Content
author's profile photo Former Member
Former Member

Object does not exist : MESSAGE OL 826 - Production issue

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.


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

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • Best Answer
    Posted on Jun 12, 2008 at 08:12 AM


    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...



    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Mike Pokraka


      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).



  • Posted on Jun 12, 2008 at 11:25 AM

    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.



    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.