Auto Assign an Agent to a Job

This page is accessed via Brokerage and Forwarding > Job Management > Job Details. Enter a Job ID and then click Refresh. When the page reloads, click Actions > Assign Shipping Agent > Auto Assign an Agent to a Job.

When planning and executing international freight, it is very common to have many parties or agents involved in the move. It is also very common for a freight forwarder to perform services for a customer that was obtained by a trading partner or external sales agent. Each of these agents receives a commission for the services they have performed on behalf of the freight forwarder. This commission can either be paid as a flat amount or a percentage of the profit made on the sale. As a result, all of these agents will be associated with particular transactions.

Agents are modeled as involved parties on a job. The agent roles of Consol Agent, Final Destination Agent, or Sales Agent will be set up as involved party qualifiers. Each assignment type will compare the job to all the agents with this role and assign the most compatible agent. A non-freight related charge (NFRC) is created if there is an NFRC Rule on the shipping agent contact.

This action automatically assigns an agent to a job. What is selected as the agent role dictates how the logic is run. In general, the job will be compared to potential matching agent involved parties and the best matching agent is assigned to the job.

When you run this action, you will be prompted to select an Agent Role ID. The table below details the different roles and what happens when each is selected.

Agent Role ID	Logic Description
CONSOL_AGENT	This assignment type assigns an agent with an involved party qualifier of 'Consol Agent.' Typically the 'Console Agent' is assigned to the Master job. Oracle Transportation Management first checks whether the corresponding 'Sales Agent' is a compatible 'secondary' agent. Oracle Transportation Management checks the job and all related jobs for an involved party with the qualifier of 'Sales Agent'. It is necessary to check the related jobs since typically the 'Sales Agent' is assigned to the 'House Job'. If more than one 'Sales Agent' is found, Oracle Transportation Management attempts to assign the primary agent. If a single 'Sales Agent' is found, then Oracle Transportation Management checks whether this agent also serves the role of 'Consol Agent'. If the agent can serve this role, the agent is found to be compatible with the job.
FINAL_DESTINATION_AGENT	This assignment type assigns an agent with an involved party qualifier of 'Final Destination Agent.' Typically the 'Final Destination Agent' is assigned to the House job. Oracle Transportation Management first checks whether a final destination agent is necessary. A final destination agent is only necessary when the final destination of the primary leg buy shipment does not equal the final destination of the primary leg sell shipment. If a final destination agent is not required, the action will simply return. Once it has been determined that a final destination agent is required, Oracle Transportation Management checks whether the corresponding 'Sales Agent' is a compatible 'secondary' agent. Oracle Transportation Management checks the job and all related jobs for an involved party with the qualifier of 'Sales Agent.' If a 'Sales Agent' is found, then Oracle Transportation Management checks whether this agent also serves the role of 'Final Destination Agent'. If the agent can serve this role, then the agent is found to be compatible with the job.
SALES_AGENT	This assignment type assigns an agent with an involved party qualifier of 'Sales Agent.' Typically the 'Sales Agent' is assigned to the House job. The logic will get the location associated with the involved party qualifier of 'Shipper' on the first order release in the job. This location is compared with all agents serving the role 'Sales Agent' which have a compatible 'Shipper' location profile. Oracle Transportation Management then gets the location associated with the involved party qualifier of 'Consignee' on the first order release in the job. This location is compared with all agents serving the role 'Sales Agent' which have a compatible 'Consignee' location profile.

Agent Role ID

Logic Description

CONSOL_AGENT

This assignment type assigns an agent with an involved party qualifier of 'Consol Agent.' Typically the 'Console Agent' is assigned to the Master job. Oracle Transportation Management first checks whether the corresponding 'Sales Agent' is a compatible 'secondary' agent. Oracle Transportation Management checks the job and all related jobs for an involved party with the qualifier of 'Sales Agent'. It is necessary to check the related jobs since typically the 'Sales Agent' is assigned to the 'House Job'. If more than one 'Sales Agent' is found, Oracle Transportation Management attempts to assign the primary agent. If a single 'Sales Agent' is found, then Oracle Transportation Management checks whether this agent also serves the role of 'Consol Agent'. If the agent can serve this role, the agent is found to be compatible with the job.

FINAL_DESTINATION_AGENT

This assignment type assigns an agent with an involved party qualifier of 'Final Destination Agent.' Typically the 'Final Destination Agent' is assigned to the House job. Oracle Transportation Management first checks whether a final destination agent is necessary. A final destination agent is only necessary when the final destination of the primary leg buy shipment does not equal the final destination of the primary leg sell shipment. If a final destination agent is not required, the action will simply return.

Once it has been determined that a final destination agent is required, Oracle Transportation Management checks whether the corresponding 'Sales Agent' is a compatible 'secondary' agent. Oracle Transportation Management checks the job and all related jobs for an involved party with the qualifier of 'Sales Agent.' If a 'Sales Agent' is found, then Oracle Transportation Management checks whether this agent also serves the role of 'Final Destination Agent'. If the agent can serve this role, then the agent is found to be compatible with the job.

SALES_AGENT

This assignment type assigns an agent with an involved party qualifier of 'Sales Agent.' Typically the 'Sales Agent' is assigned to the House job. The logic will get the location associated with the involved party qualifier of 'Shipper' on the first order release in the job. This location is compared with all agents serving the role 'Sales Agent' which have a compatible 'Shipper' location profile. Oracle Transportation Management then gets the location associated with the involved party qualifier of 'Consignee' on the first order release in the job. This location is compared with all agents serving the role 'Sales Agent' which have a compatible 'Consignee' location profile.

Auto Assign an Agent to a Job

Related Topics