Purchasing on Product Documentation

Purchasing and order processing

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page describes the purchasing processes in Automotive based on the actual purchasing and call-off pages in the application. It shows how to maintain automotive framework orders, generate delivery call-offs, review call-off documents, trigger warehouse receipts, and keep a complete audit trail through releases, posted documents, and archives.

Business value

You work with the real pages for Automotive Purchase Order, Purchase Call Off, and Purch. Det. Call Off.
You see which mandatory fields make a delivery call-off possible and traceable in the first place.
You steer release, warehouse receipt, archives, and follow-up documents through a clear operational flow.
You recognize early which purchasing fields are informative only and which fields actually drive the daily process.

Prerequisites

Vendors, item references, and supplier-related item numbers are maintained cleanly.
The global automotive setup and vendor-specific options for call-offs or EDI are aligned.
Unloading point, plant, usage, and delivery interval have been agreed with the supplier.
Export paths and EDI processing for outgoing delivery call-offs are configured.

Key working pages in daily operations

Page	What you use it for	Typical decision
Automotive Purchase Orders	Overview of all call-off-driven purchase orders	Which order must be released, called off, or posted next?
Automotive Purchase Order	Maintenance of contract, item, plant, unloading point, shipment sequence, and call-off actions	Are all mandatory and control fields correct before release?
Delivery Call Offs	List of already generated purchase delivery call-offs for the order	Was the call-off created and linked to the correct order?
Purchase Call Off	Business view of the concrete delivery call-off with references, interval, latest delivery, and packaging data	Are call-off numbers, quantities, and delivery dates plausible?
Purch. Det. Call Off	Detailed schedule view with horizons, critical stock, receipt data, and EDI references	Do detailed schedule, receipts, and progress counters fit together?
Receipts, Invoices, and archives	Evidence for warehouse receipt, posted documents, and archived orders	Is the document flow complete and audit-ready?

Process overview

graph LR;

%% Nodes
A[Create framework order or single order]
B[Maintain mandatory fields and intervals]
C[Generate delivery call-offs periodically]
D[Send call-offs to converter and supplier]
E[Approve inbound delivery-note data]
F[Process credit memo or invoice]
G[Use reports and archives]

%% Flow
A -.- B
linkStyle 0 stroke:#ffffff
B ==> C
C ==> D
D ==> E
E ==> F
F ==> G

%% Classes
class A btProcessTitle
class B,C,D,E,F,G btProcessActive

How this fits into standard Business Central

In purchasing as well, Automotive does not replace the normal BC document flow. The solution extends it with automotive framework orders, delivery call-offs, and EDI or VDA-specific control. For end users, it is therefore important to distinguish clearly between:

Periodic activities in purchasing

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page describes the recurring purchasing activities that typically run in batch mode in Automotive. It complements the purchasing overview with the legacy wiki content for purchase delivery call-offs, credit-note notifications, and inbound delivery-note approvals.

Recurring core tasks

Generate delivery call-offs from framework orders in batch.
Send credit-note notifications to suppliers.
Approve inbound delivery notes from VDA or EDI scenarios.

Create purchase delivery call-offs

The batch run for purchase delivery call-offs is the operational bridge between the framework order and the actual supplier communication. It creates the call-offs according to the selected filters and stores the resulting file in the vendor-specific location.

Purchasing reporting and history

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page extends purchasing with the reporting and archive views that are especially important for supplier communication, difference analysis, and traceability of purchasing documents.

Reports in purchasing

In purchasing, reports are usually not just prints. They are used to compare the call-off, the purchase line, and the actual deviation.

The legacy documentation especially highlights these reports:

Purchase Call-Off VDA 4905 for individual call-off lines together with purchase lines and differences,
Purchase Call-Off (List) for a filtered overview of purchase call-offs.

When to use which report

Report	Typical use
Purchase Call-Off VDA 4905	when you need to clarify one concrete deviation or one call-off line with the supplier
Purchase Call-Off (List)	when you want to evaluate multiple call-offs together by unloading point, vendor item number, or similar criteria

The difference report is especially important when supplier and purchasing refer to the same message, but derive different quantities or dates from it.