How To Fix FITP858 - PNR is locked

SAP Error Message - Details

• Message type: E = Error

• Message class: FITP -

• Message number: 858

• Message text: PNR is locked

What causes this issue?

The Passenger Name Record is currently locked, possibly by the travel
agency. It is therefore not possible to edit the booking in the SAP
system.

System Response

The process is terminated.

How to fix this error?

Wait for a while and then try again. If the problem persists, contact
your travel agency.

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 FITP858 - PNR is locked ?

  The SAP error message FITP858 indicates that a PNR (Passenger Name Record) is locked, which typically occurs in the context of travel management or airline reservation systems. This locking mechanism is in place to prevent concurrent modifications to the same PNR by multiple users, which could lead to data inconsistencies.
  Cause:
  
  Concurrent Access: Another user or process is currently accessing or modifying the PNR.
  Session Timeout: A previous session that was editing the PNR did not close properly, leaving the PNR in a locked state.
  System Error: A system error or crash may have left the PNR in a locked state.
  Long-running Transactions: If a transaction takes too long to complete, it may lock the PNR for an extended period.
  
  Solution:
  
  Wait and Retry: If the PNR is locked by another user, wait for a few moments and try again. The lock may be released once the other user completes their transaction.
  Check Lock Status: Use transaction codes like SM12 (to check for locks) to see if the PNR is locked and by whom. If you have the necessary permissions, you can unlock it.
  Contact the User: If you identify the user who has locked the PNR, you can contact them to see if they can release it.
  System Administrator: If the lock persists and you cannot identify the cause, contact your system administrator or SAP support for assistance. They may need to investigate further or clear the lock.
  Review System Logs: Check system logs for any errors or warnings that might indicate why the PNR is locked.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SM12 (to view and manage locks) and SM21 (to view system logs).
  User Permissions: Ensure that you have the necessary permissions to view and manage locks in the system.
  Documentation: Refer to SAP documentation or support notes related to PNR management and locking mechanisms for more detailed guidance.
  
  If the issue persists after trying the above solutions, it may be necessary to escalate the matter to SAP support for further investigation.