Troubleshooting: Missing Purchase Requisitions in Dynamics GP Navigation?

Table of Contents

This article addresses a common issue encountered by users of Microsoft Dynamics GP: the inability to view Purchase Requisitions within the navigation lists. This can be a frustrating problem, hindering daily operations and workflows, especially for those involved in procurement and purchasing processes. Understanding the root cause and resolution is crucial to maintain efficient use of Dynamics GP. This guide will walk you through the symptoms, causes, and step-by-step resolution to ensure Purchase Requisitions are visible and accessible within your Dynamics GP environment.

Symptoms¶

The primary symptom of this issue is straightforward: users are unable to locate and access Purchase Requisition transactions from the Navigation list pane within Microsoft Dynamics GP. This means when users navigate to the designated area for Purchase Requisitions, the expected list of requisitions is simply not displayed. This absence prevents users from performing essential tasks such as reviewing, approving, or managing purchase requests. The navigation list pane, which is designed to provide quick access to various transaction types, fails to show the Purchase Requisition entries, leading to workflow disruptions. Users might be looking in the correct navigation area but find it empty or lacking the Purchase Requisition options they anticipate.

Cause¶

The underlying cause of this visibility issue does not stem from standard Microsoft Dynamics GP security settings, which might be the initial assumption. Instead, the control lies within the Purchasing Requisition Setup window itself. Specifically, the user in question is likely not marked to have all requisitions displayed within this setup. This setting is distinct from general user permissions and is specifically designed to manage the visibility of purchase requisitions based on the configuration within the Purchasing module. It is a configuration detail often overlooked, leading to confusion as administrators might focus on standard security roles and permissions, missing this specific setup area. Therefore, the problem is not a matter of user roles or security privileges in the traditional sense, but rather a configuration choice within the requisition setup affecting display preferences.

Resolution¶

To resolve the issue of Purchase Requisitions not appearing in the Navigation List, you need to adjust the settings within the Purchasing Requisition Setup window in Microsoft Dynamics GP. Here is a step-by-step guide to ensure users can view Purchase Requisitions:

1. Access the Purchasing Requisition Setup Window:

   • Navigate to the Purchasing area page in Microsoft Dynamics GP.
   • Locate the Setup section within the Purchasing area page.
   • Click on Requisition to open the Purchasing Requisition Setup window.

   

2. Identify the “Display All Requisitions” Setting:

   • Within the Purchasing Requisition Setup window, you need to find the section related to user display options or requisition visibility.
   • Look for a checkbox or setting labeled something similar to “Display All Requisitions,” “Show All Requisitions,” or “Users See All Requisitions.” The exact wording may slightly vary depending on your Dynamics GP version, but the concept remains the same.

   

3. Enable “Display All Requisitions”:

   • Ensure that the “Display All Requisitions” checkbox is selected or the corresponding option is enabled. This setting dictates whether users, by default, will see all purchase requisitions in the navigation lists, regardless of who created them or their specific status, assuming they have general access to the Purchasing module.

   

4. Save the Changes:

   • After enabling the “Display All Requisitions” setting, click on the Save button or the equivalent action to apply the changes. It is crucial to save the setup modifications for them to take effect.

5. Verify the Resolution:

   • Ask the users who were experiencing the issue to log out of Dynamics GP and log back in. This ensures that the updated settings are properly loaded for their user sessions.
   • Instruct them to navigate to the Purchase Requisition area in the Navigation list.
   • Confirm that Purchase Requisitions are now visible in the Navigation list pane as expected. They should now be able to see the list of requisitions, allowing them to proceed with their purchasing tasks.

By following these steps, you should successfully resolve the problem of users not being able to see Purchase Requisitions in the Navigation list in Microsoft Dynamics GP. This adjustment in the Purchasing Requisition Setup window ensures that users are granted the necessary visibility to manage and interact with purchase requests efficiently.

Deeper Dive into Purchase Requisitions in Dynamics GP¶

Purchase Requisitions are a fundamental component of the procurement process within Microsoft Dynamics GP. They serve as the initial step in requesting goods or services, acting as internal documents that initiate the purchasing cycle. Understanding their role and configuration is crucial for efficient operations.

What are Purchase Requisitions?¶

A Purchase Requisition is essentially an internal request made by an employee to the purchasing department to procure specific goods or services. It outlines the details of what is needed, including:

• Items or Services: Detailed description of what needs to be purchased.
• Quantity: The number of units required.
• Requested Delivery Date: When the items or services are needed.
• Suggested Vendor (Optional): If the requester has a preferred vendor.
• Account to Charge: The General Ledger account that will bear the cost.
• Department or Project: To track expenses by organizational unit or project.

