MIGO Goods Movement Upload from Excel

Which movement type, GM code and reference for each goods movement

In PostNow.ai the GM code is a header field. You map it once per document, usually as a fixed value. The movement type and its reference fields are line fields, mapped to columns. The combinations below are the ones most uploads need. Your configuration decides the final list, so check a new movement type in OMJJ before you build a template around it.

The reversal column follows SAP's rule that the reversal movement type is the original plus one. The movement indicator (MVT_IND) is the field people forget. A PO receipt needs B and a production-order receipt needs F; leave it blank for everything else. In PostNow.ai, map it as a fixed value on the template so nobody has to type it on every row.

BAPI_GOODSMVT_CREATE: GM codes, header and item fields

PostNow.ai reads the BAPI's interface from your own system, so the Mapping Designer lists exactly the fields your release has, including the ones added after the original release. What you see there is SAP's structure, unchanged:

The GM code tells the BAPI which classic transaction to behave like. SAP keeps the assignment in table T158G:

Two things about that table catch people out. First, there is no GM code for MIGO; SAP's own knowledge base article 2304535 says so. Second, S/4HANA no longer lets you run MB01, MB1A, MB1B, MB1C or MB11 as transactions. The BAPI still accepts the codes, and SAP's S/4HANA simplification guidance points custom code that called those transactions to this BAPI. The codes are internal switches, not screens you need.

The BAPI does not commit on its own. PostNow.ai calls BAPI_TRANSACTION_COMMIT with wait only when SAP returns no error or abort message for the document, and rolls back otherwise. A material document is all or nothing: if line 3 of 5 fails, none of the five lines post, and the next document in the sheet is processed separately.

SAP goods movement automation with PostNow.ai, step by step

PostNow.ai is an Excel add-in. Everything below happens in the workbook, against your SAP system, under your own SAP user. BAPI mode installs nothing in SAP; it needs RFC access and the same goods movement authorizations you would need in MIGO. If you have never uploaded anything from Excel before, the first-upload walkthrough covers the basics in more detail.

Pick the BAPI

Search the function library by name, or type "MIGO" or "post goods issue" into Find with AI; both lead to BAPI_GOODSMVT_CREATE. PostNow.ai loads the header, code and item structures from your system.

Map columns, fixed values and documents

Map the line fields to columns: material, plant, storage location, batch, quantity, unit and the reference fields from the table above. Give GM_CODE and MVT_IND fixed values. Posting date can come from a column, or from the dynamic value SAP_DATE if every movement posts today.

Then tell PostNow.ai where one material document ends and the next begins. You have two options. You can use an H/D marker column, where an H row carries the header and the D rows below it are lines. Or you can use flat rows: every row is a line, and a new document starts when a column such as "GR Ref" or "Delivery note" changes value. Flat rows suit scanner exports, which rarely have header rows.

Set field rules

Use a per-field date format if the posting date arrives as DD.MM.YYYY. Set leading zeros, with a target length, on numeric keys such as order numbers and reservation numbers. Leading zeros apply to numeric values only, so alphanumeric materials like TG-1001 pass through untouched. Mark the fields operators must fill, and give storage location or reason for movement a restricted list where only a few values are valid.

Validate, then Simulate

Validate checks the file offline: required fields, types, lengths, dates, decimals, allowed values. With Pre-Validation switched on, it also looks up single values in SAP's check tables, so a plant or material that does not exist is caught before posting. Stock, the PO item's open quantity and the open period are SAP's checks, and Simulate covers those. It calls the BAPI for each document and then issues BAPI_TRANSACTION_ROLLBACK, so SAP runs its real checks and returns its real messages without posting anything.

Post a pilot, then the rest

Use Run Scope to post the first document or two, check them in SAP, then run the remainder. Documents post in sheet order, top to bottom. That matters when a transfer in row 40 depends on a receipt in row 10. Each row gets a Run Log entry. For this BAPI the default success message reads "Material Document $DOC_NO posted successfully", and the number can also be written to a column of its own.

Fix and retry the failures

Retry Failed re-posts only rows whose Run Log starts with ERROR, and it rebuilds the whole document they belong to. It scans from the current Start Row downwards, so after a pilot set Start Row back to the first data row. If SAP's answer for a document was lost after it was sent, its rows are marked UNKNOWN instead of ERROR, and Retry Failed leaves them alone: look the document up in MB51 before you post it again. AI Review can explain a failed row in plain English; by default it sends only SAP's messages and the field layout, not your cell values.

