Missing location code on a journal or document line
Business Central is telling you that the line has no Location Code and that the routine will not accept a blank one. This usually happens because Location Mandatory is switched on in Inventory Setup, or because the posting routine tests the field directly, as output and consumption journals do. Enter the location on the line, or set the right default so it fills in by itself.
An inventory transaction has to say where the goods are, otherwise availability, warehouse handling and costing per location all become meaningless. Inventory Setup therefore offers Location Mandatory, which makes the field compulsory on inventory lines across the company, and several routines test the field regardless of that setting because they cannot work without it. The message is precise about where to look: it names the table and the primary key of the failing record, here the item journal template, batch and line number, so you can go straight to the line rather than hunting through the batch.
The setting itself is worth keeping: without Location Mandatory, stock can be posted with no location at all, and the resulting quantities are hard to reconcile with what is physically on the shelves. The lasting fix is to make the correct location arrive by itself, through defaults on the company, on customers and vendors, and on responsibility centres, and to keep the Location Code column visible on the journals your team uses so a blank is obvious before posting. For recurring imports and integrations, set the location in the source or in the template rather than expecting users to catch it line by line.
An administrator can, and the error stops, but so does the guarantee that every inventory transaction says where the goods are. It is usually better to fix the defaults so the location fills in automatically than to remove the control that caught the blank.
The requirement applies to lines that move inventory. Lines for non-inventory or service items and general ledger lines do not need a location, while some routines, such as output and consumption journals, test the field even when Location Mandatory is off.