WM Program Custom development Fiori app

Mobile Warehouse Count App with Bin and Barcode Scanning: Bin Checks, Difference Approval and Posting

Short answer: A Fiori app in which warehouse staff enter counts from a phone, tablet or handheld by scanning the bin and the product barcode. The app checks that the scanned bin belongs to the right warehouse and to a storage type open for counting, writes the count to the EWM physical inventory document, routes differences above tolerance to approval and posts approved differences directly.

Estimated effort
L · 15–25 working days
System
ECC and S/4HANA
Tables
9
Scope
Global
Built by
NeKuDos Teknoloji
Last updated

Why is the standard not enough?

Standard EWM counting is document-driven: a physical inventory document is created first, then the count is entered per document and item in the RF menu or in /SCWM/PI_COUNT. The RF screens use technical terms and expect the counter to know the document number; a bin without an open document cannot be counted by simply scanning it. Approval of differences above tolerance by a second person is only separated by authorization in the standard flow; there is no approval list. This app starts the count by scanning the bin, finds or opens the document in the background and brings difference approval into one screen.

Who uses it? Warehouse count teams, warehouse supervisors, stock control and inventory owners, cost accounting.

Closest standard alternatives

  • /SCWM/PI_COUNT Enter Physical Inventory Count. Enters counts per document and item; the document must exist first and there is no bin scan check.
  • /SCWM/RFUI EWM RF Framework Logon. Standard RF count transactions; document-driven and without a difference approval list.
  • MI04 Enter Inventory Count with Document. Count entry with a document for storage locations outside EWM; not mobile.

Tables used

The tables the program reads and updates. ECC and S/4HANA differences are marked separately.

TableRoleAccessSystem
/SCWM/LAGPEWM Storage BinsStorage bin: warehouse number, storage type, storage section; bin checkReadECC + S/4
/SCWM/AQUAEWM Available QuantityAvailable quantity, batch and HU in the bin; book side of the differenceReadECC + S/4
/SCWM/QUANEWM QuantsQuant quantities; updated when the approved count is postedRead / writeECC + S/4
/SCWM/HUHDREWM Handling Unit HeaderHeader of the scanned handling unitReadECC + S/4
MARAGeneral Material DataProduct master and barcode resolutionReadECC + S/4
MAKTMaterial DescriptionsProduct descriptionReadECC + S/4
MATDOCMaterial Documents (S/4HANA)Material documents of posted count differences (S/4HANA)ReadS/4HANA only
IKPFPhysical Inventory Document HeaderIM physical inventory document header for storage locations outside EWMRead / writeECC + S/4
ISEGPhysical Inventory Document ItemsIM physical inventory item: counted quantity, book quantity, difference flagRead / writeECC + S/4

BAPIs and functions used

  • BAPI_MATPHYSINV_CREATE_MULTCreate Physical Inventory Documents. Creates a physical inventory document for a storage location outside EWM
  • BAPI_MATPHYSINV_COUNTEnter Physical Inventory Count. Writes the count result to the IM physical inventory document
  • BAPI_MATPHYSINV_GETDETAILRead Physical Inventory Document Details. Reads book quantity and status of the IM physical inventory document

Selection screen parameters

ParameterDescriptionTypeReference fieldRequiredExample
P_LGNUMWarehouse number (user setting)Single value/SCWM/LAGP-LGNUMYesW100
S_LGTYPStorage types open for countingRange / multiple/SCWM/LAGP-LGTYPNo0010–0050
P_BLINDBlind count (hide book quantity)Checkbox—NoX
P_TOLPCQuantity tolerance for posting without approval (%)Single value—No2

Input file columns

The columns of the upload template and the SAP fields they are written to. Columns with an asterisk are mandatory.

#ColumnTarget fieldRequired
1Bin barcode/SCWM/LAGP-LGPLAYes
2Product barcodeMARA-MATNRYes
3Batch/SCWM/AQUA-CHARGNo
4Handling unit (HU)/SCWM/AQUA-HUIDENTNo
5Counted quantityISEG-MENGEYes

Sample upload file

1Bin barcode *Product barcode *BatchHandling unit (HU)Counted quantity *
2A-01-02-03HM-1001B2611-0448
3A-01-02-04YM-2040100000000000004521120
4B-03-01-010
A view built with fictional sample data; not real system data.

Result list columns

