TABLE OF CONTENTS

• Integration Scope
• 1. Equipment/Truck Flow
  • 1.1 Description
  • 1.2 Mandatory Fields & Data Format
• 2. Driver Flow
  • 2.1 Description
  • 2.2 Mandatory Fields & Data Format
• 3. Customer/Shipper Flow
  • 3.1 Description
  • 3.2 Mandatory Fields & Data Format
• 4. Sales Order/Trip with Water Transport Flow
  • 4.1 Description
  • 4.2 Mandatory Fields & Data Format
• 51. Service Order/Trip Flow
  • 5.1 Description
  • 5.2 Mandatory Fields & Data Format
• 6. Expected Errors
  • 6.1 Description
  • 6.2 Events
• 7. General Tips
  • 7.1 Email Notifications:
  • 7.2 Trip Synchronization:
  • 7.3 Scheduled Synchronization:

Integration Scope

The scope of this integration project is to synchronize data between the SAP ERP and Tachyon systems. This ensures a seamless flow of information across different departments and operational processes.

1. Equipment/Truck Flow

1.1 Description

The Equipment/Truck Flow automates the creation of trucks in Tachyon whenever new equipment is added to SAP ERP. This flow ensures that trucks are consistently represented in both systems, enabling accurate tracking of resources across the organization.

SAP → Tachyon

1.2 Mandatory Fields & Data Format

Note: Missing data will result in default values reflected on Tachyon.

2. Driver Flow

2.1 Description

The Driver Flow is designed to keep driver records synchronized between SAP ERP and Tachyon. When a driver is created in SAP, the corresponding information will be automatically reflected in Tachyon.

SAP → Tachyon

2.2 Mandatory Fields & Data Format

Note: Missing data will result in default values reflected on Tachyon.

3. Customer/Shipper Flow

3.1 Description

The Customer/Shipper Flow automates the creation of customer records in SAP ERP whenever a new customer is added in Tachyon.

Tachyon → SAP

3.2 Mandatory Fields & Data Format

4. Sales Order/Trip with Water Transport Flow

4.1 Description

The Sales Order/Trip with Water Flow automates the creation of sales orders in SAP ERP whenever a trip for water transportation is delivered in Tachyon.

Tachyon → SAP

4.2 Mandatory Fields & Data Format

Note: 

• The fields Distance and Driver Working Hours should remain empty initially and be completed via the mobile app upon trip delivery.

• Avoid using "Myself" in the Customer (Actor Shipper) field when creating a trip, as it is not acceptable in the integration process. Instead, select a valid customer from the dropdown list to ensure proper synchronization.

• All other fields can be freely used.

All the Red boxes are mandatory for the integration to work seamlessly.

51. Service Order/Trip Flow

5.1 Description

The Service Order/Trip Flow automates the creation of service orders in SAP ERP whenever a trip is delivered to a customer in Tachyon.

Tachyon → SAP

5.2 Mandatory Fields & Data Format

Note: 

• The fields Goods Category and Goods Sub-category are set to "Others" as their type is already specified in Loading Type. 

• The fields Distance and Driver Working Hours should remain empty initially and be completed via the mobile app upon trip delivery.

• Avoid using "Myself" in the Customer (Actor Shipper) field when creating a trip, as it is not acceptable in the integration process. Instead, select a valid customer from the dropdown list to ensure proper synchronization.

• All other fields can be freely used.

6. Expected Errors

6.1 Description

This section consolidates all the expected errors that may arise during the integration process. Understanding these errors will help in troubleshooting and ensuring the smooth operation of the system.

6.2 Events

• Unlinked Entity Errors:

  • Description: Occurs when Customers created in Tachyon are not yet synchronized with SAP.

  • Solution: Ensure that all entities in Tachyon are synched with SAP before initiating further operations. Regularly check for un synched data.

• Missing Data Errors:

  • Description: Triggered when mandatory fields are left blank or filled with incorrect data formats.

  • Solution: Double-check that all required fields are populated with the correct data format before attempting to save or sync records.

• Manually Added Entities on Portals:

  • Description: Errors arise when trucks or drivers are manually added directly on Tachyon instead of being synchronized from SAP.

  • Solution: Avoid manual entries in Tachyon and ensure all data is correctly entered in SAP for automatic synchronization.

• Invalid Company in Sales Order:

  • Description: Using a local company in a sales order, which is not valid in SAP (only sister companies are accepted).

  • Solution: Ensure that only sister companies are selected in the sales order process. Verify company Dichannel before proceeding with the order.

7. General Tips

7.1 Email Notifications:

• Email alerts will be sent when errors occur during synchronization, ensuring prompt awareness and resolution.

7.2 Trip Synchronization:

• Only trips marked as "delivered" in Tachyon will be synched as orders in SAP. The synch event occurs when the trip is marked as delivered.

7.3 Scheduled Synchronization:

• Customer, driver, and truck/equipment data synchronization is done on a regular schedule. Regularly check the system to ensure all data is synched correctly.