OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ubl-dev message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [ubl-dev] EDI to UBL. Implementation questions.


Hello,
yes you can use the Despatch Advice.

"The ASN is a document that is used to notify a customer about an 
expected delivery. It is a kind of delivery confirmation. The ASN is 
typically generated based on information that is available when the 
shipment has left the warehouse"

For easier evaluation of the UBL document's structure I suggest you to 
install "UBL Swinger" an UBL instance writer at www.javest.com
NOTE: The install process will ask you to provide a folder for your 
workspace where UBL documens and schemas will be placed.
Start from the slides to have an immediate understanding of the tool.


Miguel Pérez E ha scritto:
>
>
> Hi All,  We are currently developing an integration project which includes EDI mapping to a selected XML standard. We've been studying the different standards available out there and I am working on the UBL one. Basically, I need to map POs, ASN (Advace Ship Notices) and Invoices between EDI (X12) and UBL.  First, theres segments, data elements and qualifiers that may not have a direct correspondance within the UBL. Example: Segment DTM, qualifier for Expiration date for food.  Second, about ASN I am not sure if to choose  the Despatch Advise squema. We usually follow a hierarchy like ( Shipment, Order, Package, Item ) but there is no clear way of how to implement this in the Despatch Advice Squema. One ASN may be handling good of several different POs. 
OrderReference  (0...n)

>  Almost always we need to report how the goods are going to be packed, example, Box 1{ 4 items of A, two items of B } Box 2 {5 items of B} and so on.. Is this possible in the DespatchAdvice squema? 
You should use the DispatchLine for this level of detail... inside you 
can define the "Item" information and the specific "Shipment".

The "Shipment" information available on the root is not mandatory, you 
can use it just for simple ASN.

> I wouldn't like to have to customize a standard squema for my own purposes.. , but in case I need to is that considered a good practice?   Thanks a lot for your help on this matter,   MiguelMontreal, Canada  
> _________________________________________________________________
>
>   

If really needed you can use customization... but I think it is not 
necessary.
Let me know if you have further difficulties.



Best regards,

UBL ITLSC co-chair
Roberto Cisternino


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]