Special processes and workflow on Product Documentation

Special functions and settlement processes

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

Purpose

This page bundles special-process topics from the service description that are not always daily standard but have high impact on shipping, EDI, and settlement. It covers Porsche time-slice logic, pearl-chain including special manufacturing, PUS or PSA processing, and credit-note or payment-advice procedures.

Business value

You separate standard processing clearly from OEM-specific special flows.
You see which additional fields and checks are mandatory for time-slice and sequence scenarios.
You understand how credit-note and payment-advice processing depends on posted shipments and invoices.
You document special scenarios without overloading the core sales, purchasing, and EDI pages.

Special-process landscape

graph LR;

%% Nodes
A[Delivery and detailed call-offs]
B[Porsche time-slice or pearl-chain or PUS]
C[Sequence and packaging control in goods issue]
D[Transport data and labels]
E[EDI shipment evidence]
F[One invoice per shipment]
G[Credit-note process VDA 4908]
H[Payment advice VDA 4907]

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

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

Porsche time-slice

The service description defines the Porsche flow as fixed time windows with cut-off logic. For daily operations this means:

Workflow setup and event lists

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

Purpose

This page deepens the workflow area around the practical setup of error codes and event codes, plus the daily handling of open event messages. It complements the overview page with the operational steps from the legacy documentation.

Set up error codes correctly

Error codes represent the business situations that are detected by the system. Users cannot redefine these codes freely, but they can decide which messages should be treated as ignorable in the workflow.

Workflow and event messages

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

Purpose

This page describes the workflow and event logic in Automotive. It shows how business deviations are detected, assigned to users, and tracked in daily work without requiring every process to be monitored manually.

Business value

You make deviations in sales, purchasing, and logistics processes visible early.
You assign events deliberately to users or responsibility areas.
You reduce unnecessary alerts by marking ignorable errors consciously.
You use event messages as an operational control layer above the running process.

Core logic

The workflow logic works in three steps: