Check SAP Business One inventory by tracing a sample item from its master data to the chosen warehouse, stock document and count adjustment. Record the defaults that should apply before posting. Then test an existing base document and a zero-count exception so the acceptance exercise covers more than a normal goods receipt.
Which item settings determine the proposed posting?
Prepare a small test catalogue with clear item references, descriptions and intended warehouses. Ask the logistics lead and finance lead to agree the expected treatment for each sample before the demonstration. Keep their expectations beside the sample records so the operator can explain differences against an explicit requirement.
The examples here come from SAP’s Business One 10.0 perpetual-inventory and year-end guides. Check the deployed release and localisation when applying the examples to your environment; use the relevant inventory sections as a configuration reference for the proposed exercise.
SAP Business One 10.0 offers warehouse, item-group and item-level methods for setting G/L accounts on new item records. Documentation. Ask the operator which of those methods the sample item uses and where the expected accounts should come from. Have the finance reviewer record the approved expectation before examining the resulting document. Keep a change to account determination as a specific decision with its own owner and verification evidence.
The Auto. Add All Warehouse to New Items setting adds existing warehouses to new items and new warehouses to existing items. Documentation. Include that setting in the catalogue preparation checklist. Ask the demonstrator to explain whether the proposed item-to-warehouse relationships are created through that option or maintained another way. Inspect a newly prepared sample item and compare its warehouse rows with the agreed list, including any warehouse the business does not intend to use for it.
Separate the item’s descriptive quality from its transaction settings during review. One colleague should confirm that staff can identify the intended product; another should confirm the relevant configuration against the acceptance sheet. A correct description should not be the only evidence retained for an item whose warehouse or account setup is still unresolved.
Which warehouse should a new document select?
A new SAP Business One warehouse is identified by a warehouse code and warehouse name. Documentation. Give each proposed location an unambiguous code and name in the acceptance sheet. Ask a storekeeper to identify the location without relying on the order in which warehouses happen to appear on screen. Use the same reference on the sample receipt, transfer brief and count sheet.
SAP Business One selects default warehouses in item, user and then company order. Documentation. Prepare separate examples for an item with its own default, an item using a user default and an item falling back to the company default. Ask the operator to show which warehouse is selected for a new transaction in each case. Record the actual setting used, together with the expected result and reviewer.
When a document is based on an earlier document, the documented default-warehouse change retains the warehouse from the base document. Documentation. Include an older base document in the demonstration. Change the proposed default in a controlled test environment, then create the relevant follow-on document from that base. Have the operator identify the selected warehouse and explain it against the documented rule. Keep this result separate from the example using a completely new document.
New items belonging to an item group draw defaults from that group. Documentation. Add a new sample item to an agreed group and inspect the defaults it receives. Ask the finance and logistics reviewers to compare those values with the intended treatment. If a group default is unsuitable for one item, require a documented decision about that exception rather than allowing it to disappear inside a bulk import.
Use these examples to build a compact configuration register. For each sample, record the item group, warehouse selection route, intended account determination and responsible reviewer. Preserve the register with the test documents. It should make the reason for a selected value understandable to someone who did not configure the system.
Rehearse counting and adjustment as separate decisions
Choose a small proposed counting scope and agree the physical boundaries first. Identify the item references, warehouse or bins, count time and people involved. Write down how the team will handle movements around that time, then ask the operator to demonstrate the corresponding system controls in the test environment.
SAP’s counting guide says freezing applies to selected items and is per warehouse or bin location. Documentation. Ask the demonstrator to identify exactly which item and location the proposed freeze covers. Include another location outside that scope in the worksheet and have the reviewer check the intended distinction. Require a specific explanation of the selected control rather than recording only that “stock was frozen”.
SAP’s counting example requires the count date and time to correspond to when counting takes place. Documentation. Put the intended time on the worksheet before entering the count. Have the reviewer compare the prepared list with that scope and time. If the team changes the exercise after printing or preparing the list, record the change and decide whether the original list is still suitable for the count being demonstrated.
For a counted quantity of zero, SAP’s guide requires selecting the Counted checkbox manually. Documentation. Make a zero result an explicit sample. Ask the operator to distinguish a confirmed count of zero from a line that has not yet been counted. Have the reviewer inspect the relevant state before proceeding. This is a useful handover question for staff who will enter another colleague’s physical count results.
SAP’s guide says only count results differing from in-stock quantities are copied to inventory posting. Documentation. Prepare one unchanged sample quantity and one discrepancy. Ask the operator to show what is available for posting, then have the responsible reviewer check the proposed adjustment against the physical-count worksheet. Keep the decision to accept a discrepancy assigned to the person authorised by your own process.
An original item-to-posting acceptance matrix
Complete expected values before the demonstration. Record results only after the actions have been performed, and retain the sample document references. Use a separate row for a failure and its repeat so that later reviewers can understand what changed between the two runs.
| Sample | Setting or relationship to inspect | Proposed exercise | Evidence to retain |
|---|---|---|---|
| Item with its own warehouse | Item-level default | Start a new document | Selected warehouse and item reference |
| Item using a user default | User and company settings | Start another new document | Selection route and result |
| Earlier base document | Warehouse on base document | Create follow-on document after default change | Both document references |
| Newly grouped item | Item-group defaults | Create and inspect sample item | Approved configuration comparison |
| Counted zero | Counted state and physical sheet | Enter confirmed zero | State before proposed posting |
| Count discrepancy | Count result and in-stock value | Review adjustment proposal | Reviewer decision and posting reference |
For a hypothetical parts distributor, use one item held at two warehouses. Prepare an existing document referring to the first warehouse, then propose a different default for future work. Rehearse both a new document and a follow-on document from the earlier one. Ask the reviewer to explain each selected warehouse using the configuration register and the base reference.
Next, prepare a count exercise for only one of those locations, with one unchanged quantity and one confirmed zero. Have a second colleague review the scope, count time and proposed adjustment without assistance from the operator. Any unexplained difference should remain an open acceptance item with a named investigator and a specific record to inspect.
Before closing the exercise, assemble the evidence in the same order as the workflow: item setup, warehouse selection, source document, count sheet and proposed adjustment. Ask finance to review the accounting expectation and logistics to review the physical movement. Keep their sign-offs distinct so each decision has a clear owner.
Use inventory control for the wider stock process and POS inventory integration for checkout handovers. If a website needs inventory data, describe that separate interface in the web development brief. Bring the sample configuration register to get started to discuss the intended integration scope.
By Spout Team. AI-assisted drafting by Codex using the linked primary documentation.