Test scenarios for Notification Import Documentation (submitters)

Introduction

In this document, we describe a number of functional scenarios that you can test to see if your connection is working properly. In the attached download, you will find the message specifications and example messages to set up the system interface referred to in this article.

For testing on our Customer Test environment (KT environment), a separate registration is required. Please contact our Integration Services department about this.

Process flow service

The process flow for the service 'Notification Import Documentation' for ferry and container terminals (V2):

Note! Include the following exceptions in the expected process:

• Terminals connected via a 'Message Flow V1' deviate from the above process. An overview of terminals and pilot codes can be found here.
• Ferry terminals are connected via a 'Message Flow V2'.
• The withdrawal request is a 'web only' application and is therefore not included in this flow for an EDI system interface.

Scenario 1a: NID document submission (container cargo)

1. Create an M2400 message (ImportDocument In). Use the example messages for this.
2. Enter the value “TERM1LADING” in the <receiverIdentifier> element.
3. Enter the scenario code from the table below in the <importDocument><number> element for the different scenarios. Followed by a unique code, the document number and document type must always form a unique combination.
4. Fill in all mandatory elements for testing. For container cargo, this means the <equipmentlist> element must be completed.
5. Send the message to PCS in the KT environment of Portbase.

Scenario 1b: NID document response (container cargo)

1. Check if an M2403 message (ImportDocument Functional Acknowledgement Out) has been received.
2. Check the <importDocumentAcknowledgement><responseTypeCode> element in conjunction with the chosen scenario. The outcome must then match one of the expected responses below:

Scenario 2a: NID document submission (ferry cargo)

1. Create an M2400 message (ImportDocument In). Use the example message 'M2400_ImportDocument_In_ferry_AP.xml and M2400_ImportDocument_In_ferry_RE.xml'.
2. Enter the value “TERM1LADING” in the <receiverIdentifier> element.
3. Enter the scenario code from the table below in the <importDocument><number> element for the different scenarios. Followed by a unique code, the document number and document type must always form a unique combination.
4. Fill in all mandatory elements for testing. For ferry cargo, this means the <shipmentId> element must be completed.
5. Send the message to PCS in the KT environment of Portbase.

Scenario 2b: NID document response (ferry cargo)

1. Check if an M2403 message (ImportDocument Functional Acknowledgement Out) has been received.
2. Check the element <importDocumentAcknowledgement><responseTypeCode> in combination with the chosen scenario. The outcome must then match one of the expected responses below:

• Notification Import Documentation System Link.zip3 MB