Resolving Order Placement Errors in ERP

This guide aims to help you troubleshoot and resolve common issues when placing a sales order in the ERP system. If you are experiencing an issue that prevents you from submitting a sales order, follow the steps below.

Common Errors and Solutions

1. Error Message: "Unable to process request: Server Error 502"

Steps to Resolve:

1. Check Internet Connection:
2. Ensure your internet connection is stable. A weak or unstable connection can cause server errors.
   Clear Cache and Cookies:
3. Go to your browser settings and clear your cache and cookies.
   Restart your browser and log in to the ERP system again.
   Log Out and Log Back In:
4. Log out of the ERP system.
   Close your browser or application.
   Reopen the browser or application and log back in.
   Try a Different Browser:
5. Attempt to access the ERP system using a different web browser.
   Compatible browsers typically include Chrome, Firefox, and Edge.
   Disable Browser Extensions:
6. Sometimes, browser extensions can interfere with ERP functionality.
   Disable any extensions and try placing the order again.

2. Error Message: "Invalid Customer Information"

Steps to Resolve:

1. Double-Check Customer Details:
2. Ensure all required customer fields (such as name, address, and contact information) are completed and correctly formatted.
   Verify Customer Account:
3. Confirm that the customer account exists and is active.

3. Error Message: "Order Amount Exceeds Limit"

Steps to Resolve:

1. Review Order Details. heck the total order amount and compare it against any set limits in the system.
2. Seek Approval:
   If the order amount exceeds your limit, contact your supervisor for approval or guidance on how to proceed.

Additional Support

If you have followed these steps and are still experiencing issues, please contact the IT team for further assistance. Provide them with the following details to expedite the resolution process:

• Date and time of the occurrence
• Exact error message displayed
• Steps taken before encountering the error
• Any troubleshooting steps already attempted