Reports and printouts

Purpose

This page explains which outputs Controlled Sales Core provides, which data they use, and when the required data must be maintained.

CSC reports

For the sales shipment, CSC extends the standard Sales - Shipment report with its own VDA layout (SalesShipmentVDA.rdlc). The layout includes, among other things, customer and recipient addresses, unloading point, customer references, item and variant data, delivered quantities, shipping method, tracking data, and net and gross weight.

The CSC-EDI connector has no report objects of its own. It supplies EDI and transport data to the CSC business processes. The HUM-CSC connector can provide loading units from posted HUM packages for CSC reports.

How report extensions work

Report output consists of a CSC base report and can be extended by connectors:

The extensions are used automatically when the respective connector app is installed. The user still starts the base report and maintains data in the document, packaging structure, and transport; the extension reads additional data from the connected apps.

Common workflow

1. Maintain customer, ship-to address, unloading point, location, shipping agent, and item and packaging master data before shipping.
2. Create the warehouse shipment or goods issue and register the packaging structure when packaging materials and loading units must appear in output.
3. Post the shipment.
4. For the delivery note: open Reports and Analysis, start Sales - Shipment, and filter to the posted sales shipment. Select the available CSC/VDA layout SalesShipmentVDA if it is configured as a report layout in the environment.
5. For transport output: create or open the transport from the posted shipment context.
6. Complete and review transport number, delivery notes, shipper, recipient, dates, vehicle, route, bordero, and weights.
7. Start the required transport report through Reports and Analysis.
8. Filter the report to the relevant transport and review the preview.
9. Print or export the output only after the business review is complete.

Automatic data transfer

• Transport and delivery-note data are read from the selected transport.
• The HUM-CSC connector can transfer posted HUM packages into the CSC Loading Unit Print Buffer.
• The report calculates package and weight totals from the available transport and buffer data.
• The user does not maintain the buffer manually. Without posted HUM packages, the output can only show the other transport data available.

VDA4922 checks

Before printing the shipping order, review:

• delivery notes and transport lines,
• shipper, recipient, and unloading points,
• carrier handover and delivery dates,
• package and weight totals, and
• the warehouse and transport reference in 3PL/consignment scenarios.

For several delivery notes, unloading points are output per document. In the 3PL/consignment path, an unpopulated unloading point must not be a filter prerequisite. If output stops with an error concerning the loading-unit total, first review transport lines, weights, and the available HUM packaging structure.

CMR shipping document checks

The CMR shipping document uses the posted transport and the loading units provided for it. Before printing, review carrier, vehicle, bordero, shipment reference, package quantity, and weights. Changes to master data after posting do not automatically change the historical posted document.

Error patterns