Introduction to CII (Center for the Informatization of Industry)

Transcription

1 Introduction to CII (Center for the Informatization of Industry)

2 Table of contents Table of contents... 2 Introduction to CII... 3 Outline of the CII Syntax Rule... 3 Type 12 (Normal mode)... 4 Type 12 (Dividing Mode)... 4 Type-E... 5 Compressed Mode and Extended Mode... 6 Non-Transparent Mode Option... 6 Data Element Repeating (repeating Rule: Table type data)... 6 Character Codes... 7 Format of Message Group Header... 7 More About Checksum Message (Type12) Message Header TFD Area Message Group Header Table Message Group Trailer Table Message Table... 17

3 Introduction to CII Electronic Industries Association of Japan (EIAJ) started standardization of EDI and developed a new EDI standard - EIAJ Syntax rule in cooperation with Center for the Information of Industry (CII) in This CII then developed a new EDI standard in 1991 called CII Syntax rule. The CII Syntax Rule is a syntax rule newly developed in order to standardize EDI in Japan and improve the EIAJ syntax rule. There are different CII Syntax Rule versions available - CII Syntax Rule 1.11, 1.51, 2.10 and Outline of the CII Syntax Rule The CII Syntax Rule is a system considering compatibility with Japanese EDI applicable characters and transmission systems. The following figure explains the Classification of CII Syntax Rule. The CII Syntax Rule is designed for EDI by File Transfer System and basic style is Type12 which is formed of a Message Group Header, one or more messages and a Message Group Trailer. The message group header, message and message group trailer are each stored in one-record (one message is stored in one record). Based on this design, there are 2 variations. One is a method to store one message in a number of fixed length records, called a Type12 dividing mode and the other called Type-E. All messages of CII Syntax rule contain their data in their TFDs. TFD which is the Transform Form Data are used to transfer the Data Elements in the CII Syntax Rule. In TFD, a Data Tag and Data Length Tag (length tag) are added to the Data element.

4 One message is formed by collecting the necessary number of TFDs. "Data Tag" is an ID expressing the meaning and attribute of a data element. The length tag stores the length of the data element. Type 12 (Normal mode) Here is the figure which explains the difference between Type-12 dividing, normal modes and Type E Syntax. Type-E has a syntax similar to the EDIFACT standards. In a normal mode, though the message group header and message group trailer are each stored in a single 251 bytes fixed length record, one message is stored in a single VARIABLE length record. Type 12 (Dividing Mode) This is similar to normal mode but in order to meet transmission systems, which are unable to handle variable length records, one message is stored in the plural number of 251 bytes FIXED records.

5 A message is formed of one Message Header, one TFD areas and one Message Trailer. The area between the Message Header and Message Trailer is called the TFD Area. Type-E The Message Group Header in Type-12 Normal (or Dividing mode) is replaced with UNA and UNB segments, and the Message Group Trailer is replaced with the UNZ segment. The Message Header is replaced with UNH segment and the Message Trailer is replaced with UNT segment is added to the message. Both UNA and UNB segments are stored in a VARIABLE length record together, and the other segments are stored in variable length records respectively.

6 Compressed Mode and Extended Mode A message can be in a Compressed mode or in a Extended mode according to the Data Element Identifier number which is the Data Tag. Within a message, there is a TFD area to store TFD data. In a TFD area if we have an Extended Mode Indicator (X'FO'), it indicates that the right margin is the Extended mode area. On the Left of the Extended Mode Indicator within the TFD area is a compresses mode. When there is no Extended Mode Indicator within the TFD area, the TFD area altogether becomes a compressed mode. Within the Compressed mode, a data tag becomes 1 byte unsigned binary, and represents a data element Identifier number from 1 to 329. Within the Extended mode, the data tag becomes 2 bytes unsigned binary, and represents a data element identifier number from 1 to Non-Transparent Mode Option This option is applicable to use of non-transparent mode communications systems. As the CII Syntax rule is designed for transparent mode communication systems, some data clashes with communication control characters and is not transmitted completed. The non-transparent mode is an option to avoid clashing with communication control characters. However, using this option will make the message length longer. Therefore, this option is not used together with transparent mode communication systems. Data Element Repeating (repeating Rule: Table type data) In principle, in a particular TFD area within the same message, 2 or more TFD data elements with the same data tag may not be included. To do so, CII Syntax has a repeating rule which is applied. A number of TFDs (each with a different data tag value) are collected as segments and these segments are repeated to transfer array data. A segment may be formed of a single TFD. This set of segments form the Multi Detail. A Multi Detail Header (MDH) is put at the beginning of the first segment. A return mark is also put between segments which indicate there is one more segment in the Multi Detail. This return mark is called as the Multi Detail return (MDR).

