Gentex EDI 850 (Purchase Order) Specification Document

Transcription

SPECIFICATION AND BUSINESSPROCESS DOCUMENTGentex CorporationOutbound Purchase Order(EDI 850/PO)Creation DateApril 1, 2012Last Updated:November 14th, 2018Document Ref:ANSI X12 Version 004010 Reference GuideVersion:1.6

Document ControlChange Record3DateVersionChange July-131.31-Nov-131.43-Nov-161.513-Nov-181.6No Previous DocumentTransferred existing document to the standardformat. Updated requirements for the N1ST.Updated the business requirements.Added UOM Codes, updated BEG02 segmentname to Purchase Order Type, updated/addedcomments for clarification on several segmentsUpdated dock door numbers for Centennial Eastand West ship to locationsAdded Drop Ship EDI location and “Cake” to UOMlistAdded NRB1 EDI Location and RRB Location to850 ListAdded NRB10 EDI LocationReviewersPositionGentex Functional LeadGentex EDI LeadGentex EDI CoordinatorGentex Purchasing Systems AnalystGentex Outbound EDI 850 (Purchase Order) Specifications and Business Process RulesDocument Controlii

ContentsDocument Control . iiIntroduction . 1Business Rules and Requirements . 1EDI levels and Segments . 2Segments/Elements Usage . 4Appendix: Sample 850. 14Gentex Outbound EDI 850 (Purchase Order) Specifications and Business Process RulesDocument Controliii

IntroductionThe purpose of this document is to provide the details on policies and procedures for theoutbound EDI process of Purchase order documents (850) as per Gentex’s current process.Any questions or concerns regarding EDI 850s at Gentex can be addressed directly bycontacting us at edi@gentex.com.Business Rules and Requirements Gentex will run the 850 documents generation program every 30 minutes and thesupplier should get the EDI documents within 40 minutes from when an order is approvedat Gentex. The Purchase order numbers on Standard POs will be unique on each file and with arevision number of ‘0’ , where as Releases will have common PO numbers and lines withdifferent release numbers across different EDI files. A release number should be greaterthan 0. Suppliers should ensure that they respond to our 850 document with a 997 (FunctionalAcknowledgement) within 5 minutes of receipt of our 850 document and an 855 within 24hours or less depending on the lead time between the Supplier and Gentex. If there is a disruption of the normal EDI 850 due to any reason from Gentex then thesuppliers are advised to use the Gentex Supplier portal to reconcile their orderboard to thatof Gentex Purchase Orders. However in order to avoid duplications the suppliers areadvised not to manually enter Orders from the Portal to their Order management systemsunless Gentex has informed them that they will not be sending those files after thedowntime. If an 850 file needs to be retransmitted, then Gentex can do so at Suppliers request. Only the Original Document (Standard Purchase Order or Release) will be communicatedon the EDI 850. Later revisions of the purchase orders are communicated through e-mailsince Gentex does not generate and communicate 860’s at this time.Processing StandardGentex uses ANSI X12 Version 004010 for the EDI 850.Communication InformationVAN - CovisintProduction Sender/Receiver ID – 01:065855363SUPProcessing TimesThe EDI 850 will be communicated within 40 minutes of an order being approved.Suppliers are expected to send a 997 within 5 minutes of receipt of the 850s.Suppliers are also required to send an 855 in under 24 hours after the receipt of the 850 file.Gentex Outbound EDI 850 (Purchase Order) Specifications and Business Process RulesIntroduction1 of 14

EDI levels and SegmentsNote: Please ensure you are referring to the latest version of this Guide from our supplier websitehttp://www.gentex.com Corporate Supplier Information.This document provides the format and establishes the data contents of the Purchase Order Transaction Set (850)for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be usedto provide for customary and established business and industry practice relative to the placement of purchaseorders for goods and services. This transaction will not be used to convey purchase order changes.All information in this document is subject to change at the discretion of Gentex Corporation. The users of thisdocument are advised to verify that they have the latest copy of this document from the Gentex Supplier website(as indicated above).Seg.IDHeader LevelSTBEGPERN1NameTransaction Set HeaderBeginning Segment for Purchase OrderCommunications peatDetail Item LevelPO1N1Baseline Item DataNameDetail Shipment LevelSCHLine Item ScheduleSummary SegmentsCTTSETransaction TotalsTransaction Set TrailerGentex Outbound EDI 850 (Purchase Order) Specifications and Business Process RulesEDI levels and Segments2 of 14

NNot UsedOOptionalCommentThe presence of this is dependent onthe presence of another itemThis data segment should be includedin all transactions.If this datasegment is missing, a 997 will be sentindicating the document as rejected.Note some data segments may bemarked as mandatory in the loop ofdata segments that are optional. Ifyou choose to provide these optionalsegments, the mandatory segmentsassociated with them must also beprovided.This field is not mapped at Gentexcurrently. We do not have thecapability to process this datacurrently and will not look at this dataat this point in time. Suppliers can,however, send this data – it will justbe ignored.This data is completely optional. Ifyou send it we can process and look atthis data.Gentex Outbound EDI 850 (Purchase Order) Specifications and Business Process RulesEDI levels and Segments3 of 14

