How To Fix TR590 - Reference fields of an object key are not filled (internal syntax error)

SAP Error Message - Details

• Message type: E = Error

• Message class: TR - Change and Transport System

• Message number: 590

• Message text: Reference fields of an object key are not filled (internal syntax error)

What causes this issue?

In an object key (E071K), one of the reference fields (<LS>MObj</> and
<LS>Master name</>) is not filled in, although it is a mandatory field.

System Response

The function terminates. You may have to repeat it.

How to fix this error?

If the faulty object keys are already in the request/task, you can
display them in the editor of the Transport Organizer (SE09) with the
menu function <LS>Check key</> and delete them if necessary. You can
then repeat the function.
If the faulty E071k entry is not yet in the request/task, a utility was
called to edit the request/task, but an object key in the parameters
has an invalid structure. If the error occurs repeatedly, inform the
hotline of the application in which the error occurrs.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message TR590 - Reference fields of an object key are not filled (internal syntax error) ?

  The SAP error message TR590, which states "Reference fields of an object key are not filled (internal syntax error)," typically occurs in the context of transport requests or when dealing with object keys in SAP. This error indicates that there is an issue with the reference fields that are expected to be populated but are not, leading to an internal syntax error.
  Causes:
  
  Incomplete Object Key: The object key that is being referenced may not have all the required fields filled in. This can happen if the object was not properly created or if there was an issue during the transport process.
  Transport Request Issues: If the transport request is corrupted or not properly configured, it may lead to this error.
  Custom Development: If there are custom developments or modifications that do not adhere to the expected structure, it can lead to this error.
  System Configuration: Misconfiguration in the system settings related to transport management or object keys can also trigger this error.
  
  Solutions:
  
  Check Object Keys: Review the object keys involved in the transport request. Ensure that all required fields are filled correctly. You can do this by navigating to the relevant transaction (e.g., SE01, SE09) and checking the details of the transport request.
  Recreate the Transport Request: If the transport request is corrupted, consider recreating it. This can often resolve issues related to incomplete or incorrect data.
  Review Custom Code: If the error is related to custom developments, review the code to ensure that it adheres to SAP standards and that all necessary fields are populated.
  Check Transport Logs: Look at the transport logs for any additional error messages or warnings that might provide more context about the issue.
  SAP Notes: Search for relevant SAP Notes in the SAP Support Portal. There may be specific notes addressing this error with additional guidance or patches.
  System Configuration: Ensure that the transport management system (TMS) is correctly configured. Check for any inconsistencies in the transport routes or settings.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with transaction codes like SE01 (Transport Organizer), SE09 (Workbench Organizer), and SE10 (Customizing Organizer) to manage transport requests.
  SAP Support: If the issue persists, consider reaching out to SAP Support for assistance. Provide them with detailed information about the error, including the context in which it occurs and any relevant logs.
  Documentation: Review SAP documentation related to transport management and object keys for a deeper understanding of how these components interact.
  
  By following these steps, you should be able to identify the cause of the TR590 error and implement a suitable solution.