Dynamics GP Tip: Show Required Quantity Notes on Your Picklist Summary Report

Table of Contents

The Picklist Summary Report in Microsoft Dynamics GP is a critical document for warehouse operations, providing a concise list of items and quantities needed to fulfill sales orders. It serves as the primary guide for warehouse staff to locate and pull stock from inventory. While the standard report provides essential details like item numbers, descriptions, locations, and quantities, specific nuances or instructions related to the required quantity of an item are often conveyed separately or not at all. This can lead to picking errors, delays, or incorrect fulfillment if vital information is missed.

Imagine a scenario where a customer orders a specific quantity of an item, and there are special instructions tied to that exact quantity—perhaps related to packaging, quality checks, batch selection, or handling procedures. If these instructions, stored as notes within Dynamics GP, aren’t readily available on the picklist itself, the warehouse team might proceed with standard procedures, potentially violating customer requirements or internal protocols. Integrating these “Required Quantity Notes” directly onto the Picklist Summary Report streamlines communication and improves accuracy. This tip explores how you can modify your Dynamics GP Picklist Summary report to include these important notes, focusing primarily on using the built-in Report Writer tool.

Understanding the Standard Picklist Summary Report¶

The standard Picklist Summary Report in Dynamics GP is typically generated from the Sales Order Processing (SOP) module. It aggregates line items across selected sales orders or batches. The report usually groups items by item number or location, summarizing the total quantity required across all included orders. This aggregated view is efficient for large picking operations but can sometimes obscure details specific to individual order lines, especially associated notes.

The report draws data from key SOP tables, including the SOP Header table (SOP10100) and the SOP Line table (SOP10200). Item details come from the Item Master table (IV00101). Notes in Dynamics GP are stored in a separate table, SY03900, and are linked to various records (like SOP Headers, SOP Lines, or Item Masters) via a Note Index (NOTEINDX). To display notes on a report, you need to establish the relationship between the report’s primary table (like SOP10200 for line items) and the notes table.

The primary challenge in adding notes is identifying which note is relevant and linking it correctly. While an item might have a general master note, or an order header might have an overall note, the need here is specifically for a note tied to the required quantity of a particular line item. In most standard GP configurations, a note specifically for a “required quantity” doesn’t exist as a distinct field. However, users often leverage the standard SOP Line note field (NOTEINDX on SOP10200) to capture line-specific instructions, which would implicitly include details about the quantity being ordered on that line. This is the note we will typically target.

Why Add Quantity-Specific Notes?¶

Adding notes directly onto the picklist provides immediate context and instructions to the person performing the picking task. This eliminates the need for warehouse staff to consult the original sales order screen, check separate instruction documents, or rely on verbal communication. Here are some scenarios where this is invaluable:

• Special Packaging: A customer might require a specific quantity to be packed in a non-standard way (e.g., bulk vs. individual boxes).
• Quality Control: A certain quantity from a lot might need a quality inspection before picking.
• Batch/Lot Selection: Instructions on which specific batch or lot numbers to pick for this quantity.
• Handling Instructions: Items needing special handling due to size, fragility, or temperature requirements for the ordered quantity.
• Customer-Specific Requirements: Notes detailing unique labeling or documentation needed for this specific part of the order.

Having this information printed directly on the picklist significantly reduces the chances of error. It empowers the warehouse team to pick accurately and efficiently, ensuring customer satisfaction and minimizing costly returns or rework. It transforms the picklist from a simple list of items into a comprehensive instruction set for fulfillment.

Method 1: Using Dynamics GP Report Writer¶

Dynamics GP Report Writer is the built-in tool for modifying existing reports or creating new ones. While it has limitations compared to modern reporting tools, it is powerful enough for many common customizations, including adding fields from related tables like the Notes table. This method is suitable for organizations that prefer to manage reporting directly within GP without relying on external tools like SQL Server Reporting Services (SSRS).

The process involves opening the existing Picklist Summary report, adding the Notes table (SY03900) to the report definition, linking it correctly to the SOP Line table (SOP10200), and then placing the Note Text field onto the report layout. This requires careful navigation within the Report Writer interface and an understanding of the underlying table relationships in Dynamics GP. It’s a detailed process that provides granular control over the report structure and content.

Before starting, ensure you have the necessary permissions to access and modify reports in Dynamics GP Report Writer. It is highly recommended to make a backup of the original report definition before making any changes. This allows you to revert to the standard version if needed. Customizations should ideally be done in a test environment first and thoroughly tested before deploying to the production environment. This safeguards against unintended issues or errors that might arise from report modifications.

Steps in Dynamics GP Report Writer¶

