SAP PP, PM and QM Upload Templates

One of only two interfaces in this set that commit themselves by default. The schedule table is six fields, which is the whole demand plan.

What to watchLeave the version active flag blank and the requirements are created but inactive, so MRP ignores them entirely and the upload looks like it did nothing. This is the most common failure on a demand plan load and it produces no error at all.

A compact interface. Note that RETURN here is the older BAPIRETURN1 type, which has a different layout from BAPIRET2.

What to watchRETURN here is a single exporting BAPIRETURN1, the older return type with a different layout from BAPIRET2. Error parsing written for BAPIRET2 reads the wrong fields or does not compile at all. This is the same trap as the production order BAPI, one step worse.

An unusually simple interface: one importing structure and no tables at all. The routing and BOM are pulled from master data.

What to watchRETURN on this BAPI is a single exporting structure, not a table. Every other interface in this set except the planned order one uses a RETURN table, so shared error handling breaks here. It also means exactly one message comes back, so a failed create tells you far less than usual.

An unusually thin interface. One importing structure, three exports, and no tables at all.

What to watchThe unit of measure field here has no ISO twin. Nearly every other structure in this set carries a matching field ending in _ISO so you can send PCE instead of ST. BAPI_PI_ORDER_CREATE does not, so QUANTITY_UOM must be the internal SAP unit key. The WBS element field has the same shape of trap: it is the eight digit internal number, not the readable form.

A time ticket confirmation. Goods movements can ride along with it, but only if you supply the index table that links them.

What to watchThe single RETURN can come back clean while individual confirmation lines were rejected. It is a BAPIRET1 with ten fields and no row or field reference. The per line result is in DETAIL_RETURN, and the FLG_LOCKED flag there means the order was locked, not that anything posted. Read only RETURN and a half failed run looks like a success.

Three flat importing structures and a control structure whose codes are zero padded, which is where Excel gets in the way.

What to watchThe backflush type is a two character code with a leading zero: 01 is a final backflush, 02 a reporting point backflush, 10 a separate activity backflush. Excel strips the zero and writes 1 or 2, which the interface either rejects or reads as something else entirely. Format that column as text, which this template already does.

A two step interface. The create call builds the notification in memory and a separate save call is what gives it a real number.

What to watchThe number that comes back from the create call is temporary. The real notification number only appears in the NOTIFHEADER export of BAPI_ALM_NOTIF_SAVE. A load that writes the create number into its result column records a number that does not exist, and a load that skips the save call altogether reports success and creates nothing.

A method driven interface. An instruction list says what to do and in what order, and the data sits in parallel tables.

What to watchThe order number never appears in RETURN. For internal numbering you leave the order number blank, put the placeholder %00000000001 in the method rows, and read the issued number out of ET_NUMBERS, which pairs the placeholder you sent with the number SAP assigned. Reuse the same placeholder for two orders in one call and every row collapses into one order.

Not a BAPI. This is an RFC enabled function module with classical exceptions and a commit that is on by default.

What to watchThere is no BAPI for this. BAPI_MEASUREMENTDOCUM_CREATE does not exist in the repository, and no BAPI_* module sits in the measuring point package at all. The interface people actually use is MEASUREM_DOCUM_RFC_SINGLE_001, which is RFC enabled. It behaves differently from every BAPI in this library: no BAPIRET2, classical exceptions, and it commits on its own.

The quality twin of the maintenance notification interface, with the same two step create and save behaviour.

What to watchThe work centre field takes a number, not a code. WORK_CTR is data element LGWID, NUMC 8, the work centre's internal object ID. Type a readable work centre such as ASSY01 into it and the call fails saying the value cannot be converted to a numeric type. Look up the object ID in CRHD and load that.

A three level hierarchy: characteristic, then sample, then individual measured value. Every numeric field is a character field.

What to watchThe characteristic number is not the master inspection characteristic code. INSPCHAR is a sequential number assigned to that characteristic within that lot operation when the lot was created, so it depends on the plan version and cannot be typed in from master data. Read it first with BAPI_INSPOPER_GETDETAIL and join it onto your rows.

Insert only. There is no key to re-run against, so a second load of the same file creates a second set of records.

What to watchThe hours field holds at most 99.99. CATSHOURS is a quantity of length four with two decimals, so a weekly total in one row overflows it and a third decimal is silently truncated. Enter hours per day, two decimals, or use the start and end times and let CATS work the duration out.