Skip Headers
Oracle® Application Integration Architecture Oracle Driver Management for Oracle Transportation Management and Oracle E-Business Suite Implementation Guide
Release 3.1

Part Number E50312-01
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

7 Data Requirements and Prerequisites

This chapter discusses data requirements and perquisites for the Oracle Driver Management for Oracle Transportation Management and Oracle E-Business Suite integrations.

This chapter includes the following section:

7.1 Driver Profile Integration

These are the data requirements:

These are the prerequisites:

The first name is mandatory in Oracle Transportation Management (OTM). Though not mandatory for the interface to work and for synchronizing the records, the user must enter this value in the Oracle EBS.

The driver profile flow should subscribe to a group event in the Oracle EBS HRMS Workflow. The multiple events associated with the create, remove, update, delete (CRUD) operations of the Driver Maintenance in HRMS are under one group event. This simplifies the processing of driver data from Oracle EBS to OTM. The Oracle Application Integration Architecture (Oracle AIA) user should subscribe to the group event in the Oracle EBS workflow manually.

7.1.1 Location Integration

The location integration has no data requirements or prerequisites.

7.1.2 Training and Absence Calendar Integration

These are the data requirements:

  • Drivers must be synchronized between Oracle EBS and OTM.

  • Training Locations must be synchronized to OTM for all training events.

  • All the required configuration properties should also be specified.

7.1.3 Work Invoice Integration

The prerequisite is that the driver included in the work invoice must be synchronized into OTM.