Introduction: Heading: Detail: Summary: Transaction Set Notes. Functional Group ID=IB

Transcription

1 846 Inventory Inquiry/Advice Functional Group ID=IB Introduction: This Draft Standard for Trial Use contains the format and establishes the data contents of the Inventory Inquiry/Advice Transaction Set (846) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used in the following ways: (1) for a seller of goods and services to provide inventory information to a prospective purchaser, with no obligation to the purchaser to acquire these goods or services; (2) for a representative of a seller of goods and services to supply inventory information to that seller; (3) for one location to supply another location with inventory information; and (4) for an inquiry as to the availability of inventory with no obligation on the seller of goods and services to reserve that inventory. Heading: Pos. Seg. X12 LOL Loop Notes and No. ID Name Usage Usage Max.Use Repeat Comments 005 ISA Interchange Control Header M M GS Functional Group Header M M ST Transaction Set Header M M BIA Beginning Segment for Inventory M M 1 Inquiry/Advice 060 REF Reference Identification O PER Administrative Communications Contact O 3 LOOP ID - N N1 Name O Required N3 Address Information O N4 Geographic Location O 1 Detail: Pos. Seg. X12 LOL Loop Notes and No. ID Name Usage Usage Max.Use Repeat Comments LOOP ID - LIN LIN Item Identification M M PID Product/Item Description O Required DTM Date/Time Reference O Required 10 LOOP ID - QTY QTY Quantity O Required MEA Measurements O Required 25 Summary: Pos. Seg. X12 LOL Loop Notes and No. ID Name Usage Usage Max.Use Repeat Comments 010 CTT Transaction Totals O 1 n1 020 SE Transaction Set Trailer M M GE Functional Group Trailer M M IEA Interchange Control Trailer M M 1 Transaction Set Notes 846 In Inventory Advice - X rtf (D846X41I) 1 04/02/2007

2 1. Number of line items (CTT01) is the accumulation of number of LIN segments. If used, hash total (CTT02) is the sum of the values of the quantities (QTY02) of each QTY segment. 846 In Inventory Advice - X rtf (D846X41I) 2 04/02/2007

3 Segment: ISA Interchange Control Header Position: 005 Loop: Level: Heading Usage: Mandatory Purpose: Syntax Notes: Semantic Notes: Comments: To start and identify an interchange of zero or more functional groups and interchangerelated control segments ISA01 I01 Authorization Information Qualifier M ID 2/2 M Code to identify the type of information in the Authorization Information 00 No Authorization Information Present (No Meaningful Information in I02) ISA02 I02 Authorization Information M AN 10/10 M Information used for additional identification or authorization of the interchange sender or the data in the interchange; the type of information is set by the Authorization Information Qualifier (I01) ISA03 I03 Security Information Qualifier M ID 2/2 M Code to identify the type of information in the Security Information 00 No Security Information Present (No Meaningful Information in I04) ISA04 I04 Security Information M AN 10/10 M This is used for identifying the security information about the interchange sender or the data in the interchange; the type of information is set by the Security Information Qualifier (I03) ISA05 I05 Interchange ID Qualifier M ID 2/2 M Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified All valid standard codes are used ISA06 I06 Interchange Sender ID M AN 15/15 M Identification code published by the sender for other parties to use as the receiver ID to route data to them; the sender always codes this value in the sender ID element Sender ISA ID ISA07 I05 Interchange ID Qualifier M ID 2/2 M Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified 08 UCC EDI Communications ID (Comm ID) ISA08 I07 Interchange Receiver ID M AN 15/15 M Identification code published by the receiver of the data; When sending, it is used by the sender as their sending ID, thus other parties sending to them will use this as a receiving ID to route data to them Land 'O Lakes Receiver ISA ID For Production: DFP For Testing: DFQ ISA09 I08 Interchange Date M DT 6/6 M Date of the interchange ISA10 I09 Interchange Time M TM 4/4 M Time of the interchange ISA11 I10 Interchange Control Standards Identifier M ID 1/1 M 846 In Inventory Advice - X rtf (D846X41I) 3 04/02/2007

