SD Program Custom development Mass upload

Mass Post Goods Issue from a Warehouse Confirmation File Program

Short answer: A custom program that reads the picking confirmation file from an external warehouse or warehouse system, writes the picked quantity and batch to the deliveries and then posts goods issue. It checks everything in test mode first, then lists the material document and error message for every delivery.

Estimated effort
M · 4–6 working days
System
ECC and S/4HANA
Tables
6
Scope
Global
Built by
NeKuDos Teknoloji
Last updated

Why is the standard not enough?

VL06G posts goods issue collectively but expects the deliveries to be picked in the system already and the user to select them from a list; it does not read the file from the external warehouse and does not write the picked quantity and batch to the delivery. VL02N processes one delivery at a time. An external warehouse that sends hundreds of delivery confirmations a day needs a program that reads the file, checks it and posts goods issue.

Who uses it? Logistics and shipping teams, companies working with a third-party logistics (3PL) provider and SD consultants.

Closest standard alternatives

  • VL06G List of Outbound Deliveries for Goods Issue. Posts goods issue collectively; does not read a file or write the picked quantity and batch to the delivery.
  • VL02N Change Outbound Delivery. Changes and posts goods issue for one delivery at a time.

Tables used

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

TableRoleAccessSystem
LIKPDelivery HeaderDelivery header; the actual goods issue date is writtenWriteECC + S/4
LIPSDelivery Item DataDelivery item; the picked quantity and batch are writtenWriteECC + S/4
MKPFMaterial Document HeaderMaterial document header of the goods issueWriteECC + S/4
MSEGMaterial Document ItemMaterial document items of the goods issueWriteECC + S/4
VBFASales Document FlowDocument flow from the delivery to the material documentReadECC + S/4
VBUKSales Document Header Status (ECC)Goods issue status check in ECCReadECC only

S/4HANA notes

  • MKPF → MATDOC: In S/4HANA new material documents are written to MATDOC; reading MKPF works through a compatibility view. Use MATDOC or I_MaterialDocumentItem_2 directly in new reports.
  • MSEG → MATDOC: In S/4HANA MATDOC replaces MSEG; reading MSEG works through a compatibility view but is slow at high volumes.
  • VBUK → VBAK: VBUK is not used in S/4HANA. The status fields moved to the respective document header: VBAK for sales, LIKP for deliveries, VBRK for billing. It is one of the most common fixes when custom reports move from ECC.

BAPIs and functions used

  • WS_DELIVERY_UPDATEUpdate Delivery (Picking, Packing, Goods Issue). Writes the picked quantity and batch to the delivery and posts goods issue
  • BAPI_OUTB_DELIVERY_CONFIRM_DECConfirm Outbound Delivery from Decentralized System. Alternative for the delivery confirmation in a decentralized warehouse scenario
  • BAPI_TRANSACTION_COMMITCommit a BAPI transaction. Saves successful deliveries permanently

Selection screen parameters

ParameterDescriptionTypeReference fieldRequiredExample
P_FILEConfirmation file (CSV or XLSX)Single value—Yes/interface/3pl/in/onay_20261117.csv
P_SERVERRead the file from the application serverCheckbox—NoX
S_VSTELShipping point (allowed values)Range / multipleLIKP-VSTELNo1000
P_GIDATEGoods issue date when the file has noneSingle value—No17.11.2026
P_TESTTest mode (check without posting)Checkbox—NoX

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
1DeliveryLIKP-VBELNYes
2ItemLIPS-POSNRYes
3MaterialLIPS-MATNRYes
4BatchLIPS-CHARGNo
5Picked quantityLIPS-LFIMGYes
6UnitLIPS-VRKMENo
7Storage locationLIPS-LGORTNo
8Actual goods issue dateLIKP-WADAT_ISTNo

Sample upload file

1Delivery *Item *Material *BatchPicked quantity *UnitStorage locationActual goods issue date
28000462010FG-5001B261101120PC000111/17/2026
38000462020FG-5002B26104480PC000111/17/2026
48000463310FG-610040SET000211/17/2026
58000464110FG-5001B261101300PC0001
A view built with fictional sample data; not real system data.

Result list columns

#ColumnSource
1RowCalculated Row number in the file
2DeliveryLIKP-VBELN
3ItemLIPS-POSNR
4MaterialLIPS-MATNR
5Posted quantityLIPS-LFIMG
6Material documentMKPF-MBLNR
7StatusCalculated From the checks and the update: goods issued, test OK or error
8MessageCalculated First error message or the success message

Sample result list

RowDeliveryItemMaterialPosted quantityMaterial documentStatusMessage
28000462010FG-50011204900012345Goods issuedDelivery 80004620 posted
38000462020FG-5002804900012345Goods issuedDelivery 80004620 posted
48000463310FG-61000ErrorBatch is required for a batch-managed material
58000464110FG-50010ErrorPicked quantity exceeds the delivery quantity (250)
A view built with fictional sample data; not real system data.

How does the program work?

  1. The file (CSV or XLSX) is read from the user’s PC or, in a background job, from the inbound folder on the application server.
  2. Every row is checked: the delivery (LIKP) must exist and must not be goods-issued yet (VBUK-WBSTK in ECC, LIKP-WBSTK in S/4HANA), the item and material must match the delivery item (LIPS), the picked quantity must not exceed the delivery quantity, and a batch must be given for batch-managed materials.
  3. Rows are grouped per delivery; the picked quantity and batch are written to the delivery with WS_DELIVERY_UPDATE (or BAPI_OUTB_DELIVERY_CONFIRM_DEC), and the delivery quantity is adjusted to the picked quantity.
  4. In the same call goods issue is posted with the actual goods issue date from the file (or the date in the parameter when empty). In test mode the update is not called; only the checks run.
  5. The material document created is read from VBFA (VBTYP_N = R); results and messages are listed per row, failed rows are written to a separate file and the processed file is moved to an archive folder.

Performance notes

Run daily files as a background job. Make one update call and commit per delivery; the goods issue status is re-read right before each call in case the same delivery arrives in more than one file.

Features

  • Test mode (check without posting)
  • Line-by-line result and error log
  • Download failed lines as a separate file Failed rows can be corrected and uploaded again with the same template.
  • Runs as a background job The folder where the external warehouse drops its file can be processed at fixed intervals during the day.
  • Export to Excel

Authorization objects

  • V_LIKP_VSTDelivery authorization by shipping point
  • M_MSEG_BWAGoods movement authorization by movement type

Frequently asked questions

What happens if the external warehouse picks less?

The delivery quantity is reduced to the picked quantity and goods issue is posted with it. The remaining quantity stays open on the sales order and can be delivered again in the next delivery creation run.

Is it suitable for deliveries managed by WM or EWM?

For deliveries linked to warehouse management, picking is done by confirming the transfer order or warehouse task; this program does not skip that step. It is designed for deliveries whose stock is kept only at inventory management level or managed in an external warehouse.

Does it work on S/4HANA?

Yes. The functions used exist on S/4HANA as well; only the goods issue status is read from LIKP instead of VBUK, and the material document is written to MATDOC.

Related reports

SD Report Custom ALV report

Picked but Not Goods-Issued Deliveries Report

A custom ALV report that lists deliveries whose picking is complete but whose goods issue has not been posted, with the number of days they have been …

LIKP · VBUK · LIPS · KNA1

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: Mass Post Goods Issue from a Warehouse Confirmation File Program