Re: [ubl-tsc] COO data model

[Tim McGrath <tmcgrath@portcomm.com.au>]

Yes, as far as totals go i think they should relate only to the sum of any child ABIE not grandchildren and greatgrandchildren.  So some of the Consignment totals are too high a level.

Maybe TotalGoodsItemQuantity  and TotalTransportHandlingUnitQuantity should be in Shipment and TotalTransportEquipmentQuantity and TotalPackageQuantity should be in Transport Handling Unit.

I also agree that Package Type at a consignment level is ambiguoug. We now have a Packaging Type Code in the Package, which is all we need.

Jern Kuan, Leong wrote:

Hi All,

 

To add on,

We should have TotalGoodsItemQuantity & TotalPackageQuantity @ Shipment level as well?

 

What would PackageType mean @ consignment level?

 

Rgds and thanxs

Jernkuan

---

From: Jern Kuan, Leong [mailto:jernkuan@crimsonlogic.com]
Sent: Tuesday, December 13, 2005 5:59 PM
To: ubl-tsc@lists.oasis-open.org
Subject: [ubl-tsc] COO data model

Hi All,

 

I have some doubts on having the production party at the Certificate Of Origin Application level. I would think that it would be more logical to have it at the consignment instead.

 

Another question is is the type for Additional Information correct under the Common Library:Item? It is currently Identifier.

 

Rgds and thanxs

Jernkuan

-- 
regards
tim mcgrath
phone: +618 93352228  
postal: po box 1289   fremantle    western australia 6160

DOCUMENT ENGINEERING: Analyzing and Designing Documents for Business Informatics and Web Services
http://www.docengineering.com/