4 Code to identify the agency responsible for the control standard used by the message that is enclosed by the interchange header and trailer Refer to Data Element Dictionary for acceptable code values. ISA12 I11 Interchange Control Version Number M ID 5/5 M This version number covers the interchange control segments Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1997 ISA13 I12 Interchange Control Number M N0 9/9 M A control number assigned by the interchange sender ISA14 I13 Acknowledgment Requested M ID 1/1 M Code sent by the sender to request an interchange acknowledgment (TA1) 0 No Acknowledgment Requested ISA15 I14 Usage Indicator M ID 1/1 M Code to indicate whether data enclosed by this interchange envelope is test, production or information P Production Data T Test Data ISA16 I15 Component Element Separator M AN 1/1 M Type is not applicable; the component element separator is a delimiter and not a data element; this field provides the delimiter used to separate component data elements within a composite data structure; this value must be different than the data element separator and the segment terminator 846 In Inventory Advice - X rtf (D846X41I) 4 04/02/2007

5 Segment: GS Functional Group Header Position: 008 Loop: Level: Heading Usage: Mandatory Purpose: To indicate the beginning of a functional group and to provide control information Syntax Notes: Semantic Notes: 1 GS04 is the group date. 2 GS05 is the group time. 3 The data interchange control number GS06 in this header must be identical to the same data element in the associated functional group trailer, GE02. Comments: 1 A functional group of related transaction sets, within the scope of X12 standards, consists of a collection of similar transaction sets enclosed by a functional group header and a functional group trailer. GS Functional Identifier Code M ID 2/2 M Code identifying a group of application related transaction sets IB Inventory Inquiry/Advice (846) GS Application Sender's Code M AN 2/15 M Code identifying party sending transmission; codes agreed to by trading partners GS Application Receiver's Code M AN 2/15 M Code identifying party receiving transmission; codes agreed to by trading partners Land 'O Lakes GS Receiver ID For Production: DFP For Testing: DFQ GS Date M DT 8/8 M Date expressed as CCYYMMDD GS Time M TM 4/8 M Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99) GS06 28 Group Control Number M N0 1/9 M Assigned number originated and maintained by the sender GS Responsible Agency Code M ID 1/2 M Code used in conjunction with Data Element 480 to identify the issuer of the standard X Accredited Standards Committee X12 GS Version / Release / Industry Identifier Code M AN 1/12 M Code indicating the version, release, subrelease, and industry identifier of the EDI standard being used, including the GS and GE segments; if code in DE455 in GS segment is X, then in DE 480 positions 1-3 are the version number; positions 4-6 are the release and subrelease, level of the version; and positions 7-12 are the industry or trade association identifiers (optionally assigned by user); if code in DE455 in GS segment is T, then other formats are allowed Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October In Inventory Advice - X rtf (D846X41I) 5 04/02/2007

6 Segment: ST Transaction Set Header Position: 010 Loop: Level: Heading Usage: Mandatory Purpose: To indicate the start of a transaction set and to assign a control number Syntax Notes: Semantic Notes: 1 The transaction set identifier (ST01) is used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set). Comments: Notes: Land 'O Lakes Requires This Segment to Process a Transaction ST Transaction Set Identifier Code M ID 3/3 M Code uniquely identifying a Transaction Set Refer to Data Element Dictionary for acceptable code values. ST Transaction Set Control Number M AN 4/9 M Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set 846 In Inventory Advice - X rtf (D846X41I) 6 04/02/2007

