[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [QA Team]Re: Questions on UBL_Library_0p70_Order
QA Team,
Here are the comments I referred to in today's con call.
Bill
------------- Begin Forwarded Message -------------
Date: Thu, 27 Mar 2003 13:03:27 +0000
From: Colin O'Donnell <Colin.Odonnell@Sun.COM>
Subject: Re: Questions on UBL_Library_0p70_Order
To: Bill.Meadows@Sun.COM
Cc: Stephen Cowe <Stephen.Cowe@Sun.COM>, Colin.Odonnell@Sun.COM,
Bob.Macinnes@Sun.COM
MIME-version: 1.0
Content-transfer-encoding: 7bit
X-Accept-Language: en
Original-recipient: rfc822;Bill.Meadows@Sun.COM
Hi
Yes I looked at the etrades site and the info for Code Lists.
Bill I get the feeling that the UBL Order schema should be
referencing the ISO Code List schemas. The Order UBL schema
doesn't do that currently, presumably there are plans
to incorporate ISO Code List schemas in later versions ?
Colin
Stephen Cowe wrote:
>
> Hi Colin, Bill,
>
> regarding your questions 1 & 2, if you have a look at
http://www.unece.org/etrades/unedocs/ the UN/ECE has defined the standard code
list for countries/currencies etc. into XML schemas.
>
> I'm not sure how this could or should be incorporated into the UBL schema's,
but hopefully something to think about?
>
> HTH,
>
> Stephen.
>
> Colin O'Donnell wrote:
>
> > Hi Bill
> >
> > I have been working on an example ( current state
> > attached ) for our UBL Ordering Scenario.
> >
> > A few questions :
> >
> > 1. How does one decide on what values would be allowed
> > with for example Quantity Element which has a
> > a "unitCode" attribute. Is there a defined list of what
> > the allowed values are for "unitCode" . I guess the values
> > can be anything you wish given its type is xsd:token,
> > certainly that is what I tried. I don't think we would use
> > it in our scenario, but unfortunately it has to be defined
> > in the doc. If there was a need to use it, is there a way
> > to constrain the allowed values unitCode can have ?
> >
> >
> > 2. Similar to 1. but for Elements like <TransactionCurrencyCode>,
> > <PricingCurrencyCode> . There doesn't appear to be any constraint
> > around what value can be used as the Currency Code. This also
> > appears to be the case even when using e.g <LineExtensionTotalAmount>
> > Element with attribute "currencyID". I can set currencyID="WhatEver"
> > and there isn't any issue. I guess I expected that there would
> > ultimately be a check against valid currencies. I assume it
> > is just because the attribute is a xsd:token. As per 1.
> > perhaps there is a way to constrain this ?
> >
> > 3. Address. Not sure why a <AdditionalStreet> is used rather than
> > just another or list of <Street> Elements ?
> >
> > 4. On <DeliverToAddress> why is there not an Element to describe
> > the receiver of the item ( e.g something for Person Name ) ?
> >
> > 5. <DeliverySchedule><DeliveryRequirement>
> > Don't understand the purpose of being forced to define the
<DeliveryRequirement>
> > at this level ?
> >
> > 6. Don't understand <PartyTaxScheme>.
> > The <TaxScheme> is mandatory when other Elements are optional.
> > If I interpret <CompanyTaxID> to be a VAT Number, then what is
> > <TaxScheme> ? I thought <TaxScheme> might be e.g "VAT", but whats
> > the point of that without a number associated with <TaxScheme>.
> > So maybe the VAT number is within the <TaxScheme> and
> > <CompanyTaxID> is something else. Any idea ?
> >
> > 7. There doesn't appear to be anywhere to apply line level comments
> > like <DeliveryTerms><SpecialTerms> could be used for in header
> > (that appears to be the only place to apply comments at the header
level).
> > I guess <OrderedShipment> has a couple that could be used for
> > line level comments like <HandlingInstructions>, <Information>, but
> > we may not be sure what the comments really relate to, so these
> > Elements may not really be suitable, however they can be made to
> > work.
> >
> > 8. Whats the purpose of a <DesinationParty> and how is it
> > related to <DeliveryRequirement><DeliverToAddress>. Could
<DestinationParty>
> > be used for SHIP TO details or perhaps parts of the
> > DestinationParty could be used to provide more details
> > for the <DeliverToAddress> like company name or person name. Related
> > to point 4 above.
> >
> > 9. I initially thought that the best fit for Bill To ID was
> > Order/BuyerParty/ID, but perhaps Order/BuyerParty/AccountCode
> > is a better fit, but I don't really understand what the purpose
> > is for AccountCode, any advice ?
> >
> > Thanks
> > Colin
> >
> >
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
--------------------
> > <?xml version="1.0" encoding="UTF-8"?>
> > <Order xmlns="urn:oasis:names:tc:ubl:Order:1.0:0.70"
> > xmlns:cat="urn:oasis:names:tc:ubl:CommonAggregateTypes:1.0:0.70"
> > xmlns:cct="urn:oasis:names:tc:ubl:CoreComponentTypes:1.0:0.70"
> > xmlns:ccts="urn:oasis:names:tc:ubl:CoreComponentParameters:1.0:0.70"
> > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> > xsi:schemaLocation="urn:oasis:names:tc:ubl:Invoice:1.0:0.70
0p70/xsd/UBL_Library_0p70_Order.xsd">
> >
> > <!-- MEANING : Order No. -->
> > <cat:ID>CUSTOMERPONUMBER</cat:ID>
> >
> > <!-- MEANING : Order Date. -->
> > <!-- Note: Format Expected is CCYY-MM-DD -->
> > <cat:IssueDate>2003-03-04</cat:IssueDate>
> >
> > <!-- MEANING : Currency Code -->
> > <TransactionCurrencyCode>GBP</TransactionCurrencyCode>
> >
> > <cat:BuyerParty>
> > <cat:ID/>
> > <!-- MEANING : BILL TO ID. -->
> > <!-- Note: This is ID is given to the -->
> > <!-- Buyer to use in Ordering -->
> > <!-- Transactions with SUN -->
> > <cat:AccountCode>BILLTOID</cat:AccountCode>
> >
> > <cat:BuyerContact>
> > <cat:ID/>
> > <!-- MEANING : Contact -->
> > <cat:Name>Claire Barnes</cat:Name>
> >
> > <!-- MEANING : Contact Phone No. -->
> > <cat:Phone>01635 248181</cat:Phone>
> >
> > <!-- MEANING : Contact Fax No.-->
> > <cat:Fax>01635 247924</cat:Fax>
> > </cat:BuyerContact>
> >
> > <cat:PartyTaxScheme>
> > <!-- MEANING : Vat Reg. No.
-->
> > <cat:CompanyTaxID>GB 363 3741 53</cat:CompanyTaxID>
> > <cat:TaxScheme>
> > <cat:ID/>
> > </cat:TaxScheme>
> > </cat:PartyTaxScheme>
> > </cat:BuyerParty>
> >
> > <cat:SellerParty>
> > <!-- MEANING : Customers ID for -->
> > <!-- SUN -->
> > <!-- Note: Determine if Buyer -->
> > <!-- needs to have this -->
> > <!-- data returned in -->
> > <!-- responses? -->
> > <cat:ID>CUSTOMERS SUN ID</cat:ID>
> > </cat:SellerParty>
> >
> > <cat:DeliveryTerms>
> > <cat:ID/>
> > <!-- MEANING : Header Delivery -->
> > <!-- Instructions -->
> > <cat:SpecialTerms>Header Level Comments</cat:SpecialTerms>
> > </cat:DeliveryTerms>
> >
> > <cat:OrderLine>
> > <!-- MEANING : Line No. -->
> > <!-- Note : All Line No's -->
> > <!-- must be unique -->
> > <!-- and of type -->
> > <!-- Integer -->
> > <cat:BuyersID>1</cat:BuyersID>
> >
> > <!--- MEANING : Quantity -->
> > <cat:Quantity unitCode="Each">10</cat:Quantity>
> >
> > <cat:DestinationParty>
> > <cat:ID/>
> >
> > <cat:PartyName>
> > <!-- MEANING : SHIP TO COMPANY NAME -->
> > <cat:Name>Ship To Company name</cat:Name>
> > </cat:PartyName>
> >
> > <cat:Contact>
> > <cat:ID/>
> > <!-- MEANING : SHIP TO CONTACT NAME -->
> > <cat:Name>Ship To Contact Name</cat:Name>
> >
> > <!-- MEANING : SHIP TO CONTACT PHONE
-->
> > <cat:Phone>Ship To Contact Phone</cat:Phone>
> >
> > <!-- MEANING : SHIP TO CONTACT FAX -->
> > <cat:Fax>Ship To Contact Fax</cat:Fax>
> > </cat:Contact>
> > </cat:DestinationParty>
> >
> > <cat:Item>
> > <cat:ID/>
> > <!-- MEANING : Product Description
-->
> > <!-- Note : Sun's ERP does not subscribe to this
-->
> > <!-- information. Does Buyer need to send
-->
> > <!-- this data as it needs it returned ?
-->
> > <cat:Description>Product
Description</cat:Description>
> >
> > <cat:SellersItemIdentification>
> > <!-- MEANING : Suppliers -->
> > <!-- Product Code -->
> > <cat:ID>SUN PARTNUMBER</cat:ID>
> > </cat:SellersItemIdentification>
> >
> > <cat:BuyersItemIdentification>
> > <!-- MEANING : Buyers Product Code -->
> > <!-- Note : Does Buyer intend on -->
> > <!-- sending this data ? -->
> > <cat:ID>CUSTOMER PARTNUMBER</cat:ID>
> > </cat:BuyersItemIdentification>
> >
> > <cat:BasePrice>
> > <!-- MEANING : Currency Code & Unit Price
-->
> > <cat:PriceAmount
currencyID="GBP">15200.0</cat:PriceAmount>
> > </cat:BasePrice>
> > </cat:Item>
> >
> > <cat:DeliveryRequirement>
> > <cat:ID/>
> >
> > <cat:DeliverToAddress>
> > <!-- MEANING : SHIP TO ID-->
> > <!-- Note : Sun generates-->
> > <!-- the ID's that-->
> > <!-- the Buyer can-->
> > <!-- use. -->
> > <cat:ID>SHIPTO-ID</cat:ID>
> >
> > <!-- NOTE : THE FOLLOWING ADDRESS -->
> > <!-- INFORMATION IS ONLY TO BE -->
> > <!-- USED FOR DYNAMIC SHIP TO -->
> > <!-- BUSINESS PROCESS. IF USED -->
> > <!-- THE ABOVE SHIP TO ID WILL -->
> > <!-- NOT BE USED. -->
> > <!-- FURTHER, INFORMATION FROM -->
> > <!-- DELIVERYPARTY ELEMENT CAN -->
> > <!-- BE USED FOR ADDITION INFO -->
> > <!-- ON THE SHIP TO ADDRESS LIKE -->
> > <!-- COMPANYNAME AND/OR PERSON -->
> > <!-- NAME -->
> >
> > <!-- MEANING : Building Name -->
> > <cat:Building>Building Name</cat:Building>
> >
> > <!-- MEANING : Address Line 1 -->
> > <cat:Street>Street Line 1</cat:Street>
> >
> > <!-- MEANING : Address Line 2
-->
> > <cat:AdditionalStreet>Street Line
2</cat:AdditionalStreet>
> >
> > <!-- MEANING : Address Line 3 -->
> > <cat:CityName>City</cat:CityName>
> >
> > <!-- MEANING : Address Line 4 -->
> > <cat:District>District</cat:District>
> >
> > <!-- MEANING : PostCode -->
> > <cat:PostalZone>PostCode</cat:PostalZone>
> >
> > <cat:Country>
> > <!-- MEANING : Country-->
> > <!-- Code -->
> > <cat:Code>GB</cat:Code>
> > </cat:Country>
> > </cat:DeliverToAddress>
> >
> > <cat:OrderedShipment>
> > <cat:ID/>
> > <cat:Information>Used For Line Level
Comments</cat:Information>
> > </cat:OrderedShipment>
> >
> > <cat:DeliverySchedule>
> > <cat:ID/>
> >
> > <!-- MEANING : Required By Date
-->
> >
<cat:RequestedDeliveryDate>2003-03-10</cat:RequestedDeliveryDate>
> > <cat:DeliveryRequirement>
> > <cat:ID/>
> > </cat:DeliveryRequirement>
> > </cat:DeliverySchedule>
> >
> > </cat:DeliveryRequirement>
> >
> > </cat:OrderLine>
> >
> > <cat:Contract>
> > <!-- MEANING : Agreement ID -->
> > <cat:ID>Agreement ID</cat:ID>
> > </cat:Contract>
> >
> > </Order>
------------- End Forwarded Message -------------
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]