How To Fix 3G463 - No payment run information available in table &1 (sequence number &2)

3G463 - Overview

• Message type: E = Error

• Message class: 3G - Payroll: International

• Message number: 463

• Message text: No payment run information available in table &1 (sequence number &2)

What causes this issue?

You have started the payment posting by transferring the payment run
information.
The switch in the table T77S0 <ZK>POST/PMPAY</> is active.
There is (currently) no payment run information in the payroll table &1.

System Response

The posting rejects the personnel number.

How to fix this error?

Start the preliminary data medium exchange program (for example,
RPCDTAX0) for your country for the personnel number affected. Not that
you <ZH>always</> need to start this preliminary program before posting
the payment with payment run information.
Check the payroll results for the personnel number affected.

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.

3G463 - Details

• The SAP error message 3G463 indicates that there is no payment run information available in the specified table for the given sequence number. This error typically occurs in the context of payment processing in SAP, particularly when trying to execute or display payment runs.
  
  Cause:
  The error can be caused by several factors, including:
  
  
  Missing Data: The payment run data may not have been created or saved properly in the database. This can happen if the payment run was not executed successfully or if there was an interruption during the process.
  
  
  Incorrect Sequence Number: The sequence number provided in the error message may be incorrect or does not correspond to any existing payment run in the system.
  
  
  Data Deletion: The payment run information may have been deleted or archived, leading to the absence of the expected data in the relevant table.
  
  
  Authorization Issues: The user may not have the necessary authorizations to view the payment run