Viya Logo

ROTRA

This document outlines the integration details for ROTRA using Fortras BORD512 EDI format.

Overview

ROTRA is a logistics service provider offering comprehensive road transport and distribution services. This integration enables automated shipment processing through EDI file transmission via SFTP.

Integration Architecture

  • EDI Format: BORD512 (Fortras standard)
  • Transmission: SFTP upload
  • File Format: Fixed-width text file
  • Environment: Production and Playground supported

Booking

The booking is done by generating and uploading a BORD512 EDI file to ROTRA via SFTP. No direct API communication is required.

Reference Handling

  • The AWB/tracking reference is provided in the input data
  • The shipment tracking reference uses the first 30 characters of the provided reference
  • Each handling unit tracking reference uses:
    • The requestedTrackingReference from the handling unit if provided
    • Otherwise falls back to the handling unit’s reference field

EDI File Structure

BORD512 Format

The EDI file contains multiple fixed-width record types:

Record TypeDescription
@@PHHeader record
A00Consignment data head record
B00Address records (shipper and consignee)
D00Package/handling unit records (one per package)
G00Consignment sums
H00Text codes and references
J00Consignment data totals
Z00Control record
@@PTTrailer record

File Naming Convention

Files are named using the pattern: {prefix}{timestamp}.for

  • Prefix: Configurable in integration settings (e.g., 152_ROT_)
  • Timestamp: YYYYMMDDHHMMSS format
  • Extension: .for

Example: 152_ROT_20260121143000.for

Configuration

SFTP Connections

Two SFTP connection references must be configured:

  • Production: Used when useProduction is true
  • Playground: Used for testing

Onboarding Credentials

Located in separate folder at carriers/v2/rotra/fortras/onboarding/:

  • Customer Code (ROT_CUSTOMER): ROTRA customer identifier (max 35 characters)
  • Depot Code (ROT_DEPOT): ROTRA depot identifier (max 35 characters)

Optional Settings

  • File Name Prefix: Custom prefix for generated EDI files
  • Default Incoterm: Fallback incoterm if not provided in shipment data

Implemented Code Mappings

Package Type Codes (D00 Record)

Mapped using the getPackagingCode() function:

Input TypeROTRA CodeDescription
200PALLETEP200cm pallet
EUROPALLETFPEuro pallet
60PALLETHP60cm half pallet
HALFPALLETHPHalf pallet
PALLETIPIndustrial pallet
COLLIKSCollo (default)
CARTONKTCarton
ENVELOPEKUEnvelope
QRTRPALLETVPQuarter pallet

Delivery Condition Codes (G00 Record)

Mapped using the getDeliveryConditionCode() function:

IncotermROTRA Code
EXW70
FCA72
CPT73
CIP74
DDU84
DDP85
CIF87
CFR88
FAS90
FOB11

Weight Handling

  • Input weights are converted to kilograms if provided in pounds (lbr)
  • D00 Records: Individual package weights in grams (integer)
  • G00/J00 Records: Total weights in kilograms (integer)