Direct · Express · Overnight · all Switzerland
Black VW Tiguan R on an alpine road at sunset for direct courier trips
VW Tiguan R · 320 PS4MOTION · discreet · direct
EXPRESS COURIER · DIRECT · MON–SUN
Courier service Switzerland.
Express courier. Direct.
Also overnight.

x25pronto Switzerland takes goods direct to the destination. Small loads go by car. Larger loads go by van or Van XL. Direct, express and overnight trips run Monday to Sunday when a slot is free. Free times are shown in the booking calendar. This keeps the plan clear.

Direct Mon–SunOvernight Mon–SunCar & van up to 1,000 kg
COURIER INSIGHTS

Automated matching of x25pronto bookings in SAP/Abacus

Practical guide to auto-post x25pronto booking data into SAP and Abacus. Includes mapping tables, SQL/ABAP snippets and Abacus import fields.

Quick answer

Yes. You can import x25pronto booking data into SAP (e.g. FI/CO, MM) or Abacus and post automatically. Use structured CSV/XML exports or the API, map fields to customers, cost centres and posting texts, and validate with pre-check scripts (SQL/ABAP). Below are concrete mapping tables, example SQL/ABAP snippets and recommended Abacus import fields for a reliable automated posting.

Overview: goals and prerequisites

The goal is to post x25pronto bookings into SAP or Abacus without manual entry. Prerequisites: structured export from x25pronto (CSV or XML) or API access, unique reference fields (booking_id, date), maintained customer and cost centre master data in your ERP, and import permissions.

Recommended export format and required fields

Provide a UTF-8 CSV or an XML with clear tags from x25pronto. Required fields: booking_id, booking_date, sender_id, recipient_id, weight, service_type, price_net, currency, reference_text, vehicle_type. Optional: cost_center, project_code, delivery_code. These fields simplify mapping in SAP/Abacus.

Mapping table: x25pronto -> SAP/Abacus

A concrete mapping speeds up automation. Example: - booking_id -> invoice_reference (SAP: XBLNR / Abacus: BelegNr) - booking_date -> posting_date (SAP: BUDAT / Abacus: Datum) - sender_id -> customer_number (SAP: KUNNR / Abacus: Debitor) - recipient_id -> ship_to (SAP: partner role or custom) - price_net -> amount (SAP: WRBTR / Abacus: Betrag) - currency -> currency (SAP: WAERS / Abacus: Währung) - cost_center -> cost_center (SAP: KOSTL / Abacus: Kostenstelle) - service_type -> item_text (BSEG-SGTXT / Abacus: Text) Adjust names to your internal conventions.

Example SQL query for pre-checks

Use SQL to validate records before import. Example (Postgres / MSSQL similar): SELECT booking_id, booking_date, sender_id, price_net, currency FROM x25pronto_export WHERE booking_date BETWEEN :start AND :end AND price_net IS NOT NULL AND sender_id IN (SELECT customer_number FROM customers); This identifies missing customers or null amounts before transfer to SAP/Abacus.

ABAP example: simple import and BAPI call

Small ABAP snippet as a starting point for SAP (highly simplified): DATA: lt_data TYPE TABLE OF z_x25_booking, ls_data TYPE z_x25_booking. "Populate lt_data from CSV/XML LOOP AT lt_data INTO ls_data. CALL FUNCTION 'BAPI_ACC_DOCUMENT_POST' TABLES accountgl = lt_gl currencyamount = lt_amt EXCEPTIONS OTHERS = 1. IF sy-subrc <> 0. "log error ENDIF. ENDLOOP. In production, use full BAPI table layouts and robust error handling.

Abacus: import fields and format

Abacus supports CSV or XML imports via standard tools (e.g. FiBu import). Recommended fields: - BelegNr (booking_id) - Datum (booking_date) - Debitor (sender_id) - Betrag (price_net) - Währung (currency) - Kostenstelle (cost_center) - Konto (account_code) – depending on posting logic - Text (reference_text) Ensure customer and account numbers match Abacus master data.

Frequently asked questions

How do I detect bad records before posting?

Run pre-checks via SQL: missing customers, null amounts, invalid currencies or missing cost centres. Log and quarantine those rows and notify your accounting team.

Can I route different service types to different cost centres automatically?

Yes. Define a mapping table service_type -> cost_center or project_code. During import the service_type is evaluated and the target cost centre set.

How to handle currency and VAT differences?

Provide entries in the booking currency with the currency field. If conversion is needed, convert in the ERP or supply an exchange_rate field. VAT should be handled according to your local rules; x25pronto supplies net-level pricing.

Do I need special permissions for automated imports in SAP/Abacus?

Yes. Grant service users only the required permissions for import and posting. Work with your IT security team so audit trails and authorisations meet compliance.

At a glance: Automated matching of x25pronto bookings in SAP/Abacus

Key points from this article. Follow the links to read each explanation.

Overview: goals and prerequisites The goal is to post x25pronto bookings into SAP or Abacus without manual entry. Read this section

Recommended export format and required fields Provide a UTF-8 CSV or an XML with clear tags from x25pronto. Read this section

Mapping table: x25pronto -> SAP/Abacus A concrete mapping speeds up automation. Read this section

Example SQL query for pre-checks Use SQL to validate records before import. Read this section

ABAP example: simple import and BAPI call Small ABAP snippet as a starting point for SAP (highly simplified): DATA: lt_data TYPE TABLE OF z_x25_booking, ls_data TYPE z_x25_booking. Read this section