Engineering Data Support

Appendix H. EMI format

This appendix describes the generalized interface data set from which the CEDS product expects to extract bill of material information. The overview of the purpose and structure of the file is followed by a detailed description of the layout of each record type.

Overview

This appendix describes in detail the record layout of all the record structures in the interface data set and also separately lists all of the data elements used within the file.

The interface data set is a VSAM key sequenced data set (KSDS). The data set is made up of a fixed length of 170 byte records with an imbedded key of 80 bytes. All of the data records have a 10 byte reserved field in the key for future expansion and the also have a reserved field in their data portion (the amount of reserved space in the data portion varies between record types).

Header data
Trailer data
Assembly data
Component data
Engineering change data
Drawing data

Each of these groups and the records that comprise them will be discussed in detail later in this appendix.

Purpose

The interface file will be used to transfer information from a computer aided design system to TFG2000. As discussed earlier in this manual, this information could have come directly from Computer Aided Design system or from a Data Repository, such as the Data Communication Service's Consolidated Design File.

General record format

The records of the interface data set consist of 170 byte records with an imbedded key of 80 bytes. The key of all of the record type is defined the same way and consists of the following fields:

Date: The date the interface data set was produced. This date is placed in the key so the results of different runs of the BOM extraction process can reside in the same data set and be differentiated.
Time: The time the interface data set was produced (down to .01s). This time is placed in the key so the results of different runs of the BOM extraction process can reside in the same data set and be differentiated.
Engineering Change Level: The EC level that the record corresponds to
Item Number: The item or part number the drawing represents
Component Number: The component
Reserved: Reserved for future use
Record Sequence: A record sequence number. This field is used to control the order in which the records physically reside in the VSAM KSDS. Also, the last byte of this field is used to differentiate duplicate components in the same process operation. It can also be used to accommodate multiple process IDs, multiple sub/opt insertions and multiple EC history records.
Record Group: Identifies the group, such as assembly, component, or drawing, this record belongs to. Each record has a record group and record type.
Record Type: Identifies the type of record, within a group, a particular record belongs to. For example, there are EC identifier and EC history records within the engineering change group.

Also, a data portion follows the key of each record. The data portion in each record will be different for each type of record.

Record groups

Header data

The Header Data Record in the only record type defined in the Header Data group. One Header Data Record is in every interface data set sent to TFG2000. The Header Data Record has spaces in its item number, component number and engineering change level fields. Its record group field contains an "H" and its record type field contains a "D". The record sequence field contains "0100".

The data portion of the Header Data Record contains an ID field, the date the file was created, the time the file was created, the node ID of the creator and the user ID of the creator. This record also tells how many records are in the file.

                                      key
          *іііііііііііііііііііііііііііііііііііііііііііііііііііііі*
         |                                                        T|
                                                       R    S   G Y
         date time   EC      item         component    E    E   R P
                    number   number         number     S    Q   P E
        +іііі+іііі+ііііііі+іііііііііііііі+ііііііііііі+іііі+іііі+і+і+іііііі*
        |date|time|       |              |           |    |0100|H|D|IBMEMI|
        +іііі+іііі+ііііііі+іііііііііііііі+ііііііііііі+іііі+іііі+і+і+іііііі*
 length = 6    8     10       20             20       10    4   1 1   6

 
 
 
        T    D       N      U      R
        I    A       O      S      E
        M    T       D      E      C
        E    E       E      R      S
     +іііі+ііііі+ііііііі+ііііііі+ііііі+ііііііііііі*
     |time|date | nodeid|userid |#recs| reserved
     +іііі+ііііі+ііііііі+ііііііі+ііііі+ііііііііііі*
 
length = 8   6      8       8      6      48

Header ID: IBMEMI (IBM Engineering/Manufacturing Interface)
Header Time: Time the interface file was created
Header Date: Date that the interface file was created
Header Node ID: Node ID where the file was created
Header User ID: User ID that created the interface file
Header Recs: Number of records in this interface file
Reserved: Reserved for future use

