Weissr

Weissr Capex Management Connector for SAP S/4HANA®

Master data and project financialsat the core of your business.

Keep planning, budgeting and approvals aligned with current SAP master data. Create WBS elements and budgets from Weissr Capex requests, then bring commitments, invoices and payments back into Weissr.

One version of truth for

  • GL accounts
  • Company codes
  • Plants
  • Cost centres
  • Profit centres

SAP S/4HANA

On-premise and cloud deployments

REST / JSON

Native SAP connectivity

SAP Fiori

On-demand or scheduled runs

What the connector delivers

One place for master dataand project financials.

Align GL accounts, company codes, plants, cost centres and profit centres in a governed environment, alongside the financial position of each Capex project.

01 / 06

Automatic data synchronisation

Validated SAP master data flows straight into Weissr Capex forms: company codes, GL accounts, profit centres, cost centres and plants.

02 / 06

Reliable and accurate processes

Capex requests, budgets and approvals stay aligned with current SAP S/4HANA master data, improving consistency and reducing errors.

03 / 06

Native SAP deployment

Designed to go live quickly, without custom development, middleware or complex configuration.

04 / 06

Less manual maintenance

Automatic updates replace manual data entry and spreadsheet upkeep, saving teams time across planning, budgeting and approval workflows.

05 / 06

WBS elements and budgets

Create and update WBS elements from a Weissr Capex request, with overall and annual budgets built from the planned expenditure.

06 / 06

Project financials in Weissr

Bring back open purchase order commitments, posted vendor invoices and actual vendor payments, traced to their WBS elements.

From request to cash

Follow each projectfrom request to payment.

The connector follows a Capex project from the first request to the last payment.

  1. 01 · Weissr

    Requested

    A Capex request defines the project, its budget and the planned expenditure by year.

  2. 02 · Weissr → SAP

    Created

    The WBS element and its budgets are created in SAP, or updated if they already exist.

  3. 03 · SAP → Weissr

    Committed

    Purchase orders raised against the WBS element are ordered but not yet received.

  4. 04 · SAP → Weissr

    Incurred

    The vendor has invoiced and the cost is recognised.

  5. 05 · SAP → Weissr

    Paid

    Cash has left to the vendor.

Invoices and payments share the same invoice reference. Every payment can be matched back to the invoice it settles, and every invoice to the WBS element it was charged to.

Creating WBS elements and budgets in SAP

  • A REST service in SAP receives the Capex request from Weissr and creates the WBS element under the project definition named in the request, with its description, profit centre, company code and controlling area. A responsible cost centre and business area are optional.
  • An overall budget and annual budgets are built from the planned expenditure by year. The requested amount is checked against the sum of the planned expenditures.
  • The same request can be sent again safely. An existing WBS element is updated instead of duplicated, and an unchanged request returns ‘No changes applied’.
  • On update, the description, profit centre, responsible cost centre, business area and budget can change. The company code, controlling area and project definition cannot change on an existing WBS element. Such requests are rejected with a clear message.
  • Strict update mode only changes existing WBS elements and never creates new ones.
  • Every response returns the Weissr project ID unchanged, the external WBS ID and a list of messages.

Purchase orders against WBS elements

  • Purchase orders are raised in SAP in the standard way. The connector does not create purchase orders.
  • To charge a purchase order item to a WBS element, set the account assignment category to Project (P), enter the WBS element and use a G/L account that is a cost element.
  • Typically, the WBS element must be released and marked as an account assignment element before SAP accepts a purchase order on it.
  • Only items assigned to a WBS element are sent back to Weissr. Items assigned to a cost centre or an internal order are not exported, by design.

How it works

  • The connector runs natively inside SAP S/4HANA. ABAP reports send data to Weissr over REST/JSON, and a REST service in SAP receives Capex requests from Weissr.
  • Start on demand from a tile in the SAP Fiori Launchpad, or schedule a daily background job.
  • Select by date range so scheduled runs can focus on recent documents. Selection settings are saved as variants and reused on every run.
  • Reversed invoices are excluded and credit memos carry the correct sign.
  • Purchase order items split across several WBS elements are allocated proportionally, so amounts are never counted twice.

Business outcomes

Consistent structures,visible project spend.

  • Consistent financial and organisational structures across systems
  • Reduced manual updates and integration effort
  • Higher data quality, improved compliance and reporting accuracy
  • Faster time-to-value through native SAP S/4HANA connectivity
  • Stronger collaboration between finance, controlling and IT teams
  • Streamlined capital planning and approval processes
  • Greater transparency and control over investment data
  • Stronger governance across business units and geographies
  • Full visibility of project spend from commitment through invoice to payment

Security and compliance

Data exchanged between SAP S/4HANA and Weissr Capex Management stays within your controlled environment. The connector does not store or process personal data beyond what the integration requires.

Weissr AB adheres to ISO 27001 standards and complies with GDPR and other relevant data protection regulations.

Availability

The connector is available on the SAP Store and works with SAP S/4HANA® on-premise and cloud deployments.

For support or integration details, contact sales@weissr.com.

Questions

Common questions,answered directly.

Which SAP environments does Weissr Connector support?

The connector works with SAP S/4HANA on-premise and cloud deployments and is available on the SAP Store.

Which master data does it synchronise?

Core organisational master data such as GL accounts, company codes, plants, cost centres and profit centres.

Does the connector create purchase orders?

No. Purchase orders are raised in SAP in the standard way. Only items assigned to a WBS element are sent back to Weissr; items assigned to a cost centre or an internal order are not exported.

What happens if the same Capex request is sent again?

An existing WBS element is updated instead of duplicated. A request with no changes is reported as ‘No changes applied’. Strict update mode only changes WBS elements that already exist and never creates new ones.

How are invoices and payments connected?

Invoices and payments share the same invoice reference. Every payment can be matched back to the invoice it settles, and every invoice to its WBS element.

How is synchronisation run?

Start it on demand from a tile in the SAP Fiori Launchpad, or schedule it as a daily background job. Date ranges and saved selection variants let scheduled runs focus on recent documents.

Talk to us aboutyour SAP landscape.

Tell us which SAP environment and structures you run, and we will show you how Weissr Connector fits.

Book a demo