[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Agenda for the UBL PSC meeting the 1th of October 2009
Dear all Please find the minutes
for the UBL PCS meeting the 1st of October 2009 from 17.00 to 18.00
CET STANDING CON CALL NUMBER Skype:
+9900827043982678 US/Canada toll-free:
1-888-350-0075 International:
201-793-9022 "Conference Room
Number": 3982678 then #
(applies only if calling one of the phone numbers) Arianna will send out a yougma session number
before the meeting 1)
Review of the current issue
list 2)
Review of the action
items A
Tim and Georg will come up with a resolved solution for item 23 (Item property
characteristic code) that satisfies PEPPOL WG3 requirement. (Georg has sent out
a suggestion, comment is needed from Tim) B
Martin will check the definition of Order Type Code in the common
OrderReference in the common library (this will be reused in the Order
documents). This is related to issue 40 (see answer below) C
Peter will check with Ole the use of Alternative line item (issue 37) as solved
in the common library D
Peter will check with Ole the use of Amount in ReminderLine (maybe to be
updated with SurchargeAmount) E
Martin will check the definition of OrderResponseCode (issue 28) (see answer
below) F
Georg wil send out an suggestion stepwise payment for the next meeting 3)
New Enea and iSurf documents
(by Arianna and Fulyia) 4)
Review of the CENBII
submission (By Georg. Georg, can you resend the list if there has been updates
due to the review) 5)
Updates of the spreadsheet
with the tendering submission (by Oriol) 6)
Any other business Kind regards Peter PS: Martin, we are working on UBL 2.1 and
are referring to the spreadsheets Arianna has sent out to the list. In these there
should be a ordertype in the OrderReference Fra: Martin Forsberg
[mailto:martin.forsberg@ecru.se] Hi Peter, I suppose
that the action items assigned to “Martin” means me? B
Martin will check the definition of Order Type Code in the common
OrderReference in the common library (this will be reused in the Order
documents). This is related to issue 40 There is no Order
Type Code in OrderReference in UBL2. However a Type Code is used on Order-header
level EDIFACT and Ttese are examples of document types (CL 1001) that can be
used in EDIFACT, but I'm not sure if there is a need for a specific
subset of code values. 105 Purchase order 147 Multidrop order 150 Internal
transport order 220 Order 221 Blanket order 224 Rush order 225 Repair order 226 Call off order 227 Consignment order 258 Standing order 237 Cross docking
service order 400 Exceptional order 401 Transshipment
order 402 Cross docking
order If the type code is
adopted in UBL Orders a definition could be, "A code indicating the type
of order". But I'm not sure it would be necessary to use the code in the
Order Reference ABIE. It already have an ASBIE to document reference which
includes a type code. E
Martin will check the definition of OrderResponseCode (issue 28) Use CL 1225 Definition: “A
code indicating the type of response for this Order.” /Martin Från: Peter L.
Borresen [mailto:plb@ebconnect.dk] Dear all Please find the minutes
for the UBL PCS meeting the 24th of September 2009 from 17.00 to 18.00 CET STANDING CON CALL NUMBER Skype: +9900827043982678 US/Canada toll-free: 1-888-350-0075 International: 201-793-9022 "Conference Room Number": 3982678 then # (applies only if calling one of
the phone numbers) 1)
Current status of the issue
list We went through the
issue list (version 8) and ended up with the following action list: A
Tim and Georg will come up with a resolved solution for item 23 (Item property
characteristic code) that satisfies PEPPOL WG3 requirement. B
Martin will check the definition of Order Type Code in the common
OrderReference in the common library (this will be reused in the Order
documents). This is related to issue 40 C
Peter will check with Ole the use of Alternative line item (issue 37) as solved
in the common library D
Peter will check with Ole the use of Amount in ReminderLine (maybe to be
updated with SurchargeAmount) E
Martin will check the definition of OrderResponseCode (issue 28) It was decided to
reject issue 16 about making all amounts positive. This is an issue for the
further customization to deal with. It was decided not to
have a factoring indicator on the payment terms. Instead the invoice type code for
factoring invoice is used. 2)
Review of the common library
spreadsheets (by Arianna) Common library hass
been sent out and was reviewed during item 1 on the agenda 3)
Submission from the financial
subcommittee: how to do stepwise payment (by Georg) F
Georg wil send out an suggestion for the next meeting 4)
New Enea and iSurf documents
(by Arianna and Fulyia) Postponed to next
meeting 5)
Review of the CENBII submission Postponed to next
meeting 6)
UBL PSC face to face meeting
where and when? 2nd and 3rd
of November in Brussel was suggested 7)
Any other business None Kind regards Peter L. Borresen Chariman |
No virus found in this incoming message. Checked by AVG - www.avg.com Version: 8.5.409 / Virus Database: 270.13.112/2394 - Release Date: 09/25/09 05:51:00
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]