7 A Multi Detail Trailer (MDT) is put at the end of the last segment. Any TFDs within a segment may also be suppressed and compressed if preferred. When all the TFDs are suppressed and compressed within the same segment, only the return mark will be left. Character Codes The CII Syntax Rule has JIS-X0201 and JIS-X0208 as standard character codes. In the Message Group Header and Message Group Trailer, the use of characters is prohibited except for alphanumeric characters and blanks, and JIS-X0201 must be used for character code. Format of Message Group Header This format is according to the CII Syntax rule Version 1.11 and The message group header is a header used in Type12 and is a fixed format with a length of 251 bytes as shown in the below figure. Here is the detailed description of some of the important components of the Message Group Header: Dividing-id (characters 1 byte: 0 (= X 30 )) Indicates that it is a header or trailer of Type-12. Record Identifier(characters 1 byte: C (= 43 )) Indicates that is a message group header of Type12. Operation mode (characters 1 byte) Indicates test data when 1(= X 31 ). Indicated normal data when 0 (=X 30 ). BPID: Organization code (characters 4 bytes) Code indicates managing organization of standard messages.

8 Organization code (characters 4 bytes) Code indicates managing organization of standard messages. Sub organization code (characters 2 bytes) Large classification code for managing standard messages (code managed by standard message organization). Edition (characters 2 bytes) Version number (code managed by standard message organization). Reserve (characters 12 bytes) Reserved for future extended area (all blank = X 20 ). Information ID code (characters 4 bytes) Indicates type of message. Format ID - It is set to the following values for different types of messages. However, transparent/nontransparent mode ID has no effect on the value of this code. Type12 (normal mode) (non - dividing mode) (=X 3130 ) Type12 (dividing mode) (=X 3131 ) Type12 acknowledge message (=X 3230 ) Date and Time of message creation (characters 12 bytes) - Date and time of message group production in YYMMDDHHMMSS. Syntax ID and Version number (characters 6 byte) - Indicates syntax rule managing and release version number Extended Mode (Character 1 byte) - Indicates compressed mode when blank (=X 20 ) or S (=X 53 ) is set and indicates extended mode when E (=X 45 ) is set. This character indicates that the message is in compressed mode when this area is set in compression and indicates whether the message is compressed mode or extended mode when the data is set in extension. Dividing Mode (Character 1 byte) Indicates the dividing mode when clank (=X 20 ) or M (=X 4D ) is set, and indicates normal mode when S (=X 53 ) is set. Character Code 8 bit character (1 byte) Indicates 8 bit character sets are JIS-X201 when blank or S is set 16 bit character (1 byte) Indicates 16 bit character sets are JIS-X0208 when blank or S is set. Character Code 8 bit character (1 byte) Indicates 8 bit character sets are JIS-X201 when blank or S is set 16 bit character (1 byte) Indicates 16 bit character sets are JIS-X0208 when blank or S is set. Non-transparent mode NOTE: Always view a CII file in hex format so that you can get the hex values of all the characters in a CII file. 1st Total items No(characters 3 bytes *2) and 2nd Total Items No(characters 5 bytes *2) : Data element tag number is assigned to create check-sum when compression mode is set (1st total items No). For 2nd Total Items No, Data element tag number is assigned to create check-sum when extension mode is set. If these areas are blank, check-sum will not be calculated. Let s take an example to example to these components. Let s take an order sheet as an example. In CII, you can specify maximum 2 items, for example quantity and price. Let's assume that the order sheet you got has 3 items like this: Item#1