7 Segment: BIA Beginning Segment for Inventory Inquiry/Advice Position: 020 Loop: Level: Heading Usage: Mandatory Purpose: To indicate the beginning of an Inventory Inquiry/Advice Transaction Set Syntax Notes: Semantic Notes: 1 BIA03 identifies the number of the inquiry/advice that is transferred. 2 BIA04 identifies the date of the inquiry/advice that is transferred. 3 BIA05 identifies the time of the inquiry/advice that is transferred. Comments: Notes: Land 'O Lakes Requires This Segment to Process a Transaction BIA Transaction Set Purpose Code M ID 2/2 M Code identifying purpose of transaction set 08 Status BIA Report Type Code M ID 2/2 M Code indicating the title or contents of a document, report or supporting item AA Agent Inventory Report BIA Reference Identification M AN 1/30 M Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier BIA Date M DT 8/8 M Date expressed as CCYYMMDD Date in BIA 04 is the date in which the data was pulled. BIA Time O TM 4/8 Used Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99) Time in BIA 05 is the time in which the data was pulled. 846 In Inventory Advice - X rtf (D846X41I) 7 04/02/2007

8 Segment: REF Reference Identification Position: 060 Loop: Level: Heading Usage: Optional 2 Purpose: To specify identifying information Syntax Notes: 1 At least one of REF02 or REF03 is required. 2 If either C04003 or C04004 is present, then the other is required. 3 If either C04005 or C04006 is present, then the other is required. Semantic Notes: 1 REF04 contains data relating to the value cited in REF02. Comments: REF Reference Identification Qualifier M ID 2/3 M Code qualifying the Reference Identification Refer to Data Element Dictionary for acceptable code values. REF Reference Identification X AN 1/30 Used Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier REF Description X AN 1/80 Used A free-form description to clarify the related data elements and their content 846 In Inventory Advice - X rtf (D846X41I) 8 04/02/2007

9 Segment: PER Administrative Communications Contact Position: 070 Loop: Level: Heading Usage: Optional Max Use: 3 Purpose: To identify a person or office to whom administrative communications should be directed Syntax Notes: 1 If either PER03 or PER04 is present, then the other is required. 2 If either PER05 or PER06 is present, then the other is required. 3 If either PER07 or PER08 is present, then the other is required. Semantic Notes: Comments: PER Contact Function Code M ID 2/2 M Code identifying the major duty or responsibility of the person or group named IC Information Contact PER02 93 Name O AN 1/60 Used Free-form name PER Communication Number Qualifier X ID 2/2 Used Code identifying the type of communication number WP Work Phone Number PER Communication Number X AN 1/80 Used Complete communications number including country or area code when applicable PER Communication Number Qualifier X ID 2/2 Used Code identifying the type of communication number EM Electronic Mail PER Communication Number X AN 1/80 Used Complete communications number including country or area code when applicable 846 In Inventory Advice - X rtf (D846X41I) 9 04/02/2007

10 Segment: N1 Name Position: 080 Loop: N1 Optional (Must Use) Level: Heading Usage: Optional (Must Use) Purpose: To identify a party by type of organization, name, and code Syntax Notes: 1 At least one of N102 or N103 is required. 2 If either N103 or N104 is present, then the other is required. Semantic Notes: Comments: 1 This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party. 2 N105 and N106 further define the type of entity in N101. Usage Notes: Land 'O Lakes requires this segment to process a transaction N Entity Identifier Code M ID 2/3 M Code identifying an organizational entity, a physical location, property or an individual WH Warehouse N Name X AN 1/60 Used Free-form name N Identification Code Qualifier X ID 1/2 Used Code designating the system/method of code structure used for Identification Code (67) 6 Plant Code N Identification Code X AN 2/80 Used Code identifying a party or other code Use 3 digit Land O' Lakes Warehouse/Branch Plant ID 846 In Inventory Advice - X rtf (D846X41I) 10 04/02/2007

11 Segment: N3 Address Information Position: 100 Loop: N1 Optional (Must Use) Level: Heading Usage: Optional Max Use: 2 Purpose: To specify the location of the named party Syntax Notes: Semantic Notes: Comments: N Address Information M AN 1/55 M Address information N Address Information O AN 1/55 Used Address information 846 In Inventory Advice - X rtf (D846X41I) 11 04/02/2007

