How+to+test+RQ1058+%26+1059_TP DOcs

8/13/2019 How+to+test+RQ1058+%26+1059_TP DOcs

http://slidepdf.com/reader/full/howtotestrq1058261059tp-docs 1/69

Review log:

Date Action

7/8/2013 Initial draft sent to IBM

7/9/2013 v1 created

7/10/2013 v2 created

7/16/2013 v3



Comments

Some scenarios such as multiple operational shipments and negative testing not yet

complete

Added test case descriptions at bottom of tabs - added scenarios with multiple operationalshipments and dual tpdocs - ready for IBM to review and comment

Have updated document after initial review with IBM, renumbered test cases and classified

some test cases in basic scenarios tab as "low priority". Low priority test cases are to be

tested last if there is time for it

Added a scenario where an OS is made that later catches up to the original route. See

'catching up scenarios sheet'





Basic business assumptions:

1. Operational shipments, also referred to as 'short shipped cargo' usually occur due to inter

shipments with 2 containers or more that start the journey together , but for whatever reas

of the cargo going on a different v/v and then cathing up to the other cargo later in the jour

2. Common reasons could be damaged containers, overbooked vessels, etc.

Basic booking principles:

1. Bookings must be made in the past. You cannot make an operational shipment in the futu

2. Issue Original TPDoc tasks must be closed, as well as relevant RKEM tasks (such as Equip

3. You must alternate carrier between MSL, SAF, SGO, MCC (some routes might not have pr

4. Operational shipments must have at least one leg in common and same place of receipt a

5. Operational shipments will occur at the transshipment ports

6. Products must have at least 2 legs for the basic operational shipment scenarios and at lea

shipment or an operational shipment from an operational shipment.

Simple scenarios (1 TPDoc, 1 shipment, 1 OS), 2 Equipments:

In this scenario, the original route is market with R and the operational shipment created for E2 is m

split and goes to P3 and P4 on different vessels.

When the TPDoc for Rop is created, if P3 and/or P4 are compliance ports (for example first port of e

filed separetely from the original TPDoc for R.

R:

Rop:

P1 P2 P3 P4 P5VV1

P1 P2 P3 P4 P5

VV2

Place of

receipt

Place of

delivery

Final discharge

port Transshipment

port

VV3

VV4

Multiple operational shipment scenarios (1 TPDoc, 1 shipment , 2 OS) 3 equipments:

All three containers start out at same place of receipt on Route R and make it to the load port, P2.

At P2, E2 and E3 get short shipped going on VV3 intead of VV1, creating operational shipment Sop1

R:

Rop1:

P1 P2 P3 P4 P5VV2

P1 P2 P3 P4 P5VV2

Place of

receipt

Place of

delivery

Final discharge

port

Rop2: P1 P2 P3 P4 P5VV4

VV1

VV3

VV3

Transshipment

port



,

In order to be able to recreate these scenarios in testing , bookings must be made about 6 weeks in

Dual TPDocs (1 shipment) and operational shipment:

Initially one shipment S with two containers, E1 and E2, where both E1 and E2 contains cargo docum

shipment Sop with route Rop. Altogether this results in:

Notice that T1 covers both E1 and E2, as does T2.

S

Sop

T1

E1

E2

R

Rop

T2

R:

Rop:

P1 P2 P3 P4 P5VV1

P1 P2 P3 P4 P5VV2

Place of

receipt

Place of

delivery

Final discharge

port



nal operational issues and are not at the request of the customer. They involve a

n are split up at a transshipment port - part of the cargo going on the original v/v, part

ey.

re - i.e. where the journey has not begun. This would be a normal split TPDoc instead.

ent pick-up, and OPS out from load port)

duct for all carriers)

nd final place of delivery.

st 3 legs for the complicated scenarios in which you create more than one operational

arked as Rop. As can be seen, the Operational shipment occurs at P2 when the cargo is

ntry into the EU or China) then a compliance for these should be created in Hermes and

ith Rop1 (E1 remains on original route). Then when the cargo reaches P3, E3 gets short



.

the past.

ented by two TPDocs, T1 and T2. Container E2 is short shipped creating operational



Note: Booking should have at least two (water) legs

Type of bookingCompliance

Status in Hermes Action in GCSS and RKEM

Testcase 1 1 TPDoc, 1 shipment, 3Equipments (E1, E2 and E3), ENS

compliance

