Pre-built sap tm to oracle fusion data mapping for /SCMTMS/D_FRO_ROOT, D_FB_ROOT and D_FS_ROOT plus master data, customs documents and dangerous-goods records. 1,400+ fields mapped to Fusion SCM, Oracle OTM and Fusion Payables. Configurable, auditable, signed off field-by-field.
More projects fail on mapping than on extract. The /SCMTMS/ business-object graph has more relationships than any single transportation ops or finance lead carries in their head — pre-built crosswalks are the only way to ship a freight-order load that actually reconciles to the cent.
Every sap tm to oracle fusion migration eventually narrows down to one question: when a /SCMTMS/D_FRO_ROOT freight-order record lands on the Oracle Fusion / Oracle OTM side, exactly which fields go where, in what shape, with what default rules for unmapped attributes, and with what cross-reference back to the source. Multiply that by the 500+ attributes on a single freight order, the 200+ attributes on a settlement document, the 150+ attributes on a booking, the master-data domains and the customs chain, and the mapping problem alone consumes 3–5 months on a consultant-led project.
Syntra ETL ships the canonical sap tm to oracle fusion data mapping pre-built. The default crosswalk covers roughly 1,400 fields across the three primary roots plus master data and customs documents — refined across dozens of SAP TM conversions. Customer-specific Z-fields and custom freight-order types layer on top of the default via the configurable mapping editor. Transportation ops, finance, customs and IT review proposed mappings together in a reviewable table, override specific rules where the business demands a non-default routing, and sign off field-by-field before extraction begins.
The mapping is version-controlled and auditable. Every override is captured with a timestamp, the approver, and the business rationale. Six months after go-live, when auditors ask why Z-field CUSTOM_LANE_ID landed in Descriptive Flexfield ATTRIBUTE3 on Fusion Shipment, the answer is one click away — not a three-day archaeology dig through a developer's laptop.
Each domain ships with its canonical default mapping plus the configurable override layer for project-specific extensions.
Freight-order header, items, stages, business partners, document flow → Order Release header + lines + stops + Trading Partners. Document-number preserved as Fusion cross-reference.
Booking headers, items, capacity allocations, tariffs → OTM Booking / Fusion Forwarding-Agent Shipment. Booking-to-freight-order linkage preserved.
Settlement documents, charge lines, accruals → FBDI AP Invoice Import. Charge-line-level traceability to source freight order.
HTS / HS codes, MRN, CBP entry numbers, certificates of origin → Fusion Trade Operations Customs Declarations or long-term archive. Chain preserved.
UN numbers, classes, packing groups, segregation rules → OTM DG Profile / Fusion Item Hazmat attributes. Multimodal IMDG / IATA / ADR / 49 CFR preserved.
Carriers → Fusion Suppliers + OTM Service Providers; Locations → OTM Locations + Fusion HR Locations; Equipment → OTM Equipment. Dependency-ordered load sequence.
From scope review to signed-off field-level crosswalk to extract-ready configuration in 3–4 weeks.
Pull the active /SCMTMS/ table list, the freight-order type catalog, the charge-type registry, the custom Z-field inventory, the BAdI registry. Output: the complete mapping surface area sized in fields, freight-order types and custom extensions.
Open the Syntra ETL canonical sap tm to oracle fusion data mapping in the editor. Transportation ops walks freight order + booking; finance walks settlement + charge management; customs walks customs documentation; IT walks integration and master-data dependencies. Each domain lead approves or flags the default.
Capture project-specific overrides: custom Z-field routing, custom freight-order type → Fusion shipment-type mapping, customer-specific charge-line attribute handling, business-unit-specific accrual treatment. Each override timestamped, approved, version-controlled.
Field-level sign-off pack issued: PDF + machine-readable JSON. Transportation ops, finance, customs and IT sign off domain-by-domain. Sign-off pack becomes the audit reference for the rest of the project.
Mapping translated automatically into extract-ready configuration: OData / CDS / BAPI scope, field-level transformation rules, target-payload templates (FBDI / OTM REST / OIC iflow). No manual SQL written.
Pilot extract runs end-to-end on 1–2% of freight orders. Output validated against the signed-off mapping pack field-by-field. Any discrepancy fed back into the editor, re-signed, re-run before bulk extract begins.
The sap tm to oracle fusion data mapping editor is the single source of truth — version-controlled, reviewable, signed-off field-by-field.
Every source /SCMTMS/ field shown next to its proposed Fusion / OTM target field, transformation rule, default-value behaviour, and approver. Filter by domain, by business unit, by status.
Click any default mapping to override. Capture the business rationale in the comment field. Override requires sign-off from the domain owner before it activates.
Every mapping change versioned, timestamped, attributed. Six months post-go-live, auditors get a one-click view of the mapping as-of any historical date.
Domain-by-domain sign-off captured in the editor — transportation ops, finance, customs, IT each approve their slice. Sign-off pack auto-generated as PDF + JSON.
Mapping changes automatically regenerate extract scope and target-payload templates. No manual SQL or ABAP re-writing. The mapping is the configuration.
Live coverage report: how many /SCMTMS/ source fields mapped vs unmapped, how many have approved overrides, how many are still pending sign-off. Project-management visibility from day one.
Sap tm to oracle fusion data mapping is the field-by-field, business-object-by-business-object crosswalk that translates the SAP Transportation Management /SCMTMS/ namespace — freight orders, freight bookings, freight settlement documents, charge management, transportation requirements, customs documentation, dangerous-goods records — into Oracle Fusion SCM, Oracle Transportation Management Cloud (OTM) and Oracle Fusion Payables domain shapes. The mapping has to preserve the freight-order document number as a foreign key into Fusion / OTM shipments, the customs entry-number chain end-to-end, and the charge-line traceability from /SCMTMS/D_FS_ROOT into Fusion Payables invoice lines. Syntra ETL ships pre-built crosswalks across roughly 1,400 fields covering all three primary roots (D_FRO_ROOT, D_FB_ROOT, D_FS_ROOT) plus master data and customs documents — refined across dozens of SAP TM conversions, not invented week by week.
The freight order root /SCMTMS/D_FRO_ROOT carries the header attributes — freight-order number, freight-order type, source location, destination location, business partner assignments, ordering-party, transportation mode, planned departure and arrival dates, status, document flow and the link to settlement. Syntra ETL's sap tm to oracle fusion data mapping translates this into Oracle Transportation Management Cloud's Order Release header plus the related Shipment header when Oracle OTM is the target, or into Oracle Fusion SCM Shipment + Trade Operations when Fusion SCM is the target. Items under the freight order (/SCMTMS/D_FRO_ITEM) map to Order Release Lines and Shipment Items. Stages map to Shipment Stops. Business partners map to OTM Location-Contact or Fusion Trading Partner. The freight-order document number is preserved as a Fusion-side cross-reference attribute so any Fusion shipment can be traced back to its source SAP TM freight-order number for audit.
Freight bookings — /SCMTMS/D_FB_ROOT, used heavily in ocean and air-freight forwarding scenarios — carry booking headers, capacity allocations, tariff terms and carrier-contract context. The sap tm to oracle fusion data mapping translates booking headers into Oracle OTM's Booking object (where OTM is the target) or into Fusion SCM's Shipment with Forwarding Agent attribution. Capacity allocations map to OTM Service Provider Capacity or Fusion Forwarding-Agent Allocation. Tariff and contract context — surcharge schedules, fuel-adjustment factors, currency-conversion rules — flow into OTM Rate Offering or Fusion Freight Terms. Booking-to-freight-order linkage is preserved so the document flow from booking → freight order → shipment → settlement remains queryable end-to-end after the migration.
Freight settlement is the financially sensitive end of the sap tm to oracle fusion data mapping. /SCMTMS/D_FS_ROOT settlement documents carry the header attributes — settlement number, business partner (carrier), document date, freight-invoice-request linkage, status. Charge lines under the settlement carry the freight-cost components — base freight, fuel surcharge, accessorials, duties, tolls — with per-currency amounts and accrual references. Syntra ETL maps settlement headers into Fusion Payables Invoice headers via FBDI AP Invoice Import; charge lines map to AP Invoice Lines with full carrier, lane, freight-order and accrual-period traceability. Accrual reversals carry through so period-end finance reporting stays continuous. Currency translation preserves the original transaction currency, the company functional currency and the period-end reporting currency.
Yes. Customs documentation is one of the four core domains in the sap tm to oracle fusion data mapping (alongside freight orders, freight settlement and master data). HTS / HS codes, country of origin, customs values, broker references, CBP entry numbers, EU Customs Union MRN numbers, certificates of origin and proof-of-export documents tied to freight orders all carry through. The target landing depends on the deployment shape: Oracle Fusion Trade Operations carries customs declarations and entry summaries when Fusion is the customs system of record; Oracle Transportation Management Cloud carries customs documentation tied to Order Releases when OTM is the customs system of record; the customs-archive bucket on cloud object storage carries the full historical chain for CBP 5-year, EU 10-year and country-specific retention windows. Every customs document keeps its source freight-order document number as a cross-reference.
Dangerous-goods data — UN numbers, hazmat classes, packing groups, segregation requirements, emergency-response numbers — is bound to freight order items in SAP TM, typically through the dangerous-goods management subcomponent. The sap tm to oracle fusion data mapping translates these attributes into Oracle Transportation Management Cloud's Dangerous Goods Profile on Order Release items, or into Oracle Fusion SCM Item Hazmat attributes when Fusion is the target. The mapping preserves the segregation-rule context (which classes can ship together, which can't), the limited-quantity and excepted-quantity status, and the multimodal classification (IMDG for ocean, IATA-DGR for air, ADR for road in Europe, DOT 49 CFR for road in the US). Dangerous-goods evidence is preserved through the shipment lifecycle for DOT, IMDG and ADR audit continuity.
Master data carries roughly 30% of the sap tm to oracle fusion data mapping work but enables every other domain — load a freight order without its carrier and the load fails. Syntra ETL ships pre-built mappings: SAP TM carrier business partners (BUT000 with carrier role + /SCMTMS/ carrier attributes) → Fusion Suppliers via FBDI Supplier Import + OTM Service Providers via Service Provider REST; SAP TM locations (/SCMTMS/D_LOCATION) → Fusion HR Locations + OTM Locations via Location REST; SAP TM equipment (trucks, trailers, containers) → OTM Equipment via Equipment REST or Fusion Asset for owned fleet; SAP TM transportation networks, lanes and schedules → OTM Network / Lane / Schedule via Network REST. Drivers when applicable route to Fusion HCM via HDL Worker.dat. The dependency graph is respected: carriers before freight orders, locations before shipments, equipment before assignments.
Yes. Every Syntra ETL crosswalk is configurable. The default ships with the canonical mapping refined across dozens of SAP TM conversions, but every project carries customer-specific extensions — custom Z-fields on /SCMTMS/D_FRO_ROOT, customer-specific charge-line attributes, custom freight-order types tied to specific business processes, custom customs-document categories. The Syntra ETL mapping editor exposes the full field-level crosswalk in a reviewable table; transportation ops, finance, customs and IT can review proposed mappings together, override specific rules (e.g., 'route Z-attribute CUSTOM_LANE_ID into Fusion Shipment Descriptive Flexfield ATTRIBUTE3 instead of the default Cross-Reference Notes'), and sign off field-by-field before extract begins. Override rules are captured in version control so the mapping is auditable at any later point.
Book a 30-minute discovery call. We'll show you the canonical /SCMTMS/ → Fusion / OTM crosswalk, walk through how project-specific overrides work, and give you a sized mapping timeline for your freight-order, booking and settlement footprint before the call ends.