cancel
Showing results for 
Search instead for 
Did you mean: 

BSP Error- cx_os_object_not_found while saving Incidents

Former Member
0 Kudos

Hi Experts,

We have implemented ITSM in SOlman 7.1 SP13. While saving or closing some incidents we are getting below error message

BSP Error

Exception class: CX_OS_OBJECT_NOT_FOUND

PROGRAM: CL_TRIGGER_PPF========Cp

Include:        CL_TRIGGER_PPF======CM001

ABAP Class: CL_TRIGGER_PPF

METHOD: IF_OS-STAT~HANDLE_EXCEPTION

Please see the attached screenshot.

Kindly suggest.

Regards,

Rahul

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi there,

we have the same problem.

Are there any news about how to resolve this issue?

Many thanks in advance!

Best

Lucas

Former Member
0 Kudos

Hi Lucas,

This issue was coming for us because of SLA Escalation actions. We deactivated the actions and this error stopped coming.

This could be a reason for you also, check if you are using any SLA escalation actions in action profile and deactivate if found any and then test the scenario again.

Regards,

Rahul

Former Member
0 Kudos

Hi Rahul,

Many thanks. Your hint solved this issue.

However, it is hard to understand why the SLA settings affect the processor choice...

Thanks again, good job

Best

Lucas

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Rahul,

Did you look at SAP Note

http://service.sap.com/sap/support/notes/2059079

It seems to be a program error detailed in this particular note.

Regards

Aditya Khorana

Former Member
0 Kudos

Hi Aditya,

Thanks for your reply..

I implemented note :2059079 in my system but still i am getting same error.

Whenever i open any incident in edit mode, it gives one popup asking whether you want to change processor, once i select YES to assign my id as a processor it gives this BSP error

Also, sometimes it gives same error while changing a ticket's status.

Please suggest if there is any other note.

Regards,

Rahul

dillipkumar_r
Participant
0 Kudos

Hi Rahul,

Did you find a solution for this issue. Even we are experiencing the same issue.

Regards,

Dillip