Agents for EBS Integration

EBS ALLOCATE ORDER RELEASE WHEN PLANNED

ORDER - BUILD BUY SHIPMENTS

ORDER - BULK PLAN BUY

(SHIPMENT) ALLOCATE SHIPMENT: PLANNING

EVENT

• Order on Shipment - Assigned, This event is triggered anytime an order is planned onto a shipment (independent of how it was planned, bulk plan, direct, etc)

ACTIONS

• Checks to see if the shipment(s) created are valid for EBS and sets status type SENT TO EBS to a status value of INVALID FOR EBS.
• • Valid - Single first leg shipment with single equipment
  • Invalid  - Parallel first leg shipments. First leg shipment has multiple pieces of equipment

This agent reacts when the order release is planned onto a shipment. It marks the status of shipments if they cannot be accepted by EBS:

EBS cannot accept multiple shipments/trips for a single delivery. Shipments are marked as INVALID FOR EBS if there are multiple first leg shipments (a later agent will exclude these from being sent to EBS).

Additionally, EBS cannot accept shipments that have multiple equipment so they are marked as INVALID FOR EBS as well.

EBS ORDER BASE OMD

(This is an OMD agent that can be used for the EBS integration out of the box)

ORDER MODIFIED - INTEGRATION

FUTURE PROCESSING!

If location changes - Full impact

If dates change - propagate dates

If quantity changes - propagate quantity

If freight terms, carrier, mode or Incoterm changes - Full impact

EBS ORDER RELEASE OMD

(This is an OMD agent that can be used for the EBS integration out of the box)

ORDER MODIFIED - INTEGRATION

If the order has a remark of ACTUALS_RECEIVED, update the order release.

If locations, mode, service provider or Incoterm changes - Unassign order

If dates change - propagate dates

If quantity changes - propagate quantity

This agent reacts to Order Release modifications when they are received via integration.

EVENT

This agent listens for any modifications to the order via integration.

ACTIONS

If saved condition ACTUALS RECEIVED FOR OR is true, that means the order release already has a remark of ACTUALS_RECEIVED and the update shall not be processed and the agent processing should not continue past this point.

If the expression #ORDER_RELEASE_REMARK/REMARK_QUAL_GID=ACTUALS_RECEIVED is true, the remark ACTUALS_RECEIVED is being added to the order release on this update and the modification should be processed but not affect the shipment.

• The actual shipment XML is expected immediately following this update and will update the shipment.
• The expression is querying the XML to check that a value is added to the ORDER_RELEASE_REMARK table via this update with a remark qualifier of ACTUALS_RECEIVED.

If the Order Release is on a Shipment:

• If the custom event ORDER CONSTRAINTS MODIFIED (locations, mode, service provider, or Incoterm are modified) is raised perform the full impact action
• If Date change - edit shipment
• If Quantity change - edit shipment

Else (if something other than what has been previously mentioned changes on the order release), raise the custom event, EBS.OR ON SHIPMENT MODIFIED, for each shipment the order is on, the shipment mod agent is listening for this event to send out a shipment update since EBS expects a shipment update anytime the order is updated.

If the Order Release is not on a shipment, the FUTURE PROCESSING action is invoked to update the order release.

SEND FIRST LEG SHIPMENT TO EBS

SHIPMENT TENDER ACCEPT

SEND INTEGRATION (you need to define an external system and select Notify Type as Service)

SET STATUS: SENT TO EBS_SENT

1. This agent listens for the tender of a shipment to be accepted.
2. The shipment meets the criteria (it does not contain a PO and is not marked as INVALID)
3. Next, it must record the fact that is was sent by setting the status to SENT TO EBS_SENT.

EBS SHIPMENT MOD REALLOCATE

SHIPMENT-COST MODIFIED: NONE

SHIPMENT-QUANTITIES MODIFIED:NONE

ALLOCATE SHIPMENT: PLANNING

SHIPMENT COMPLETED - PERFORM FINANCIALS

SET POD RECEIVED STATUS,-PERFORM FINANCIALS ACTIVITIES

SHIPMENT STATUS - RECEIVED

Is event group SHIPMENT_COMPLETE and Status Type: POD_RECEIVED

IF:
The event is associated with the last stop, ($EVENT GROUP.IS_LAST_STOP=Y) the following actions are performed:
-SET INTERNAL STATUS: ENROUTE_COMPLETED
-ALLOCATE SHIPMENT: PLANNING
-GENERATE INVOICE
-(SHIPMENT TO INVOICE) INVOICE - AUTO APPROVE
-Set shipment status to ENROUTE_COMPLETED
-Set shipment status to POD _RECEIVED
-Allocate Shipment - Buy Side
Create Invoice (SHIPMENT TO INVOICE) INVOICE-AUTO APPROVE

Listens for shipment events received that belong to the group SHIPMENT_COMPLETE. The following status codes are valid:

• CD - Carrier Departed Delivery Location

• OA - Out-Gate

• D - Delivered

• D -  Completed Unloading at Delivery Location

If the event entered is associated with the last stop of the shipment, the following will take place:

1. Set the status of the shipment to ENROUTE_COMPLETE
2. Allocate shipment
3. Generate the Invoice
4. Auto Approve the Invoice

SHIPMENT MOD - RESEND TO EBS

SHIPMENT MODIFIED (Integration, Internal or User)

Shipment designated as SENT TO EBS_SENT and SHIP CONFIRMED_NOT CONFIRMED and does not contain any orders with a purchase order reference number.

SEND INTEGRATION (you need to define an external system and select Notify Type as Service).

Reacts when a shipment is modified (the custom event raised in the OMD agent or modified by the user) and has been previously SENT TO EBS.

If the Quantity or Cost changes as a result of the modification, the shipment needs to be re-allocated and sent to EBS again. No status is changed since the status already reflects the fact that it has been SENT TO EBS.

SHIPMENT DELETE - SEND TO EBS

SHIPMENT - REMOVED (Internal or User)

SEND INTEGRATION: ID ONLY (you need to define an external system and select Notify Type as Service).

Anytime a shipment is deleted, an interface containing the shipment ID only is sent to EBS

If the shipment has already generated a trip in EBS, that trip should be deleted, if the trip does not exist in EBS, this message is disregarded.