How To Fix RSO672 - Object &1 &2 is generated and cannot be transported

SAP Error Message - Details

• Message type: E = Error

• Message class: RSO - BW Repository

• Message number: 672

• Message text: Object &1 &2 is generated and cannot be transported

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message RSO672 - Object &1 &2 is generated and cannot be transported ?

  The SAP error message RSO672 indicates that a specific object (identified by &1 and &2) has been generated and cannot be transported. This typically occurs in the context of SAP BW (Business Warehouse) or SAP BI (Business Intelligence) when dealing with objects like InfoObjects, DataSources, or other BW-related objects.
  Cause:
  The error usually arises due to one of the following reasons:
  
  Generated Objects: The object in question has been generated in the system, which means it is in a state that is not transportable. This often happens with objects that have been activated or generated in a development environment.
  Transport Layer Issues: The transport layer settings may not be correctly configured, or the object may not be included in the transport request.
  Missing Transport Request: The object may not be assigned to a transport request, which is necessary for it to be moved to another system (e.g., from development to quality assurance).
  
  Solution:
  To resolve the RSO672 error, you can follow these steps:
  
  
  Check Object Status: Verify the status of the object in the SAP system. If it is generated, you may need to deactivate and then reactivate it to make it transportable.
  
  
  Assign to Transport Request:
  
  Go to the object in the SAP GUI.
  Check if it is assigned to a transport request. If not, you can manually assign it to a transport request.
  Use transaction code SE09 or SE10 to manage transport requests.
  
  
  
  Re-generate the Object: If the object is still not transportable, you may need to delete the generated version and re-generate it. This can sometimes reset its status.
  
  
  Check Transport Layer Configuration: Ensure that the transport layer is correctly configured for the object type you are working with. This can be checked in the transport management system (TMS).
  
  
  Consult Documentation: If the issue persists, refer to SAP Notes or documentation related to the specific object type for any additional troubleshooting steps.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SE09 (Transport Organizer), SE10 (Transport Organizer - Display), and RSA1 (Data Warehousing Workbench).
  SAP Notes: Search for SAP Notes related to RSO672 for any specific patches or updates that may address this issue.
  Transport Management System (TMS): Understanding how TMS works can help in managing transport requests effectively.
  
  If you continue to experience issues, consider reaching out to your SAP Basis team or consulting SAP support for further assistance.