How To Fix PRF_CNTRL_MSG103 - Source Doc. &2 of type &1 could not be locked.

SAP Error Message - Details

• Message type: E = Error

• Message class: PRF_CNTRL_MSG - Message Class for control messages of PRF

• Message number: 103

• Message text: Source Doc. &2 of type &1 could not be locked.

What causes this issue?

Source Document might be in locked status when screen is getting
launched.
It can happen in some scenarios as given below:
?,,source document Create/Edit transaction(s) and change data leading to
trigger of screen and hence document still locked with the transaction.
?,,locked the Source Document using some editing transaction and then
launched PRF screen using Edit PRF record Button / from POWL Screen
PRF_ID Button.
?,,locking of source document not handled / locking failed hence message
is displayed for Warning to user about consequences.

System Response

System Displays Message to user for proving information about
consequences.
Consider the scenarios:
?,,User changes parent Document while PRF screen is open in change mode
and saves the parent document data, thus system will not be able to
update PRF record as its locked by screen but Parent document updated
hence data is no longer consistent with the parent document.
?,,If any amendment is made to code to enable editing of screen even if
locking fails there would be probability that even though source
document changes will be updated to PRF tables those changes will not be
available in PRF buffer until the screen is relaunched, As a result if
PRF screen changes are saved by user the old data will overwrite the
latest automatic updated information from Source Document.
Note: If Custom implementation changes the message to error the screen
is displayed in Display Mode.

How to fix this error?

Please follow the update process.
?,,If you need to edit/change data in source parent document the same
documents PRF records should not be opened in Edit Mode.
?,,When you are changing the PRF Record, Change and save the Data and
close the PRF application then make changes to Parent Document if
required.

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 PRF_CNTRL_MSG103 - Source Doc. &2 of type &1 could not be locked. ?

  The SAP error message PRF_CNTRL_MSG103 indicates that a source document of a specific type could not be locked. This typically occurs in scenarios where multiple users or processes are trying to access or modify the same document simultaneously, leading to a conflict in locking mechanisms.
  Cause:
  
  Concurrent Access: Another user or process is currently accessing the document, preventing your session from obtaining a lock.
  Long-Running Transactions: A transaction that takes a long time to complete may hold the lock longer than expected.
  System Performance Issues: High system load or performance issues can lead to delays in lock acquisition.
  Database Locking Issues: There may be issues at the database level that prevent locks from being acquired.
  Configuration Issues: Incorrect configuration of the locking mechanism in SAP.
  
  Solution:
  
  Wait and Retry: If the document is being accessed by another user, wait for a few moments and then try again.
  Check Lock Entries: Use transaction code SM12 to check for existing lock entries. You can identify if another user is holding the lock and, if necessary, request them to release it.
  Analyze Long-Running Transactions: Use transaction code SM66 to monitor active processes and identify any long-running transactions that may be holding locks.
  System Performance Check: Ensure that the system is performing optimally. Check for any performance bottlenecks that may be affecting lock acquisition.
  Database Administration: If you suspect database issues, consult with your database administrator to check for any locking issues at the database level.
  Configuration Review: Review the configuration settings related to locking in your SAP system to ensure they are set up correctly.
  
  Related Information:
  
  Transaction Codes:
  
  SM12: Display and manage lock entries.
  SM66: Global overview of active processes.
  SM21: System log for error messages and warnings.
  
  
  SAP Notes: Check SAP Notes for any known issues or patches related to locking mechanisms.
  Documentation: Review SAP documentation on locking mechanisms and concurrency control for further insights.
  
  If the issue persists after trying the above solutions, it may be necessary to involve your SAP Basis team or SAP support for further investigation.