IE328 Ok to Load Make Operational Shipment for E1 andE2 and complete the route on the

operational shipment. Make sure the

operational shipment will have compliance

as well.

Testcase 2 1 TPDoc, 1 shipment, 2

Equipments (E1 and E2), ENS

compliance, 1 amendment

Amendment Rejected Make Operational Shipment for E1 and

complete the route on the operational

shipment. Make sure the operational

shipment will have compliance as well.


Equipments (E1 and E2), IE344compliance ONLY. No ENS

compliance (for example Sweden-

Finland)

Sent Make Operational Shipment for E1 and

complete the route on the operationalshipment. Make sure the operational



Equipments (E1, E2 and E3),

IE344 compliance ONLY. No ENS

compliance

IE328 Ok to Load Make Operational Shipment for E1 and





Equipments (E1 and E2), IE344-V

compliance ONLY. No ENS

compliance

IE328 Ok to Load Make Operational Shipment for E1 and






IE344-V compliance ONLY. No

ENS compliance

Submission error Make Operational Shipment for E1 and

E2 and complete the route on the



as well.



IE344-V compliance ONLY. No

ENS compliance

IE316- Rejected Make Operational Shipment for E1 and




as well.


Equipments (E1, E2 and E3), DIS-

MAN compliance

Ok to Load- happens

automatically two

hours after submission

Make Operational Shipment for E1 and




as well.




Equipments (E1 and E2),

CNXSHIP compliance, 2

amendments

Latest amendment in

Submission error with

No ACK/E9999





as well.




amendment

Amendment in

Submission error with

E000x





as well.


Equipments (E1 and E2) CNXSHIP

compliance

01 or 11 Make Operational Shipment for E1 and







amendments

Latest amendment in

02









CNXSHIP compliance

03 Make Operational Shipment for E1 and




as well.

Testcase 14

Low priority

1 TPDoc, 1 shipment, 2


compliance





Testcase 15

Low priority



compliance





Testcase 16

Low priority


Equipments (E1 and E2), IE344


compliance





Testcase 17Low priority

1 TPDoc, 1 shipment, 2Equipments (E1 and E2), IE344


compliance

IE316- Rejected Make Operational Shipment for E1 andcomplete the route on the operational



Testcase 18

Low priority




compliance (for example an intra

Europe route)





Testcase 19

Low priority



compliance ONLY. No ENScompliance

IE351 Hold at

discharge

Uploading IE345response as IE351 is

NOT a valid response



shipment. Make sure the operationalshipment will have compliance as well.



Testcase 20

Low priority



CNXSHIP compliance





as well.

Testcase 21

Low priority



CNXSHIP compliance

12 or 13 Make Operational Shipment for E1 and




as well.

How to test: 1. In GCSS, create a booking with ENS compliance, two legs and two containers.

Test case 1 2. Submit the compliance in Hermes and create an IE328 OK to load dummy resp

3. In GCSS, create an operational shipment for E1. Make sure it has an ENS com

4. In Hermes UI, check the following:

4a. Ensure that the original compliance already submitted retains its status and

4b. Ensure that Hermes displays and creates a compliance for the link related t

4c. Check the TPDoc list to ensure the OS compliance is displaying correctly.5. Submit the operational shipment

6. Check Hermes UI to ensure that the compliance for the operational shipment h

7. Check in GCSS that the compliance is also visible in the compliance window

7a. Check the TPDoc list to ensure the OS compliance is displaying correctly.

8. In AMPS, look up the APP*MANIFEST for the operational shipment compliance

8a. Tag HM10 element 13 contains the ORR number (the shipment number cre

8b. TagHM20 contains a reference to the ORR number (the operational shipme

9. Go in AMPS and create a dummy response of Rejected for the OS

10. In Hermes, check the UI screens to ensure that the response is displaying cor

How to test: 1. In GCSS, create a booking with CNXSHIP compliance, two legs and two contaiTest case 11 2. Submit the compliance in Hermes and create a customs dummy response of 01

3. In GCSS, create an operational shipment for E1. Make sure it has an CNXSHIP


4a. Ensure that the original compliance already submitted retains its status and

4b. Ensure that Hermes displays and creates a compliance for the link related t

4c. An amendment for seal change will be created in Ready status for the origin

4d. Check the TPDoc list to ensure the OS compliance is displaying correctly.

5. Submit the operational shipment

6. Check Hermes UI to ensure that the compliance for the operational shipment h

7. Check in GCSS that the compliance is also visible in the compliance window







1) Hermes retains the original

compliance and the status it was in.

2) For the China compliance: Detection