Modifying the Picklist Summary Report in Report Writer involves several key steps. Let’s outline the typical process assuming you are starting with a standard Picklist Summary report that you want to enhance. The specific report name might vary slightly depending on your GP version and any existing customizations, but the principles remain the same.

1. Open Report Writer: Navigate to Microsoft Dynamics GP, then go to Tools > Customize > Report Writer. Select Microsoft Dynamics GP as the Product and click OK.
2. Select the Report: In Report Writer, go to the Reports menu. In the Original Reports list, find the Picklist Summary report. The standard name might be something like “SOP Pick List” or “SOP Picking Report”. Select it and click Insert >> to move it to the Modified Reports list. Then select the modified report in the Modified Reports list and click Open.
3. Add Tables: In the Report Definition window, click the Tables button. You will see a list of tables already linked to the report. You need to add the Notes Master table. Click New, select System as the series, find SY03900 (Notes Master) in the list, select it, and click OK.
4. Link Tables: After adding the table, you need to link it correctly. In the Report Table Relationships window, select SOP Document Line (SOP10200) as the Primary Table. Click New. In the Child Table list, select Notes Master (SY03900). Dynamics GP will attempt to suggest a linking field based on common relationships. The correct link between SOP10200 and SY03900 is typically using the Note Index field (NOTEINDX). Ensure that NOTEINDX from SOP10200 is linked to Note Index from SY03900. The relationship type should likely be One to One or Many to One depending on how the join is configured, but the key is linking on NOTEINDX. Click OK to save the relationship. You might need to link it from the SOP Line table as the primary table to the Notes Master as the secondary table.
5. Return to Report Definition: Close the Report Table Relationships window to return to the Report Definition window.
6. Open Report Layout: In the Report Definition window, click the Layout button. This opens the report layout window, where you can visually design the report. You’ll see the headers, footers, and body sections of the report.
7. Add Note Field: In the toolbox on the left, select the Calculated Fields tab, or potentially the Table Fields tab if the link was successful. You might need to create a relationship using Calculated Fields if a direct table link isn’t straightforward or doesn’t yield the specific note you need, but linking SY03900 to SOP10200 on NOTEINDX is the standard approach. On the Table Fields tab, select Notes Master (SY03900) as the Table. You should see a field like Text Field or Note Text. Drag this field onto the Body section of the report layout, likely near the item description and quantity.
8. Format and Position: Once the Text Field (or equivalent note field) is on the layout, you can resize it, position it, and apply formatting (like font size, bolding, etc.) using the tools in the layout window. You might need to adjust the height of the Body section or other sections to accommodate the note text, especially if notes can be lengthy. Consider adding a static text label like “Note:” next to the field.
9. Save Changes: Close the report layout window, saving your changes when prompted. Close the Report Definition window, again saving your changes.
10. Grant Security: After modifying the report, you need to grant users access to the modified version. Go back to Microsoft Dynamics GP, then navigate to Tools > Setup > System > Alternate/Modified Forms and Reports. Select your User ID and the Product (Microsoft Dynamics GP), then the Type (Reports) and Series (Sales). Find the Picklist Summary report in the list. Expand it and select the radio button for “Microsoft Dynamics GP (Modified)”. Click Save. Users assigned this User ID (or a Role/Class using this ID) will now see the modified report when printing.

This detailed process in Report Writer allows you to embed the note linked directly to the sales line item quantity onto the picklist.

Considerations for Report Writer Method¶

• Note Index: Ensure the NOTEINDX field on the SOP10200 table is populated when notes are added to sales line items. If users are adding notes elsewhere (e.g., header notes, item master notes), you might need to link different tables.
• Note Length: The Text Field in SY03900 can hold substantial text. Ensure the field object on the report layout is large enough to display the note, or consider using a scrolling field or adjusting section heights.
• Performance: Adding joins to the Notes table can sometimes impact report generation performance, especially for large numbers of lines or notes. Test performance thoroughly.
• Multiple Notes: If multiple notes are associated with a single line item (less common via standard UI but possible), Report Writer might only display one, or you might need more complex logic.
• Alternative Linking: If the note you need isn’t directly on the SOP line but is perhaps on the Item Master (IV00101), you would link SOP10200 to IV00101 (on Item Number) and then IV00101 to SY03900 (on NOTEINDX from IV00101).

Report Writer is a robust tool for this type of modification, but it requires careful attention to table relationships and layout design.

Method 2: Leveraging SQL Server Reporting Services (SSRS)¶

For more complex reporting needs, or if you are already using SSRS extensively with Dynamics GP, creating the Picklist Summary report in SSRS offers greater flexibility and power. SSRS allows you to build reports using SQL queries directly against the Dynamics GP database.