Trailer data

The Trailer Data Record is the only record type defined in the Trailer Data group. One Trailer Data Record is similar to the Header Data Record except for its record group field. This field has a "T" instead of an "H". The Trailer Data Record has "9s" in its item number, component number and engineering change level fields. Its record group field contains a "T" and its record type field contains a "D". The record sequence field contains "0900".

The data portion of the Trailer Data Record contains an ID field, the date the file was created, the time the file was created, the node ID of the creator and the user ID of the creator. This record also tells how many records are in the file.

 
                                   key
         *ііііііііііііііііііііііііііііііііііііііііііііііііі*
        |                                                   T|
                                                 R    S   G Y
        date time  EC      item      component   E    E   R P
                  number   number     number     S    Q   P E
       +іііі+іііі+іііііі+ііііііііііі+іііііііііі+іііі+іііі+і+і+ііііііі*
       |date|time|999999|99999999999|9999999999|    |0900|T|D|IBMEMI|  
       +іііі+іііі+іііііі+ііііііііііі+іііііііііі+іііі+іііі+і+і+ііііііі*
length = 6    8     10       20         20       10    4   1 1   6

 
 
 
        T    D       N      U      R
        I    A       O      S      E
        M    T       D      E      C
        E    E       E      R      S
     +іііі+ііііі+ііііііі+ііііііі+ііііі+ііііііііііі*
     |time|date | nodeid|userid |#recs| reserved
     +іііі+ііііі+ііііііі+ііііііі+ііііі+ііііііііііі*
 
length = 8   6      8       8      6      48

Trailer ID: IBMEMI (IBM Engineering/Manufacturing Interface)
Trailer Time: Time the interface file was created
Trailer Date: Date that the interface file was created
Trailer Node ID: Node ID where the file was created
Trailer User ID: User Id that created the interface file
Trailer Recs: Number of records in this interface file
Reserved: Reserved for future use

Assembly data

The Assembly Data Group contains two record type definitions: the Assembly Header Record and the Assembly Process Record. Both records use the standard key definition. The component field in the key is blank for both kinds of assembly records because the records do not refer to a specific component. The data portion in the item record contains the item number, the item description and the item type. The assembly process record's data portion contains the routing number and the routing type. The format of the Assembly Header Record is as follows:

 
                                  key
         *ііііііііііііііііііііііііііііііііііііііііііііііііі*
        |                                                   T|
                                                 R    S   G Y
        date time   EC      item     component   E    E   R P
                   number   number    number     S    Q   P E
       +іііі+іііі+іііііі+ііііііііііі+іііііііііі+іііі+іііі+і+і*
       |date|time|EC num| item num  | comp num |    |0200|A|H|  
       +іііі+іііі+іііііі+ііііііііііі+іііііііііі+іііі+іііі+і+і*
length = 6    8     10       20        20        10   4   1 1

 
               I                 I
               T         D       T
               E         E       Y
               M         S       P
               #         C       E
             +іііііі+ііііііііі+іііі+іііі*
          |item #|item desc|type|
             +іііііі+ііііііііі+іііі+іііі*
     length = 20       30       1     39

The format of the Assembly Process Record is as follows:

 
                                  key
         *ііііііііііііііііііііііііііііііііііііііііііііііііі*
        |                                                   T|
                                                 R    S   G Y
        date time   EC      item     component   E    E   R P
                   number   number    number     S    Q   P E
       +іііі+іііі+іііііі+ііііііііііі+іііііііііі+іііі+іііі+і+і*
       |date|time|EC num| item num  | comp num |    |0300|A|P|  
       +іііі+іііі+іііііі+ііііііііііі+іііііііііі+іііі+іііі+і+і*
