# Mass Post Goods Issue from a Warehouse Confirmation File Program

> 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.

- Type: Program, Custom development, Mass upload
- Module: SD
- Estimated effort: M (4–6 working days)
- Last updated: 2026-11-17
- URL: https://nekuhub.com/en/programs/mass-post-goods-issue-from-warehouse-confirmation-file/


## 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.

### Closest standard alternatives

- VL06G: Posts goods issue collectively; does not read a file or write the picked quantity and batch to the delivery.
- VL02N: Changes and posts goods issue for one delivery at a time.

## Tables used

| Table | Role | Access | Join | System |
|---|---|---|---|---|
| LIKP | Delivery header; the actual goods issue date is written | Write | - | ECC + S/4 |
| LIPS | Delivery item; the picked quantity and batch are written | Write | - | ECC + S/4 |
| MKPF | Material document header of the goods issue | Write | - | ECC + S/4 |
| MSEG | Material document items of the goods issue | Write | - | ECC + S/4 |
| VBFA | Document flow from the delivery to the material document | Read | VBFA-VBELV = LIKP-VBELN (VBTYP_N = R) | ECC + S/4 |
| VBUK | Goods issue status check in ECC | Read | VBUK-VBELN = LIKP-VBELN | ECC only |

## BAPIs and functions used

- WS_DELIVERY_UPDATE: Writes the picked quantity and batch to the delivery and posts goods issue
- BAPI_OUTB_DELIVERY_CONFIRM_DEC: Alternative for the delivery confirmation in a decentralized warehouse scenario
- BAPI_TRANSACTION_COMMIT: Saves successful deliveries permanently

## Selection screen parameters

| Parameter | Description | Type | Reference field | Required |
|---|---|---|---|---|
| P_FILE | Confirmation file (CSV or XLSX) | Single value | - | Yes |
| P_SERVER | Read the file from the application server | Checkbox | - | No |
| S_VSTEL | Shipping point (allowed values) | Range / multiple | LIKP-VSTEL | No |
| P_GIDATE | Goods issue date when the file has none | Single value | - | No |
| P_TEST | Test mode (check without posting) | Checkbox | - | No |

## Input file columns

| Column | Target field | Required |
|---|---|---|
| Delivery | LIKP-VBELN | Yes |
| Item | LIPS-POSNR | Yes |
| Material | LIPS-MATNR | Yes |
| Batch | LIPS-CHARG | No |
| Picked quantity | LIPS-LFIMG | Yes |
| Unit | LIPS-VRKME | No |
| Storage location | LIPS-LGORT | No |
| Actual goods issue date | LIKP-WADAT_IST | No |

## Result list columns

| Column | Source |
|---|---|
| Row | Calculated: Row number in the file |
| Delivery | LIKP-VBELN |
| Item | LIPS-POSNR |
| Material | LIPS-MATNR |
| Posted quantity | LIPS-LFIMG |
| Material document | MKPF-MBLNR |
| Status | Calculated: From the checks and the update: goods issued, test OK or error |
| Message | Calculated: First error message or the success message |

## 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.

## Authorization objects

- V_LIKP_VST: Delivery authorization by shipping point
- M_MSEG_BWA: Goods 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.

---
Let us build this program for your system: https://nekuhub.com/en/request-a-quote/?report=sd-goods-issue-from-warehouse-file
