Skip to content
Learn
Presentations P-00000 to P-00999
The table that decides what each document can find

The table that decides what each document can find

Make each document find the one before it · presentation 1 of 3 · for the whole-system operator — you run the books Read the transcript · Back to the series

These slides need JavaScript to advance one at a time. Without it every slide is shown below, one after another, each with its own player — or read the transcript, which carries the same steps and every word.

Make each document find the one before it · presentation 1 of 3

The table that decides what each document can find

You can say what a knock-off copies and links, explain why a finalised document can be invisible to the next one…

The link

Step 1 — Know what ties one document to the next

You will know what finding the one before it means in BigLedger.

What this step names
  1. On the new document's KO For tab you pick a finalised source
  2. Its open lines
  3. With the customer or supplier
  4. The items
  5. The quantities and the prices
  6. Are copied forward

Step 2 — See what finalising a source leaves for the next document

You will know why a finalised order can be invisible.

What this step names
  1. For every target type enabled there for this source type
  2. It writes one open-queue row per goods line
  3. Holding the quantity still open
  4. The next document's KO For grid reads nothing but those rows

The table

Step 3 — Write the pairs for each company before its first document

Each GadgetSphere company will have the pairs its documents need.

What you do
  1. Write each company's list from how it actually trades…

Step 4 — Choose one route into each downstream document

Your staff will have one way, not two, to bring goods onto an invoice.

Where this step sits
    flowchart TD
  s1["1. Know what ties one document to…"]
  s2["2. See what finalising a source leaves…"]
  s3["3. Write the pairs for each company…"]
  s4["4. Choose one route into each downstream…"]
  s5["5. Prove the chain on each company…"]
  s1 --> s2
  s2 --> s3
  s3 --> s4
  s4 --> s5
  classDef here fill:#1e40af,stroke:#1e40af,color:#ffffff,font-weight:bold;
  class s4 here;

Prove it

Step 5 — Prove the chain on each company before go-live

You will know the table works before go-live week, not during it.

What you do
  1. Keep the list of enabled pairs with each company's set-up notes…

NarrationSlide 1 of 9

Left and right arrows, or the space bar, move between slides; f is full screen and Esc leaves it. Clicking the left or right half of a slide pages it. Play and pause belong to you — nothing moves on by itself unless you tick the box above.

Last updated on
Link the login, work the exceptions, and take access back — transcriptThe table that decides what each document can find — transcript