length = 6    8     10       20        20        10   4   1 1

 
 
                  R
                  O
            U     U
            O     T   ROUT
            M     #   TYPE
          *іііі+ііііі+іііі+ііііі*
     |uom |rout#|type|
          *іііі+ііііі+іііі+ііііі*
 length =    2   19    3    66

Engineering change data

The Engineering Change Data Group contains two record type definitions: the Engineering Change Identifier Record and the Engineering Change History Record. The Engineering Change Identifier Record contains all the information pertaining to an engineering change.

Since an engineering change is not usually specific for a component, the Engineering Change Identifier Record contains blanks in its component field the way assembly records do. The Engineering Change Identifier Record uses the standard key definition and contains an "E" in the group field and an "I" in the record field of the key. The data portion of the Engineering Change Identifier Record contains the engineering change number, the responsible engineer, the EC status code, the EC reason code and the effective date.

The data portion of the Engineering Change History record contains the previous engineering change and has a type field of "H". The format of the Engineering Change Identifier Record is:

 
                                   key
          *ііііііііііііііііііііііііііііііііііііііііііііііііі*
         |                                                   T|
                                                  R    S   G Y
         date time   EC      item     component   E    E   R P
                    number   number    number     S    Q   P E
        +іііі+іііі+іііііі+ііііііііііі+іііііііііі+іііі+іііі+і+і*
        |date|time|EC num| item num  | comp num |    |0400|E|I|  
        +іііі+іііі+іііііі+ііііііііііі+іііііііііі+іііі+іііі+і+і*
 length = 6    8     10       20        20        10   4   1 1

                                         EC
                EC      RESP      EC     REASON  EFF
                NUM     ENG       STATUS CODE    DATE
               *ііііііі+ііііііііі+іііііі+ііііііі+іііі+ііііііі*
            |ec num |resp eng |status|reason |date|
               *ііііііі+ііііііііі+іііііі+ііііііі+іііі+ііііііі*
      length =    10       10       2      2       8     58

EC Number: Engineering change level
Responsible Eng: Engineer responsible for this EC
EC Status Code: Distinguishes between parts required for regular production and those maintained for other purposes
EC Reason Code: Code indicating the reason for the engineering change
Earliest Eff Date: Date on which the records with the given EC become effective for production
Reserved: Reserved for future use

The format of the Engineering Change History Record is:

 
 
                                   key
          *іііііііііііііііііііііііііііііііііііііііііііііііііі*
         |                                                   T|
                                                  R    S   G Y
         date time   EC      item     component   E    E   R P  PREVIOUS
                    number   number    number     S    Q   P E  EC
        +іііі+іііі+іііііі+ііііііііііі+іііііііііі+іііі+іііі+і+і+іііііііііііі+-
        |date|time|EC num| item num  | comp num |    |0500|E|H|            |
        +іііі+іііі+іііііі+ііііііііііі+іііііііііі+іііі+іііі+і+і+іііііііііііі*-
 length = 6    8     10       20        20        10   4   1 1     10      71

Previous EC: Engineering change that immediately preceded the EC shown in the key
Reserved: Reserved for future use

Drawing data

The Drawing Data Group has one different record type defined in it, the Drawing Identifier Record. The Drawing Identifier Record uses the standard key definition with a group field value of "D" and a record Type value of "I". The data portion of the record consists of the following fields:

Drawing Number: 20 character identifier
Drawing Size: Values A thru E
Reserved: Reserved for future use

 
                                       key
         *іііііііііііііііііііііііііііііііііііііііііііііііі*
        |                                                  T|
                                                R    S   G Y
        date time   EC     item      component  E    E   R P  DRAW   DRAW
                   number  number     number    S    Q   P E  NUM    SIZE
       +іііі+іііі+іііііі+ііііііііііі+іііііііііі+іііі+іііі+і+і+ііііі+ііііі+*
       |date|time|EC num| item num  | comp num |    |0600|D|I|     |     |
 
       +іііі+іііі+іііііі+ііііііііііі+іііііііііі+іііі+іііі+і+і+ііііі+ііііі+*