made as COLLECTING or CREATED

for DE88 Seal on the original TPDoc

depending on its status (due to

instanceId for equipment and cargo

changed when split) regardless that no

change was made in GCSS for any ofthe DE.

3) Ensure that Hermes creates

compliance for links related to the

Operational Shipment if applicable.

Yes 1) The link displaying in Hermes

with the operational shipment will

be submitted, go to Sent status

Yes Sent with E000x








changed when split) regardless that nochange was made in GCSS for any of

the DE.







Yes Submission error with

ACK/E9999









change was made in GCSS for any of

the DE.







Yes 02





for DE88 Seal on the original TPDocdepending on its status (due to




the DE.







Yes 12 or 13











change was made in GCSS for any ofthe DE.







Yes Submission error with

E000x


compliance and the status.







Yes Yes- Ok to Load









Yes Yes- IE351 Hold at

Discharge









Yes No- submission erro

1) Hermes retains the originalcompliance and the status.




Yes 1) The link displaying in Hermeswith the operational shipment will


Yes Yes- Ok to Load









Yes Yes- Ok to Load



2) Ensure that Hermes createscompliance for links related to the





Yes Yes- IE316 Rejected












the DE.

3) Ensure that Hermes createscompliance for links related to the





Yes 01- Pending 24 hours










the DE.


compliance for links related to theOperational Shipment if applicable.




Yes 01 or 11

nse

liance as well. Get the booking to Ready status.

is still in Sent status.

the operational shipment

s been correctly submitted and is in Sent status with e-view and ICN number

submitted and ensure that:

ated by GCSS for the operational shipment)

nt) and NOT to the original TPDoc

ectly

ers. To make it easier, you can name the containers, E1 and E2or 11

compliance as well. Get the booking to Ready status.

is still in Sent status.

the operational shipment

al compliance even though the seal was not changed - this is a known defect.

s been correctly submitted and is in Sent status with e-view and ICN number





TP Doc Number

Actual TP Doc Number Used

R26TC0101 R26TC0101

R26TC0201 -

Wasted

R26TC0201

R26TC0301

R26TC0401

R26TC0501 R26TC0501

R26TC0601

R26TC0701

R26TC0801



R26TC0901

R26TC1001

R26TC1101 -

Defect

R26TC1102 -

Retest

R26105872



R26105871

R26105808

OS :510093788

ORR No. :

Y00000412

R26105807 -

Wasted

R26105810

OS No. :510093948

ORR No. :

Y00000430

R26105809

ORR Number :

510093833

ORR Number :

Y00000415

R26105812

OS : 510093853 -

WASTED

R26105813

OS No. :

510093856

ORR : Y00000419








Type of bookingCompliance Status in

Hermes Action in GCSS and RKEM

Testcase 22 1 TPDoc, 1 shipment, 3Equipments (E1, E2 and

E3), ENS and CNXSHIP

compliance

Both compliances should bein Sent status

Make Operational Shipment for E1 andcomplete the route on the operational




Equipments (E1, E2 and


compliance, 1

amendment for China

IE328 Ok to Load for ENS

and Amendment for China in

01- Accepted




operational shipment will have

compliance as well.




compliance

Both compliances in

Submission error





compliance as well.



ENS and CNXSHIP

compliance, 1

amendment for each

compliance

For ENS amendment status

should be accepted. For

CNXSHIP, amendment

should be in 03- Rejected






Equipments (E1, E2),

ENS and CNXSHIPcompliance

ENS inIE316- Rejected,

CNXSHIP in Sent with E000x









compliance

ENS in IE351 Hold at

Discharge, CNXSHIP in 01 or

11





compliance as well.




compliance, 1

amendment for ENS

ENS amendment in Accepted

and CNXSHIP in 12 or 13





compliance as well.



ENS and CNXSHIPcompliance

ENS in IE328 Ok to Load and

CNXSHIP in 02 Pending

customs' decision.






E3), ENS and IE344

compliance, 1

amendment for ENS

ENS amendment Accepted

and IE344 in Ok to Load





compliance as well.



ENS and IE344v

compliance

Both ENS and IE344 in Ok to

Load







ENS and IE344v

compliance, 1

amendment for ENS

ENS amendment Accepted

