Reporting, labels, and history
Purpose
This page extends the sales process with reports, reprints, and historical control views. It describes how to reprint goods labels, which archive objects matter in daily work, and how the navigator shows gaps between shipment, transport, and EDI output.
Reports and reprints
In sales, you have not only standard BC reports, but also automotive-specific reprints and evaluation views. The important point is not only the print itself, but the right business reason for using it.
Typical reasons for a reprint are:
- damaged or lost goods labels,
- reprints for subsequent shipments or clarifications,
- quality or shipping checks,
- lack of visibility in warehouse or transport.
Reprint goods labels
Goods labels can be reopened and printed in different formats. The legacy documentation explicitly references formats such as WA VDA4902 D KLT and WA GM1724 A5.
In practice, this means:
- Choose the right label type for customer, process, and packaging.
- Filter as narrowly as possible to the concrete order or customer.
- Before printing, confirm that the correct package or shipment information is being used.
- Do not use a reprint as a correction tool for wrong document data. Use it only for business-correct information.
History and archive objects
In the historical area, these views are especially important:
- Posted transport orders for already completed transports,
- PDF monitor history for received or generated EDI file processing.
These objects answer different questions. Posted transport orders show the business-completed transport reference. PDF monitor history is more about the technical or document-related file processing.
Navigator as a control cockpit
The navigator is based on posted delivery notes and links them with transport and EDI-output information. It is therefore one of the most useful control views when you want to understand the relationship between multiple follow-up objects instead of checking only one document.
Typical questions answered by the navigator are:
- Was a transport created for a delivery note?
- Was a delivery-note EDI created for every transport?
- Are there posted delivery notes whose follow-up objects are still missing?
Working with the navigator
- Open the navigator.
- Use Re-read to load the relevant delivery notes again.
- Let the view rebuild itself based on the automotive orders.
- Narrow the list through filters.
- Jump into the individual documents when needed.
The navigator is not just a table. It is a launch point for targeted traceability.
Control steps
| Situation | What to check |
|---|---|
| Before a reprint | Is the underlying document business-correct and final? |
| When shipping transparency is missing | Is the delivery note posted, but the transport not created yet? |
| For EDI questions | Does the related file exist technically and from a business perspective? |
| For claims or clarifications | Do delivery note, transport, and goods label still match each other? |
Typical error patterns
| Situation | Possible cause | Check |
|---|---|---|
| Wrong goods label is reprinted | filters or label format were chosen too broadly | review customer scenario and report choice |
| Navigator shows gaps | transport or EDI output was never created | compare posted delivery notes with their follow-up objects |
| PDF history looks empty or incomplete | file was not processed or not archived | inspect technical processing and monitor history |
Result
- You can reprint goods labels in a controlled way.
- You know the different roles of transport archive, PDF history, and navigator.
- You can detect gaps between delivery note, transport, and EDI output early.
Links