Hazards

• ApplyObservedPlacardsToUnit    1

• LogHazardMission    1

• ReadHazards    1

• RejectCtrHazardsNotChecked    1

• RejectCtrHazardsNotMatchingBookingHazard    1

• RejectMissingPlacards    1

• RejectUnExpectedPlacardsPresent    1

ApplyObservedPlacardsToUnit

This business task applies the observed placards recorded at the gate to the unit.

N4 displays an error if a recorded placard already exists on the unit.

Functional Area

Gate

Execution Level

Transaction

Transaction Type(s)

Gate: Receive Export (RE), Dray In (RI), Receive Empty (RM), and Receive Breakbulk (RB)

Client Type(s)

UI and Gate API

Parameters

None

Dependencies

If you provide placards in the process-truck API for the gate transaction and want to apply this information to the unit, you must include the ApplyContainerExportGoods business task in your gate configuration.

Related Business Task(s)

None

Custom Code

None

Field(s)

Placards - Add/Edit

LogHazardMission

Constructs and logs the mission statement to instruct the driver about the hazards. N4 prints this statement on a gate ticket using the document type specified in the CreateDocument (on page 1) business task.

ReadHazards

Reads hazard information from a pre-advised unit or an order (booking or rail order), if a pre-advised unit does not exist, and copies the information to the container being received at the gate.

Include the ReadHazards business task only for automated gates. For manual gates, the gate forms automatically copy the hazard information.

RejectCtrHazardsNotChecked

Rejects a gate transaction for a hazardous container if the gate clerk does not select the Hazard Checked check box in the gate form. If you include the RejectCtrHazardsNotChecked business task for a gate transaction type, you must also include the Hazard Checked check box in the gate form for the gate transaction type.

RejectCtrHazardsNotMatchingBookingHazard

Rejects a gate transaction if the hazardous class noted for the specified container does not match the hazardous classes in the equipment order. For example:

• If a container is assigned hazard class 1.1 and the equipment order hazard classes are 1.2 and 6.1, N4 rejects the gate transaction.

• If a container is assigned hazard class 1.2 and the equipment order is non-hazardous, N4 rejects the gate transaction.

If included, the RejectTranNotMatchingNonHazardBooking (on page 1) business task validation also fails.

• If a container is assigned hazard class 1.2 and the equipment order hazard classes are 1.2 and 6.1, N4 does not reject the gate transaction.

• If a container is non-hazardous and the equipment order hazard classes are 1.2 and 6.1, N4 does not reject the gate transaction.

However, if included, the RejectTranNotMatchingHazardBooking (on page 1) business task validation fails.

RejectMissingPlacards

Rejects a gate transaction if a hazardous placard is associated with the hazard specified for the gate transaction but the placard is not present during the inspection.

You can include the Placards - Add/Edit button in the gate form to enable a user to record the hazard placards for a gate transaction.

RejectUnExpectedPlacardsPresent

Rejects a gate transaction if the hazardous placards recorded at the gate do not match the placards specified on the booking.

To update the Placards Mismatch column in the Pre-advised Units view, you must include the RejectUnExpectedPlacardsPresent business task.

You can include the Placards - Add/Edit button in the gate form to enable a user to record the hazard placards for a gate transaction.