and IE344 in Ok to Load







ENS and Arrival

Notification


Arrival Notification in Sent

status







E3), ENS and Arrival

Notification


Arrival Notification in

Accepted status





compliance as well.

How to test: 1. In GCSS, create a booking with ENS and CNXSHIP compliance, two legs a





Expected outcome in Hermes

Submit the

operational shipment

compliance(s)?

Yes/No

1) Hermes retains the original compliances and their status.2) For the China compliance: Detection made as COLLECTING or

CREATED for DE88 Seal on the original TPDoc depending on its

status (due to instanceId for equipment and cargo changed when

split) regardless that no change was made in GCSS for any of the

DE.

3) Ensure that Hermes creates compliance for links related to the


Yes

1) Hermes retains the original compliances and their status.

2) For the China compliance: Detection made as COLLECTING or

CREATED for DE88 Seal on the original TPDoc (due to instanceId

for equipment and cargo changed when split) regardless that no

change was made in GCSS for any of the DE.3) Ensure that Hermes creates compliance for links related to the


Yes



CREATED for DE88 Seal on the original TPDoc (due to instanceId

for equipment and cargo changed when split) regardless that no

change was made in GCSS for any of the DE.



Yes






DE.



Yes






DE.



Yes








DE.



Yes






DE.



Yes






DE.



Yes




Yes




Yes




Yes




Yes




Yes

d three containers



nd CNXSHIP compliance as well. Get the booking to Ready status.

and is still in Sent status.

ted to the operational shipment

a on the original compliance even though the seal was not changed - this is

y.

nts have been correctly submitted and is in Sent status with e-view and ICNow

y.

nce submitted and ensure that:

r created by GCSS for the operational shipment)

ment) and NOT to the original TPDoc

K E9999 for the CNXSHIP compliance

correctly

d as the compliance has gotten an E9999.



Expected outcome in HermesCheck AMPS

Yes/No

Create dummy customs

response for operational

shipment(s)?

Yes/No

Other Comments

1) The link(s) displaying in Hermes withthe operational shipment will be submitted,

go to Sent status

Yes Yes- IE328 for ENS and VA ACK E9999 for CNXSHIP

1) The link(s) displaying in Hermes with

the operational shipment will be submitted,

go to Sent status

Yes Yes- IE328 for ENS and 01 for

CNXSHIP



go to Sent status


CNXSHIP



go to Sent status


CNXSHIP



go to Sent status

Yes Yes- IE328 for ENS and 12 OR

13 FOR CNXSHIP





go to Sent status

Yes Yes- IE316 for ENS and VA

ACK E000X for CNXSHIP



go to Sent status

Yes No- Let them fall into

submission error



go to Sent status


submission error



go to Sent status

Yes Yes- IE328 for both ENS and

IE344



go to Sent status


submission error R26105801

510093612

Operational route reference

Y000004031) The link(s) displaying in Hermes with


go to Sent status


IE344v TP Doc Number :R26105803

OS 510093620 - Wasted

TP Doc Number : R26105806

OS : 510093689

ORR : Y00000410



go to Sent status


Arrival Notification



go to Sent status


submission error



known defect.

umber





In Progress

Passed

Defect Raise

Defect

667

UI Issue

Passed

Passed











Testcase 40 1 TPDoc, 1 shipment, 3 Equipments (E1,

E2 and E3), CNXHIP compliance

Route should preferably have 2

transshipment ports

01 or 11




transshipment ports

12 or 13




transshipment ports

VA ACK E000x

How to test: 1. In GCSS, create a booking with ENS compliance, two legs a

Test case 36 2. Submit the compliance in Hermes and create An IE 328 OK

3. In GCSS, create an operational shipment for E1 at the first tr


4a. Ensure that the original compliance already submitted re

4b. Ensure that Hermes displays and creates a compliance f

4c. Check the TPDoc list to ensure the OS compliance is dis

5. Do not submit the compliance. Leave it in Ready

6. In GCSS, create a second operational shipment for E2 at th


7a. Ensure that the original compliance already submitted re

7b. Ensure that Hermes still displays the first operational shi

7c. Ensure that Hermes displays and creates a compliance f

7d. Check the TPDoc list to ensure the OS compliance is dis

8. Submit the second operational shipment

9. Check Hermes UI to ensure that the compliance for the oper

10. Check in GCSS that the compliance is also visible in the c

