DespatchAdvice and updates ...

UBL Dev readers,

I am getting a request to implement a method to be able to handle updates on DespatchAdvice documents.

As far as I can see does UBL not really support this in the DespatchAdvice (there is no “DespatchAdviceDocumentReference” in the DespatchAdvice to reference to a previously sent DespatchAdvice)

In UBL we only have a “cac:AdditionalDocumentReference” that could be used for this reference … but it is not a “named reference”

When the DespatchAdvice document was designed .. was this subject discussed? And what would be the best practice to update DespatchAdvice documents?

My position is that each UBL document should have it’s own unique (document)ID, so an update to a already send DespatchAdvice should have a new unique (document)ID.

You could use the DespatchAdviceTypeCode to specify that this new document is an update/change to an already send DespatchAdvice but not sure if that is the correct place. Also because there is also a “DocumentStatusCode” that could be used in the header.

There is also the “FulfilmentCancellation” document .. but that can only be used to cancel a whole document .. so that would mean two document from the seller (one FulfilmentCancellation and one new DespatchAdvice) which might put to much burden on the sender.

If I look at the GS1 DESADV documentation:

http://www.gs1.org/docs/gsmp/eancom/2012/print/ean02s4.pdf/desadv.pdf

I see that on page 26 they describe an element called “Message Function Code”. In there you can specify information that you can use in relation to a previously send DespatchAdvice.

If you use message function code to cancel, update or replace a GS1 DESADV you use the RFF element to specify which DESADV document you want to cancel, update or replace.

So what is the UBL equivalent to this?

So I’m looking for pointers on how to implement this in a “correct” way.

Thanks,

Kees Duvekot

ubl-dev message