Import MJO / LTO / RJO Files A Practical Guide

Many enterprise systems rely on filebased data exchange to move large volumes of information between applications. Three of the most common proprietary formats you will encounter are MJO, LTO and RJO. Although they serve different business domainsmaintenance job orders, logistics transport orders, and resource job ordersthey share a similar structure and typical import workflow. This page explains what each file type is, how to recognise them, the steps required to import them safely, and some bestpractice tips to avoid common pitfalls.

1. What Are MJO, LTO and RJO Files?

1.1 MJO Maintenance Job Order

An MJO file contains a list of scheduled maintenance tasks for equipment or facilities. It is generated by Computerised Maintenance Management Systems (CMMS) and usually includes:

• Job identifier and description
• Asset reference (equipment tag, location)
• Planned start and finish dates
• Required labour hours, parts, and tools
• Priority and safety instructions

1.2 LTO Logistics Transport Order

LTO files are exchanged between Warehouse Management Systems (WMS) and Transportation Management Systems (TMS). The file holds data for a single or batch of shipments, such as:

• Consignment number
• Origin and destination addresses
• Carrier details
• Weight, volume and product codes
• Special handling requirements

1.3 RJO Resource Job Order

RJO files are used in projectbased environments where resources (people, machines, licences) are allocated to tasks. Typical fields include:

• Resource ID and skill set
• Task ID and description
• Allocation dates and durations
• Cost centre and budget codes
• Utilisation percentages

2. Common File Characteristics

Although the business purpose differs, MJO, LTO and RJO files usually share these technical traits:

Characteristic	Typical Value
File extension	.mjo, .lto, .rjo
Encoding	UTF8 or ISO88591
Delimiter	Comma (CSV) or pipe (|) rarely tabdelimited
Header row	Present column names in upper case
Record separator	CRLF (Windows) or LF (Unix)

3. Import Workflow Overview

1. Receive the file via SFTP, shared folder, or API endpoint.
2. Validate format check delimiter, encoding, mandatory columns, and file size.
3. Run business rules verify that referenced assets, locations or resources exist in the target system.
4. Transform if needed map external codes to internal ones, convert dates to ISO8601, or split combined fields.
5. Load into staging tables use bulkinsert utilities (e.g., SQL Server BCP, PostgreSQL COPY) to minimise transaction time.
6. Process into production tables execute stored procedures or ETL scripts that move data, apply defaults and generate audit logs.
7. Generate a report success count, rejected rows, and any warnings.
8. Archive the source file move to a readonly folder with a timestamped name for audit purposes.

4. Detailed Steps for Each File Type

4.1 Importing MJO Files

Key validation rules

• Job ID must be unique within the import batch.
• Asset tag must exist in the Asset Master table.
• Planned dates cannot be in the past unless the job status is Reopened.
• Labour hours must be a positive decimal.

Sample SQL staging table

CREATE TABLE dbo.Stg_MJO (    JobID               varchar(20)   NOT NULL,    Description         varchar(250),    AssetTag            varchar(30)   NOT NULL,    PlannedStart        datetime      NOT NULL,    PlannedFinish       datetime      NOT NULL,    LabourHours         decimal(6,2)  NOT NULL,    PriorityCode        char(1),    SourceFile          varchar(100)  NOT NULL,    ImportDateTime      datetime      DEFAULT GETDATE());    

After loading the staging table, call a procedure such as sp_ProcessMJOImport that performs the business logic and moves validated rows to dbo.MaintenanceJobs.

4.2 Importing LTO Files

Typical pitfalls

• Inconsistent carrier codes maintain a mapping table.
• Weight expressed in pounds while the system expects kilograms.
• Missing destination postcode leading to failed address validation.

Sample transformation using Python (optional)

import pandas as pddf = pd.read_csv('incoming.lto', delimiter='|')df['WeightKg'] = df['Weight'].apply(lambda x: round(float(x) * 0.453592, 2))df['CarrierID'] = df['CarrierCode'].map(carrier_map)df.to_sql('Stg_LTO', con=engine, if_exists='append', index=False)