10a. Check the TPDoc list to ensure the OS compliance is di

11. In AMPS, look up the APP*MANIFEST for the operational s11a. Tag HM10 element 13 contains the ORR number (the

11b. TagHM20 contains a reference to the ORR number (th

Scenarios creating an operational shipment from an operationNote: Booking needs to have 3 water legs





8d. Check the TPDoc list to ensure the OS compliance is dis

9. Submit the second operational shipment

10. Check Hermes UI to ensure that the compliance for the op

11. Check in GCSS that the compliance is also visible in the c

11a. Check the TPDoc list to ensure the OS compliance is di

12. In AMPS, look up the APP*MANIFEST for the operational s

12a. Tag HM10 element 13 contains the ORR number (the

12b. TagHM20 contains a reference to the ORR number (th



d, a product with 2 water legs can be used.

at eact port. If uing a product with 1 transshipment port, both operational shipments will be done at t

Action in GCSS and RKEM Expected outcome in Hermes

Submit first

operational

shipmentcompliance(s)?

Yes/No At the first transshipment port, make first

operational Shipment for E1 and complete the

route on the operational shipment. Make sure

the operational shipment will have

compliance as well.

1) Hermes retains the original compliance and its status.

2) Ensure that Hermes creates compliance for links related to

the Operational Shipment if applicable.

Yes

At the first transshipment port, make first

operational Shipment for E1 and complete theroute on the operational shipment. Make sure


compliance as well.


2) Ensure that Hermes creates compliance for links related tothe Operational Shipment if applicable.

No





compliance as well.




Yes





compliance as well.




Yes





compliance as well.


2) For the China compliance: Detection made as

COLLECTING or CREATED for DE88 Seal on the original

TPDoc (due to instanceId for equipment and cargo changed

when split) regardless that no change was made in GCSS for

any of the DE



Yes







compliance as well.






any of the DE



Yes





compliance as well.






any of the DE



No





compliance as well.





when split) regardless that no change was made in GCSS forany of the DE



Yes

nd three containers.

o Load response

ansshipment port. Make sure it has an ENS compliance as well. Get the booking to Ready status.

ains its status and is still in Ok to Load status.

or the link related to the operational shipment

playing correctly.

second transshipment port (or first if you are using a 2-leg product). Make sure it has an ENS compliance a

ains its status and is still in OK to load status.

ment in Ready status

or the link related to the second operational shipment

playing correctly.

ational shipment has been correctly submitted and is in Sent status with e-view and ICN number

mpliance window

isplaying correctly.

hipment compliance submitted and ensure that:hipment number created by GCSS for the operational shipment)

operational shipment) and NOT to the original TPDoc

al shipment:







at port.


Yes/No

Create dummy

customs response for

first operational

shipment(s)?

Yes/No1) The link(s) displaying in Hermes with the operational shipment

will be submitted, go to Sent status

No No

1) The link(s) displaying in Hermes with the operational shipment

will stay in Ready status

N/A N/A



No Yes- Ok to Load



No No



No No





No Yes- 03



N/A N/A



No Yes- 11

well. Get the booking to Ready status.




Yes/No

Create dummy


operational

shipment(s)?

Yes/No1) The link(s) displaying in Hermes with the operational shipment


Yes Yes- Rejected



Yes No



Yes Yes- 03 Rejected



Yes No

. Get the booking to Ready status.





Second Action in GCSS and RKEM Expected outcome in Hermes

At the second transshipment port, make second

operational Shipment for E2 and complete the route

on the operational shipment.

Note: If you are using a route that only has 2 legs

and 1 transshipment port, complete this step at that

port.

1) Hermes retains the original compliance and its status as

well as the first operational shipment compliance submitted

earlier.


the latest created Operational Shipment if applicable.






port.


well as the first operational shipment compliance in Ready

status.






Note: If you are using a route that only has 2 legsand 1 transshipment port, complete this step at that

port.



earlier.

2) Ensure that Hermes creates compliance for links related tothe latest created Operational Shipment if applicable.






port.



earlier.








port.



earlier.





any of the DE










port.



earlier.





any of the DE

3) Ensure that Hermes creates compliance for links related tothe latest created Operational Shipment if applicable.






port.



earlier.





any of the DE




operational Shipment for E2 and complete the routeon the operational shipment.



port.


well as the first operational shipment compliance submittedearlier.





any of the DE





Second Action in GCSS and RKEM Expected outcome in Hermes

