How To Fix PG186 - At least one infotype was skipped (authorization)

PG186 - Overview

• Message type: E = Error

• Message class: PG - Error Messages for Master Data Programs

• Message number: 186

• Message text: At least one infotype was skipped (authorization)

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

PG186 - Details

• The SAP error message PG186, which states "At least one infotype was skipped (authorization)," typically occurs when a user attempts to access or modify employee data in the Human Capital Management (HCM) module but lacks the necessary authorizations for one or more infotypes.
  
  Cause:
  The error is primarily caused by insufficient authorization for the user role assigned to the individual trying to perform the action. Each infotype in SAP HCM has specific authorization checks, and if the user does not have the required permissions for any of the infotypes involved in the transaction, the system will skip those infotypes and display this error message.
  
  Solution:
  To resolve this issue, you can take the following steps:
  
  
  Check User Authorizations:
  
  Use transaction code SU53 immediately after encountering the error to see which authorization checks failed. This will provide insight into which specific infotype or authorization object is causing the issue.
  Alternatively, you can use transaction code PFCG to review