Ask your ERP the question you would ask a colleague
Daslab reads and writes S/4HANA over a conversation: every standard OData service, live ABAP against CDS views, BAPIs and any table. The same surface covers SuccessFactors, and one prompt can use both.
No integration project.
| CustomerS/4HANA | FY revenueS/4HANA | Account managerSuccessFactors | Q4 planSuccessFactors |
|---|---|---|---|
| Meridian Steel | 4,182,900 | K. Alvarez | Tier 2 |
| Northgate Foods | 3,740,100 | R. Okafor | Tier 1 |
| Halden Marine | 2,915,600 | K. Alvarez | Tier 2 |
| Vaster Ltd | 2,204,850 | S. Lindqvist | Tier 3 |
| Order | Supplier | Quoted | Ordered | Over |
|---|---|---|---|---|
| 4500019283 | Meridian Steel | 121,000 | 128,400 | +6.1% |
| 4500018844 | Halden Marine | 64,500 | 71,900 | +11.5% |
| 4500017120 | Vaster Ltd | 18,200 | 18,640 | +2.4% |
What you paid against what you agreed
The order total is a field. The price you actually agreed is usually in the quote comparison somebody attached, so the two have never been comparable in one query.
Daslab reads both. On one on-premise estate that meant 45,188 purchase orders with their attachments filed alongside the rows, so a question can cross from one to the other without anybody exporting anything.
s4_get_purchase_orders4_get_purchase_requisitions4_get_rfqs4_get_purchase_contracts4_get_supplier_invoices4_get_attachment
Where a batch went, without opening four transactions
Stock, movements, deliveries and process orders are four screens and one story. Asked as a question, the answer is the story.
Useful when it matters most: a customer complaint, a recall, a quality hold, a count that does not reconcile.
s4_get_material_stocks4_get_material_documents4_get_outbound_deliverys4_get_inbound_deliverys4_get_process_orders4_get_product
material RETTSTE001 × 400 kg
price from contract 46000291
req. date 2026-04-02
The ones that change something stop and ask
Creating a sales order, approving leave, releasing a requisition. Real actions, through the same transaction layers your own users go through, so they are undoable by the same means.
Writes require approval. The trace covers every action, reads included. The gate is on the action, not on the conversation, so nobody is clicking through a permission dialog to ask a question.
Every approval, and who gave it, is on the scene's record afterwards.
s4_create_sales_ordersf_submit_time_offsf_approve_time_offsf_list_pending_approvals
The HR question that needs the plant to answer it
Leave requests are approved against a calendar. Whether a shift can absorb them is in the other system.
Employee Central, Compensation, Recruiting, Performance and Learning read the same way S/4 does, and a single prompt can hold both sides of the question.
sf_list_pending_approvalssf_get_time_balancesf_get_org_chartsf_list_positionssf_list_employees
| Employee | Requested | Line coverfrom S/4 | |
|---|---|---|---|
| J. Suwan | 06 to 10 Apr | 2 of 4 | clash |
| M. Prasert | 07 to 08 Apr | 2 of 4 | clash |
| A. Chai | 21 to 24 Apr | 4 of 4 | clear |
s4_abap_runs4_abap_edits4_abap_deploys4_abap_searchs4_abap_read_sources4_describe_tables4_analytic_query
A dev system you cannot break
Most ABAP work happens on a shared dev system: a heavyweight IDE, a transport request for every iteration, manual cleanup, and the risk of breaking something a colleague depends on.
Here every run is isolated in $TMP, activated, executed and deleted. Try fifty things and leave nothing behind. No transports.
Test BAPI signatures, check CDS view shapes, prove out logic, then hand over the permalink instead of a screenshot.
For the person who has to approve this
The honest answers to the objections you are about to raise, in the order they usually come up.
All of it runs through the controls your existing users already have, and the account decides the rest.
| S/4HANA | read-only account |
| SuccessFactors | read-only account |
| Gateway node | the local copy, plus documents |
| Slack, Drive, Postgres | whatever else the question needs |
SAP is rarely the only system in the question
100+ native integrations plus any MCP server. Same conversation, same scene, no glue code.
When nothing pre-built fits, Daslab writes its own code, runs it in an isolated sandbox, captures the output and cleans up.