OASIS UBL TC Brussels Meeting UBL JPLSC Report May 22, 2006 Yukinori Saito Vice Chair of OASIS UBL JPLSC Fuji Electric Information Service Co. , Ltd. saito-yukinori@fujielectric. co. jp 1
Recent Activities (F 2 F Meeting) 10 th Meeting - Discussion about JPLSC’s proposal to UBL TC regarding ECALGA. (2005. 03. 17) - Mr. Naito (Osaka Institute of Technology) has firstly joined. 11 th Meeting - Report of UBL TC Hangzhou meeting by Y-Saito. (2005. 25) - Introduction of OASIS PPS (Production Planning and Scheduling) TC by A-Kawauchi. 12 th Meeting - Study of UBL activities, e. g. Development activities to UBL V 2. 0, (2005. 11) Cooperation between UBL and UN/CEFACT, UBL deployment. - Study about differences between UBL and OAGIS. 13 th Meeting - Study and evaluation of UBL V 2. 0 specification ’Universal (2006. 01. 06) Business Language 2. 0 (index. html)’. Then JPLSC have submitted the comments to UBL TC. 14 th Meeting - Study and evaluation of UBL V 2. 0 business documents. UBL (2006. 03. 11) JPLSC members have shared their working concerning the checking of V 2. 0 business documents. Then JPLSC have submitted the comments to UBL TC. 15 th Meeting - Study and evaluation of UBL V 2. 0 business documents (continued). 2 (2006. 05. 24)
Members of JPLSC ■Chair * Noboru Itoh. Sunbridge Solutions Corp. ■Vice Chair * Yukinori Saito Fuji Electric Information Service Co. , Ltd. Chair of B 2 B-EC framework WG in ECOM ■Members Nobuyuki Sambuichi Hitachi Systems and Services, Ltd. Shin Takagi Hitachi Systems and Services, Ltd. Kentaro Ejima Infoteria Corporation * Hiroshi Naito Osaka Institute of Technology * Naomasa Hosoda NEC Soft, Ltd. * Akihiro Kawauchi Process Business Research Institute * Kunio Ohno Justsystem Corporation * Keisuke Ueno Japan Petrochemical Industry Association *: active member 3
Comments to UBL V 2. 0 business documents (1/4) JPLSC have submitted some comments of UBL V 2. 0 business documents to UBL TC on March 24, 2006. The followings are some of them. 1. Ordering - Many BIE are added comparing V 1. 0. Approximately 50% process BIEs are changed. UBL Names of some BIEs are changed. We don’t know why these are changed. 2. Billing, Payment process - We think that there are many mistakes and omissions in UML activity diagrams. - There is no description regarding Application Response in UBL V 2. 0 (index. html). Therefore, we cannot understand how to use or manage the Application Response business document. 3. Transportation process - There are some use cases descriptions regarding Transportation business process in the section 5. 8 “Initiate Transport Service Collaboration” in UBL V 2. 0 (index. html). We think that there is a business process that the buyer goes 4 to the supplier to get the ordering Items.
Comments to UBL V 2. 0 business documents (2/4) 4. Compatibility between V 1. 0 and V 2. 0 -There are many changes in Business Document V 2. 0 comparing V 1. 0. We think that UBL V 2. 0 specification cannot keep downward compatibility to V 1. 0. - What is a design policy in UBL specifications regarding compatibility among V 1. 0, V 2. 0, and next V 3. 0? 5. Definitions - There are many codes in UBL business documents. However, of Code value there are very few definitions of Code’s values. In case to use UBL business documents, this would become big problems. - We think that there are two kinds of Codes. One is universal codes, those are defined by some standard bodies. For example: Country Code, Currency Code. The other one is a code that is defined by the trading partners themselves. In case of this kind of trading partner’s defined codes, we would like to have some principles or guidelines regarding the code values. Let me cite an example regarding Code definition in Japanese business documents. There are many business documents in many industries in Japan. These business documents have Code Definitions. The Code Definitions define the meaning of code and 5 definition of code values.
Comments to UBL V 2. 0 business documents (3/4) 6. The size of YS: Reusable V 1. 0 contains 60 ABIEs. And Reusable spreadsheet has 431 items (ABIE, BBIE, ASBIE). This is quite a big size already. Reusable The Reusable V 2. 0 will contain 104 ABIEs. I think that this size is spreadsheet too big to manage. I have no suitable ideas about this issue. Alternative idea is that the Reusable spreadsheet will be divided to two or three peaces physically. TM: Only one "common" spreadsheet sorted in order of "all contexts", "procurement", then "transportation" ABIEs (based on their business process). 6
Comments to UBL V 2. 0 business documents (4/4) YS: Please provide us (UBL users) Reusable ABIEs reference table 7. Provide a reference table that explains referring business documents and referring Reusable ABIEs by each ABIE. between I think that this reference table is a kind of support documents. Reusable and The attached document is a sample of Reusable ABIEs reference business table. In this document, the key item is ABIEs in reusable. The contents are referring business documents and referring Reusable documents ABIEs. TM: Provide a reference table as you suggest. Once we have stablized the "common" spreadsheet (following the UBL Plenary meeting on May 22 -25) we may ask if the JPLSC can prepare the reference table. Is that reasonable? 7
Reusables V 1. 0 Reference table No. 1 ABIE in Reusable Address 2 3 Address. Line Allowance. Charge 4 5 6 Base. Price Branch Buyer. Party 7 8 Card. Account Commodity. Cllasifi cation 9～ Referring documents Order, Order. Response, Order. Change, Invoice Referring Reusables Branch, Delivery, Financial. Instruction, Party. Tax. Schema, Tax. Schema Address Delivery. Terms, Invoice. Line, Line. Item Invioce. Line, Item, Line. Item Financial. Account Order, Order. Response, Order. Change, Order. Cancellation, Despatch. Advice, Receipt. Advice, Invoice Payment. Means Item 8
Related activities concerning UBL in Japan 1. ECOM (Electronic Commerce Promotion Council of Japan) - - ECOM developed a business document named ‘Business document model for the manufacturing domain’ in 2004. This business document is a subset of ECALGA. ECOM did mapping study from ‘Business document model for the manufacturing domain (ECALGA based)’ to UBL in 2004. In this mapping studying process, ECOM developed a UBL subset for ebusiness between SMEs and big enterprises in Japan. 2. Common XML/EDI Practice Promotion Council - - The Common XML/EDI Practice Promotion Council has been established in May, 2004. This council promote next generation common XML/EDI system for not only big enterprises but also SMEs. This council developed the Common XML/EDI framework standards. The business document in this Common XML/EDI framework standards is ‘Business document model for the manufacturing domain (ECALGA based)’ 9 and UBL subset.
Common XML/EDI framework will adopt UBL as an international business documents to overseas trading companies. Common XML/EDI framework Big enterprises VAN terminal Push type XML/EDI Closed network VAN server Industry specific business document, or Business document model for the manufacturing domain Business document Internet model for the Manu. Other Hub server EDI-ASP Hub server Overseas UBL Subset Business document model for the Manufacturing domain Common XML/EDI framework Push type XML/EDI Medium sized SME Pull type XML/EDI Small sized SME ・Push type EDI：Sender sends the business document to receiver. Constructed by server computer. 10 ・Pull type EDI： Receiver gets the business document from the sender. Constructed by personal computer.
Скачать презентацию OASIS UBL TC Brussels Meeting UBL JPLSC Report
a8d39f31c6097c41fe36b1feb907d8b6.ppt