#ColumnSource
1Warehouse/SCWM/LAGP-LGNUM
2Storage bin/SCWM/LAGP-LGPLA
3Storage type/SCWM/LAGP-LGTYP
4ProductMARA-MATNR
5Product descriptionMAKT-MAKTX
6Batch/SCWM/AQUA-CHARG
7Book quantity/SCWM/AQUA-QUAN
8Counted quantityCalculated Quantity entered in the app
9DifferenceCalculated Counted quantity − book quantity
10Unit/SCWM/AQUA-UNIT
11StatusCalculated Posted, awaiting approval, recount or empty bin confirmed

Sample result list

WarehouseStorage binStorage typeProductProduct descriptionBatchBook quantityCounted quantityDifferenceUnitStatus
W100A-01-02-030010HM-1001Kraft paper reel 120 gB2611-045048-2STPosted
W100A-01-02-040010YM-2040Corrugated board sheet10012020ADAwaiting approval
W100B-03-01-010030000Empty bin confirmed
W100B-03-01-020030AM-3315Stretch film 23 micron3630-6RLRecount
A view built with fictional sample data; not real system data.

How does the program work?

  1. When the user opens the app, the warehouse number and the storage types the user may count come from the user settings; the EWM physical inventory authorization (/SCWM/PIPR) is checked. The app runs on an OData service and can be used from a browser, a handheld or a phone camera.
  2. The bin barcode is scanned. The app checks that the bin exists in /SCWM/LAGP for the selected warehouse number, that its storage type is open for counting and that the bin is not reserved for another count. If a wrong warehouse or storage type is scanned, the screen shows a red warning and the count does not start.
  3. The product, GTIN or handling unit barcode is scanned; the product name comes from MARA/MAKT. A batch is requested for batch-managed products and the HU number for handling units. If blind counting is on, the book quantity is not shown to the counter.
  4. The counted quantity is entered. If an open EWM physical inventory document exists for the bin, the count is written to its item; otherwise an ad hoc document is created for the bin and the count is entered in the same step. An empty bin is confirmed as ’empty’ with one tap.
  5. The difference is calculated against the available quantity in /SCWM/AQUA. Differences within the quantity and value tolerance set during installation are ready to post. For differences above tolerance, the /SCWM/EX_PI_PREVENT_POST BAdI blocks posting; the difference goes to the warehouse supervisor’s approval list, where the supervisor either requests a recount or approves it.
  6. Approved counts are posted in EWM: the quant quantity is updated and the difference is passed to accounting through the difference analyzer; in S/4HANA the difference material document is created in MATDOC. For storage locations not managed by EWM, the same screen opens an IM physical inventory document with BAPI_MATPHYSINV_CREATE_MULT and writes the count to IKPF/ISEG with BAPI_MATPHYSINV_COUNT (this path is also used in ECC).
  7. Every scan, count and approval is logged with user and time; the count list can be exported to Excel.

Performance notes

Use a single select per scan for the bin and stock checks; read /SCWM/AQUA by warehouse number and bin key. Cache the product barcode resolution. Post differences at the approval step in packages rather than at the moment of counting; on busy count days, leave the mass posting from the approval list to a background job.

Features

  • Line-by-line result and error log Every scan, count and approval is traced with user and time.
  • Double-click drill-down to the document The bin stock and the physical inventory document can be opened from the approval list.
  • Export to Excel The count and difference list can be exported to Excel.

Authorization objects

  • /SCWM/PIPRCreate EWM physical inventory documents and enter counts
  • /SCWM/PIBKPost inventory differences in EWM (approvers)
  • M_ISEG_WZBEnter IM counts for storage locations outside EWM
  • S_SERVICECall the app's OData service

Frequently asked questions

Do we need to create a physical inventory document beforehand?

No. If an open document exists for the bin, the app uses it; otherwise it creates an ad hoc document for the bin itself. Planned periodic or cycle count documents can be counted with the same screen.

Can the counter post the difference directly?

Only within the tolerance set during installation. Differences above tolerance are stopped before posting by the standard BAdI and go to a person with approval authorization; the approver can request a recount.

Is scanning with a phone camera enough?

For low-volume counts, yes. For intensive counting, a handheld with a trigger scanner is recommended; the app works with the same screen on both devices.

Related reports

WM Package Custom

Physical Inventory Count and Difference Pack

A four-component pack that runs a count campaign from start to finish: storage bins due for counting, bulk entry of count results from handheld …

4 components · v1.0

WM Report Custom ALV report

Cycle Count Due Bins and Count Progress Report

A custom ALV report that shows the storage bins whose count is due or overdue based on the last count date and the material's cycle counting …

LAGP · LQUA · MARC · LINK

Let us build this program for your system

Briefly describe your system and expectations. We will clarify the scope and come back with an effort and price quote.

Related report: Mobile Warehouse Count App with Bin and Barcode Scanning: Bin Checks, Difference Approval and Posting