Re: [ubl-dev] Modelling internal documents with UBL v2.0

["Stephen Green" <stephengreenubl@gmail.com>]

I would think a Request for Delivery is a Delivery Advice in reverse
- sent from receiver to deliverer. In that case you might be able to
use the Delivery Advice but with some care over how the ID works.
The ID will then be the ID given it by the receiver, rather than the
delivery party. (A parallel is with the use of Order as a Sales Order
or with some punch-out when the order is produced by the seller.)

On 01/02/2008, JAVEST <roberto@javest.com> wrote:
> Hello Michael,
>
> I agree with the use of UBL Order for the Warehouse Requisition but I do
> not understend perfectly the "Request for Delivery", can you please show
> in a timeline when it is used exactly ?
>
> For a fast and easy evaluation and understanding of UBL Documents and
> business entities I suggest you to use "UBL Swinger" software available
> for free at www.javest.com
>
> This software show you on the right side the UBL documentation
> dinamically (where sometime is available a sample for input data too).
>
> Hope this helps.
>
> Roberto Cisternino
>
> ---
>
> Michael Strasser ha scritto:
> > I am new to UBL (but not to XML) and am looking to model five documents to be generated by one of our systems that will be converted into faxes to be sent both internally and externally. I looked for standard XML vocabularies for such documents and naturally found UBL.
> >
> > The documents are Purchase Order, Remittance Advice, Request for Quotation, Warehouse Requesition and Request for Delivery (expedite letters for ordered items outstanding). The first three map directly to their UBL namesakes.
> >
> > The other two are not so simple. My instinct is that Warehouse Requisition is really a type of order where the seller is another part of our organisation. I'm not sure about Request for Delivery. I suspect that UBL-Order may model it as well but I'm don't know if these requests can refer to multiple previous orders. Does this sound reasonable or have I missed a document type?
> >
> > I may also ask questions about how to cope with UBL's complexity. The range of choices appear overwhelming at first and I am looking for some best-practice or common-practice advice in using documents and common components. That advice may be from the list or from resources you recommend.
> >
> > I really appreciate any help you can give on any of these matters.
> >
> >
> > Regards
> >
> > Michael Strasser
> > Enterprise ICT Architecture
> > Brisbane City Council
> > Brisbane, Australia
> >
> >
> >
> > **********************************************************************
> >    This message has passed through an insecure network.
> >     Please direct all enquiries to the message author.
> > **********************************************************************
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: ubl-dev-unsubscribe@lists.oasis-open.org
> > For additional commands, e-mail: ubl-dev-help@lists.oasis-open.org
> >
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ubl-dev-unsubscribe@lists.oasis-open.org
> For additional commands, e-mail: ubl-dev-help@lists.oasis-open.org
>
>


-- 
Stephen D. Green

Partner
SystML, http://www.systml.co.uk
Tel: +44 (0) 117 9541606

http://www.biblegateway.com/passage/?search=matthew+22:37 .. and voice