SAP Business ByDesign connection for LinkyFlow

The fields of one report: dimensions to group by, measures to total (exact decimals), their texts and currencies, and the parameters the report is run with — mandatory ones flagged, with how each takes values and its format.

Runs one report, read-only: the columns in select, grouped by the dimensions among them, filtered — mandatory parameters included — by filters. Measures are exact decimal strings, each with its currency; a dimension comes with its text.

The analytics reports this connection’s user may run — SAP’s standard reports and the tenant’s own, from the work centres the user is assigned. Search them, read one report’s fields with reportFields, run it with reportRows.

The lines of the posted accounting documents: G/L account, debit or credit, the amount in the line and in the company currency, the profit centre and segment, and whether a reversal cancelled the line.

The documents the general ledger holds, posted (SAP AccountingDocument), read-only: company, set of books, fiscal year and period, posting date, type, and whether it reverses another. Every posting — a journal entry, an invoice, a payment — lands here; their lines are accountingDocumentLines.

The bank statements of the house bank accounts: date, account, opening and closing balance, debit and credit totals, currency, status. The closing balance of a day is the statement’s; successive statements are never added up.

Cancel Journal Entry

The companies of the tenant, by ID and UUID: what a journal entry, a document or a payment is booked for. A company ID can differ from the ID of its intercompany business partner.

The cost centres, by ID and UUID: what an expense line is assigned to.

The valid values of the codes finance publishes — types, statuses, units, accounts — so a code is never guessed. A contextual list (a G/L account per chart of accounts) answers each code with its Context.

The companies’ own bank accounts: bank account ID and IBAN, currency, house bank, blocked or not, and the minimum, maximum and overdraft thresholds — thresholds, never balances.

Journal entry vouchers (SAP AccountingEntry), newest first: what a user drafts and posts to the general ledger — company, posting date, currency, reference and three statuses (posting, life cycle, approval). Their lines are journalEntryLines; once posted, the ledger holds an accounting document of its own number (accou...

Create Journal Entry

The lines of the journal entry vouchers: G/L account, debit or credit, and the signed amounts in the transaction and the company currency. Two measures, never added together.

Incoming and outgoing payments of the companies: business partner, amounts in the transaction and the cash-location currency, value and due dates, payment form and transaction status. A payment confirmed is not yet allocated to an invoice.

Post Journal Entry

The profit centres, by ID and UUID: what a line of the ledger is reported on.

Simulate Journal Entry

Submit Journal Entry

Void Journal Entry

Acknowledge Delivery Note

Approve Return

Cancel Outbound Delivery

Customer returns: customer, date, amount, and their statuses kept apart — life cycle, approval, inbound (goods received back) and credit memo. A return proves neither a refund nor a cancelled invoice; the quantity credited is not the quantity received.

Inbound deliveries: what a supplier announced or delivered, with its processing, release, delivery-note and cancellation statuses kept apart. Stock moves when its goods receipt is posted, not before.

What is expected to arrive, from a purchase order: its source document. A request announces nothing to the warehouse and moves no stock.

The valid values of the codes logistics publishes — types, statuses, units, accounts — so a code is never guessed. A contextual list (a G/L account per chart of accounts) answers each code with its Context.

The materials (stocked products): ID, description, base unit of measure, product category. A service product is another object; the sales, logistics and valuation views of a material are each their own.

Outbound deliveries: what is shipped to a customer, with its processing, release and cancellation statuses kept apart. Stock leaves when the goods issue is posted (outboundDeliveryRequestItems), not when a delivery is created.

The lines of the outbound delivery requests: product, source line, fulfilment and cancellation status — and the goods issue that ships them without warehouse tasks.

What is to be shipped, from a sales order: its source document. A request moves no stock; its lines are outboundDeliveryRequestItems.

Post Goods Issue

Post Goods Receipt

Release Inbound Delivery

Release Outbound Delivery

Request Return Follow-Up

Revoke Delivery Cancellation

Set Delivery as Advised

The sites and locations of the tenant: ID, name, whether it is a site, a ship-from or ship-to location, whether it manages inventory, its status and time zone. A site is not a company.

The lines of the stock movements: direction (1 Inventory issue, 2 Inventory receipt), reason, stock type, location, transfer group. A transfer is an issue and a receipt sharing a transfer group — not two consumptions.

Goods and activity confirmations: the documents that record a stock change — transaction date, the document it confirms, whether it reverses another. Their lines (stockMovementLines) say the direction; the service lists movements, not stock balances.

Submit Return for Approval

Fix Planning Order

The valid values of the codes production publishes — types, statuses, units, accounts — so a code is never guessed. A contextual list (a G/L account per chart of accounts) answers each code with its Context.

Production orders, newest first: site, main product with its planned, fulfilled and open quantities, lot, requested dates, priority and status. Planned, fulfilled and open quantities are three measures, each in its own unit: never add them.

Production proposals from planning: dates, whether planning may still move them (fixed or not), supply status and status. Releasing one requests production — a requisition, then an order.

Production requisitions — what a released proposal asks the shop floor to make — and how far it went: requested, order creation started, started, finished, closed.

Release Planning Order

Release Production Order

Unfix Planning Order

Approve Time

Close Task

Create Project Baseline

Discard Time Changes

The lines of the time sheets: date, start and end, duration (ISO 8601 duration as SAP spells it: P4D (four days), PT4H (four hours). Not a number of hours.) and billable duration when it differs, project and task, service product, type and approval status.

Time sheets: the employee, the approval status and the life cycle of what they recorded. Dates, durations, projects and tasks are on their lines (employeeTimeItems).

The employees of the tenant: ID and name — the people a project, a task or a time sheet names.

Finish Task

The tasks of the projects — the summary task included — with their parent, responsible employee, planned duration, constraints and status. A tree by ParentTaskID; RightNeighbourTaskID orders siblings and is no dependency.

Create Project Task

Update Project Task

Projects, newest first: ID, name, manager, type, responsible cost centre, planned dates, completion and status. Started makes a project chargeable without releasing its tasks; Released releases them; Closed and Stopped block time and costs.