12 Segment: N4 Geographic Location Position: 110 Loop: N1 Optional (Must Use) Level: Heading Usage: Optional Purpose: To specify the geographic place of the named party Syntax Notes: 1 If N406 is present, then N405 is required. Semantic Notes: Comments: 1 A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location. 2 N402 is required only if city name (N401) is in the U.S. or Canada. Data Eleme nt Summary N City Name O AN 2/30 Used Free-form text for city name N State or Province Code O ID 2/2 Used Code (Standard State/Province) as defined by appropriate government agency N Postal Code O ID 3/15 Used Code defining international postal zone code excluding punctuation and blanks (zip code for United States) N Country Code O ID 2/3 Used Code identifying the country N Location Qualifier X ID 1/2 Used Code identifying type of location Refer to Data Element Dictionary for acceptable code values. N Location Identifier O AN 1/30 Used Code which identifies a specific location 846 In Inventory Advice - X rtf (D846X41I) 12 04/02/2007

13 Segment: LIN Item Identification Position: 010 Loop: LIN Mandatory Level: Detail Usage: Mandatory Purpose: To specify basic item identification data Syntax Notes: 1 If either LIN04 or LIN05 is present, then the other is required. 2 If either LIN06 or LIN07 is present, then the other is required. 3 If either LIN08 or LIN09 is present, then the other is required. 4 If either LIN10 or LIN11 is present, then the other is required. 5 If either LIN12 or LIN13 is present, then the other is required. 6 If either LIN14 or LIN15 is present, then the other is required. 7 If either LIN16 or LIN17 is present, then the other is required. 8 If either LIN18 or LIN19 is present, then the other is required. 9 If either LIN20 or LIN21 is present, then the other is required. 10 If either LIN22 or LIN23 is present, then the other is required. 11 If either LIN24 or LIN25 is present, then the other is required. 12 If either LIN26 or LIN27 is present, then the other is required. 13 If either LIN28 or LIN29 is present, then the other is required. 14 If either LIN30 or LIN31 is present, then the other is required. Semantic Notes: 1 LIN01 is the line item identification Comments: 1 See the Data Dictionary for a complete list of IDs. 2 LIN02 through LIN31 provide for fifteen different product/service IDs for each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU. Notes: Land 'O Lakes Requires This Segment to Process a Transaction LIN Assigned Identification O AN 1/20 Used Alphanumeric characters assigned for differentiation within a transaction set LIN Product/Service ID Qualifier M ID 2/2 M Code identifying the type/source of the descriptive number used in Product/Service ID (234) UA SW UA -U.P.C./EAN Case Code (2-5-5) if 12 digit product item code SW - Stock Number if using 14 digit product item code LIN Product/Service ID M AN 1/48 M Identifying number for a product or service LIN Product/Service ID Qualifier X ID 2/2 Used Code identifying the type/source of the descriptive number used in Product/Service ID (234) LT Lot Number LIN Product/Service ID X AN 1/48 Used Identifying number for a product or service LIN Product/Service ID Qualifier X ID 2/2 Used Code identifying the type/source of the descriptive number used in Product/Service ID (234) UC U.P.C. Suffix (Defines Packing Variations) LIN Product/Service ID X AN 1/48 Used Identifying number for a product or service Use 2 digit Packing Variation: Regular Item 02 FID 03 FID 04 FID 846 In Inventory Advice - X rtf (D846X41I) 13 04/02/2007

14 05 International 07 International or Customer Specific Pkg 08 Within Package Giveaway 09 Promotional 12 Test Marketing of New Packaging 44 International (Pkg Var) 55 Extended Shelf Life (Frozen Butter or Cheese) 66 Aged 77 Off Grade 88 Kiel Value Added for Packaging at Copacker 99 Recall- Not for Human Consumption 846 In Inventory Advice - X rtf (D846X41I) 14 04/02/2007