length = 6    8     10       20        20       10    4   1 1  20     1  69

Component data

The Component Data Group has two different record types defined in it: the Component Header Record and the Component Reference Record. The Component Header Record uses the standard key definition with a group field value of "C" and a record Type value of "H". The data portion of the record consists of the following fields:

Component Number: Component number
Component Description: Brief description of the component
Quantity/Assembly: Quantity of this component per assembly
Unit of Measure: Units used for the Quantity/Assembly
Engineering Planning Code: Special conditions of usage in an application
Engineering BOM Status Code: Indicates the status of a BOM (development, pre-release, etc.)
Component Sequence Number: Unique key to identify duplicate components in the same process operation
Effective Date: Date on which the records with a given EC number become effective for production, can be different from, but not later than the earliest effective date
Item Type: Type of component (i.e. assembly, sub-assembly, part etc.)
Manufacturing Planning Code: Bulk or As Required
Reserved: Reserved for future use

The Component Reference Record's data portion consists of the following fields:

Reference Item: Used with substitutes and optionals
Reference Type: Inverse of engineering planning code

The format of the Component Header Record is:

 
 
                                              key
         *іііііііііііііііііііііііііііііііііііііііііііііііі*
        |                                                  T|
                                                 R   S   G Y
        date time   EC     item      component   E   E   R P
                   number  number      number    S   Q   P E
       +іііі+іііі+іііііі+іііііііііі+іііііііііі+іііі+іііі+і+і*
       |date|time|EC num| item num | comp num |    |0700|C|H| 
       +іііі+іііі+іііііі+іііііііііі+іііііііііі+іііі+іііі+і+і*
length = 6    8     10       20        20       10    4  1 1

                 COMP                     UNIT   ENG   BOM                MAN.
        COMP     SEQ   COMP       QUANT/  OF     PLAN  STAT EFFECT  ITEM  PLAN
        NUM      NUM   DESC       ASSEM   MEAS   CODE  CODE DATE    TYPE  CODE
       +іііііііі+іііі+ііііііііііі+ііііііі+ііііі+іііііі+іііі+іііііі+ііііі+ііііі+іі*
    |        |    |           |       |     |      |    |      |     |     |
       +іііііііі+іііі+ііііііііііі+ііііііі+ііііі+іііііі+іііі+іііііі+ііііі+ііііі+іі*
  length = 20    5      30         13     2      1     1     8      1      1    7

 
                                  key
         *ііііііііііііііііііііііііііііііііііііііііііііііііі*
        |                                                   T|
                                                 R    S   G Y
        date time   EC      item     component   E    E   R P
                   number   number    number     S    Q   P E
       +іііі+іііі+іііііі+ііііііііііі+іііііііііі+іііі+іііі+і+і*
       |date|time|EC num| item num  | comp num |    |0800|C|R|  
       +іііі+іііі+іііііі+ііііііііііі+іііііііііі+іііі+іііі+і+і*
length = 6    8     10       20        20        10   4   1 1

 
 
                 REF
         REF     ITEM
         ITEM    TYPE
        +ііііііі+ііііііііі+ііііі*
     |       |         |
        +ііііііі+ііііііііі+ііііі*
 length = 20        1        69

Data elements used in the Interface File

The list includes all data elements used in the interface data set records. For each element, its name, where it is derived from, its standard name, data type, length and notes on its composition and usage are given.

Data Element Source Std Name Type Len Notes/Usage
Item Number drawing item_no A/N 20 Padded with blanks. Left justified. No imbedded blanks.
A generic identifier comprised of up to 20 characters. Implies it represents an assembly or sub-assembly.
Component Number drawing comp_no A/N 20 Padded with blanks. Left justified. No imbedded blanks. A generic identifier comprised of up to 20 characters. It is implied that it represents a detailed part of an assembly or sub-assembly and can be a sub-assembly.
Item Description drawing item_desc text 30 Free form text.
Information which will help to describe the item to which it refers.
Item Type user item_type A/N 1 Defaults to a "2" in an assembly record. Defaults to a "4" in the component record unless specified by the ADDP keyword. In this case, it is assigned a "5".

