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

SAP Error Message - Details

• 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.

Smart SAP Assistant

• What is the cause and solution for SAP error message TR_AUSL795 - Inconsistent package/development class information (&1) ?

  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 class.
  
  
  
  Transport Directory Check:
  
  Ensure that the transport directory is correctly set up and that there are no issues with the transport files.
  You can use transaction SE01 to check the transport logs for any inconsistencies.
  
  
  
  Reassign Objects:
  
  If the object is assigned to a non-existent package, reassign it to a valid package using transaction SE80 or SE11.
  
  
  
  Transport Layer Configuration:
  
  Check the transport layer configuration using transaction STMS. Ensure that the transport routes are correctly set up.
  
  
  
  Repair Transport Requests:
  
  If the transport request is corrupted, you may need to repair or recreate it. This can be done by creating a new transport request and moving the objects to it.
  
  
  
  Consult SAP Notes:
  
  Check for any relevant SAP Notes that may address this specific error. SAP Notes often provide specific solutions or patches for known issues.
  
  
  
  System Consistency Check:
  
  Perform a consistency check of the transport system using transaction SE03. This can help identify any inconsistencies in the transport landscape.
  
  
  
  Contact SAP Support:
  
  If the issue persists after trying the above steps, consider reaching out to SAP Support for further assistance.
  
  
  
  Related Information:
  
  Transaction Codes: SE80 (Object Navigator), SE11 (Data Dictionary), SE01 (Transport Organizer), STMS (Transport Management System), SE03 (Transport Organizer Tools).
  SAP Notes: Always check the SAP Support Portal for any relevant notes that may provide additional insights or solutions for this error.
  Documentation: Review SAP documentation related to transport management and package handling for best practices and troubleshooting tips.
  
  By following these steps, you should be able to identify and resolve the inconsistency causing the TR_AUSL795 error in your SAP system.