15 Segment: PID Product/Item Description Position: 030 Loop: LIN Mandatory Level: Detail Usage: Optional (Must Use) Max Use: 200 Purpose: To describe a product or process in coded or free-form format Syntax Notes: 1 If PID04 is present, then PID03 is required. 2 At least one of PID04 or PID05 is required. 3 If PID07 is present, then PID03 is required. 4 If PID08 is present, then PID04 is required. 5 If PID09 is present, then PID05 is required. Semantic Notes: 1 Use PID03 to indicate the organization that publishes the code list being referred to. 2 PID04 should be used for industry-specific product description codes. 3 PID08 describes the physical characteristics of the product identified in PID04. A "Y" indicates that the specified attribute applies to this item; an "N" indicates it does not apply. Any other value is indeterminate. 4 PID09 is used to identify the language being used in PID05. Comments: 1 If PID01 equals "F", then PID05 is used. If PID01 equals "S", then PID04 is used. If PID01 equals "X", then both PID04 and PID05 are used. 2 Use PID06 when necessary to refer to the product surface or layer being described in the segment. 3 PID07 specifies the individual code list of the agency specified in PID03. Usage Notes: Land 'O Lakes requires this segment to process a transaction PID Item Description Type M ID 1/1 M Code indicating the format of a description F Free-form PID Agency Qualifier Code X ID 2/2 Used Code identifying the agency assigning the code values Refer to Data Element Dictionary for acceptable code values. PID Product Description Code X AN 1/12 Used A code from an industry code list which provides specific data about a product characteristic PID Description X AN 1/80 Used A free-form description to clarify the related data elements and their content PID Source Subqualifier O AN 1/15 Used A reference that indicates the table or text maintained by the Source Qualifier PID Yes/No Condition or Response Code O ID 1/1 Used Code indicating a Yes or No condition or response Yes = On Hold No = Off Hold N Y No Yes 846 In Inventory Advice - X rtf (D846X41I) 15 04/02/2007

16 Segment: DTM Date/Time Reference Position: 100 Loop: LIN Mandatory Level: Detail Usage: Optional (Must Use) 0 Purpose: To specify pertinent dates and times Syntax Notes: 1 At least one of DTM02 DTM03 or DTM05 is required. 2 If DTM04 is present, then DTM03 is required. 3 If either DTM05 or DTM06 is present, then the other is required. Semantic Notes: Comments: Usage Notes: Land 'O Lakes requires this segment to process a transaction DTM Date/Time Qualifier M ID 3/3 M Code specifying type of date or time, or both date and time 036 Expiration Date coverage expires DTM Date X DT 8/8 Used Date expressed as CCYYMMDD 846 In Inventory Advice - X rtf (D846X41I) 16 04/02/2007

17 Segment: QTY Quantity Position: 320 Loop: QTY Optional (Must Use) Level: Detail Usage: Optional (Must Use) Purpose: To specify quantity information Syntax Notes: 1 At least one of QTY02 or QTY04 is required. 2 Only one of QTY02 or QTY04 may be present. Semantic Notes: 1 QTY04 is used when the quantity is non-numeric. Comments: Usage Notes: Land 'O Lakes requires this segment to process a transaction QTY Quantity Qualifier M ID 2/2 M Code specifying the type of quantity 17 Quantity on Hand QTY Quantity X R 1/15 Used Numeric value of quantity QTY03 C001 Composite Unit of Measure O Us ed To identify a composite unit of measure (See Figures Appendix for examples of use) C Unit or Basis for Measurement Code M ID 2/2 M Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken BG Bag BL Block BR BX CA CN DR EA GA LB TE Barrel Box Case Can Drum Each Gallon Pound Tote 846 In Inventory Advice - X rtf (D846X41I) 17 04/02/2007

