Blind receipt or ASN — and why it resumes an old one

Receipts differ by where the goods came from:

• from outside the company (a supplier or customer) — standard receiving, using a PZ (external receipt) document;
• from another company warehouse — the Receive from our warehouse tile on the terminal: the document is an MM issued by the warehouse the goods came from, or — if there are no MM documents — an internal receipt (PW). The tile is available only on the WMS2 terminal and only for warehouses whose transfer route specifies a return through Receiving (Shipping to a parcel for repair or a manufacturer — packing, dispatch and return).

A standard PZ receipt can be blind or based on an ASN — the only difference is whether someone specified in advance what to expect. Receiving from our warehouse works like blind receiving: you receive what arrived.

With blind receiving, the expected quantity is kept equal to the received quantity as you go — specifically to avoid reporting a false shortage.

Step by step

Start a blind receipt

1. On the WMS2 Terminal, select the Receiving module.
2. Tap New receipt.
3. If you already have an open blind receipt, the terminal returns to it with an amber Receipt resumed · Open operation · lines: {n} banner. Read the document number — it may not be today’s delivery.
4. Really need a second document? Tap New separate receipt. This button appears only when a blind receipt is already open.
5. Scan a shelf code — it is pinned in the Location bar, and the banner changes to Scan goods. From then on, every product scan goes to that shelf.
6. You can also do it in reverse: scan a product; the banner will ask you to Scan location, then scan the shelf.
7. Every put-away immediately posts the goods to stock. There is no undo — check what you scan.
8. A whole pallet? Tap Quantity: {n}, enter the number, and confirm. Above 100 units, the terminal asks again in the Confirm large quantity dialog.
9. To change shelves, tap the cross in the Location bar (hint: Remove location) or simply scan another shelf.
10. Finished? Tap Hand over for approval. The document stays a draft; the office team reconciles shortages and overages.

Receive from an ASN

1. In Receiving mode, tap From an ASN.
2. Find the document using Search number or contractor; load a longer list with Load more ({n}).
3. Is the list empty? You will see No ASNs to receive in this warehouse. This means nobody created a PZ draft — it does not mean something is broken.
4. Select an ASN. The header will show ASN · document number.
5. Scan just as you would for blind receiving. For each line, you see expected and received quantity, and the chips above the list show Matched, Shortage, and Overage.
6. An overage does not block the work — the banner turns yellow and says Overage.
7. Does the ASN track batches or serial numbers? The terminal asks you to Complete batch details; tap Batch and traceability and fill in Batch number / LOT, Serial number, or Expiry date.
8. Finished? Tap Hand over for approval.

Return to a receipt you started

1. On the start screen in Receiving mode, find the In progress section. It contains only your operations in your active warehouse.
2. Tap a row to return to the receipt with all its lines.
3. The pinned shelf does not return. Scan the location again before scanning goods.
4. Can’t see your receipt, but you know you started it? Check that you are in the same warehouse. A receipt cannot span warehouses.

Where ASNs come from

Not from the warehouse. The From an ASN list shows only PZ drafts that are not yet receipts. They are created in the Documents module — most often by processing a purchase order (ZZ → PZ) or by importing one.

If the list is empty, nobody has issued a PZ; it does not mean something is broken.

Why it resumes instead of opening a new one

Before opening a blind receipt, the terminal checks whether you already have one open in this warehouse. If you do, it returns to that receipt with an amber banner:

Receipt resumed · Open operation · lines: {n}

This is intentional. Without this behavior, frantic clicking or returning to the mode would leave more empty documents in the manager’s panel that cannot be approved or deleted.

The code you scanned to resume the receipt is not consumed as the first scan — so it does not overwrite a message you have not had a chance to read.

I really want a second receipt

When you have an open blind receipt, a second option appears: “New separate receipt.” There is one caveat — if the open one is empty, the terminal refuses:

You already have an empty receipt open. Return to it or ask the office to delete it.

Someone else’s receipt

The In progress list shows only your operations in your active warehouse. Working on a receipt started by someone else requires a separate permission; without it, you will be refused with “No permission to access this receipt.”

You cannot take over an ASN that another operator is already receiving.

Receive from our warehouse — approval and MM document

A manager approves a receipt started from the Receive from our warehouse tile in the Receiving panel, just like any other receipt. If the route uses MM documents, approval does one more thing: it creates an MM document for the ERP (for example, Wasilków → MAG) based on what was actually received.

• Approval does not wait for Subiekt. The receipt is approved even if Subiekt does not respond. Only afterwards does the system ask Subiekt how much stock the warehouse the goods returned from (in our case, Wasilków) has, and issue MM for the quantity available.
• Anything missing goes on the MM pending list in Documents. Below the approval banner, a message appears: MM did not cover N units — added to MM pending (with the reason if Subiekt did not respond). The Receive from our warehouse tile on the terminal also shows an MM pending: N units chip.
• When the goods appear in Subiekt, issue the pending MM from the list using Issue MM; or reconcile it if someone moved the goods there manually — MM shortages — when Subiekt does not have enough goods for an MM document.
• Approval is blocked only for cases MM could never accept: a receipt line with neither SKU nor EAN, no active MM document type, an MM type without a draft or numbering, or a destination warehouse belonging to another company. The receipt stays unapproved, and the message says what to fix and where.

What receiving cannot do

A PZ document type that requires a contractor, a line price, a sale date, a payment due date, or approval is not suitable for receiving — the warehouse has no way to supply that data. The terminal will say:

This PZ type requires a contractor or price that receiving cannot provide. Ask an administrator to change the type settings.

Receiving itself has no supplier, price, invoice, currency, photos, damage marking, or EDI ASN. These are not missing from the documentation — they simply are not supported.