Working Group meeting 26/01/2023

Date: 26/01/2023
Participants: Natalie Muric, Svante Shcubert, Pietro Palermo, Peter, Thomas Pettersson, Ivan Weller
Model editor: Eugeniu Costetchi
Note editor: Jana Ahmad

Agenda

  • eOrdering open discussion

    • Goal is to ensure completeness of the current model

Discussion

The WG discussed the Order diagram with respect to Peppol Order transaction 3.2 (T01) to be sure that they are compatible.

Methodology:

The current approach to assessing the completeness of the ePO model with respect to PEPPOL requirements involves determining whether the following requirements are already covered by ePO. If they are, the WG will map them to ePO. If they are not covered, they will be implemented as follows. The bullet points represent the PEPPOL requirements, while the sub-bullets indicate their mapping to ePO.

  • ubl:order

    • order only diagram renamed to order

    • epo-cat:lineSet changed to eop-cat:PostAwardObject

B+GIypGNZCU6AAAAAElFTkSuQmCC

  • identifiers : (cbc:CustomizationID, cbc:ProfileID, cbc:ID)

    • epo:hasID, epo:hasPprofileID and epo:hasCustomizationID object properties are added to epo-cat:PostAwardObject and defined

wDSzYPpmN96SAAAAABJRU5ErkJggg==

  • cbc:SalesOrderID

    • ope-ord:hasSalesID: this relation should be created on an object of type Offer when it is modeled

    • Note: in Sales order, the order can be sent from seller to buyer to sign it.

  • cbc:IssueDate, cbc:IssueTime

    • Time is at the metadata level.

    • time and date properties should be added

    • A link between eop-Order to epo-Document should be added

    • Crate relation between eop-Document and eop-cat:PostAwardObject

      • Link the document “metadata layer”with the content of document

  • cbc:OrderTypeCode: for Order type:

H9tnVisnSEdCgAAAABJRU5ErkJggg==

  • Cbc:note

    • epo:hasAdditinalinformation is added to eop-cat:postAwardObjec

  • cbc:DocumentCurrencyCode

    • Mapped to epo:MonetaryValue.

    • epo:oderLine has price which is a MonetaryValue

  • cbc:CustomerReference

    • eop-ord:hasChttps://docs.peppol.eu/poacc/upgrade-3/syntax/Order/cbc-CustomerReference/[ustomerReference] t is added to order object

  • cbc:AccountingCost

    • eop-ord:hasAccountingCost t is added to order object

weHT0z2YE3AaAAAAABJRU5ErkJggg==

  • cac:ValidityPeriod:

    • eop-cat:PostAwardObjec has (epo:hasValidatyPeriod) relation with epo:Period class

j+WpHcypzL6sAAAAABJRU5ErkJggg==

To be continued with “cac:QuotationDocumentReference” - https://docs.peppol.eu/poacc/upgrade-3/2022-Q4/syntax/Order/tree/

Ideas for future development:

  • Generate automatically an application profile listing all properties for a Create a table that contains all the properties for all the concepts in the Order phase.

  • There is a need for mapping UBL , UNCFACT and ePO

  • There is a digital gap between TC440 and ePO Work GRoup

    • Need to extract a worksheet from the class diagram and just have the list of classes and properties, in the likes of tabular application profile definition. This shall include the inherited properties as well.