ubl-jplsc — archive

[Tim McGrath]

 MHonArc v2.5.0b2 -->




















ubl-jplsc message






[Date Prev]
 | [Thread Prev]
 | [Thread Next]
 | [Date Next]

--

[Date Index]
 | [Thread Index]
 | [List Home]








Subject: Re: [ubl-psc] Re: Issues with Libraries for UBL 2.0.




From: Tim McGrath <tmcgrath@portcomm.com.au>
To: Yukinori Saito <saito-yukinori@fujielectric.co.jp>
Date: Thu, 25 May 2006 16:48:12 +0800










sorry i wasn't too clear.


the answer is:

(2) All ABIEs will be integrated to one common spreadsheet. However,
the contents of this spreadsheet is divided to three categories. For
example: The first group is Common, the second group is Procurement,
the third group is Transportation.

and

(part of 1) A new column 'Business Process column' will be added in the
spreadsheet for the user to understand the usage (Common, Procurement,
or Transportation) of the targeted ABIE


Yukinori Saito wrote:


  
  
  
  
  
Dear Tim McGrath,
  
JPLSC has discussed about your reply on May 24 at F2F Meeting in
Tokyo.
  
The followings are an additional question and answer.
  
 
  
1. Spreadsheet architecture
  
We cannot understand your reply sentence 'only one "common"
spreadsheet sorted in order of "all contexts", "procurement", then
"transportation" ABIEs (based on their business process)' clearly.
  
Which of followings is the suitable understanding regarding the
new Spreadsheet architecture?
  
(1) All ABIEs will be integrated to one common spreadsheet. The
order of the ABIE items is an alphabetical order like Reusable V1.0.
However, new column 'Business Process column' will be added in the
spreadsheet for the user to understand the usage (Common, Procurement,
or Transportation) of the targeted ABIE. 

(2)  All ABIEs will be integrated to one common spreadsheet. However,
the contents of this spreadsheet is divided to three categories. For
example: The first group is Common, the second group is Procurement,
the third group is Transportation.
  
 
  
2. Reference table
  
OK, we (JPLSC) will prepare the reference table.
  
 
  
Best Regards,
  
Yukinori Saito