Ocean Docs Commodity Table (feature)

From UG

Contents 1 Prerequisites, Classified As, Parent Mantis 2 Business Needs and Requirements 3 Technical Specification 3.1 Summary 3.2 Assumptions 3.3 User Interface and Functionality 3.3.1 Use case A: CT No Group No Master 2 ctnrs 3 commods 3.3.2 Use case B: 2 CTs Grouped No Master No Container overlap 3.3.3 Use case C: 2 CTs Grouped In a Master No Container overlap 3.3.4 Use case D: 2 CTs Grouped In a Master One Container overlap 3.4 Volume logic 3.4.1 LCL 3.4.2 FCL 3.5 Special Case: Volume Validation for HBL (LCL case) 3.6 Misc 3.7 Look And Feel 3.7.1 Naming / style for table header 3.7.1.1 HBL 3.7.1.2 Freight Release 3.7.1.3 All others 3.8 Figures 3.8.1 Figure 1: FCL Commod Table CT No Group ctnrs 3 commods (Cont Tab) 3.8.2 Figure 2: FCL Commod Table CT No Group 2 ctnrs 3 commods (Template) 3.8.3 Figure 3: FCL Commod Table CT No Group 2 ctnrs 3 commods (Pdf) 3.8.4 Figure 4: 2 CTs Grouped No Container overlap (Cont Tab CT2) 3.8.5 Figure 5: 2 CTs Grouped No Container overlap [Group generate] (Template) 3.8.6 Figure 6: 2 CTs Grouped No Container overlap [Group generate] (Pdf) 3.8.7 Figure 7: 2 CTs Grouped One Container overlap (Cont Tab) 3.8.8 Figure 8: 2 CTs Grouped One Container overlap [Group generate] (Template) 3.8.9 Figure 9: 2 CTs Grouped One Container overlap [Group generate] (Pdf) 3.8.10 Figure 10: HBL Commod table header 3.8.11 Figure 11: Freight Release Commod table header 3.8.12 Figure 12: Ocean Commod table header 4 RFC (Ideas for Future Discussion) 5 Known Non Critical Bugs and Issues 6 History 6.1 Old spec 6.2 SA 6.2.1 M1995 7 DB

Prerequisites, Classified As, Parent Mantis

• Classified As: (large) component
• Parent Mantis: 1680

• Prerequisites:
  • read Generic Docs Commodity Table (feature) - describes "super-class" of Docs Commodity Table feature.

Business Needs and Requirements

Technical Specification

Summary

List of documents that have commodity table design as defined here:

Ocean docs:

• Arrival Notice Ocean
• Delivery Order Ocean
• Freight Release
• HBL
• MBL (M)

Truck docs:

• Delivery Order Trucking Ocean

Assumptions

• User should not really generate pdf with "unassigned" commodities (both FCL and LCL).
  • In this case please give Error pop-up message "Error: At least one commodity item in CT# XXX is unassigned. " Block pdf generation.
  • This case applies for all docs listed above, except "Dock Receipt" and "Delivery Order for Export case". For Delivery Order case, as system blocks pdf generation from the beginning before user even selects Export radio button, since it is default to Import.
    • For Delivery Order options:
      • 1) System should allow user to select Export/Import radio button before allowing to generate pdf/ block pdf generation with "Unassigned" commodities. This case will block for Import, but not for export. Container(s) is assigned later on for the export case.
      • or 2) System defaults Ocean Delivery Order to export, and then do not block for the export, but for the Import if container(s) is unassigned.
    • For Dock Receipt case, it should not block generating pdf at all, since this document, user enter container information later.
• For LCL there is additional condition: all commodities in one CT must be assigned to only one container.
  • In this case please give Error pop-up message "Error: All commodities in LCL CT# XXX must be assigned to only one container" Block pdf generation.

• If there is no commodity table A in a shipment defined (commodity table A is empty)
  • In this case please give Error pop-up message "Error: Commodity Table A in a shipment cannot be empty." Block pdf generation.

• In case of groups and Masters same as above.

User Interface and Functionality

Use case A: CT No Group No Master 2 ctnrs 3 commods

Example: see Figure 1,2,3.

