How To Fix PG628 - Information type '&1 (&2)' not permitted


SAP Error Message - Details

  • Message type: E = Error

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

  • Message number: 628

  • Message text: Information type '&1 (&2)' not permitted

  • Show details Hide details
  • What causes this issue?

    Infotype &V1& (&V2&) cannot be maintained for this personnel number.

    How to fix this error?

    The authorization of a country grouping for an infotype and type is
    specified in table T582L <LS>Infotypes - Country-Specific Settings</>.
    Make the missing entry or contact your administrator.

    Error message extract from SAP system. Copyright SAP SE.


Smart SAP Assistant

  • What is the cause and solution for SAP error message PG628 - Information type '&1 (&2)' not permitted ?

    The SAP error message PG628, which states "Information type '&1 (&2)' not permitted," typically occurs in the context of Human Capital Management (HCM) when there is an attempt to access or modify an infotype that is not allowed for the current user or in the current context. This can happen due to various reasons, including authorization issues, configuration settings, or the specific context in which the infotype is being accessed.

    Causes:

    1. Authorization Issues: The user may not have the necessary authorizations to access or modify the specified infotype.
    2. Infotype Configuration: The infotype may not be configured correctly in the system, or it may be set to be inactive for certain user groups or organizational units.
    3. User Status: The employee or object associated with the infotype may be in a status that does not allow changes (e.g., inactive, terminated).
    4. Time Constraints: The infotype may be restricted to certain time periods, and the current date may fall outside of those periods.
    5. Custom Development: If there are custom enhancements or modifications in the system, they may inadvertently restrict access to certain infotypes.

    Solutions:

    1. Check Authorizations: Ensure that the user has the necessary authorizations to access the infotype. This can be done by reviewing the user's roles and authorizations in transaction code PFCG or SU53.
    2. Review Infotype Configuration: Check the configuration of the infotype in transaction code SPRO. Ensure that it is active and properly configured for the relevant user groups and organizational units.
    3. Verify User Status: Check the status of the employee or object associated with the infotype. If the employee is inactive or terminated, you may need to reactivate them or use a different infotype.
    4. Check Time Constraints: Ensure that the date you are trying to access or modify the infotype is within the allowed time frame. You can check the validity period of the infotype in the infotype maintenance screen.
    5. Consult with Technical Team: If there are custom developments, consult with your technical team to ensure that there are no restrictions imposed by custom code that could be causing this error.

    Related Information:

    • Transaction Codes: You may use transaction codes such as PA20 (Display HR Master Data), PA30 (Maintain HR Master Data), and SPRO (SAP Reference IMG) to investigate and resolve the issue.
    • SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional guidance.
    • Documentation: Review SAP documentation related to infotypes and authorization management in HCM for further insights.

    If the issue persists after checking the above points, it may be beneficial to engage with your SAP support team or consult SAP's support channels for more tailored assistance.

    • Do you have any question about this error?


      Upgrade now to chat with this error.


Instant HelpGet instant SAP help. Start your 7-day free trial now.


Related SAP Error Messages

Click the links below to see the following related messages:

Click on this link to search all SAP messages.


Rating
ERPlingo simplifies finding the accurate answers to SAP message errors. I now use every week. A must have tool for anyone working with SAP! Highly recommended!
Rate 1
Kent Bettisworth
Executive SAP Consultant