Dynamics GP: Back Ordered POP Items Received - Streamline Your Inventory Now!

Table of Contents

Managing inventory efficiently is critical for any business, especially when dealing with items that are temporarily out of stock but needed for customer orders. Microsoft Dynamics GP provides robust tools within its Purchase Order Processing (POP) and Sales Order Processing (SOP) modules to handle these situations. A key component in this process is understanding how the system tracks back-ordered items and their fulfillment status upon receipt from vendors. The “Back Ordered Items Received” report is designed specifically for this purpose, offering visibility into items received against open back orders.

This report serves as a bridge between purchasing and sales, indicating which received goods should be used to fulfill existing customer back orders. By providing this information, businesses can quickly allocate newly arrived inventory to waiting customers, improving fulfillment times and customer satisfaction. However, users sometimes encounter challenges with this report, such as it appearing empty or not being available when expected. Understanding the specific conditions under which this report generates data is essential for leveraging its benefits effectively.

The Back-Ordered Items Received Report: Understanding Its Purpose and Potential Issues¶

The primary function of the Back Ordered Items Received Report is to display items that have been received from a vendor via a Purchase Order Shipment and are simultaneously on back order within the Sales Order Processing module. In essence, it highlights the arrival of goods that are needed to satisfy existing customer demand captured as back orders. This report is triggered by the receiving process in POP and aims to provide an immediate link between received purchase orders and outstanding sales back orders.

When items are received against a purchase order, Dynamics GP checks if any of those items are currently on back order in SOP. If a match exists, these items are candidates for appearing on the report. The report lists the items received, the quantities, and typically identifies the sales documents (customer orders) that are waiting for these specific items. This allows warehouse or sales teams to prioritize allocation and shipment to customers who have been patiently waiting.

However, a common frustration reported by users is that this report frequently appears empty, even when they know items have been received and customer back orders exist for those items. This situation arises not from a system error, but from the specific workflow followed during the receiving transaction. The report’s generation is intricately tied to the state of the receiving transaction at a particular point in time.

The Back Ordered Items Received Report generates data only when the receiving transaction (entered via the Receivings Transaction Entry window) is saved into a batch before being posted. If a user enters a receiving transaction and immediately posts it without first saving it to a batch, the window of opportunity for this specific report to be generated in its dedicated inquiry or report window is missed. When a receipt is posted directly, the information about back-ordered items received is typically included as part of the posting journal reports, rather than appearing in the standard “Back-Ordered Items Received” report viewing area.

This distinction is crucial. Saving the receipt to a batch holds the transaction in a pending state, allowing you to review or print reports related to that batch before final posting updates inventory levels and vendor records. Posting the receipt finalizes the transaction, updating inventory and making the items available. At the moment of posting, the system processes the fulfillment of back orders, and the report information transitions from a pre-posting analysis tool to a historical record within the posting journals.

Therefore, if you find the Back-ordered items received report consistently empty, the first step in troubleshooting should be to review your receiving process. Ensure that receiving transactions are being saved to a batch before posting. This procedural step is necessary to capture the data required for this particular report to be accessible outside of the posting journal itself. Implementing a standard operating procedure that requires saving receipts to a batch can resolve this common issue and ensure valuable visibility into back-ordered item fulfillment.

Workflow Impact on Report Generation¶

To further illustrate why the report might be empty, consider the typical inventory and order flow in Dynamics GP involving back orders:

1. A Sales Order is entered for an item that is not in stock. The system records a ‘Back Order’ quantity for this item on the sales document.
2. A Purchase Order is created for this item to replenish stock and fulfill the back order.
3. The vendor ships the item.
4. Upon receiving the item, a Receivings Transaction Entry is created in POP.
5. Crucially, if this receipt is saved into a batch and then printed, the Back-Ordered Items Received Report is available for that batch. This report shows which received items can fulfill which back orders.
6. When the batch (or individual transaction if not using batches) is posted, the inventory is increased, and the system often automatically allocates stock to waiting back orders depending on setup. The Back-Ordered Items Received information becomes part of the permanent posting journal history.

If step 5 is skipped (i.e., the receipt is posted immediately without saving to a batch), the window where the report is accessible via its standard menu path is missed. The information was generated by the system during the posting process, but it resides within the posting journal for that specific receipt transaction.

For a snapshot of potential back-order fulfillment before posting a shipment (not necessarily a full receipt with cost updates), the PO Analysis Report can be useful. This report can also show items received via shipments that are saved in a batch. While similar in showing received items against purchase orders saved in a batch, its focus might be broader than just back-ordered items in SOP, depending on report options. It’s another tool for analyzing received goods before they fully hit inventory and affect back orders.

Can the Back-Ordered Items Received Report Be Reprinted?¶

