How To Fix 5W751 - Important primary table entries are missing in table OBJS -> no transport

SAP Error Message - Details

• Message type: E = Error

• Message class: 5W - Messages for PD (Particularly Workflow)

• Message number: 751

• Message text: Important primary table entries are missing in table OBJS -> no transport

What causes this issue?

The object list for the PD transport object contains errors, probably
because table OBJS is incomplete. Check that entries have been
maintained for the PLOGI, PLOGI_DEL, HRP1000, HRIADATANR, and HRITABNR
tables.

System Response

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

How to fix this error?

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 5W751 - Important primary table entries are missing in table OBJS -> no transport ?

  The SAP error message 5W751 indicates that there are important primary table entries missing in the table OBJS, which is related to transport requests. This error typically occurs when you are trying to transport objects (like customizing settings, development objects, etc.) and the system cannot find the necessary entries in the OBJS table, which is used to manage transport objects.
  Cause:
  
  Missing Entries: The primary cause of this error is that the required entries in the OBJS table are missing. This can happen if the objects were not properly created or if there was an issue during the transport request creation.
  Inconsistent Transport Request: If the transport request is inconsistent or if the objects were deleted or not included in the transport request, this error can occur.
  Transport Directory Issues: Problems with the transport directory or transport management system can also lead to this error.
  
  Solution:
  
  Check Transport Request: Verify the transport request to ensure that all necessary objects are included. You can do this by checking the transport logs and ensuring that the objects you are trying to transport are correctly listed.
  Recreate the Transport Request: If the transport request is found to be inconsistent, consider recreating it. This can be done by creating a new transport request and adding the necessary objects again.
  Check for Missing Entries: Use transaction SE03 (Transport Organizer Tools) to check for missing entries in the OBJS table. You can also use transaction SE09 or SE10 to analyze transport requests.
  Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that might address this specific error. There may be patches or updates that resolve known issues related to this error.
  Transport Directory Check: Ensure that the transport directory is correctly set up and that there are no issues with the transport management system. You can check the transport directory settings in transaction STMS.
  Contact SAP Support: If the issue persists and you cannot find a resolution, consider reaching out to SAP Support for assistance. They can provide more specific guidance based on your system configuration and the details of the error.
  
  Related Information:
  
  Transaction Codes: SE03, SE09, SE10, STMS
  Tables: OBJS (Transport Objects)
  SAP Notes: Always check for relevant SAP Notes that may provide fixes or workarounds for this error.
  Transport Management System (TMS): Familiarize yourself with TMS as it plays a crucial role in managing transport requests and objects.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.