Purchase Requisitions are not legally binding documents like Purchase Orders; they are internal communication tools. Once a requisition is approved, it is converted into a Purchase Order, which is then sent to the vendor.

Importance of Purchase Requisitions¶

Implementing Purchase Requisitions offers several key benefits for organizations:

• Control over Spending: Requisitions ensure that all purchases are formally requested and approved before orders are placed. This helps in controlling expenses and adhering to budgets.
• Streamlined Procurement Process: They provide a structured and documented process for initiating purchases, leading to a more organized and efficient procurement cycle.
• Improved Budgeting and Forecasting: By tracking requisitions, organizations gain better visibility into upcoming expenditures, aiding in more accurate budgeting and financial forecasting.
• Enhanced Audit Trail: Requisitions create a clear audit trail of purchase requests, approvals, and the subsequent purchase orders, improving accountability and transparency.
• Centralized Purchasing: They facilitate centralized purchasing by routing all purchase requests through a designated purchasing department, enabling better negotiation and vendor management.

Configuration Options in Purchasing Requisition Setup¶

Beyond the “Display All Requisitions” setting, the Purchasing Requisition Setup window in Dynamics GP offers several other configuration options that impact how requisitions are managed and processed. These settings allow organizations to tailor the requisition process to their specific needs. Some notable configurations include:

• Requisition Numbering: Setup options for how requisition numbers are generated (e.g., automatic or manual numbering, prefix, and suffix).
• Approval Workflow: Dynamics GP allows for the configuration of approval workflows for requisitions. This can include defining multiple levels of approval based on requisition amounts, departments, or other criteria. Workflows ensure that requisitions are reviewed and authorized by the appropriate personnel before being processed further.
• Email Notifications: Settings to enable email notifications for various stages of the requisition process, such as requisition submission, approval, rejection, and conversion to purchase orders. Automated notifications improve communication and keep stakeholders informed.
• Requisition Types: Defining different types of requisitions to categorize requests (e.g., standard, capital expenditure, IT equipment). This can help in routing requisitions to appropriate approvers and tracking spending by category.
• Default Settings: Setting default values for certain fields in requisitions, such as default GL accounts or requester information, to streamline data entry.

Common Issues and Troubleshooting Tips¶

While the “Missing Purchase Requisitions in Navigation List” issue is addressed by adjusting the “Display All Requisitions” setting, other common issues can arise with Purchase Requisitions in Dynamics GP. Here are some troubleshooting tips for general requisition-related problems:

• Approval Workflow Issues:
  • Problem: Requisitions are stuck in the approval process and not moving forward.
  • Troubleshooting: Verify the approval workflow setup. Ensure that approvers are correctly assigned, approval limits are properly configured, and email notifications are working. Check if approvers are receiving and acting upon approval requests. Dynamics GP workflow history can be reviewed to pinpoint where the requisition is stalled.
• Data Entry Errors:
  • Problem: Requisitions are rejected due to incorrect or incomplete data.
  • Troubleshooting: Review the data entry process and ensure users are properly trained on filling out requisition fields correctly. Implement data validation rules where possible to prevent errors at the point of entry. Provide clear instructions and guidelines for completing requisitions.
• Integration with Inventory and Purchasing Modules:
  • Problem: Issues with items not being correctly linked to inventory or purchase order creation failing after requisition approval.
  • Troubleshooting: Verify item setup in Dynamics GP. Ensure items are properly configured in both the Inventory and Purchasing modules. Check for any discrepancies in item numbers, descriptions, and unit of measure. Review the process of converting requisitions to purchase orders for any errors or missing steps.
• User Permissions and Security:
  • Problem: Users are unable to create or modify requisitions, even if they should have access.
  • Troubleshooting: While the navigation list issue is not related to standard security, general requisition access is controlled by Dynamics GP security roles and tasks. Verify that users have the necessary security roles and tasks assigned to access and manage requisitions. Check for any custom security settings that might be restricting access.

By understanding the functionality of Purchase Requisitions, their importance, and the configuration options within Dynamics GP, organizations can effectively manage their procurement processes. Regularly reviewing setup configurations and addressing common issues proactively ensures a smooth and efficient purchasing workflow.

If you continue to experience issues with Purchase Requisitions in Dynamics GP, or have further questions about configuration and best practices, consider reaching out to a Dynamics GP consultant or your internal IT support team for specialized assistance.

Do you have any further questions or experiences with Purchase Requisitions in Dynamics GP that you’d like to share in the comments below?