How To Fix HRASR00_POBJ012 - No authorization to add another case object to the process object

HRASR00_POBJ012 - Overview

• Message type: E = Error

• Message class: HRASR00_POBJ - Message Class for Process Object Runtime

• Message number: 012

• Message text: No authorization to add another case object to the process object

What causes this issue?

When linking a case object to a process object, the authorization check
in Case Management or Records Management failed.

System Response

The case object (scenario object/step object) cannot be linked with the
process object.

How to fix this error?

Check the authorization profile that is maintained for the authorization
objects specific to Case Management and Records Management.

Procedure for System Administrators

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message HRASR00_POBJ012 - No authorization to add another case object to the process object ?

  The SAP error message HRASR00_POBJ012 indicates that a user does not have the necessary authorization to add another case object to a process object in the SAP system, particularly in the context of SAP's HR (Human Resources) module and its associated applications.
  
  Cause:
  The error typically arises due to one or more of the following reasons:
  
  Authorization Issues: The user lacks the required authorizations in their role/profile to perform the action of adding a case object to a process object.
  Role Configuration: The roles assigned to the user may not include the necessary permissions related to the specific HR processes or case management functionalities.
  Process Object Restrictions: There may be specific restrictions or configurations in the process object that prevent additional case objects from being added.
  
  
  Solution:
  To resolve the issue, you can take the following steps:
  
  
  Check User Authorizations:
  
  Use transaction code SU53 immediately after the error occurs to check the authorization check failure. This will provide insights