At the second transshipment port, make a second

operational Shipment from the one you created

earlier, by opening the OS in GCSS and creating anOS for E2. Complete the route on the operational

shipment.



earlier.2) Ensure that Hermes creates compliance for links related to




earlier, by opening the OS in GCSS and creating an

OS for E2. Complete the route on the operational

shipment.



earlier.







shipment.



earlier.



TPDoc depending on its status (due to instanceId for

equipment and cargo changed when split) regardless that no








shipment.



earlier.



TPDoc depending on its status (due to instanceId for

equipment and cargo changed when split) regardless that no








Submit the second

operational

shipment

compliance(s)?Yes/No

Check AMPS

Yes/No

Create dummy


second operational

shipment(s)?Yes/No

TP Doc Number

Yes Yes Yes- IE328

Yes Yes No

Yes Yes Yes- Ok to Load

First OS : 510093676

Y00000406

Second OS : 510093678

Y00000407 - DEFECT RAISED

RETEST :

TP Doc No. R26105827

OS No. 510093909

First ORR : Y00000421Yes Yes Yes- IE316 Rejected

R26105828

1st OS No. : 510093926

ORR Number: Y00000425

2nd OS No. : 510093928

2nd ORR No. : Y00000426

Defect 666

Yes Yes Yes- 01



Yes Yes Yes- 03

Yes Yes Yes- 01

Yes Yes Yes- 12 or 13



Submit the second

operational

shipment

compliance(s)?

Yes/No

Check AMPS

Yes/No

Create dummy


operational

shipment(s)?

Yes/No

TP Doc Number

Yes Yes Yes- IE328

R26105829

First OS No. : 510093936

1st ORR No. : Y00000427Yes Yes Yes- IE328

R26TC4801

First OS :510093967

First ORR : Y00000431Yes Yes Yes- 01/11

R26TC4901Yes Yes Yes- 03

R26TC5001




Type of booking

Testcase 51 1 shipment, 2 Equipments (E1 and E2), where

both E1 and E2 contains cargo documented by

two TPDocs, TP1 and TP2.

ENS compliance.




ENS compliance.




CNXSHIP compliance.




CNXSHIP compliance.



Compliance Status in Hermes Action in GCSS and RKEM

The compliance on both TPDocs should be in

Sent

Make Operational Shipment for E1 and complete

the route on the operational shipment. Make

sure the operational shipment will have

compliance as well.


Ok to Load




compliance as well.


Sent




compliance as well.

The compliance on both TPDocs should be in 01 Make Operational Shipment for E1 and complete



compliance as well.



Expected outcome in HermesSubmit the operational shipment

compliance? Yes/No

1) Hermes retains the original compliance and

the status on both TPDocs

2) Ensure that Hermes creates compliance for

links related to the Operational Shipment if

applicable on both TPDocs

Yes






Yes




COLLECTING or CREATED for DE88 Seal onthe original TPDocs (due to instanceId for

equipment and cargo changed when split)

regardless that no change was made in GCSS

for any of the DE.




Yes




COLLECTING or CREATED for DE88 Seal on

the original TPDocs (due to instanceId forequipment and cargo changed when split)

regardless that no change was made in GCSS

for any of the DE.




Yes





Create dummy customs response for

operational shipment?

Yes/No

TP Doc

Number

Yes- Ok to Load

R26TC5101,R26TC5111Yes- 316 Rejected

R26TC5201,R26TC5211Yes- VA ACK E9999

R26TC5301,R26TC5311Yes- 12 or 13

R26TC5401



Note: Booking should have at least three (water) legs. Rerout

Type of bookingCompliance Status in

Hermes

Test case 55 1 TPDoc, 1 shipment, 2 Equipments (E1, andE2), ENS and/or CNXSHIP compliance

Example of route (double compliance):

St. Petersburg (Russia)- Gdansk (P1 --> P2)

Gdansk- Bremerhaven (P2 --> P3)

Bremerhaven- Yantian (P3 --> P4)

Yantian- Yokohama (Japan) (P4 ---> P5)

ENS in OK to Load, CNXSHIP in01/11





Submit first

operational

shipment

compliance(s)?

Yes/No

Expected outcome in

Hermes

Check AMPS

Yes/No

Create dummy

customs

response for first

operational

shipment(s)?

Yes 1) The link displaying inHermes with the operational

shipment will be submitted, go