1
Final Assembly - An end product, or second order product composed of one or more feature assemblies or sub-assemblies.

2
Sub-Assembly - A part number supported by a bill of material which may be assembled as an entity. The sub-assembly is part of the base end product.

3
Feature Assembly - A part number supported by a bill of material which may be assembled as an entity. The assembly is an optional feature of the end product.

4
Detail Part - A part which is used in an assembly or assemblies which is not supported by a bill of material.

5
Reference Material (factory) - A reference document used in the manufacture of the product or assembly. This reference item is the type that would normally be found on an assembly drawing.

6
Reference Material (shipped) - A reference document, such as a set up manual which is shipped with the product. This reference item would not normally be found on an assembly drawing.

7
Group B/M - A group of parts supported by a Bill of Material, but which cannot be assembled as an entity. Examples are packing material, hook-up cables and parts not added to the end product until customer delivery, such as decorative wheel covers.

Unit of Measure user unit_meas A/N 2 Defaults to each.
Identifies the measurements by which items are purchased, used, priced and sold (feet, gallons, pair, each etc.).
Data Element Source Std Name Type Len Notes/Usage
Routing Number user rout_no A/N 19 Padded with blanks. Left justified. No imbedded blanks.
Identifies the process routing. It can represent the part number or it can represent an enterprise definable item that specifies a routing process.
Routing Type user rout_type A/N 3 Padded with blanks. Left justified. No imbedded blanks.
Identifies a specific kind of routing (such as normal build, pilot build etc.) also specifies alternate multiple routings.
EC Number user chg_no A/N 3 Always or never there.
The item identifier of the Engineering Change.
Responsible Eng user resp_eng A/N 10 The identifier of the person responsible for this Engineering Change.
Earliest Eff Date user eff_date A/N 8 Date Format = YYMMDD
The date on which the records with a given EC number become effective for production.
EC Status Code user chg_stat A/N 2 Blanks allowed.
EC Reason Code user chg_reas A/N 2 Blanks allowed.
Component Sequence Number drawing comp_seq num 5 Blanks allowed.
Provides a unique key to identify duplicate components in the same process operation.
Drawing Number user draw_no A/N 20 Blanks allowed
Item identifier for a drawing.
Drawing Size user draw_size A 1 Values = A through F
Indicates what size a particular drawing is.
Component Description drawing comp_desc text 30 Free format.
Descriptive text to help identify a component or its use.
Engineering Planning Code user eng_plng A 1

S
Substitute
F
Substitute available
O
Option
T
Option available
R
Reference
M
Remove
Note: Engineering Plan code of "R" or "S" is ignored by the CEDS Load program. Component records with these codes will not be processed.

Reference Item Type system ref_type A 1 Inverse of engineering planning code.

S
Substitute
F
Substitute available
O
Option
T
Option available

Only used with substitute and optionals. Indicates the relationship between the referenced and referencing items. For example, if a part has an engineering planning code that indicates a substitute part, the substitute part would have a reference item type indicating that substitute part.
Reference item user ref_item A 20 Padded with blanks. Left justified. No imbedded blanks.
Only used with substitute and optionals. Indicates this item was referenced by another item as being a substitute or optional item.
Manufacturing Planning Code drawing mp_code A 1

J
Note: Manufacturing Plan Code of "J" is ignored by the CEDS Load program. Component records with this code are not processed.