Every row shows either a material document number or SAP's error text.

Once the template works, publish it. A published workbook is run-only: operators paste the day's movements, validate and run, but cannot change the mapping. If your portal has an approval policy on the template, Run waits until someone other than the submitter approves that exact data. How templates, roles and approvals fit together is on the Excel to SAP automation page.

Batches, serial numbers and stock types

PostNow.ai treats batch, stock type and serial data as ordinary BAPI fields. The rules come from SAP:

• Batch-managed materials need BATCH on every line that moves them. Without it SAP answers M7 018 "Enter batch". On a 311 transfer, put the receiving batch in MOVE_BATCH; SAP does not assume it is the same as the issuing batch.
• Stock type (STCK_TYPE) decides where a receipt lands: blank for unrestricted use, or quality inspection or blocked stock. A receipt into quality inspection is invisible to an issue that expects unrestricted stock, which is a common cause of M7 021 later in the same file.
• Serial numbers go in a second table, linked to a line by its position. One serial per line maps cleanly. Several serials on one line do not fit a one-row-per-line sheet. Prove the serial-number layout in Simulate on a test client before you rely on it.

Posting period errors: M7 053 and the open MM period

PostNow.ai sends the posting date you map, and SAP decides whether that period is open. Materials Management allows postings in the current period and the previous one. When the posting date falls outside them, every document fails with M7 053 "Posting only possible in periods &1 and &2 in company code &3". If you Simulate first, this shows on the first document and a wrong date never reaches a real run.

Look at the two periods in the message. If they are behind the calendar, the MM period has not been moved forward yet. MMRV shows the current setting, and closing the period with MMPV is a job for whoever owns period-end, not for the upload. If the periods are right and the date is wrong, the usual cause is a date read as month-first; fix it with the field's date format rather than in the cells. Finance can close the FI period separately in OB52, so a date can pass the MM check and still fail.

Reversing a goods movement: 102, 262 and BAPI_GOODSMVT_CANCEL

Documents that already posted stay in SAP when you press Stop, and a reversal is an SAP posting like any other. You can do it by hand or from a second template.

• By hand: cancel the material document in MIGO (on ECC, MBST also exists; S/4HANA removed it in favour of MIGO).
• In volume: build a PostNow.ai template on BAPI_GOODSMVT_CANCEL. It takes the material document, the year and an optional posting date, plus a table if you only reverse some lines. SAP derives the reversal movement type (102 for 101, 262 for 261) from the original. Run it on a test client first and check that the Run Log shows the reversal document's number. If it does not, build a Custom Message from SAP's message variables.
• Posting the reversal type yourself (a 262 return to stock, a 102 against the PO) also works through BAPI_GOODSMVT_CREATE. It is a new movement with its own references, not a link to the original document. Use it when the return is a business event, and use the cancel BAPI when the original was simply wrong.

Checking the result: MB51, MIGO display and MATDOC

PostNow.ai gives you the document number per row; SAP gives you the proof. Use these:

• MB51, the material document list. Select by posting date, movement type, plant and your user to see everything the run posted, line by line.
• MIGO, Display for one document. On ECC, MB03 shows it too; S/4HANA removed MB03.
• MMBE for the stock that moved, and the PO history in ME23N for receipts against purchase orders.
• Tables: on ECC the documents are in MKPF (header) and MSEG (items). In S/4HANA they are stored in MATDOC; MKPF and MSEG still answer reads, as compatibility views, so existing queries keep working.

If you have the Reports permission, the Report Library's MM-07 Goods Movements 360 pulls material documents into Excel by document, posting date or material. It shows movement-type text, quantity and local-currency value, so you can reconcile a run against its source file in the same workbook. Operators run it; designers author new queries. Its columns are shown on the goods movements report in Excel page: the same material documents, with movement-type text and material data, in one sheet.

What to plan for in a goods movement upload

PostNow.ai uses SAP's own goods movement logic, so SAP's checks come with it. Plan for these points:

• Check MB51 before re-posting a new file or an UNKNOWN row. A second Run on the same sheet offers to skip posted documents from its Run Log; for a new file with the same movements, or a row marked UNKNOWN, confirm in MB51 what already posted.
• Prove stock and open quantities with Simulate. Stock levels and PO open quantities are SAP's checks: Simulate and Run see them, and stock can change between the two.
• Warehouse and EWM follow-on steps (transfer requirements, putaway tasks) are created by SAP according to your configuration. Test one document in a warehouse-managed storage location before running a full file.

SAP goods movement upload: frequently asked questions