Segments/Elements UsageST Transaction set HeaderSegment:Level:Usage:Max Use:Purpose:Syntax:Example:HeadingMandatory1To indicate the start of a transaction set.ST*850*100012379 action Set IDM ID 3/3RequiredST02329Transaction set ControlNumM AN 4/9Gentex Outbound EDI 850 (Purchase Order) Specifications and Business Process RulesCOMMENTSSegments/Elements Usage4 of 14

BEG Beginning Segment for Purchase OrderSegment:Level:Loop:Usage:Max tory1To transmit identifying numbers to indicate the beginning of the Purchase Order transaction set.BEG*00*SA*1298493*0*20120313 redATTRIBUTESM ID 2/292NAMETransaction set purposeCode Name00OriginalPurchase Order TypeCodeNameRLRelease OrdersSAStand Alone OrdersKCContract OrdersBEG03324Purchase Order NumberM AN 1/22RequiredBEG04328Release NumberNote: This field will be used topopulate the Release number forBlanket releases and as RevisionNumbers for Standard or standalone purchase ordersO AN 1/30RequiredBEG05373DateM DT 8/8COMMENTSM ID 2/2Gentex Outbound EDI 850 (Purchase Order) Specifications and Business Process RulesIf the 850 BEG02 segment istransmitted as ‘SA’, this indicatesthe Revision Number of the standalone order or standard PurchaseOrder. If the 850 BEG02 isindicated as ‘RL’ this will indicatethe Release Number.System date of transactionDate Format : CCYYMMDDSegments/Elements Usage5 of 14

PER Administrative Communications ContactSegment:Level:Loop:Usage:Max tory1To identify a person or office to whom administrative communications should be directedPER*OC*MATTHEW SMITH*TE*616-772-1800 uiredPER03RequiredPER04NAMEContact Function CodeCode NameOCOrder ContactNameATTRIBUTESM ID 2/2COMMENTSM AN 1/60If populated, this is the name ofthe person at Gentex whorequested the goods/services365Communication Number QualifierCodeNameTETelephoneM ID 2/2364Communication NumberM AN 1/80Gentex Outbound EDI 850 (Purchase Order) Specifications and Business Process RulesTelephone NumberSegments/Elements Usage6 of 14

N1 NameSegment:Level:Loop:Usage:Max atory1To identify a party by type of organization, name and codeSU identification code is provided to the supplier using our 850 documentN1*SU**92*13791-MAIN ARMReqRequiredELEMIDN101ELE#98NAMEEntity Identification CodeCode NameSUSupplier CodeATTRIBUTESM ID 2/3COMMENTSThis is the supplier code siteas defined in Gentex EBSsystemRequiredN10366Identification Code QualifierC ID 1/2'92' for Buyer assigned onlyRequiredN10467Identification CodeC AN 2/80Gentex Outbound EDI 850 (Purchase Order) Specifications and Business Process RulesSegments/Elements Usage7 of 14

PO1 Baseline Item DataSegment:Level:Loop:Usage:Max To specify basic and most frequently used line item 00-0010-000*DR*001*PD*SMD XTAL, 25.00000MHZ CTS 405C ARMReqRequiredELEMIDPO101ELE#350NAMEAssigned IdentificationATTRIBUTESM AN 1/20RequiredPO102330Total Quantity OrderedC R 1/15PO103355Unit of measure codeCode NameEAEachBGBagBOBottleBXBoxCKCakeCACaseCCCubic CentimeterCICubic InchUNUnit **DZDozenDRDrumOZDry OunceFOFluid OunceFTFootGAGallonGRGramKGKilogramKHKilowatt SOSpoolTOTroy OunceY4TubUQWaferYDYardM IC 2/2Gentex Outbound EDI 850 (Purchase Order) Specifications and Business Process RulesCOMMENTS** A value of UN (Unit) is used tocommunicate quantities forSemiconductor DieSegments/Elements Usage8 of 14

RequiredPO104212Unit PriceC R 1/17RequiredPO106235Product/Service IDQualifierCode NameMGMFG Part NumberC ID 2/2RequiredPO107234Product/Service IDC AN 1/48RequiredPO108235Product/Service IDQualifierCode NameBPCustomer PartNumberC ID 2/2RequiredPO109234Product/Service IDC AN 1/48RequiredPO110235Product/Service IDQualifierCode NameDRDrawing RevisionC ID 2/2RequiredPO111234Product/Service IDC AN 1/48RequiredPO112235Product/Service IDQualifierCode NamePDPart DescriptionC ID 2/2RequiredPO113234Product/Service IDC AN 1/48Gentex Outbound EDI 850 (Purchase Order) Specifications and Business Process RulesManufacturer’s part numberGentex Item Revision Number(can be alpha or numericdepending on what Gentex hasordered).Segments/Elements Usage9 of 14