Using SSRS, you can write a query that joins SOP10100, SOP10200, IV00101, and SY03900. The join to SY03900 would be a LEFT JOIN on SOP10200.NOTEINDX = SY03900.NOTEINDX. A LEFT JOIN is important so that lines without notes are still included in the report. You can then pull the TXTFIELD from SY03900 directly into your dataset.

Example SQL Query Snippet (Illustrative)¶

SELECT
    -- Select relevant fields from SOP Header and Line
    H.SOPNUMBE,
    H.CUSTNMBR,
    L.ITEMNMBR,
    L.ITEMDESC,
    L.UNIT_PRICE,
    L.QTYTOINV, -- Required Quantity
    L.UOFM,
    -- Select note text
    N.TXTFIELD AS RequiredQuantityNote
FROM
    SOP10100 H -- SOP Sales Order Header
JOIN
    SOP10200 L ON H.SOPTYPE = L.SOPTYPE AND H.SOPNUMBE = L.SOPNUMBE -- SOP Sales Order Line
LEFT JOIN
    SY03900 N ON L.NOTEINDX = N.NOTEINDX -- Notes Master
WHERE
    H.SOPTYPE = 3 -- Assuming Sales Order type (adjust if needed)
    -- Add filters for specific orders, dates, etc.

This query structure provides the foundation for an SSRS report. You would then design the report layout in SSRS, arranging the fields, grouping, and totaling as needed for a picklist summary. SSRS offers advanced formatting, conditional visibility, and deployment options not available in Report Writer. It also centralizes reporting if you are using SSRS for other business intelligence needs.

However, creating SSRS reports requires access to SQL Server Management Studio and SSRS Report Builder or Visual Studio, as well as expertise in SQL querying and SSRS report design. Security management for SSRS reports is also handled separately from GP’s internal report security.

Benefits of Enhanced Picklists¶

Integrating required quantity notes into your Picklist Summary Report offers significant operational benefits:

• Reduced Errors: Clear instructions on the picklist minimize misinterpretations and incorrect picking or packaging.
• Increased Efficiency: Warehouse staff have all necessary information in one place, reducing time spent seeking clarification.
• Improved Customer Satisfaction: Accurate and compliant order fulfillment leads to fewer customer complaints and returns.
• Streamlined Training: New staff can quickly understand specific picking requirements by referring directly to the notes.
• Enhanced Accountability: Documented notes on the physical picklist serve as a record of instructions followed or missed.

By making this seemingly small modification, you empower your warehouse team and contribute directly to more accurate and efficient order fulfillment processes within Dynamics GP. Whether you choose Report Writer or SSRS, the investment in adding this detail pays off in operational improvements and reduced costs associated with errors.

Troubleshooting and Best Practices¶

When modifying reports and working with notes in Dynamics GP, keep these points in mind:

• Test Thoroughly: Always test report modifications in a non-production environment before deploying them. Print reports with various scenarios (items with notes, items without notes, multiple lines, large quantities) to ensure everything displays correctly.
• Backup Original Reports: Before making any changes in Report Writer, export the original report definition as a package file (.package) for easy restoration.
• Document Changes: Keep clear documentation of the changes you made, including table links, fields added, and layout adjustments. This helps with future updates or troubleshooting.
• User Training: If you implement notes as a standard practice, train your order entry staff on how and where to add these quantity-specific notes (e.g., specifically using the line item note button).
• Performance Monitoring: After deploying, monitor report generation time. If performance degrades significantly, review your table links and consider optimizing the report design or the underlying data.
• Security Layers: Remember to grant security access to the modified report in Dynamics GP after saving it. Without this step, users will continue to print the original version.
• Alternative Note Sources: If your organization uses custom fields or other methods to store quantity-specific instructions, you would need to link the report to those specific tables and fields instead of or in addition to the standard SY03900 notes table.

Implementing these best practices ensures a smooth process and a reliable, enhanced picklist report that serves your warehouse operations effectively.

Conclusion¶

Enhancing your Dynamics GP Picklist Summary report to display required quantity notes is a practical customization that can significantly improve warehouse efficiency and accuracy. By leveraging tools like Dynamics GP Report Writer or SSRS, you can seamlessly integrate crucial picking instructions directly into the document used on the warehouse floor. This reduces reliance on external information sources, minimizes potential errors, and ultimately leads to faster, more accurate order fulfillment. Investing time in this report modification can yield substantial returns in operational performance and customer satisfaction.

What are your experiences with customizing Dynamics GP reports? Have you added notes or other detailed instructions to your picklists? Share your tips, challenges, and successes in the comments below!