EndpointID on only two parties

[agrindst]

When it comes to information sharing, Logistics might be a bit closer to Pre-Awards (PrAC) when it comes to who needs/wants the information. In Logistics we have a sender and a receiver of the document, but there can be other parties who need the information and want to be informed about updates etc. This can be done in several ways:​

1. The Sender of the document sends it to all relevant parties​
2. The integrator (organizer of the transport) sends this to all relevant parties​
3. The distribution of information to the parties involved in the logistics happens with other means than Peppol. The Peppol message is only passed between the sender and the receiver of the document.

How do we want to solve this in the Transport Execution Plan Request? Do we want to follow a principle with only two EndpointIDs, or do we want to solve this in a different way with more than two EndpointIDs?​​

[agrindst]

Will be discussed in project group meeting. Suggested decision:​ Keep only two EndpointIDs (Sender / Receiver of document).

[agrindst]

As decided by the project group we will keep only two EndpointIDs

Action needed:

• [ ] remove additional EndpointIDs, and keep only two

[PeterLBorresen]

I think we need to solve the different Party templates. In Advanced Despatch Advice we have two.

[agrindst]

As agreed on in WG, Peter will check and look into rules of different party templates

[agrindst]

One possible solution is to have EndpointID on two parties mandatory, however open to the possibility to have EndpointIDs on others as well (optional).

[agrindst]

Actions:

• [ ] Have EndpointID on only sender and receiver

[areberg]

Does this mean the SenderParty and the ReceiverParty or the party actually sending and receiving the transaction, the TransportUserParty and the TransportServiceProviderParty? The last two are mandatory in UBL.

[PeterLBorresen]

Done

[agrindst]

Completed,

there are only EndpointID on:

• TransportUserParty
• TransportServiceProviderParty