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


Help: OASIS Mailing Lists Help | MarkMail Help

ubl-australia message

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

Subject: Re: ubl-australia] Agenda for ALSC Call 9 January 11:00 AEDT

All, the call  has been cancelled for attendance reasons

Thank you

Levine Naidoo
On 6 Jan 2019, 11:55 +1100, Levine Naidoo <levine@lxndigital.com>, wrote:
Dear all 

Please find below the  agenda and updated progress for our net all. We shall resume from the section labelled  "Resume from January 2019"

Agenda for ALSC Call 9 January  11:00 AEDT



Meeting ID: 547 975 473

Join from PC, Mac, Linux, iOS or Android:

Or iPhone one-tap (Australia): +61280152088,,547975473#

Or additional telephone numbers:

Many thanks to http://eFact.pe for sponsoring our teleconferences.

        OASIS Universal Business Language (UBL) v2.2
Google sheets are located in the ALSC google drive 


  1. Review of minutes
  1. Review of DBC semantic model (Invoice) approach:
    • Review model issues
      • Optionality in single child elements
      • Cardinality one Accounting Supplier and Customer Party
      • Invoice line documentation (PO, Despatch and Receipt)
      • Party Contact
      • Use of CompanyID in PartyTaxScheme - is it ABN or Branch ID and Cardinality
    • Industry Scenarios
      • Existing trading networks 
        • A detailed analysis has been conducted on the MIGS published by Woolworths, Metcash and Coles. They all use the same version of EANCOM but to varying degrees - stats can be provided. The observations are that
          • The Delivery ABIE child elements should be reviewed for cardinality to support the way EANCOM is used by the retailers
          • The Shipment ASBIE within Delivery should be made optional to to support the way EANCOM is used by the retailers 
          • There is a finite list of supporting documents in the way EANCOM is used - should we create a code list for the DocumentType?- recommend to leave as per consumersâ implementation guide, as a courtesy there would not be too much effort to create a sample genericode file to assist with validations  
          • Item.BuyersItemIdentification should be made available due to being required by Woolworths
          • Pricing can be done by basis value and measurement units which (within UBL) are attributes of price
          • Linetotals inclusive of GST are also included in EANCOM - this may be a requirement for UBL2.3 under the principle that all values should be manifest and that there should not be any calculations in the rendering mechanism or even receipt. This is also a requirement within a state government implementation. Issue is raised - https://issues.oasis-open.org/browse/UBL-182
        • GS1 XML - Levine

  1. Documentation Approach
    • Proposed approach for review and creation of ALSC artefacts with coaching from Ken
- cnd01dw01 as working draft for artefacts
- cnd01dw01 be reviewed under public consultation
- Templates are available from OASIS
- ALSC Artefacts should be:
- spreadsheets
- schemas & html
- schematron
- document (xml via docbook or word document)

  1. P2P scope - numbered in priority order
    • Purchasing (2)
      • Order, Order Response Simple, Order Response, Order Change, Order Cancellation
    • Fulfilment (3)
      • Despatch Advice, Receipt Advice, Fulfilment Cancellation
    • Accounts Payable
      • Invoice including elaborate payment means (1), Remittance (1), statement (4), reminder (4), Utility Statement (4)

  1. JIRA tickets
Summary - https://issues.oasis-open.org/issues/?jql=project%20%3D%20UBL%20AND%20component%20%3D%20%22Australia%20SC%22

When creating tickets for the SC, remember to use âAustralia SCâ to distinguish between the following components by how they are described to be used as categories:
if you leave the "Component/s" field empty, the ticket will not show up in the SC summary filter.

Status and resolution values:

See also the discussion on the status workflows here:

Members please note to discuss ticket issues as comments to the ticket so that we can audit the discussion when making decisions about the ticket, without having to find the discussion on the main mail list


Will review on an as needed basis



Thank you

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