SAP MM Upload Templates

The Enjoy generation requisition interface, which is the one behind ME51N. The older BAPI_REQUISITION_CREATE is structurally different and should not be used for anything current.

What to watchThe X structure trap on this BAPI is specific and catches almost everyone. In PRITEMX the field PREQ_ITEM is NUMC and holds the actual item number (00010), not a flag. PREQ_ITEMX and every other field in that structure are the flags. Put an X in PREQ_ITEM and the X row silently detaches from its data row, and the item comes back empty.

Step by step ME51N upload guide

The Enjoy generation purchase order interface. Same business logic as ME21N, including release strategy.

What to watchA purchase order is three levels deep in SAP: header (EKKO), items (EKPO) and schedule lines (EKET). This flat template covers header and item, and the schedule line is derived from the delivery date. Every data structure needs its X partner flagged, or the field is ignored.

Step by step ME21N upload guide

The change counterpart to BAPI_PO_CREATE1. The X structures do all the work here: they are what separates a field you are changing from one you are leaving alone.

What to watchThe X trap here is precise. In POITEMX the field PO_ITEM is NUMC 5 and must carry the real item number, while PO_ITEMX beside it is the flag. Put an X in PO_ITEM and the value is invalid, so the row is either ignored or applied to the wrong item. Omit the X rows entirely and the BAPI silently changes nothing at all.

The largest interface in this set, with 24 TABLES parameters. It follows the standard MM pattern of paired X structures throughout.

What to watchThe X pairing here has a twist. In ITEMX the field ITEM_NO keeps its real data element and holds the actual item number for row matching, and there is a SEPARATE ITEM_NOX flag beside it. So an item X row needs ITEM_NO set to the item number AND ITEM_NOX set to X, plus an X on every field you are sending.

One of the few interfaces that commits internally by default. It also has the most demanding structural requirement in this set: a two level package hierarchy.

What to watchService lines need a two level package hierarchy, and getting it wrong is the usual failure. One outline row carries the outline indicator and points at a sub package number, and the actual service rows sit under that sub package. Flatten it into a simple list and nothing loads.

The single interface behind every goods movement. What changes between a receipt, an issue and a transfer is the movement type and the goods movement code.

What to watchGOODSMVT_CODE is a separate parameter, not a field on the header, and the BAPI does nothing useful without it. For a goods receipt against a purchase order it is 01. Getting it wrong produces errors that read like data problems and send people looking in the wrong place.

Step by step MIGO upload guide

The same interface as any goods movement. For an other goods receipt the goods movement code is 05.

What to watchMovement type 561 is initial stock entry and it posts against an offsetting account rather than a purchase order. That makes it the fastest way to put opening balances into a new plant, and also the fastest way to put wrong numbers into the ledger. Reconcile the value, not just the quantity.

The same interface as any goods movement. For an issue the goods movement code is 03.

What to watchFor a goods issue the goods movement code is 03, and it is a separate parameter from the movement type. The movement type then decides which assignment field is mandatory: 201 needs a cost center, 261 needs an order, 551 needs a scrap reason and usually a cost center.

The same interface as any goods movement. For a transfer posting the goods movement code is 04.

What to watchA transfer has two sides and the item carries both. The issuing side uses PLANT and STGE_LOC, the receiving side uses MOVE_PLANT and MOVE_STLOC. For batch managed materials you need MOVE_BATCH as well, because the receiving batch is not assumed to be the same as the issuing one.

A compact interface. The header uses ABAP field names while the item structure uses English BAPI names, which is a frequent source of wrong column mappings.

What to watchThe header uses ABAP field names and the items use English ones, in the same call. The movement type is BWART not MOVE_TYPE, the cost center is KOSTL not COST_CENTER, and the base date is BSTER. Then on the item it is MATERIAL, PLANT and ENTRY_QNT. Mapping the header from the item's naming convention is a common failure.

The first of three steps. This creates the document, the count is entered separately, and differences are posted separately again.

What to watchThere is no exporting document number on this BAPI. The new document number comes back only inside the RETURN message variables, not in a typed field. That matters because the count step needs that number, so the loader has to parse it out of the message rather than read a clean export.

Step two of three. The document must already exist and the item numbers must be the ones SAP assigned when it was created.

What to watchA counted zero is not the same as a blank. ENTRY_QNT of zero with ZERO_COUNT blank reads as not counted. Set ZERO_COUNT to X for a line genuinely counted at zero, or the difference posting will skip it and the stock will stay on the books.

Step three of three. The difference is whatever the count step already recorded, so this interface carries no quantities at all.

What to watchThere is no quantity field in this interface at all. The difference is whatever the count step recorded, so this step only identifies which lines to post and why. A template that carries a quantity column here has been modelled on the wrong structure and the column maps to nothing.

The logistics invoice verification interface. It is what makes three way matching and GR/IR clearing work, which FB60 cannot do.

What to watchGROSS_AMOUNT and CALC_TAX_IND interact, and this is where most files fail. With automatic tax calculation on, the sum of the item amounts is net and GROSS_AMOUNT must include the tax. The BAPI rejects the document when the two do not reconcile, and the message does not always make the arithmetic obvious.

Step by step MIRO upload guide

The same structures as the invoice create BAPI. What differs is that the document is parked rather than posted, so nothing hits the ledger until someone releases it.

What to watchParking is not posting. The document gets a number and a fiscal year, and nothing reaches the general ledger until someone releases it in MIR4 or MRBR. That makes this the safe route for a bulk load of invoices that need human review, and it means reconciliation has to look at parked documents, not postings.