Production-grade sap tm data extraction tool. Read-only Basis-approved authorisations, every /SCMTMS/ business object covered (Freight Order, Freight Booking, Freight Settlement, Forwarding Order), OData + CDS + BAPI + IDoc, scheduled deltas, Parquet / JSON / FBDI / OTM REST outputs. No bespoke ABAP scaffolding.
Hand-built ABAP extractor programs against SAP TM always start cheap and end expensive. /SCMTMS/ business-object reassembly, OData pagination, CDS view authorisations and IDoc archive volume break them one by one.
SAP TM's /SCMTMS/ namespace is not difficult to read — but it is difficult to read correctly at scale. Each business object (Freight Order, Freight Booking, Shipment, Freight Settlement Document, Forwarding Order) has its own canonical graph spanning header, items, stages, business-partner assignments, charge management and document flow. Each has its own preferred extraction path (OData service, CDS view, BAPI, direct table read) depending on S/4HANA release and Feature Pack Stack. Each has its own authorisation profile. A custom ABAP program written for freight orders breaks on settlement. The settlement program breaks again on customs documentation. The customs program falls over on archived IDoc volumes the first time someone tries to read from SARA.
Syntra ETL's sap tm data extraction tool ships pre-built support for every production /SCMTMS/ business object, every OData endpoint, every CDS view and every BAPI — plus the undocumented authorisation quirks we've discovered across dozens of customer deployments. Backed by an SLA. Customers typically pay back the tool in week-three savings versus equivalent custom ABAP development, and the ongoing maintenance burden (chasing OData deprecations, updating authorisation profiles, handling new /SCMTMS/ structures introduced in each S/4HANA release) disappears entirely.
Whether you need a one-shot bulk extract for Oracle Fusion / Oracle OTM migration, a scheduled nightly delta feeding your Snowflake / BigQuery / Databricks warehouse, or a multi-TB customs and IDoc archive pull for CBP and EU customs compliance — the same sap tm data extraction tool covers every case with the same Basis-approved governance model.
Every production /SCMTMS/ business object, every interface type, every quirk handled.
Freight order roots, items, stages, business partner assignments, document flow — walked as a coherent business object via OData I_FreightOrderTP, CDS view and BAPI/SCMTMS/FRO_GET fallback.
Booking headers, items, capacity allocations, tariffs — OData I_FreightBookingTP. Modified-since watermark for delta extraction during parallel-run.
Shipment headers, deliveries, loading status, transportation networks, lanes, schedules — extracted via BAPI_SHIPMENT_GETLIST plus CDS views, preserved with execution-state for in-flight load continuity.
Settlement documents, charge lines, accruals, freight invoice requests, credit memos — OData I_FreightSettlementDoc with charge-level granularity for cent-perfect Fusion Payables reconciliation.
Forwarding orders, forwarding settlement, customs documentation (HTS, MRN, CBP entry numbers), certificates of origin — OData I_ForwardingOrderTP plus direct customs-document attachment harvest.
Archived IDocs (TRANSPORT_ORDER, SHIPMENT_NOTIF, FRT_BIL) via SARA, PI/PO and CPI integration logs — feeds the discovery / re-platform / OIC migration loop without manual export.
From PFCG role provisioning to first scheduled delta run, typically completes in 3–7 days.
Basis team imports Syntra-shipped read-only PFCG role definition scoped to /SCMTMS/ authorisations, S_RFC for BAPI calls, S_SERVICE for OData services. Technical user created. Credentials stored in your cloud KMS — Syntra never holds them in plaintext.
Extractor runtime deployed to your cloud environment (containerized, runs on Kubernetes, ECS, Cloud Run or bare VM). Network connectivity to SAP TM verified (typically via VPN or AWS PrivateLink). Output destination configured: S3 / GCS / Azure Blob for files, plus optional Fusion FBDI / OTM REST drop targets.
Per-/SCMTMS/-business-object extraction scope configured (which fiscal years, which business units, which document types). Schedule defined: one-shot bulk, nightly delta, weekly full snapshot, or any cron schedule. Output format per BO set: Parquet / JSON / FBDI / OTM REST.
Initial full-snapshot extract runs across all configured /SCMTMS/ business objects in parallel. For multi-TB customs and IDoc archives, throttled to overnight or weekend windows. Signed manifest produced with counts, sums and hashes per partition for downstream reconciliation.
Scheduled delta runs execute on cron, capturing modified-since records since the last watermark. Run logs feed your SOC 2 audit trail. Failures surface as alerts via email, Slack, PagerDuty or webhook — no silent drift.
The details that matter when the tool has to run unattended for years.
Every extract is idempotent — re-running the same scope produces byte-identical output. Failed runs resume from the last checkpoint rather than starting over.
Respects SAP Gateway throughput limits (default 12 concurrent connections, configurable lower). Automatic 503 back-off with exponential retry. Never throttles live freight tendering or settlement processing.
Every run produces a signed JSON manifest with record counts, sum totals, hash signatures, and source-modified timestamps per partition — ready for downstream reconciliation.
SAP technical user credentials encrypted at rest in cloud KMS. Parquet output and customs-document archives encrypted at rest with KMS-managed keys. TLS 1.3 in transit, SAP SNC where Basis requires.
Prometheus metrics exposed for extraction throughput, error rates, BAPI latencies, queue depth. Grafana dashboards shipped. Plug into your existing observability stack.
Every BAPI call, every OData request, every output write logged with user, timestamp, authorisation context and result. Audit logs ship to SIEM via standard syslog or CloudTrail integration.
A sap tm data extraction tool is software that authenticates to a SAP TM system, reads /SCMTMS/ namespace business objects (freight orders, freight bookings, shipments, freight settlements, charge management) through OData services, ABAP CDS views, BAPIs and archived IDocs, and streams the resulting data to a destination of your choice. Syntra ETL's sap tm data extraction tool authenticates via Basis-approved technical user with read-only authorisations, paginates through every OData endpoint, executes CDS views with proper selection criteria, calls BAPIs (BAPI_TR_GET, BAPI_TRANSPORT_GET_LIST, BAPI_SHIPMENT_GETLIST and the /SCMTMS/ BAPI family) when OData coverage is incomplete, captures modified-since watermarks for delta runs and hash-signs every output for downstream reconciliation. Output formats include Parquet for analytics, JSON Lines for downstream ETL, and FBDI / OIC payloads for direct Oracle Fusion / Oracle OTM loading.
Custom ABAP extractor programs always start cheap and end expensive. SAP TM's /SCMTMS/ namespace has hundreds of tables with intricate business-object relationships, OData services with evolving schemas across S/4HANA release lines, CDS views that change between Feature Pack Stacks, BAPIs with subtle parameter quirks, and a long tail of authorisation requirements that vary by domain. A custom ABAP program that works for freight orders falls over on settlement (different BO graph), then breaks again on customs documentation (different authorisation profile). Syntra ETL's sap tm data extraction tool ships pre-built support for every /SCMTMS/ business object, every CDS view, every BAPI quirk — backed by an SLA. Customers typically pay back the tool in week-three savings versus a hand-built equivalent.
All of them in production use: /SCMTMS/ OData services published from the SAP Gateway (Freight Order, Freight Booking, Freight Settlement Document, Forwarding Order, Forwarding Settlement Document), ABAP CDS views including I_FreightOrderTP, I_FreightSettlementDoc and I_ForwardingOrderTP, BAPI/SCMTMS/ function modules (FRO_GET, FBO_GET, FSD_GET, plus the older BAPI_SHIPMENT and BAPI_TRANSPORT families for SAP TM 9.x compatibility), archived IDocs (TRANSPORT_ORDER, SHIPMENT_NOTIF, FRT_BIL via SARA), PI/PO and CPI integration logs, and direct read-only table extracts where OData / CDS coverage is incomplete. New interface coverage gets folded in via quarterly extractor releases tracking SAP's own S/4HANA Transportation Management roadmap, so you never have to chase an OData deprecation announcement on your own.
SAP TM extraction uses a Basis-provisioned technical user with read-only authorisations scoped to the domains in your extraction plan (S_TABU_NAM for table access where required, S_RFC for BAPI calls, S_SERVICE for OData services, S_TCODE for relevant transactions, /SCMTMS/-specific authorisation objects for business-object access). Syntra ETL ships a vetted authorisation pattern: read-only role definitions you import into PFCG, encrypted credential storage in cloud KMS, SOC 2-compliant audit logging of every BAPI call and OData request, no admin shortcuts. The Basis team approves the role on first review; customers in regulated sectors (pharma, defence, financial services) routinely pass internal security review on the first attempt.
Yes. The extractor includes a built-in scheduler with cron syntax and supports modified-since delta extraction on every /SCMTMS/ business object that exposes a CHANGED_AT or LAST_CHANGE timestamp field (freight orders, bookings, settlement documents, shipments). Common schedules: nightly delta extract feeding a downstream Snowflake / BigQuery / Databricks warehouse, weekly full-snapshot extract for backup, monthly settlement-document and customs-document archive batch for CBP / EU / SOX compliance. Each scheduled run produces a signed manifest (counts, sums, hashes per partition) plus a run log captured for SOC 2 audit. Failures surface as alerts through email, Slack, PagerDuty or webhook — no silent drift.
Three primary formats: Parquet (columnar, partitioned by fiscal year and business unit, ideal for downstream analytics in Athena / BigQuery / Snowflake / Databricks / Spark), JSON Lines (newline-delimited JSON preserving the full /SCMTMS/ business-object shape, ideal for streaming pipelines or downstream ETL), and Oracle-native loaders (FBDI ZIPs for Supplier / AP Invoice / Item Import, OTM Order Release REST payloads for shipments, OIC iflow payloads for real-time integration, HDL bundles for any HCM-routed driver data). Customs documents and IDoc archives stream as their original format (XML, PDF, CSV) into cloud object storage with a hash-signed sidecar JSON capturing freight-order document number, source-modified timestamp and authorisation context. Custom output formats are configurable per domain.
Multi-TB SAP TM extractions are routine for global 3PLs and shippers. The extractor streams /SCMTMS/ business objects in parallel using a configurable connection pool (default 12, matching typical SAP Gateway throughput limits to avoid impacting live freight tendering). The extractor checkpoints progress per business object so a failed run resumes from the last successful freight order rather than starting over. Output is written directly to cloud object storage (S3, GCS, Azure Blob) with KMS-managed encryption at rest and hash signatures stored alongside. For multi-TB customs and IDoc archives, the extract is partitioned across parallel workers and typically completes in 12–36 hours depending on volume and SAP Gateway throughput. Throughput in production: roughly 50K–250K freight orders per hour per worker pod.
Yes. The sap tm data extraction tool authenticates with read-only authorisations, so no write operations ever touch the system. OData and CDS calls are rate-limited to respect SAP Gateway throughput limits (default 12 concurrent connections, configurable lower) so live freight tendering, shipment execution and settlement processing are never throttled. Heavy extracts (10 years of freight orders, customs archives, IDoc histories from SARA) are scheduled for overnight or weekend windows. No SAP TM configuration changes are required, no Basis downtime is needed, and live transportation operations continue uninterrupted. Customers routinely run scheduled nightly extracts against live production tenants for years without a single user complaint.
30-minute discovery call. We'll scope your /SCMTMS/ business-object profile, customs documentation volume, PFCG role design and downstream destination — and have a working sap tm data extraction tool running on your system within a week.