How To Fix TR_AUSL795 - Inconsistent package/development class information (&1)

TR_AUSL795 - Overview

• Message type: E = Error

• Message class: TR_AUSL - Software Delivery Composer Messages

• Message number: 795

• Message text: Inconsistent package/development class information (&1)

What causes this issue?

The package/software class of the displayed objects is assigned to the
coftware component (TDEVC~DLVUNIT) '&V2&' but the <LS>Flag for Customer
Delivery</> (TDEVC~TPCLASS) is '&V3&'. It is therefore not possible to
identify the delivery relevance exactly.

System Response

Affected objects are displayed in the results overview of the object
list check.

How to fix this error?

Check the delivery relevance of the specified objects. Change the
package/delivery class assignment or package/delivery class definition
yourself and then repeat the object list check. You can remove
irrelevant object entries from the delivery by selecting them and
choosing <LS>Correct Entries</>.

Error message extract from SAP system. Copyright SAP SE.

TR_AUSL795 - Details

• The SAP error message TR_AUSL795 indicates that there is inconsistent information regarding a package or development class in the SAP system. This typically occurs during transport operations or when trying to manage objects in the Transport Organizer.
  
  Cause:
  The inconsistency can arise from several scenarios, including:
  
  Transport Directory Issues: Problems with the transport directory or transport files can lead to inconsistencies.
  Missing or Incorrect Package Assignment: Objects may be assigned to a package that does not exist or has been deleted.
  Transport Layer Issues: The transport layer may not be correctly configured or may have been modified incorrectly.
  Development Class Issues: The development class may not be properly defined or may have been deleted or changed.
  
  
  Solution:
  To resolve the TR_AUSL795 error, you can follow these steps:
  
  
  Check Package/Development Class:
  
  Verify that the package or development class mentioned in the error message exists and is correctly defined in the system.
  Use transaction SE80 or SE11 to check the package or development