N1 NameSegment:Level:Loop:Usage:Max atory1To identify a party by type of organization, name and codeST identification code is provided to the supplier using our 850 documentN1*ST**92*STA ARMReqRequiredELEMIDN101ELE#98NAMEEntity Identification CodeCode NameSTShip to LocationATTRIBUTESM ID 2/3COMMENTSRequiredN10366Identification Code QualifierC ID 1/2'92' for Buyer assigned onlyRequiredN10467Identification CodeC AN 2/80This is the location at Gentex towhich the goods must bedeliveredLocation NameN104 ValueFire ProtectionCHIGentex Physical Address10985 Chicago Drive Zeeland, MI 49464Centennial WestCENW600 North Centennial Street Dock Doors 1-4 Zeeland, MI 49464State Street SouthSTA675 North State Street Zeeland, MI 49464RileyRIL58 East Riley Street Zeeland, MI 49464Centennial EastCENE600 North Centennial Street Dock Doors 5-11 Zeeland, MI 49464JamesJAM11768 James Street Holland, MI 49424Riley PrototypeWarehouseRiley Raw MaterialWarehouseRiley 220 (ChemicalSynthesis)Case KarstenPRO380 East Riley Street Zeeland, MI 49464DIST310 East Riley Street Zeeland, MI 49464CHEM220 East Riley Street Zeeland, MI 49464CKN790 Case Karsten Drive Zeeland, MI 49464Drop ShipDRPNorth Riley Building 1NRB1This is a virtual location only used for items drop shipping to our customers.Suppliers will be contacted by Gentex to communicate specific N104 valuesfor each customer along with the corresponding address. Forecast files (830)will be communicated with this location, but 850 files will not.9001 Riley Street Zeeland, MI 49464North Riley Building 10NRB109001 Riley Street Building 10 Zeeland, MI 49464Resource RecoveryRRB900 Brooks Avenue Holland, MI 49423Gentex Outbound EDI 850 (Purchase Order) Specifications and Business Process RulesSegments/Elements Usage10 of 14

SCHSegment:Level:Loop:Usage:Max Use:Purpose:Syntax:Comments:Example:Line Item ScheduleDetailSCHMandatory200To specify the data for scheduling a specific line-itemSCH*5000*EA***112*20120313******90 SCH*25000*EA***112*20120329******91 MEQuantityUnit of Measure Code **ATTRIBUTESM R 1/15M ID 2/2RequiredSCH05374M ID 3/3RequiredSCH06373Date/Time QualifierCode Name112Dock DateDock DateRequiredSCH12350Assigned IdentificationM AN 1/11COMMENTS** Please reference the PO103 segmentabove for a complete list of UOM CodesM DT 8/8Gentex Outbound EDI 850 (Purchase Order) Specifications and Business Process RulesAlphanumeric code assigned to the POshipment line. Must be returned on the 855.Segments/Elements Usage11 of 14

Segment:CTT Transaction TotalsLevel:Usage:Max Use:Purpose:Comments:Examples:SummaryOptional1To transmit total for a specific element in the transaction setThis segment is intended to provide hash totals to validate transaction completeness and correctness.CTT*7*700 ARMReqRequiredELEMIDCTT01ELE#354NAMENumber Of Line ItemsATTRIBUTESM N0 1/6OptionalCTT02347Quantity Hash TotalO R 1/10Gentex Outbound EDI 850 (Purchase Order) Specifications and Business Process RulesCOMMENTSTotal number of line items in the transactionsetSegments/Elements Usage12 of 14

SE Transaction Set TrailerSegment:SummaryNAMandatory1To indicate the end of the transaction set and provide the count of the transmitted segments[including the beginning (ST) and ending (SE) segments].SE*250*0001 Level:Loop:Usage:Max SRequiredSE0196Number of Included SegmentsM N0 1/10RequiredSE02329Transaction set ControlNumberM AN 4/9Gentex Outbound EDI 850 (Purchase Order) Specifications and Business Process RulesCOMMENTSSame as ST02 valueSegments/Elements Usage13 of 14

Appendix: Sample 850ISA*00**00**01*065855363SUP *01*XXXXXXXXX*120504*0902*U*00401*000006467*0*T* X*004010 ST*850*1026229 BEG*00*SA*247654*0*20090627 PER*OC*MIKE SMITH*TE*616-772-1800 N1*SU**92*SUPPLIERCODE , CENTIPEDE IMAGER N1*ST**92*CENE SCH*17982*EA***112*20090615******1 SCH*17982*EA***112*20090622******2 SCH*17982*EA***112*20090713******3 PO1*1*4050*EA*0.01****BP*100-0001-000*DR*C*PD*PCB SINGLE QUAZI-DOT RED LCD N1*ST**92*RIL SCH*4050*EA***112*20090817******1 CTT*2SE*14*1026229 GE*1*102028 IEA*1*000006467 Gentex Outbound EDI 850 (Purchase Order) Specifications and Business Process RulesAppendix: Sample 85014 of 14

Gentex Outbound EDI 850 (Purchase Order) Specifications and Business Process Rules Introduction 1 of 14 Introduction The purpose of this document is to provide the details on policies and procedures for the outbound EDI process of Purcha