The ability to reprint reports in an ERP system like Dynamics GP is often a key requirement for auditing, review, or historical analysis. However, the Back-Ordered Items Received Report has specific limitations regarding reprinting, tied directly to its purpose as a transactional report capturing a specific state at a particular moment.

You can reprint the unposted Back-Ordered Items Received Report. This is done by navigating through the Dynamics GP menus: Reports >> Purchasing >> Analysis >> Back-Ordered Items Received. This menu path allows you to access the report for receiving transactions that have been saved into a batch but have not yet been posted. In this state, the report shows items received that are currently back-ordered in Sales Order Processing, providing actionable information before the inventory levels are finalized and allocations occur.

The report can also be printed as part of the posting process from the Receivings Transaction Entry window or the batch posting window. When you post a receipt that contains items designated for back orders, Dynamics GP offers to print various journals, including the Back-Ordered Items Received Report as a component of the posting journals. Printing it at this stage captures the details of which back orders were addressed by that specific receipt.

However, the critical limitation is that this report cannot be reprinted after the shipment or shipment/invoice batch has been fully posted. Once the posting process is complete, the status of the received items changes. They are no longer considered “back-ordered items received” in the sense that they are waiting to be allocated or have just been made available. The quantities have moved from a received/pending state to an available state, and often automatically allocated to the waiting sales orders depending on your system’s setup for automatic allocation.

The system design prevents reprinting because the underlying condition the report describes – items being received while on back order – no longer exists in the same way after posting. The back-ordered quantities on the sales orders are typically reduced or fulfilled, and the inventory quantities are updated. The report is essentially a snapshot of this fulfillment event at the moment it occurs during the receipt and subsequent posting process.

If you absolutely need to see the report information after posting has occurred, the only standard method is to retrieve the posting journal that was generated at the time of the receipt’s posting. This journal contains the details of the Back-Ordered Items Received alongside other information about the transaction. Unfortunately, accessing this historical data through a dedicated, easily filterable “Back-Ordered Items Received” report window after posting is not possible within the standard functionality.

In extreme circumstances, if a historical copy of the report is crucial and the posting journal is not available, the only technical method to reproduce the scenario and potentially regenerate the report would involve restoring a database backup from before the receipt was posted. This is a drastic measure, typically only considered in critical situations due to the complexity and potential disruption it causes to ongoing system activity. It highlights how tied this report is to the live transaction state.

Understanding this limitation is key for businesses. It emphasizes the importance of printing the Back-Ordered Items Received Report either from the batch before posting or ensuring it is selected as a posting journal report during the posting process. Establishing procedures to consistently capture this report output ensures that the information is available for future reference without needing to resort to complex data recovery methods.

Visualizing the POP to SOP Back Order Flow¶

To better grasp the interaction between purchasing, inventory, sales, and the Back-Ordered Items Received Report, consider the following simplified workflow diagram:

mermaid graph TD A[Sales Order Entered] --> B{Item In Stock?}; B -- No --> C[Item Back Ordered in SOP]; B -- Yes --> D[Allocate Stock & Ship]; C --> E[Create Purchase Order]; E --> F[Receive Items from Vendor]; F --> G{Save Receipt to Batch?}; G -- Yes --> H[Batch Created]; H --> I[Print Back-Ordered Items Received Report from Batch]; H --> J[Post Receiving Batch]; G -- No --> J[Post Receiving Transaction Directly]; J --> K[Inventory Updated]; J --> L{Allocate Received Stock to Back Orders?}; L -- Yes --> M[Back Orders Fulfilled in SOP]; J --> N[Back-Ordered Items Received Info in Posting Journal]; M --> O[Ship to Customer]; I --> Review[Review Fulfillment]; N --> Review;

Diagram: Simplified workflow illustrating how items flow from Purchase Order to Sales Order back order fulfillment in Dynamics GP and where the Back-Ordered Items Received Report fits in.

This diagram shows that the opportunity to print the Back-Ordered Items Received Report from a batch (I) exists specifically after saving the receipt to a batch (H) but before posting (J). Posting (J) leads to the inventory update (K), potential allocation (L) and fulfillment (M), and importantly, places the report data into the posting journal (N), making it inaccessible from the dedicated report window afterwards.

Viewing Purchase Order Commitments Against Sales Orders¶

Beyond the specific Back-Ordered Items Received Report, which focuses on received items fulfilling back orders, users often need broader visibility into which purchase orders are intended to fulfill which sales orders, regardless of whether the items have arrived yet. This is referred to as viewing “PO Commitments.” Dynamics GP provides an inquiry window specifically for this purpose, offering a different perspective on the link between purchasing and sales demand.