18 Segment: MEA Measurements Position: 340 Loop: QTY Optional (Must Use) Level: Detail Usage: Optional (Must Use) Max Use: 25 Purpose: To specify physical measurements or counts, including dimensions, tolerances, variances, and weights (See Figures Appendix for example of use of C001) Syntax Notes: 1 At least one of MEA03 MEA05 MEA06 or MEA08 is required. 2 If MEA05 is present, then MEA04 is required. 3 If MEA06 is present, then MEA04 is required. 4 If MEA07 is present, then at least one of MEA03 MEA05 or MEA06 is required. 5 Only one of MEA08 or MEA03 may be present. Semantic Notes: 1 MEA04 defines the unit of measure for MEA03, MEA05, and MEA06. Comments: 1 When citing dimensional tolerances, any measurement requiring a sign (+ or -), or any measurement where a positive (+) value cannot be assumed, use MEA05 as the negative (-) value and MEA06 as the positive (+) value. Usage Notes: Land 'O Lakes requires this segment to process a transaction MEA Measurement Qualifier O ID 1/3 Used Code identifying a specific product or process characteristic to which a measurement applies N Actual Net Weight MEA Measurement Value X R 1/20 Must Use The value of the measurement MEA04 C001 Composite Unit of Measure X Us ed To identify a composite unit of measure (See Figures Appendix for examples of use) C Unit or Basis for Measurement Code M ID 2/2 M Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken LB Pound 846 In Inventory Advice - X rtf (D846X41I) 18 04/02/2007

19 Segment: CTT Transaction Totals Position: 010 Loop: Level: Summary Usage: Optional Purpose: To transmit a hash total for a specific element in the transaction set Syntax Notes: 1 If either CTT03 or CTT04 is present, then the other is required. 2 If either CTT05 or CTT06 is present, then the other is required. Semantic Notes: Comments: 1 This segment is intended to provide hash totals to validate transaction completeness and correctness. CTT Number of Line Items M N0 1/6 M Total number of line items in the transaction set 846 In Inventory Advice - X rtf (D846X41I) 19 04/02/2007

20 Segment: SE Transaction Set Trailer Position: 020 Loop: Level: Summary Usage: Mandatory Purpose: Syntax Notes: Semantic Notes: To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments) Comments: 1 SE is the last segment of each transaction set. Notes: Land 'O Lakes Requires This Segment to Process a Transaction SE01 96 Number of Included Segments M N0 1/10 M Total number of segments included in a transaction set including ST and SE segments SE Transaction Set Control Number M AN 4/9 M Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set 846 In Inventory Advice - X rtf (D846X41I) 20 04/02/2007

21 Segment: GE Functional Group Trailer Position: 030 Loop: Level: Summary Usage: Mandatory Purpose: To indicate the end of a functional group and to provide control information Syntax Notes: Semantic Notes: 1 The data interchange control number GE02 in this trailer must be identical to the same data element in the associated functional group header, GS06. Comments: 1 The use of identical data interchange control numbers in the associated functional group header and trailer is designed to maximize functional group integrity. The control number is the same as that used in the corresponding header. GE01 97 Number of Tr ansaction Sets Included M N0 1/6 M Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element GE02 28 Group Control Number M N0 1/9 M Assigned number originated and maintained by the sender 846 In Inventory Advice - X rtf (D846X41I) 21 04/02/2007

22 Segment: IEA Interchange Control Trailer Position: 040 Loop: Level: Summary Usage: Mandatory Purpose: Syntax Notes: Semantic Notes: Comments: To define the end of an interchange of zero or more functional groups and interchangerelated control segments IEA01 I16 Number of Included Functional Groups M N0 1/5 M A count of the number of functional groups included in an interchange IEA02 I12 Interchange Control Number M N0 9/9 M A control number assigned by the interchange sender 846 In Inventory Advice - X rtf (D846X41I) 22 04/02/2007