How To Fix PG279 - Infotype & cannot be automatically moved

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 279

• Message text: Infotype & cannot be automatically moved

What causes this issue?

The employee's entry date should be moved. However, if a new time
interval is created for an infotype, then an automatic move is no
longer possible. Please check the infotype and delete the time interval
that falls before the actual entry date.

System Response

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

How to fix this error?

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message PG279 - Infotype & cannot be automatically moved ?

  The SAP error message PG279, which states "Infotype & cannot be automatically moved," typically occurs during the processing of personnel actions or when trying to move infotypes in the SAP Human Capital Management (HCM) module. This error indicates that the system is unable to automatically transfer a specific infotype due to various reasons.
  Causes:
  
  Infotype Configuration Issues: The infotype may not be configured correctly in the system, or there may be missing settings that prevent it from being processed.
  Data Inconsistencies: There may be inconsistencies or missing data in the infotype records that prevent the system from moving them.
  Authorization Issues: The user may not have the necessary authorizations to perform the action related to the infotype.
  Custom Logic: Custom enhancements or user exits may be interfering with the standard processing of infotypes.
  Infotype Locking: The infotype might be locked by another process or user, preventing it from being moved.
  
  Solutions:
  
  Check Infotype Configuration: Review the configuration of the infotype in transaction code SPRO. Ensure that all necessary settings are in place and that the infotype is correctly defined.
  Data Validation: Check the data in the infotype for any inconsistencies or missing fields. Ensure that all required fields are filled out correctly.
  Authorization Check: Verify that the user has the necessary authorizations to perform the action. This can be done by checking the user's roles and authorizations in transaction code SU53.
  Review Custom Code: If there are any custom enhancements or user exits related to the infotype, review them to ensure they are not causing the issue.
  Check for Locks: Use transaction code SM12 to check if the infotype is locked by another user or process. If it is, you may need to wait for the lock to be released or contact the user who has locked it.
  Manual Processing: If automatic processing fails, consider manually processing the infotype as a temporary workaround.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as PA30 (Maintain HR Master Data), PA40 (Personnel Actions), and SPRO (SAP Reference IMG).
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error or provide additional guidance.
  Documentation: Review SAP documentation related to infotype management and personnel actions for further insights.
  
  If the issue persists after trying the above solutions, it may be beneficial to consult with your SAP Basis or HCM support team for further assistance.