Do you have any question about this error?
Message type: E = Error
Message class: /ACCGO/UIS_MSG -
Message number: 349
Message text: New vendor update not possible
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.
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.
/ACCGO/UIS_MSG349
- New vendor update not possible ?The SAP error message
/ACCGO/UIS_MSG349
indicating "New vendor update not possible" typically arises in the context of vendor master data management. This error can occur for several reasons, and understanding the cause is essential for finding a solution. Here are some common causes and their corresponding solutions:Causes:
- Vendor Status: The vendor may be marked as inactive or blocked, preventing any updates.
- Authorization Issues: The user attempting to make the update may not have the necessary authorizations to modify vendor data.
- Data Consistency: There may be inconsistencies or missing mandatory fields in the vendor data that need to be addressed before an update can be made.
- Configuration Settings: Certain configuration settings in the SAP system may restrict updates to vendor data under specific conditions.
- Transaction Type: The transaction type being used may not allow for the creation or update of vendor records.
Solutions:
Check Vendor Status:
- Navigate to the vendor master record and check if the vendor is active. If it is inactive or blocked, you will need to reactivate or unblock it.
Review Authorizations:
- Ensure that the user has the appropriate authorizations to update vendor data. This can be checked in the user roles and profiles assigned to the user.
Validate Data:
- Review the vendor data for any missing mandatory fields or inconsistencies. Ensure that all required information is filled out correctly.
Configuration Review:
- Consult with your SAP Basis or configuration team to review any settings that may be preventing updates to vendor data. This may include checking the configuration of the vendor master data settings.
Use Correct Transaction:
- Ensure that you are using the correct transaction code for updating vendor data. For example, use
XK02
for changing vendor data.Check for Open Transactions:
- Sometimes, if there are open transactions related to the vendor, updates may be restricted. Check for any pending transactions that may need to be completed or cleared.
Related Information:
By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.
Get instant SAP help. Start your 7-day free trial now.
/ACCGO/UIS_MSG348
External ID &1: UoM &2 is invalid for characteristic &3
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
/ACCGO/UIS_MSG347
External ID &1: Characteristic &2 is invalid
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
/ACCGO/UIS_MSG350
LDC ID &1: Save failed; check the application log
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
/ACCGO/UIS_MSG351
Selected LDC objects have different purchase orders
What causes this issue? The selected LDC objects cannot be merged as they have different purchase orders.System Response The system issues an error ...
Click on this link to search all SAP messages.