To see sales documents that have items linked to open purchase orders (PO commitments), you can use the following navigation path in Dynamics GP: Inquiry >> Sales >> Sales Items. This window allows you to look up sales document details based on various criteria. Once you find a specific sales document or item within the sales module, you can drill down for more information.

Within the Sales Items Inquiry window, after locating the relevant sales document number, there is typically a link or button (often labeled like “Document Number” or similar, allowing drill-down into the document details). Clicking this link takes you to the Sales Document Inquiry window. From here, you can view details of the specific sales order, invoice, or back order. Within the line items of this sales document, if a line item is linked to a purchase order (i.e., it has a PO Commitment), there will be a visual indicator or a Purchasing button (as mentioned in the original text) that allows you to drill down further into the linked purchase order details.

Clicking the Purchasing button will display information about the purchase order(s) that are linked to that specific line item on the sales document. This shows you the PO number, vendor, quantities ordered, quantities received, and expected arrival dates (if entered). This view provides visibility into the supply side (the PO) that is intended to meet the demand side (the sales order line).

This inquiry method is invaluable for sales staff who need to provide customers with updates on their back-ordered items. By checking the PO commitment, they can see if the item has been ordered and track its progress through the purchasing cycle. It allows them to manage customer expectations based on the expected delivery from the vendor.

Furthermore, within the Sales Items Inquiry or the linked Sales Document Inquiry, you can often filter or restrict your search based on several criteria:

• Document Type: Filter by Sales Order, Back Order, Invoice, etc. Focusing on “Back Order” documents is particularly useful here.
• Item Number: Look up all sales documents (including back orders) that contain a specific item.
• Document Number: Go directly to a known sales document.
• Customer ID: View all sales documents for a particular customer.

By using these filtering options, businesses can efficiently find sales documents with PO commitments, understand the status of the linked purchase orders, and get a comprehensive view of their back order situation from the sales perspective. This inquiry differs from the “Back Ordered Items Received” report in that it shows the link between sales and purchasing before receipt, whereas the report specifically flags items at the moment of receipt that fulfill back orders. Both are essential tools for managing back orders effectively in Dynamics GP.

Best Practices for Managing Back Orders and Using Reports¶

Effective management of back-ordered items is crucial for customer satisfaction and maintaining accurate inventory records. Here are some best practices when using Dynamics GP:

1. Standardize Receiving Procedures: Implement a clear process for receiving goods. Always saving receipts into a batch before posting ensures that transactional reports like the Back-Ordered Items Received Report can be reviewed or printed from the batch.
2. Regularly Review Back Order Reports: Periodically review reports related to back orders in both Sales Order Processing and Purchase Order Processing. Understand which items are frequently back-ordered and ensure purchasing is aligned with demand.
3. Print Posting Journals: Ensure that the Back-Ordered Items Received Report is selected as a posting journal report when posting receiving transactions that include items for back orders. Save these posting journals electronically or physically for historical reference.
4. Utilize the Sales Items Inquiry: Train sales and customer service staff on how to use the Sales Items Inquiry window to view PO commitments. This empowers them to provide accurate status updates to customers waiting on back-ordered items.
5. Monitor Inventory Levels: Use Dynamics GP’s inventory management tools to set reorder points and minimum/maximum stock levels. Proactive inventory management can help reduce the frequency of back orders.
6. Understand Allocation Methods: Be aware of how your Dynamics GP system is configured to allocate received inventory to waiting sales orders (e.g., manual allocation, automatic allocation during posting). This affects how quickly back orders are fulfilled after receipt.
7. Periodic Data Review: Occasionally review historical back order data and posting journals to identify trends, bottlenecks, or recurring issues in the procurement and fulfillment process.

By following these practices and understanding the specific functionality and limitations of reports like the Back-Ordered Items Received Report, businesses can significantly improve their handling of back orders, leading to better inventory accuracy and enhanced customer service. Dynamics GP offers the tools; effective process execution ensures you get the most out of them.

Conclusion¶

The Back-Ordered Items Received Report in Microsoft Dynamics GP is a valuable tool for identifying received goods that can fulfill outstanding customer back orders. Its utility is maximized when receiving transactions are saved into batches, allowing the report to be generated and reviewed before final posting. While the report cannot be reprinted from its standard menu after posting, the information is preserved within the posting journals. Complementary tools like the Sales Items Inquiry provide broader visibility into PO commitments against sales documents, offering essential information for managing customer expectations. By understanding the workflow dependencies and utilizing the available inquiry and reporting tools effectively, businesses can streamline their back order fulfillment process and maintain accurate inventory control within Dynamics GP.

Do you have experience using the Back-Ordered Items Received report or managing back orders in Dynamics GP? Share your tips, challenges, or questions in the comments below!