Document Flow

Document Flow defines a chain of screens (for example order to delivery to invoice) and how each step is linked, for the relationship map on documents.

Where

Application Configuration › Helps and Document Flow (ACDR)

Who uses it

ABS consultants

When

When the product’s configuration is changed

Needs first

Nothing

What it is for

These are configuration screens: they change the product for every client that shares the configuration, so they are worked by ABS consultants, normally on the development system. The relationship map button on a saved document draws the documents it came from and led to along these steps.

Every field in plain words

General

Field	What it means	What to put
Flow	The flow code.	Required, unique.
Name	Its name.	Free text.

Flow Steps

Column	What it means	What to put
Line Sequence	Order of the step.	Optional.
From Processcode	The screen the step starts from.	Optional.
To Processcode	The screen it leads to.	Optional.
Mandatory	The step is required.	Optional.
Relation	How the two are related.	Optional.
Origin Table	Table holding the link on the line.	Optional.
Origin Header Table	Table holding the link on the header.	Optional.
Origin Key	The field that holds the source document.	Optional.
Link Method	How the link is followed.	Optional.
From Table	Source table.	Optional.
From Field	Source field.	Optional.
To Field	Target field.	Optional.
Card Display Field	Field shown on the map card.	Optional.
Card Amount Field	Amount shown on the map card.	Optional.

How to configure it

These are configuration screens: they change the product for every client that shares the configuration, so they are worked by ABS consultants, normally on the development system.

What it is connected to

If something looks wrong

• “Flow No cannot be empty”
• “Flow No cannot be Duplicate”