How To Fix FARR_RAI227 - No transport request created for generated objects

SAP Error Message - Details

• Message type: E = Error

• Message class: FARR_RAI - Revenue Accounting Item

• Message number: 227

• Message text: No transport request created for generated objects

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 FARR_RAI227 - No transport request created for generated objects ?

  The SAP error message FARR_RAI227 indicates that no transport request was created for generated objects in the context of the Asset Accounting (FI-AA) module. This typically occurs when you are trying to generate or modify certain objects (like reports, forms, or configurations) in the Asset Accounting area, and the system fails to create a transport request for these changes.
  Causes:
  
  Transport Request Not Configured: The system may not be configured to create transport requests for certain types of objects.
  Authorization Issues: The user may not have the necessary authorizations to create transport requests.
  Development Environment: The changes might be made in a system that is not set up for transport requests (e.g., a sandbox or test environment).
  Missing Transport Layer: The transport layer for the objects being generated may not be defined correctly.
  System Settings: Certain system settings or parameters may prevent the creation of transport requests.
  
  Solutions:
  
  Check Transport Configuration: Ensure that the transport configuration is set up correctly in the system. This includes checking the transport layer and ensuring that the objects you are working with are included in the transport.
  User Authorizations: Verify that the user has the necessary authorizations to create transport requests. This can be checked in transaction SU53 or by consulting with your security team.
  Use Correct Environment: Make sure you are working in the correct environment (development system) where transport requests can be created.
  Manual Transport Request Creation: If the system does not automatically create a transport request, you may need to create one manually using transaction SE09 or SE10 and then assign the generated objects to it.
  Check for Notes and Patches: Sometimes, SAP releases notes or patches that address specific issues. Check the SAP Support Portal for any relevant notes related to this error message.
  Consult Documentation: Review the SAP documentation for Asset Accounting to ensure that you are following the correct procedures for generating objects.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SE09 (Transport Organizer), SE10 (Transport Organizer - Display), and SE01 (Transport Organizer - Change).
  SAP Notes: Search for SAP Notes related to FARR_RAI227 in the SAP Support Portal for any specific fixes or recommendations.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered and resolved similar issues.
  
  If the problem persists after trying the above solutions, it may be beneficial to contact SAP support for further assistance.