It all started with a comment on my previous blog about purchase requisitions (PRs) making the journey to purchase orders (POs). Someone asked, “Do you have any insight on using PR with catchweight inventory? It seems not to be compatible.” And they were right, PRs and catchweight (CW) items in Dynamics 365 Finance & Operations (D365 F&O) are like oil and water. If you’ve ever scratched your head over this, you’re not alone.
If you’re anything like me, you’ve stared at your screen wondering why you can’t add catchweight (CW) items to purchase requisitions (PRs) in Dynamics 365 Finance & Operations (D365 F&O).
While it’s a bummer that PRs and CW items don’t play nicely in D365 F&O, there’s always a way to keep your procurement process humming along.
What Are Catchweight Items?
Catchweight items are those that need to be tracked in two units of measure (UoM) simultaneously. For example:
Food Industry: A box of chicken that’s sold by the box (primary UoM) but tracked by its weight (secondary UoM).
Chemical Industry: Drums of liquid chemicals tracked by volume and weight.
This dual UoM setup ensures that inventory reflects the real-world variability in weights or volumes. The nuances of catchweight go even deeper than dual UoMs—it includes considerations like weight tolerances, supplier agreements based on yield, and industry-specific compliance requirements.
Curious about the full complexity behind catchweight configurations and how they vary by industry? Don’t worry, I’m cooking up a future blog that dives into the advanced world of catchweight strategies and configurations. Stay tuned!
Why PRs and CW Items Are Not Compatible
Here’s the catch (pun intended): The purchase requisition functionality in D365 F&O is built for standard UoM items. It does not support the complexities of dual UoMs that CW items require. The system limitations include:
No Dual UoM Support in PRs
PRs are designed to capture quantities in a single UoM, making them incompatible with the two UoMs required for CW items.
Integration Gap
PRs lack the logic needed to validate and convert quantities between the primary and secondary UoMs.
Process Misalignment
CW items require specific configurations that PRs don’t accommodate, such as weight tolerances or real-time updates.
As a result, organizations relying on CW items must find alternative approaches to procure these items.
Three Workarounds for PRs with CW Items
Direct Purchase Orders (POs)
Skip the PR step altogether and create POs directly for CW items. Here’s how it works:
Enable departments to create POs with CW configurations.
Implement approval workflows on POs to ensure procurement control and compliance.
Pros: Fully compatible with CW items. Cons: Bypasses the structured PR-to-PO process, potentially increasing workload for the procurement team.
Procurement Categories in PRs
Instead of requesting a specific item, use procurement categories in PRs. For example:
Create a PR for “Frozen Meat” without specifying the exact CW item.
After approval, the procurement team converts the PR into a PO with the correct CW item details.
Pros: Maintains the PR workflow. Cons: Adds a manual step to align PRs with CW-specific configurations.
Custom Solutions
Develop a customization in D365 to enable PRs to handle CW items. This can include:
Adding fields for secondary UoMs.
Automating conversions between primary and secondary UoMs during PR approval and PO creation.
Pros: Fully integrates CW items into the PR-to-PO process. Cons: Requires development resources and ongoing maintenance.
Other Scenarios Where PRs Might Face Challenges
Catchweight isn’t the only scenario where PRs encounter hurdles. Here are additional cases to consider:
1. Non-Stocked Items with Complex Pricing Structures
Issue: Non-stocked items with tiered pricing or cost breakdowns (e.g., freight, taxes) aren’t well-handled by PRs.
Impact: Missing fields or logic in PRs may lead to inaccuracies during procurement.
2. Service-Based Procurement
Issue: PRs struggle to handle variable durations, milestones, or deliverables for services like maintenance or consulting.
Impact: These details often require manual adjustments or alternative workflows.
3. Configured or Custom Items
Issue: Items requiring specific configurations or options (e.g., manufactured-to-order items) aren’t supported in PRs.
Impact: PRs can’t capture configuration details, necessitating POs or custom processes.
4. Items Requiring Lot Tracking or Serialization
Issue: Lot or serial number tracking (e.g., pharmaceuticals) isn’t supported in PRs.
Impact: Compliance or traceability may be compromised.
5. Advanced Inventory Scenarios (e.g., Consignment Stock)
Issue: PRs can’t handle consignment inventory models where ownership and replenishment differ.
Impact: These scenarios require alternative processes or PO adjustments.
Alternative Processes to Consider
If your organization heavily relies on these specialized scenarios, consider shifting to other processes in D365:
Requests for Quotation (RFQs): For competitive sourcing of unique items.
Purchase Agreements: To lock in terms with vendors for long-term needs.
Direct POs with Workflows: Skip PRs for these cases and implement robust approval mechanisms in POs.
Pro Tips for Managing CW Items and Beyond in D365
Leverage POs: The PO module is fully compatible with CW items and other advanced procurement needs.
Vendor Collaboration: Use the vendor portal to ensure accurate tracking and updates.
Regular Reviews: Periodically review procurement workflows to identify opportunities for efficiency.
Sources Used
Final Dad Joke
Why don’t PRs like CW items? Because they just can’t carry that weight!
Catch you next time,
DynamicsDad
Comments