How To Fix PBAS_SERVICE070 - Record &1 could not be updated (see long text)

SAP Error Message - Details

• Message type: E = Error

• Message class: PBAS_SERVICE - HR Master Data: Service Functions

• Message number: 070

• Message text: Record &1 could not be updated (see long text)

What causes this issue?

The following infotype record was not updated:
<ZH>Personnel Number:</> &V2&
<ZH>Infotype:</> &V3&
<ZH>Payroll Area:</> &V4&
<ZH>Record Key:</> &V1&

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

The error message is caused by one of the following:
The payroll area &V4& does not exist (T549A)
The control record for the payroll area &V4& does not exist (T569V)
The current payroll period for the payroll area &V4& does not exist
(T549Q)
The control record (T569V) has the status '0' ("Created new") or the
status '9' ("Deleted")
The start date of the corresponding infotype record is in a payroll
period for which it is possible to run payroll again. This means that
the control record is open and payroll results (HRPY_RGDIR) already
exist for the current period for the personnel number &V2&.

System Response

The infotype record was not updated.

How to fix this error?

Perform the IBAN conversion again at a later point in time once the
payroll area is closed (status '3').

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 PBAS_SERVICE070 - Record &1 could not be updated (see long text) ?

  The SAP error message PBAS_SERVICE070 indicates that a specific record (denoted by &1) could not be updated in the system. This error typically arises in the context of the SAP Benefits Administration (PBAS) module, which is part of the Human Capital Management (HCM) suite.
  Possible Causes:
  
  Data Locking: The record may be locked by another user or process, preventing updates.
  Authorization Issues: The user may not have the necessary permissions to update the record.
  Data Integrity Issues: There may be inconsistencies or errors in the data that prevent the update.
  Technical Issues: There could be a problem with the underlying database or application logic.
  
  Configuration Issues: Incorrect configuration settings in the benefits administration module may lead to this error.
  
  Solutions:
  
  Check for Locks: Use transaction codes like SM12 to check if the record is locked by another user. If it is, you may need to wait for the lock to be released or contact the user who has