4.3 Importing RJO Files

RJO imports tend to be the most complex because they involve manytomany relationships (resources tasks). A common approach is to split the file into two staging tables:

• Stg_RJO_Tasks one row per task.
• Stg_RJO_Allocations one row per resourcetask allocation.

Business rule examples:

• Allocation percentage for a task must sum to 100%.
• Resource must be active and have the required skill level.
• Budget code must be valid for the projects fiscal year.

5. Error Handling & Logging

Implement a central ImportLog table that captures:

• File name and type
• Start and end timestamps
• Total rows processed
• Number of successful inserts
• Number of rejected rows with error codes

Example:

CREATE TABLE dbo.ImportLog (    LogID          int IDENTITY PRIMARY KEY,    FileName       varchar(200),    FileType       char(3),         -- MJO/LTO/RJO    StartedAt      datetime,    CompletedAt    datetime,    TotalRows      int,    SuccessRows    int,    ErrorRows      int,    Remarks        varchar(500));

6. Security Considerations

• Transfer files over SFTP or HTTPS; never use plain FTP.
• Validate the files digital signature or checksum (MD5/SHA256) before processing.
• Run import jobs under a leastprivilege service account that only has write access to staging tables.
• Sanitise all string fields to prevent SQL injection when constructing dynamic queries.

7. Automation Tips

Most organisations schedule imports during lowtraffic windows. Tools you might use:

• Windows Task Scheduler or cron for script execution.
• SQL Server Integration Services (SSIS) or Apache NiFi for visual data flows.
• Docker containers that encapsulate the import logic, making it easy to move between environments.

8. Frequently Asked Questions

Q: Can I import a mixedtype file (e.g., MJO and LTO together)?

A: Not recommended. Keep each file type separate to maintain clear validation rules and audit trails.

Q: What size limit should I expect?

A: Most modern databases can handle millions of rows per batch, but practical limits are defined by network bandwidth and stagingtable indexes. Split files larger than 200MB.

Q: How do I handle duplicate records?

A: Use a MERGE statement (SQL Server) or ON CONFLICT clause (PostgreSQL) to upsert based on the natural key (e.g., JobID for MJO).

9. Sample EndtoEnd Workflow (Shell Script)

#!/bin/bash# Simple import orchestrator for MJO/LTO/RJO filesIN_DIR="/data/incoming"ARCHIVE_DIR="/data/archive"LOG_DIR="/data/logs"for file in "$IN_DIR"/*.{mjo,lto,rjo}; do    [ -e "$file" ] || continue    TYPE=$(echo "${file##*.}" | tr '[:lower:]' '[:upper:]')    echo "$(date +%F%T) Starting $TYPE import: $file" >> "$LOG_DIR/import.log"    # Validate checksum (assumes .sha256 file exists)    sha256sum -c "${file}.sha256" >/dev/null 2>&1    if [ $? -ne 0 ]; then        echo "Checksum failed for $file" >> "$LOG_DIR/error.log"        continue    fi    # Call the appropriate Python/SQL script    case $TYPE in        MJO) python3 import_mjo.py "$file" ;;        LTO) python3 import_lto.py "$file" ;;        RJO) python3 import_rjo.py "$file" ;;    esac    rc=$?    if [ $rc -eq 0 ]; then        mv "$file" "$ARCHIVE_DIR/$(basename "$file").$(date +%Y%m%d%H%M%S)"        echo "$(date +%F%T) Completed $TYPE import successfully." >> "$LOG_DIR/import.log"    else        echo "$(date +%F%T) $TYPE import failed with code $rc." >> "$LOG_DIR/error.log"    fidone    

10. Conclusion

Importing MJO, LTO, and RJO files follows a repeatable pattern: receive, validate, transform, stage, process, and archive. By standardising each stage, using staging tables, and maintaining detailed logs, organisations can minimise errors, keep audit trails, and ensure that critical maintenance, logistics and resource data flow smoothly into their enterprise systems.

For deeper technical references, consult the integration guides of your specific CMMS, WMS, or ERP platform, and always test new import logic in a sandbox before promoting to production.