to Sent status

No No



How to access "Split" options from Shipment?-> Pre-conditions: Atleast 2 containers and the shipment should have only one

TPDoc (be in Shipment Mode)

-> See Attached image

How to perform "Auto Split"?

-> This will create a shipment for each container in the original shipment.

Original shipment will remain with one container. Each of these shipments (with

one container each) will have their won TPDocs.

How to perform "Manual Split"?

-> This will create a shipment for each container selected. You can specify the

shipment number

How to perform "Operational Shipment"?


shipment number

How to perform "Operational Shipment before Issue Original"?


shipment number

How to perform "TPDoc Split"? (TEST CASE 25)

-> To make at TPDoc Split

-> You need to have one shipment SH1 with E1 -C1 and E2-C2 where E1-C1

documented on TPD1 and E2-C2 documented on TPD2.

When you select TPD2 and press 'SPLIT' then GCSS will create one new

shipment with E2-C2 and the cargo will be documented on TPD2.

-> The shipment will get new shipment version id and same applies for

equipment id.

How to perform "Create" new TPDoc from transport document. (TEST

CASE 11 on Negative TEST)

-> one shipmnet SH1 with E1-C1 and E2-C2 where both documented on TPD1.

-> select the E1-C1 and press 'CREATE'This will create a new TPDoc and the selected container/cargo E1-C1 will now

be documented on this new TPDoc. The TPDoc create will not make any

changes to the shipment, hence shipment will not get new shipment version id

nor will the equipment get new instanceId.

What is Split Shipment?

If all the containers in a shipment cannot be loaded at the first port, and if the orig

customer yet, depending on customer preference, Maersk can opt to split the shi

that the containers that can be loaded will proceed. Left over containers can com

next available vessel.



Testcase 6 shipment with 3 equipment and autosplit

1. Where only Consignee changed before the split.

2. 11, 22 and 33 all 3 equipmnet will be shown as AmendItem on the original

where the EquipInstanceId referres to the 'old' EquipInstanceId which is the id

before the split was performed.

3. Hermes will detect that 11, 22 and 33 has been removed (the 'old'

EquipInstanceId not on shipment after the split), hence orig value 11, 22 and 33

and new value for all 'space'4. Hermes will detect that 22 has been added (the 'new' EquipInstanceId that 22

got after the split), hence orig space and new value = '22'

Example of a split scenario :

When split performed in GCSS - GCSS will create new shipment(s) for equipmen

The original shipment (510088881) will get new Version ID as SJXMNBJBWWGI

The InstanceId of the equipment that remain on the original Shipment will also ge

GDS - Shipment

Shipment No: 510088881

GDS - Equipment Container No: SJ1111

Instance ID: V2VD9BEBWWGIB

GDS - TPDoc TPDoc Number: 510088881

GDS - Equipment Container No: SJ2222

Instance ID: VRLC9BEBWWGIB

GDS - Shipment

Shipment No: 5100

GDS - Equip

Container No:

Instance ID:


GDS - Equip

Container No:

Instance ID:

GDS - Shipment

Shipment No: 51008




Note: Once you create a new booking, it may

be difficult to find the actual booking that was

newly created. Follow the steps suggested

below to easily find the new bookings created.

inal TPDoc has not been issued to the

ment in to two or, multiple shipments so

e on a different route hopefully taking the



t that is removed from the original Shipment

B

t new InstanceId's 02JCQBJBWWGIB the container with SJ1111

8881

ent SJ1111 02JCQBJBWWGIB

81

ent SJ2222

8OPVZBJBWWGIB

886

86



510093174

R26105801 Used

R26105802 R26TC0203

R26105803 Used R26ENS001 Used for P



R26105806 Used R26ENS004R26105807 Used R26DEN001 Used

R26105808 Used

R26105809 Used

R26105810 Used

R26105811 Used

R26105812 Used

R26105813 Used

R26105814

R26105827 Used

R26105828 Used

R26105829

R26105830R26105831

R26105832

R26105833

R26105834

R26105835

R26105836

R26105837

R26105838

R26105839

R26105840

R26105841

R26105842

R26105843

R26105844

R26105845

R26105846



land Testing

land Testing

land Testing

Date post:	04-Jun-2018
Category:	Documents
Upload:	manjunathganguly771275
View:	217 times
Download:	0 times

How+to+test+RQ1058+%26+1059_TP DOcs

Documents