How To Fix HRPBS00_MD035 - The change of fields for the action &1 is not allowed

SAP Error Message - Details

• Message type: E = Error

• Message class: HRPBS00_MD - Message class for Master Data Tool

• Message number: 035

• Message text: The change of fields for the action &1 is not allowed

What causes this issue?

The fields employee group, employee subgroup and personnel area can be
changed only for special action types. The action type is changed to
values which does not allow any change to one of these fields.

System Response

The value of the fields are set back to the original-value which is
stored in the Personnal-Administration.

How to fix this error?

Use an action type which allows the change of the requested field.

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 HRPBS00_MD035 - The change of fields for the action &1 is not allowed ?

  The SAP error message HRPBS00_MD035, which states "The change of fields for the action &1 is not allowed," typically occurs in the context of personnel actions in the Human Resources (HR) module. This error indicates that there are restrictions on modifying certain fields during a specific personnel action.
  
  Cause:
  
  Field Restrictions: Certain fields in the infotype (like infotype 0000 for actions) are locked for changes based on the action type. For example, if you are trying to change fields that are not allowed for a specific action (like hiring, termination, etc.), this error will be triggered.
  Action Configuration: The configuration of the personnel action may not allow changes to specific fields. This is often defined in the customizing settings of the HR module.
  Data Consistency: SAP enforces data consistency rules, and if changing a field would violate these rules, the system will prevent the change.
  
  
  Solution:
  
  Check Action Configuration: Review the configuration of the personnel action