# Export Shipping Documents: Packing List, Certificate of Origin, A.TR, EUR.1 and Bill of Lading Instructions

> A custom form program that prepares the export document set automatically from the export delivery. The packing list is built per carton and pallet, the certificate of origin and the A.TR and EUR.1 movement certificates follow the field layout of the official forms, and the bill of lading instructions are prepared for the forwarder; the documents are produced as PDF in the language and layout the customer asks for.

- Type: Program, Custom development, Form
- Module: SD
- Estimated effort: L (10–15 working days)
- Last updated: 2026-11-17
- URL: https://nekuhub.com/en/programs/export-shipping-documents-forms/


## Why is the standard not enough?

Standard SAP keeps export data (commodity code, country of origin, customs office of exit) and packing data on the delivery, but has no ready forms that print a packing list, certificate of origin, A.TR, EUR.1 or bill of lading instructions from this data. VL71 processes delivery output but does not produce these documents, and global trade products need a separate licence and implementation. As a result the documents are usually retyped in Excel and figures such as weights and carton counts drift away from the delivery.

### Closest standard alternatives

- VL71: Processes delivery output; does not produce the export document set.
- VL03N: Shows the foreign trade and packing data on the delivery; does not print documents.

## Tables used

| Table | Role | Access | Join | System |
|---|---|---|---|---|
| LIKP | Delivery header: ship-to, goods issue date, total weight and volume (driving table) | Read | - | ECC + S/4 |
| LIPS | Delivery items: material, batch, quantity, weight | Read | LIPS-VBELN = LIKP-VBELN | ECC + S/4 |
| VEKP | Handling unit (carton, pallet) header: packaging material, weight, volume | Read | VEKP-VPOBJKEY = LIKP-VBELN | ECC + S/4 |
| VEPO | Handling unit contents: delivery item and packed quantity | Read | VEPO-VENUM = VEKP-VENUM | ECC + S/4 |
| EIKP | Foreign trade header data: customs office of exit, mode of transport | Read | EIKP-EXNUM = LIKP-EXNUM | ECC + S/4 |
| EIPO | Foreign trade item data: commodity code and country of origin | Read | EIPO-EXNUM = EIKP-EXNUM | ECC + S/4 |
| VBPA | Consignee, notify party and forwarder | Read | VBPA-VBELN = LIKP-VBELN | ECC + S/4 |
| VBKD | Incoterms and location | Read | VBKD-VBELN = LIPS-VGBEL | ECC + S/4 |
| KNA1 | Customer name, language and country | Read | KNA1-KUNNR = LIKP-KUNNR | ECC + S/4 |
| T005 | Country names and country groupings | Read | T005-LAND1 = KNA1-LAND1 | ECC + S/4 |
| NAST | Output record of the printed documents | Read | NAST-OBJKY = LIKP-VBELN | ECC + S/4 |

## BAPIs and functions used

- FP_FUNCTION_MODULE_NAME: Finds the interface function of each document form
- FP_JOB_OPEN: Opens the document set as one print job
- FP_JOB_CLOSE: Closes the print job and returns the PDF
- READ_TEXT: Reads the shipping and packing notes on the delivery
- SO_NEW_DOCUMENT_ATT_SEND_API1: Emails the documents to the forwarder and the customer

## Selection screen parameters

| Parameter | Description | Type | Reference field | Required |
|---|---|---|---|---|
| S_VBELN | Delivery | Range / multiple | LIKP-VBELN | Yes |
| S_VSTEL | Shipping point | Range / multiple | LIKP-VSTEL | No |
| S_WADAT | Planned goods issue date | Range / multiple | LIKP-WADAT | No |
| P_PACK | Packing list | Checkbox | - | No |
| P_ORIG | Certificate of origin | Checkbox | - | No |
| P_MOVC | A.TR / EUR.1 movement certificate | Checkbox | - | No |
| P_BLINS | Bill of lading instructions | Checkbox | - | No |
| P_SPRAS | Document language (blank = customer language) | Single value | KNA1-SPRAS | No |
| P_MAIL | Send the documents by email | Checkbox | - | No |

## Result list columns

| Column | Source |
|---|---|
| Delivery | LIKP-VBELN |
| Customer | LIKP-KUNNR |
| Destination country | KNA1-LAND1 |
| Cartons / pallets | Calculated: Number of VEKP records (without packing, the carton count in the delivery text) |
| Gross weight (kg) | Calculated: Σ VEKP-BRGEW; without packing LIKP-BTGEW |
| Commodity codes | Calculated: Number of distinct EIPO-STAWN values |
| Document | Calculated: Packing list, certificate of origin, A.TR, EUR.1 or bill of lading instructions |
| Language | NAST-SPRAS |
| Status | Calculated: Prepared, sent, warning or error |
| Message | Calculated: Missing data warning or sending message |

## How does the program work?

1. LIKP/LIPS are read for the selected export deliveries; if packing is used, cartons and pallets come from VEKP/VEPO and gross and net weight, volume and contents are derived for each handling unit. Without packing, weights are calculated from the delivery items.
2. Export data comes from EIKP and EIPO: commodity code (STAWN), country of origin (HERKL) and customs office of exit. Items with a missing commodity code or origin go to a warning list before printing.
3. The parties are taken from VBPA: consignee, notify party and forwarder. Incoterms and their location come from VBKD, country names from T005.
4. Depending on the selection the document set is produced: packing list, certificate of origin, A.TR or EUR.1, and bill of lading instructions. The choice between A.TR and EUR.1 follows a rule defined during installation for the destination country and the origin status of the goods; the movement certificates are printed to match the fields of the official form or produced as a data sheet for the electronic application.
5. Customer-specific layout settings (language, extra columns, use of logo) are read per customer. The documents are converted to PDF and, if requested, sent to the forwarder and the customer with SO_NEW_DOCUMENT_ATT_SEND_API1.
6. The result is listed for each delivery and document; the print information is written to the delivery's output record (NAST).

## Authorization objects

- V_LIKP_VST: Delivery display and output authorization by shipping point
- S_OC_SEND: Authorization to send external email from SAP

## Frequently asked questions

### How are A.TR and EUR.1 printed on the official forms?

Because the official forms are pre-printed, the program prints the values so that they fall into the boxes of the form; alignment is calibrated with the printer used during installation. If the certificates are applied for electronically, the same data is prepared as a sheet to transfer into the application.

### We do not use handling units; can the packing list still be prepared?

Yes. In that case weight and volume come from the delivery items, and the carton count and contents are entered in the delivery text or in a small entry screen of the program.

### Each customer wants a different packing list format; is that supported?

The set of columns, language and use of logo are set per customer. If a completely different layout is needed, an additional form variant using the same data structure is added; this means roughly 1–2 extra days per variant.

---
Let us build this program for your system: https://nekuhub.com/en/request-a-quote/?report=sd-export-shipping-documents
