[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [ubl] Process for validitating the delivery
Hi Peter, In the diagram you the flow starts with Accept/reject shipment. If the shipment is rejected the consignee is unable to count the packages, look for damage or let the originator check the goods and is unable to send a
ReceiptAdvice. If you reject something you have to know what is rejected. We have to look at the hole 2.3.5 Deliver paragraph.
In 2.3.5.1.3 Receipt Advice Business Rules: The Receipt Advice provides for two situations. For ease of processing claimed receipt against claimed delivery, it needs to be organised in the same way as the
corresponding Despatch Advice:
If cac:ReceiptLine is to become optional the cac:DespatchLine should also be optional. Kind regards, Wim Van: ubl@lists.oasis-open.org <ubl@lists.oasis-open.org>
Namens plb@ebconnect.dk Dear all As agreed on the UBL meeting I here send you a descriptipon of the validation process that happens in the delivery. Questions: Can a receipt advice reject the shipment? If not, how is the sender of the despatch advice informed that his despatch was rejected?
I agree with Kees that rejecting the shipment belongs to the logistics process, but it also belong to the fulfilment since the fulfilment has failed.
Best regards Peter Dit bericht kan informatie bevatten die niet voor u is bestemd. Indien u niet de geadresseerde bent of dit bericht abusievelijk aan u is toegezonden, wordt u verzocht dat aan de afzender te melden en het bericht te verwijderen. De Staat aanvaardt geen aansprakelijkheid voor schade, van welke aard ook, die verband houdt met risico's verbonden aan het elektronisch verzenden van berichten. This message may contain information that is not intended for you. If you are not the addressee or if this message was sent to you by mistake, you are requested to inform the sender and delete the message. The State accepts no liability for damage of any kind resulting from the risks inherent in the electronic transmission of messages. |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]