This is the simplest case:

• only one CT
• CT does not belong to any Master
• CT does not belong to any Group

Use case B: 2 CTs Grouped No Master No Container overlap

This case is built upon previous. We grouped CT from Case A with additional CT that has one container.

But still no Master.

Example: see Figure 4,5,6. This is a Group Generate case.

Indiv Generate should give same result as case A.

Use case C: 2 CTs Grouped In a Master No Container overlap

Let's add group in case B to empty Master.

In this case (Master exists) system should give same result as in case B.

Use case D: 2 CTs Grouped In a Master One Container overlap

Now let's expand once more on previous case. Let's:

• add CCCC container to CT# *11
• add one more commodity in CT# *11 to container CCCC

For group generate case - see See Figures 7,8,9.

Indiv Generate case is already defined - see case A.

Volume logic

LCL

If CT group contains LCL CTs and user is trying to "group generate" pdf then it is possible to meaningfully pre-fill Volume column.

Above True for indiv CT as well.

FCL

If CT group contains FCL CTs and user is trying to "group generate" pdf then it is NOT possible to meaningfully pre-fill CT column in some cases. It is because we might have 2 blocks with same CT but different container. At the same time in the system we do not store volume per commodity line or per container. So we can not calculate volume per block.

Therefore in case of "group generate for FCL CTs" system must default to all 0s on template and let user edit manually.

! In case user leaves 0s on template in volume column - print blank on pdf (do not print 0s).

Also in this case show #FCL volume statistics on pdf.

For indiv CT show 0 for volume as well.

Special Case: Volume Validation for HBL (LCL case)

In case of HBL (LCL case) issue Error Window when user clicks "Show Template" if ContTab, Table B, Total (in cbm) = 0. Do not generate template.

Misc

• see Palets / cartons / loose count (feature)
• KG/LB, CBM/KG, HU/AMS and related functionality - see Measurement Unit Converters (feature)
•  ! "No. of Pieces" column (as seen on Templates Figures) should be renamed into "PCS" and have HU/AMS dropdown functionality attached to it - see Measurement Unit Converters (feature)

Look And Feel

• See Generic Docs Commodity Table (feature)#Look And Feel

• See Figures for examples

Naming / style for table header

• Must be same on template and pdf

HBL

see #Figure 10: HBL Commod table header

Freight Release

see #Figure 11: Freight Release Commod table header

All others

see #Figure 12: Ocean Commod table header

Figures

Figure 1: FCL Commod Table CT No Group ctnrs 3 commods (Cont Tab)

Figure 2: FCL Commod Table CT No Group 2 ctnrs 3 commods (Template)

Figure 3: FCL Commod Table CT No Group 2 ctnrs 3 commods (Pdf)

Figure 4: 2 CTs Grouped No Container overlap (Cont Tab CT2)

Figure 5: 2 CTs Grouped No Container overlap [Group generate] (Template)

Figure 6: 2 CTs Grouped No Container overlap [Group generate] (Pdf)

Figure 7: 2 CTs Grouped One Container overlap (Cont Tab)

Figure 8: 2 CTs Grouped One Container overlap [Group generate] (Template)

Figure 9: 2 CTs Grouped One Container overlap [Group generate] (Pdf)

Figure 10: HBL Commod table header

Figure 11: Freight Release Commod table header

Figure 12: Ocean Commod table header

RFC (Ideas for Future Discussion)

1) FCL volume statistics on pdf This is a string to be shown on pdf template above commodity table. It must show volume for all CTs participating in pdf.

Example:

CT#123444: 3.12 cft; CT#123444: 1.01 cft;

2) Multiple blocks per container case: show one check box per container so that you can move everything that belong to one container together.

Known Non Critical Bugs and Issues

• does it matter where / how CT# is displayed - before or after descr, etc?

History

Old spec

See Commodity Table for Pdfs

SA

M1995

• Mantis 1995
• To allow PDF generation for ONLY Ocean Dock Receipts & "Export" Delivery Orders without a container # being assigned. At the moment of these 2 document generation, we do not know the container number (it comes late) and now system blocs pdf generation.
• See #Assumptions

DB