How To Fix TN_PROCESS104 - The number of objects (&1) does not match the number of requests (&2)

TN_PROCESS104 - Overview

• Message type: E = Error

• Message class: TN_PROCESS - Message Class for OCS Change Processes

• Message number: 104

• Message text: The number of objects (&1) does not match the number of requests (&2)

What causes this issue?

Correction packages are recorded automatically in a transport request
for further transports in the system landscape. Every correction package
has two entries:
Logical transport object (R3TR CPKM)
Object list entry (LIMU COMM)
The number of logical transport objects &V1& does not match the number
of object list entries &V2&. This inconsistency is usually caused by
manual deletions in the automatically created transport request.

System Response

The request is inconsistent.

How to fix this error?

Add the missing entries.

Procedure for System Administrators

Do not delete entries in automatically created requests manually.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message TN_PROCESS104 - The number of objects (&1) does not match the number of requests (&2) ?

  The SAP error message TN_PROCESS104 indicates a mismatch between the number of objects being processed and the number of requests that are expected. This error typically occurs in the context of SAP's transport management system (TMS) when there is an inconsistency in the transport requests.
  
  Cause:
  
  Mismatch in Transport Requests: The error usually arises when the number of objects (like programs, function modules, etc.) that are included in a transport request does not match the number of requests that are being processed.
  Incomplete Transport: If a transport request was not fully completed or if some objects were not included in the request, this error can occur.
  Manual Changes: If changes were made manually to the transport request or if objects were added or removed after the request was created, it can lead to this inconsistency.
  System 
  Configuration Issues: Sometimes, configuration issues in the transport landscape can lead to this error.
  
  
  Solution:
  
  Check Transport Request: Review the transport