Ocean Docs Commodity Table (feature)

From UG

Revision as of 22:02, 20 January 2010 (edit) Alex (Talk | contribs) (→Misc) ← Older edit		Revision as of 22:05, 20 January 2010 (edit) (undo) Alex (Talk | contribs) (→Look And Feel) Newer edit →
Line 107:		Line 107:
	=== Look And Feel ===		=== Look And Feel ===
-		+	* Generic Docs Commodity Table (feature)#Look and Feel
		+
		+	* See Figures for examples
		+
	=== Figures ===		=== Figures ===

---

Revision as of 22:05, 20 January 2010

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.4.3 FCL volume statistics on pdf 3.5 Misc 3.6 Look And Feel 3.7 Figures 3.7.1 Figure 1: FCL Commod Table CT No Group ctnrs 3 commods (Cont Tab) 3.7.2 Figure 2: FCL Commod Table CT No Group 2 ctnrs 3 commods (Template) 3.7.3 Figure 3: FCL Commod Table CT No Group 2 ctnrs 3 commods (Pdf) 3.7.4 Figure 4: 2 CTs Grouped No Container overlap (Cont Tab CT2) 3.7.5 Figure 5: 2 CTs Grouped No Container overlap [Group generate] (Template) 3.7.6 Figure 6: 2 CTs Grouped No Container overlap [Group generate] (Pdf) 3.7.7 Figure 7: 2 CTs Grouped One Container overlap (Cont Tab) 3.7.8 Figure 8: 2 CTs Grouped One Container overlap [Group generate] (Template) 3.7.9 Figure 9: 2 CTs Grouped One Container overlap [Group generate] (Pdf) 4 RFC 5 Known Non Critical Bugs and Issues 6 History 6.1 Old spec 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
• Dock Receipt
• Dock Receipt (M) - ???
• 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.

• 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.

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.

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.

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;

Misc

• see Palets / cartons / loose count (feature)
• for definitions of KG/LB, CBM/KG, HU/AMS dropdown and related functionality see Measurement Unit Converters (feature)

Look And Feel

• Generic Docs Commodity Table (feature)#Look and Feel

• See Figures for examples

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)

RFC

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

DB