Specifies that the Bulk of As Required keywords were used.
Quantity per Assembly drawing qty_assm DEC 13 Zoned decimal.
Indicates the required quantity of a certain component in an assembly in zoned numeric format: 13,5. That is, 13 digits, five of which are assumed to be right of the decimal point.
Component Effective Date user comp_date A/N 8 Date Format = YYMMDD
The date on which the records with a given EC number become effective for production. Can be different from, but not later than, the earliest effective date.
EC BOM Status Code user bom_stat A/N 1 Blanks allowed. Indicates the status of a BOM (e.g. development, pre-release etc.).
Header ID system head_ID A 6 Will always be IBMEMI (IBM Engineering Manufacturing Interface).
Indicates this data set is an IBM Engineering/Manufacturing Interface data set.
Header Date system head_date A/N 8 Format = YYMMDD
Indicates the date that this data was produced.
Header Time system head_time A/N 6 Format = HHMMSS
Indicates the time that this data was produced.
Header Node ID user head_node A/N 8 Creation Node ID
Indicates the node ID where this interface data set was produced.
Header User ID user head_user A/N 8 Creation User ID
Indicates the user ID that produced this interface data set.
Header Recs system head_recs NUM 6 Number of records written.
Trailer ID system trl_ID A 6 Will always be IBMEMI (IBM Engineering Manufacturing Interface).
Indicates this data set is an IBM Engineering/Manufacturing Interface data set.
Trailer Date system trl_date A/N 8 Format = YYMMDD
Indicates the date this data was produced.
Trailer Time system trl_time A/N 6 Format = HHMMSS
Indicates the time this data was produced.
Trailer Node ID user trl_node A/N 8 Creation Node ID
Indicates the node ID where this interface data set was produced.
Trailer User ID user trl_user A/N 8 Creation User ID
Indicates the user ID that produced this interface data set.
Trailer Recs system trl_recs NUM 6 Number of records written.

Data Element	Source	Std Name	Type	Len	Notes/Usage
Item Number	drawing	item_no	A/N	20	Padded with blanks. Left justified. No imbedded blanks. A generic identifier comprised of up to 20 characters. Implies it represents an assembly or sub-assembly.
Component Number	drawing	comp_no	A/N	20	Padded with blanks. Left justified. No imbedded blanks. A generic identifier comprised of up to 20 characters. It is implied that it represents a detailed part of an assembly or sub-assembly and can be a sub-assembly.
Item Description	drawing	item_desc	text	30	Free form text. Information which will help to describe the item to which it refers.
Item Type	user	item_type	A/N	1	Defaults to a "2" in an assembly record. Defaults to a "4" in the component record unless specified by the ADDP keyword. In this case, it is assigned a "5".
					1 Final Assembly - An end product, or second order product composed of one or more feature assemblies or sub-assemblies.
					2 Sub-Assembly - A part number supported by a bill of material which may be assembled as an entity. The sub-assembly is part of the base end product.
					3 Feature Assembly - A part number supported by a bill of material which may be assembled as an entity. The assembly is an optional feature of the end product.
					4 Detail Part - A part which is used in an assembly or assemblies which is not supported by a bill of material.
					5 Reference Material (factory) - A reference document used in the manufacture of the product or assembly. This reference item is the type that would normally be found on an assembly drawing.
					6 Reference Material (shipped) - A reference document, such as a set up manual which is shipped with the product. This reference item would not normally be found on an assembly drawing.
					7 Group B/M - A group of parts supported by a Bill of Material, but which cannot be assembled as an entity. Examples are packing material, hook-up cables and parts not added to the end product until customer delivery, such as decorative wheel covers.
