Working With Inventory Visibility Across Sites
Pulled up the standard report this morning only to find three warehouses showing zero stock when I knew damn well we had product sitting on the shelf. The discrepancy came down to how the system was classifying unrestricted-use stock versus quality inspection stock, and more importantly, which plant-specific parameters were actually being used in the query. If you are trying to get a clean read on your Iv Sites On Hand data, here is what you need to know. The basic view pulls stock quantities across your defined warehouse or plant sites and breaks them down by material, stock type, and availability status. Most people stop there. The report itself is straightforward enough, but the real problems show up when you start digging into the details. In a standard setup, unrestricted stock at a given site will report correctly, but blocked stock, returns, or goods in transit can be hidden depending on your selection parameters. I spent two weeks tracking down phantom stock disappearances before I realized our team had been running the query with a date restriction that excluded recently posted goods receipts. The stock was there. It just had a posting date that fell outside the default filter window. Start by making sure your selection screen includes the relevant date fields. Posting date, entry date, and movement date are three different things and they do not always align. If you only filter on posting date and your team is doing backdated goods receipts, you will miss material that physically arrived but was entered into the system retroactively. Add all three date fields to your query parameters. It adds about thirty seconds to the setup time but saves you from coming back to the same problem three days later.
Next, check your storage location assignments. Material numbers exist at the plant level, but the actual site-level on-hand figures depend on whether the storage location is properly assigned in your master data. I have seen multiple instances where a material showed zero on hand at a site because the storage location master record was missing an entry, even though warehouse staff were actively pulling from that location. Running a quick master data review at the plant level will catch this before it becomes a bigger issue. My workaround was to create a simple comparison report that listed every active storage location against its assigned material records, which flagged mismatches in about an hour for a mid-size operation.
Common Pitfalls That Nobody Warns You About
The biggest issue I run into repeatedly is stock that belongs to special stock types. Project stock, consignment, and subcontracting components are all inventory, but they do not appear in a standard sites on hand report unless you explicitly include them in your selection criteria. This is not an edge case. It is standard behavior, and most beginners do not realize it until they have a discrepancy between what the system says and what the warehouse floor reports. Another thing that catches people is the difference between available stock and total on-hand quantity. Available stock factors in committed quantities, quality inspection blocks, and returns pending disposal. If you are using this data for sales promises or production planning, relying on total on-hand without checking availability can lead to overselling or material shortfalls downstream. The system gives you both figures, but they are presented side by side and easy to skim past if you are not paying attention. There are also scenarios where the report simply will not work for you. If you operate with batch-managed materials across multiple countries with different regulatory requirements, the site-level breakdown can become unreliable without additional customization. Batch-specific stock assignments vary by region, and the standard query does not always reconcile these differences cleanly. In those cases, you are better off building a tailored report or pulling from the batch determination logs directly rather than relying on the standard on-hand view.
Getting The Data Into A Usable Format
Once you have the query dialed in, export the results to a structured format like CSV or Excel. The system does not hold onto customized selection screens very long, and if you come back to this a month later, you will spend twenty minutes re-entering parameters you had already worked out. Save your selection variant and name it something that actually describes what it does. Something like "Full On-Hand With Special Stock And Date Ranges" beats "Standard Report Two" every time. For regular reporting needs, consider scheduling the report to run automatically and distribute the output via email or file drop. This takes the manual effort out of it and gives you a consistent baseline to compare against each week. I usually set these to run Monday mornings so I can flag discrepancies before the operations team starts their week. It cuts down on late-night stock reconciliation calls significantly. If you need to pull this data programmatically, check your system's API or IDoc capabilities depending on your release. Direct extraction through a BDC session or functional module call will give you more control over which fields are included and how the data is structured before it leaves your environment. The trade-off is development time, but if you are doing this more than once a month, the investment pays for itself quickly.
Iv Sites On Hand reporting is one of those things that sounds simple until you actually need it to be accurate. The report works fine for basic checks, but the real value comes from understanding what is not being shown and adjusting your parameters accordingly. A few hours of setup now prevents hours of guesswork later.
