Generic suggestion:
In such cases I would either place a break-point at the message to see where the error is raised or I would check for recent transport requests.
Questions, which might help you figuring out what is going on:
Have you noticed at which point exactly the error is raised - when you enter a customer, when you enter a material, when you reprice, when you add/modify a condition, when you save?
Did you try also with orders, resulting in a different pricing procedure (preferably a standard one)? What about different order types and item categories?
It is very hard to suggest anything more specific considering the available information.
If that has "just occurred" then you should ask your IT to check which changes have been transported into your system.
Transaction ANST can also be used to analyze the transaction, it will also show exits and modifications.
Are you the only one in your organization who creates Sales orders? Are others not affected?
Not being able to create sales orders would classify as major incident in our company and the alarm bells would not calm down until the error is solved. Someone in your local IT should be able to find the recent transports by using SE10 transaction
(Coincident or you work in the same company with this guy: https://answers.sap.com/questions/180348/erron-in-va01.html )
If this is really a new bug then it should as well be possible to find the root cause by checking recent updates/changes/transports/notes implementations ,asking colleagues and supervisors.
Add comment