9 -- QTY:10 -- Price: 6,700 JPY Item#2 Item#3 -- QTY: 5 -- Price: 380 JPY -- QTY: Price: 24,000 JPY In this case, the sender can specify those data as total items like this: Total item-1: QTY -->> = 27 Total item-2: Price -->> = 31,080 JPY However, you can these components in both CII header and trailer and each area has 2 TFD, #1 and #2 - So totally 4 TFDs exist. If we are using normal mode (compressed mode), we have to use 1st total items area only. And if you're using extended mode, you have to use 2nd total items area only. You can use only 1 area depending on a mode and unnecessary one will be ignored. You can use 1st total items #1 and #2 only in compressed mode. In compressed mode, above example should be like this: Message Group Header Extended mode flag -->> 0x20 or 0x53 1st total items num -#1 -->> QTY's tag 1st total items num -#2 -->> Price's tag 2nd total items num -#1 -->> Ignored 2nd total items num -#2 -->> Ignored Message Group Trailer Total items #1 -->> Total items #2 -->> You can use 2nd total items #1 and #2 only in extended mode. In extended mode, above example should be like this: Message Group Header Extended mode flag -->> 0x45 1st total items num -#1 -->> Ignored 1st total items num -#2 -->> Ignored 2nd total items num -#1 -->> QTY's tag 2nd total items num -#2 -->> Price's tag Message Group Trailer Total items #1 -->> Total items #2 -->>

10 More About Checksum The calculation is simple in the case of integer. Just add one by one and padding with zero in left side of the total. If the total number becomes more than 15 digits, you have to cut off like this: >> In the case of decimal number, it is little bit tricky. You need to remove the decimal point and add as normal integer before you calculate, like this: >> = >> If data has zero in a smallest digit of decimal, you can not ignore it. You have to calculate like this: >> = >> Refer the following data for a clear idea about Check sum which is explained with screen shots : Let's take an example of a CII file to understand more about check sum : This is a outbound CII file where a positional file is translated into a CII file using a map in the outbound CII Envelope. The tag which is expected to get a total is highlighted below in the Message Group header. In this case, translator should calculate the summery of all #015 in each message. As the compression mode is switched on in this CII message, 1st total items No will be calculated and will be put in the Message Group Trailer.

11 In the map, #015 is here, and the tag with hex value 'F'.

12 Please search the tag '0F' in the file, This output includes 5 messages. So there are 5 '0F's. Here is the data element value which has data tag as 0F in the First message Here is the data element value which has data tag as 0F in the Second message

13 Here is the data element value which has data tag as 0F in the Third message Here is the data element value which has data tag as 0F in the Fourth message

14 Here is the data element value which has data tag as 0F in the Fifth message As a result, the total of #015 should be = This calculated sum is put in Message Group Trailer as follows :

15 Message (Type12) One message is formed of a Message header, TFD area and Message trailer and is equivalent to one transaction. For Ex: one order sheet. Here is the structure of a message of Type 12 Syntax rule. Message Header Dividing-id (9=X 39 ) - Indicated dividing situation of record containing message. Record-id (D=X 44 ) - Indicated a record containing a message. Sequence No (5 digit number) - 5 digit up-count sequence number of a record containing a message. The number immediately after the Message Group Header is 1 and counts up by 1. Message Length(2 byte binary number) Indicates the total length from the front of the record containing the message to just before the message trailer. Note that the trailer itself is not included in the message length. TFD Area The TFD Area always begins with the compressed mode and changes to extended mode when an extended mode indicator appears. The data tag of a TFD can be of 1 byte or of 2 bytes whether it is compressed or extended mode. Whether a tag is data tag or control tag is determined by the first 1 byte value of the tag. When this 1 byte value is less than 240 (X F0 ), the tag is a data tag and when the value is more than or equal to 240 (X F0 ), it is a control tag. The control tag controls the TFD area mode and repeat function. Therefore, it is also called a TFD controller. In other words, a data tag or control tag (TFD controller) is the most important factor for the CII Syntax Rule and thus the CII Syntax Rule is called the tag method.

16 Here are the tables which will help you in scanning through all the components of a Message Group header, Message Group Trailer and a Message. It also gives the possible values of some of the components. Message Group Header Table

17 Message Group Trailer Table Message Table