This article will provide some examples of SubmitShipment requests when you are booking Dangerous Goods using Shipment Server. Not all carriers support dangerous goods - if in doubt, ask your carrier if they support it.

Examples:

• Example with dangerous goods using UN number
• Example using DG Office integration

Example with dangerous goods using UN number

This example shows a SubmitShipment with UN number and with a lot of dangerous goods fields filled in. Typically, only UN number (UN), class (Class), volume (Vol) and number (count) are mandatory. Most carriers do not use most of the other fields but they are supported for special cases when needed.

If you choose this method, it is always your responsibility that any dangerous goods documents fulfill all legal requirements. It varies from carrier to carrier if they support dangerous goods and which fields are required and supported. Some carriers also require the selection of a dangerous goods service.

Data:

{
  "Kind": 1,
  "ActorCSID": 8995,
  "ProdConceptID": 112,
  "Addresses": [
    {
      "Kind": 1,
      "Name1": "Jane Doe",
      "Street1": "Testgade 10",
      "PostCode": "7600",
      "City": "Struer",
      "Mobile": "12345678",
      "Attention": "Jane",
      "CountryCode": "DK"
    },
    {
      "Kind": 2,
      "Name1": "nshift",
      "Street1": "Bredskifte alle 11",
      "PostCode": "8210",
      "City": "AARHUS V",
      "Phone": "70273377",
      "Attention": "John Doe",
      "CountryCode": "DK"
    }
  ],
  "Lines": [
    {
      "LineWeight": 50000,
      "PkgWeight": 50000,
      "GoodsTypeKey1": "PL1",
      "References": [
        {
          "Kind": 23,
          "Value": "Test contents"
        }
      ],
      "Pkgs": [
        {
          "ItemNo": 1
        }
      ]
    }
  ],
  "DangerousGoods": [
    {
      "UN": 3304,
      "Name": "COMPRESSED GAS, TOXIC, CORROSIVE, N.O.S.",
      "Class": 2,
      "Classification": "1TC",
      "IdentificationNo": "268",
      "Count": 1,
      "GrossWeight": 60000,
      "NetWeight": 50000,
      "Vol": 600000000,
      "Labels": "2.3 ; +8",
      "PackingTypeName": "Aluminiumcylinder",
      "PackingTypeID": 256,
      "OuterPackingType": "Aluminiumcylinder",
      "OuterPackingTypeID": 256,
      "SpecialProvisions": "274",
      "LimitedQuantities": "LQ0",
      "ExceptedQuantities": "E0",
      "PackingInstructions": "P200",
      "MixedPackingProvision": "MP9",
      "PortTankBulkContInstructions": "(M)",
      "ADRtankTankCode": "CxBH(M)",
      "ADRtankSpecialProvisions": "TU6 ; TA4 ; TT9",
      "Vehicle": "AT",
      "TransportCategory": "1 ; (C\/D)",
      "SpecialProvisionsHandling": "CV9 ; CV10 ; CV36",
      "SpecialProvisionsOperation": "S14",
      "GoodsLineNo": 1,
      "TransportMode": 2,
      "UnitOfMeasure": 1
    }
  ]
}

Example using DG Office integration

This example shows a SubmitShipment that includes the mandatory fields for a dangerous goods shipment using a DG Office integration. DG Office is a 3rd party software specializing in making dangerous goods documents, and they will ensure that the documents you print fulfill the legal requirements. Read more about DG Office here.

If you are using a DG Office integration while also sending information about dangerous goods to your carrier in the EDI, it is important to remember to include both the fields required by DG Office as well as the fields your carrier may require. All the parameters mentioned under the DG Office parameters must be included together with the UN Number. It may also be mandatory to include other fields like class, volume and number but this varies from carrier to carrier.

DG Office parameters:

Data:

{
  "Kind": 1,
  "ActorCSID": 8995,
  "ProdConceptID": 112,
  "Addresses": [
    {
      "Kind": 1,
      "Name1": "John Doe",
      "Street1": "Testvej 10",
      "PostCode": "8000",
      "City": "AARHUS C",
      "Mobile": "12345678",
      "Attention": "Doe",
      "CountryCode": "DK"
    },
    {
      "Kind": 2,
      "Name1": "nshift",
      "Street1": "Bredskifte alle 11",
      "PostCode": "8210",
      "City": "AARHUS V",
      "Phone": "70273377",
      "Attention": "CS",
      "CountryCode": "DK"
    }
  ],
  "Lines": [
    {
      "LineWeight": 50000,
      "PkgWeight": 50000,
      "GoodsTypeKey1": "PL1",
      "References": [
        {
          "Kind": 23,
          "Value": "Test contents"
        }
      ],
      "Pkgs": [
        {
          "ItemNo": 1
        }
      ]
    }
  ],
  "DangerousGoods": [
    {
      "GoodsLineNo": 1,
      "Count": 1,      
      "ArticleNo": "334",
      "TransportMode": 2, 
      "DeclarantName": "Muller"      
      "UN": 3304,
      "Name": "COMPRESSED GAS, TOXIC, CORROSIVE, N.O.S.",
      "Class": 2,
      "Classification": "1TC",
      "GrossWeight": 60000,
      "NetWeight": 50000,
      "Vol": 600000000,
      "PackingTypeName": "Aluminiumcylinder",
      "PackingTypeID": 256,
      "UnitOfMeasure": 1
    }
  ]
}

The example above includes some of the most common fields. You may also use the method GetDGArticleNoInfo to return DG data from DG Office that you can include into your SubmitShipment request together with DG Office and carrier required fields.

The method GetDocument is needed to be called in order to retrieve the DG freight letter once the shipment has been created. A delay between SubmitShipment and GetDocument is also required since the document is created by a third party vendor.