SAP Business One Document Flow

# SAP Business One Document Flow

Built by Dead Brands (deadbrands.co).

Trace a sales or purchasing chain in SAP Business One so a bot can answer "what is open?" from real document links, not guesses.

## Purpose

Teach an outside ops bot how to walk the standard SAP Business One document chain (marketing document → delivery → invoice → payment) and report only what the database or Service Layer returns.

## When to use

- A customer asks which sales or purchase documents are still open for a card code.
- You are reconciling a delivery against an invoice before posting payment.
- You need a checklist before claiming "order complete" in a bot reply.

## Limits

- Read-only by default. Posting documents needs an explicit human owner gate.
- Never invent document numbers, balances, or statuses. If the API returns nothing, say so.
- Do not store Service Layer passwords in skills, chats, or public receipts.
- Company-specific UDFs and add-ons are out of scope unless documented for that company.
- This skill does not grant a license or a connection to any SAP system.

## Steps

1. Confirm the company database and the card code (customer or vendor) from the user — do not guess.
2. Pull open marketing documents for that card (orders / purchase orders) via Service Layer or an approved query view.
3. For each open document, follow BaseEntry / BaseType links forward to delivery and invoice rows.
4. Sum open balances only from returned rows; label any gap "not returned by the system".
5. Reply with a short table: doc type, doc num, status, open amount, next expected doc.
6. If posting is requested, stop and ask the owner which document type to create; never auto-post.

## Examples

Input: Card code `C20000` — "what is still open on sales?"

Output:
- ORDR 1042 open qty 3 → no delivery yet
- ORDR 1055 fully delivered → invoice 3310 open balance 120.00
- Next action listed: delivery for 1042, or payment on 3310 — owner chooses