How To Fix RSMIGRATE035 - New InfoSource &1 could not be created


SAP Error Message - Details

  • Message type: E = Error

  • Message class: RSMIGRATE - Migration

  • Message number: 035

  • Message text: New InfoSource &1 could not be created

  • Show details Hide details


  • 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 RSMIGRATE035 - New InfoSource &1 could not be created ?

    The SAP error message RSMIGRATE035 indicates that a new InfoSource could not be created during the data migration process. This error typically occurs in the context of SAP BW (Business Warehouse) or SAP BW/4HANA when trying to migrate or create InfoSources as part of data modeling or data extraction processes.

    Causes:

    1. Missing Authorization: The user executing the migration may not have the necessary authorizations to create InfoSources.
    2. Technical Issues: There may be technical issues such as database connectivity problems or issues with the underlying data model.
    3. Existing Objects: An InfoSource with the same name may already exist, leading to a conflict.
    4. Incorrect Configuration: The system configuration may not be set up correctly for the migration process.
    5. Data Model Issues: There may be inconsistencies or errors in the data model that prevent the creation of the InfoSource.

    Solutions:

    1. Check Authorizations: Ensure that the user has the necessary authorizations to create InfoSources. This can be done by checking the user's roles and authorizations in the SAP system.
    2. Review Existing Objects: Check if an InfoSource with the same name already exists. If it does, consider renaming the new InfoSource or deleting the existing one if it is no longer needed.
    3. Technical Checks: Verify the technical setup, including database connections and system configurations. Ensure that all necessary services are running.
    4. Error Logs: Check the system logs (transaction SLG1) for more detailed error messages that can provide additional context on why the InfoSource could not be created.
    5. Data Model Validation: Validate the data model to ensure there are no inconsistencies or errors that could be causing the issue. This may involve checking the underlying data sources and transformations.
    6. Consult Documentation: Refer to SAP documentation or notes related to the specific version of SAP BW or BW/4HANA you are using for any known issues or additional troubleshooting steps.

    Related Information:

    • SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that may address this specific error or provide additional troubleshooting steps.
    • SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they found effective.
    • Transaction Codes: Familiarize yourself with relevant transaction codes such as RSA1 (Data Warehousing Workbench) and RSMIGRATE (for migration tasks) to navigate the system effectively.

    If the issue persists after trying the above solutions, it may be beneficial to reach out to SAP support for further assistance.

    • Do you have any question about this error?


      Upgrade now to chat with this error.


Instant HelpGet instant SAP help. Start your 7-day free trial now.


Related SAP Error Messages

Click the links below to see the following related messages:

Click on this link to search all SAP messages.


Rating
ERPlingo's SAP support assistant is amazing. Saves me countless hours trying to solve complex SAP issues myself. It's a real game changer!
Rate 1
Thomas Michael
SAP Consultant, Author & Speaker