Unit of Measure	user	unit_meas	A/N	2	Defaults to each. Identifies the measurements by which items are purchased, used, priced and sold (feet, gallons, pair, each etc.).
Data Element	Source	Std Name	Type	Len	Notes/Usage
Routing Number	user	rout_no	A/N	19	Padded with blanks. Left justified. No imbedded blanks. Identifies the process routing. It can represent the part number or it can represent an enterprise definable item that specifies a routing process.
Routing Type	user	rout_type	A/N	3	Padded with blanks. Left justified. No imbedded blanks. Identifies a specific kind of routing (such as normal build, pilot build etc.) also specifies alternate multiple routings.
EC Number	user	chg_no	A/N	3	Always or never there. The item identifier of the Engineering Change.
Responsible Eng	user	resp_eng	A/N	10	The identifier of the person responsible for this Engineering Change.
Earliest Eff Date	user	eff_date	A/N	8	Date Format = YYMMDD The date on which the records with a given EC number become effective for production.
EC Status Code	user	chg_stat	A/N	2	Blanks allowed.
EC Reason Code	user	chg_reas	A/N	2	Blanks allowed.
Component Sequence Number	drawing	comp_seq	num	5	Blanks allowed. Provides a unique key to identify duplicate components in the same process operation.
Drawing Number	user	draw_no	A/N	20	Blanks allowed Item identifier for a drawing.
Drawing Size	user	draw_size	A	1	Values = A through F Indicates what size a particular drawing is.
Component Description	drawing	comp_desc	text	30	Free format. Descriptive text to help identify a component or its use.
Engineering Planning Code	user	eng_plng	A	1	S Substitute F Substitute available O Option T Option available R Reference M Remove Note: Engineering Plan code of "R" or "S" is ignored by the CEDS Load program. Component records with these codes will not be processed.
Reference Item Type	system	ref_type	A	1	Inverse of engineering planning code. S Substitute F Substitute available O Option T Option available Only used with substitute and optionals. Indicates the relationship between the referenced and referencing items. For example, if a part has an engineering planning code that indicates a substitute part, the substitute part would have a reference item type indicating that substitute part.
Reference item	user	ref_item	A	20	Padded with blanks. Left justified. No imbedded blanks. Only used with substitute and optionals. Indicates this item was referenced by another item as being a substitute or optional item.
Manufacturing Planning Code	drawing	mp_code	A	1	J Note: Manufacturing Plan Code of "J" is ignored by the CEDS Load program. Component records with this code are not processed. Specifies that the Bulk of As Required keywords were used.
Quantity per Assembly	drawing	qty_assm	DEC	13	Zoned decimal. Indicates the required quantity of a certain component in an assembly in zoned numeric format: 13,5. That is, 13 digits, five of which are assumed to be right of the decimal point.
Component Effective Date	user	comp_date	A/N	8	Date Format = YYMMDD The date on which the records with a given EC number become effective for production. Can be different from, but not later than, the earliest effective date.
EC BOM Status Code	user	bom_stat	A/N	1	Blanks allowed. Indicates the status of a BOM (e.g. development, pre-release etc.).
Header ID	system	head_ID	A	6	Will always be IBMEMI (IBM Engineering Manufacturing Interface). Indicates this data set is an IBM Engineering/Manufacturing Interface data set.
Header Date	system	head_date	A/N	8	Format = YYMMDD Indicates the date that this data was produced.
Header Time	system	head_time	A/N	6	Format = HHMMSS Indicates the time that this data was produced.
Header Node ID	user	head_node	A/N	8	Creation Node ID Indicates the node ID where this interface data set was produced.
Header User ID	user	head_user	A/N	8	Creation User ID Indicates the user ID that produced this interface data set.
Header Recs	system	head_recs	NUM	6	Number of records written.
Trailer ID	system	trl_ID	A	6	Will always be IBMEMI (IBM Engineering Manufacturing Interface). Indicates this data set is an IBM Engineering/Manufacturing Interface data set.
Trailer Date	system	trl_date	A/N	8	Format = YYMMDD Indicates the date this data was produced.
Trailer Time	system	trl_time	A/N	6	Format = HHMMSS Indicates the time this data was produced.
Trailer Node ID	user	trl_node	A/N	8	Creation Node ID Indicates the node ID where this interface data set was produced.
Trailer User ID	user	trl_user	A/N	8	Creation User ID Indicates the user ID that produced this interface data set.
Trailer Recs	system	trl_recs	NUM	6	Number of records written.

[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]