Special functions and settlement processes

Porsche time-slice, pearl-chain flow, PUS, and credit-note or payment-advice handling in Automotive as one connected special-process area.

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:

  1. Call-offs are planned by time window, not only by quantity.
  2. Cut-off times must be maintained consistently so call-off and goods issue stay synchronized.
  3. Transport planning and shipment release follow time-slice logic, not only calendar dates.

Pay special attention to timing consistency between detailed call-off data, shipping control, and transport order.

Pearl-chain and pearl-chain special manufacturing

In pearl-chain processing, sequences are handled in fixed order. The source adds:

  • Forecast and shipment call-offs must be treated as a synchronized takt chain.
  • Logistic part numbers bundle multiple items into uniquely movable package units.
  • Sequence release can be manual or automatic based on truck-fill logic.
  • Packaging and label printing must follow the required sequence.

For special manufacturing, additional rules apply:

  1. Special parts are planned early as a dedicated commission flow.
  2. Reference lists link commission number and production number.
  3. During goods issue, the special part must be inserted at the correct production number in the sequence.

Pick-Up Sheet (PUS) and PSA process

The PUS process controls deliveries by a specific call-off number. This number must be carried consistently across shipping and EDI output.

Operational core points from the service description:

  • The order is maintained with the matching subtype for PUS handling.
  • Detailed call-offs come from DELJIT conversion or from controlled manual creation.
  • Pick-Up-Sheet overview is the operational selection point for goods issue.
  • Labels and shipment EDI must contain the required PUS data.

For PSA scenarios, keep the planning relevance of the applicable order lines intact.

Credit-note and payment-advice handling

Credit-note process (VDA 4908)

When customer credit-note settlement is agreed, incoming data is reconciled against posted invoices and shipments.

Important rule from the service description:

  • One internal invoice per shipment is required so later reconciliation remains unambiguous.

Payment advice process (VDA 4907)

Payment advice processing builds on the credit-note layer. Reconciliation still runs through the related posted shipments and invoices.

In standard setup, both flows are processed through payment journal handling with automotive extensions.

Operational control steps

Time Controls
Before starting special flow Check order subtype, call-off mode, sequence context, and EDI guideline
Before goods issue Check sequence release, packaging order, label data, and transport linkage
Before EDI dispatch Check VDA message type, partner context, and scenario-specific required fields
Before settlement reconciliation Check one-invoice-per-shipment, credit-note references, and payment-advice references
In deviation cases Review process state across sales, transport, and EDI together

Typical failure patterns

Situation Possible cause Check
Time-slice delivery drifts in timing Missing or inconsistent cut-off definitions Review detailed call-off timing, shipping release, and transport timing together
Pearl-chain is packed in wrong order Sequence release or package logic incomplete Check sequence data, packaging structure, and label order
PUS data is missing in shipping output PUS number was not carried consistently Check order subtype, Pick-Up-Sheet selection, and EDI shipment data
Credit-note reconciliation is ambiguous No one-invoice-per-shipment pattern Review full chain of shipment, invoice, and VDA 4908 message
Payment advice cannot be matched clearly Missing reference to credit-note or shipment Review VDA 4907, VDA 4908, and payment posting together

Result

  • You have one clear anchor page for OEM-specific special flows and settlement scenarios.
  • You can position time-slice, pearl-chain, and PUS inside the standard process without losing detail.
  • You can secure credit-note and payment-advice reconciliation through a complete document chain.