Transcription
EDI IMPLEMENTATION GUIDE830 ANSI X12 V4010Planning ScheduleWith Release CapabilityRevision Date: 02/08/2017 Revision number: 6Vendor EDI 1Specifications1ANSI X12
830 Planning Schedule with Release CapabilityPSFunctional Group ID Introduction:This Draft Standard for Trial Use contains the format and establishes the data contents of the Planning Schedulewith Release Capability Transaction Set (830) for use within the context of an Electronic Data Interchange (EDI)environment. The transaction set can be used to provide for customary and established business practice relative tothe transfer of forecasting/material release information between organizations. The planning schedule transactionmay be used in various ways or in a combination of ways, such as: (1) a simple forecast; (2) a forecast with thebuyer's authorization for the seller to commit to resources, such as labor or material; (3) a forecast that is also usedas an order release mechanism, containing such elements as resource authorizations, period-to-date cumulativequantities, and specific ship/delivery patterns for requirements that have been represented in "buckets," such asdaily, weekly, monthly, or quarterly. The order release forecast may also contain all data related to purchase orders,as required, because the order release capability eliminates the need for discrete generation of purchase orders.ANSI standards and AIAG guidelines list many optional segments and elements in the v4010 830. Segments andelements not listed below will not be used by Flex-N-Gate. The supplier’s software must be able to process allsegments and elements listed. The left-hand column provides information on FNG’s normal usage. “Always” meansthat the segment or element will always be sent by Flex-N-Gate.”Optional ” indicates that this segment is usually sent. “Optional –“means that this segment is rarely used.Within one day of receiving an 830, a 997 should be returned. See end of this documentation for a sample of the997.Changes made:Revision 6: dated: 02 08 2017 - There was a note added to explain the past due calculation.Revision Date: 02/08/2017 Revision number: 6Vendor EDI 2Specifications2ANSI X12
eAlways10STTransaction Set HeaderM1Always20BFRBeginning Segment for PlanningScheduleLOOP ID - N1M1Notes andRepeatComments200Always 240N1NameO1Optional 290PERAdministrative pUsageUseRepeatLOOP ID – LIN350LINItem IdentificationM1Always360UITUnit DetailO1Optional -460PRSPart Release StatusO1Optional -470REFReference IdentificationO12Optional 550ATHResource AuthorizationO20LOOP ID – LIN/N1200Optional 690N1NameO1Optional 710N3Address InformationO1Optional 720N4Geographic LocationO1LOOP ID – LIN/FST800FSTComments 1AlwaysOptional Notes andForecast Schedule260O1LOOP ID – LIN/SHP25Optional 900SHPShipped/Received InformationO1Optional 910REFReference IAGMaxLoopUsageUseRepeatAlways950CTTTransaction TotalsO1Always960SETransaction Set TrailerM1Notes andCommentsn1Transaction Set Notes1.Number of line items (CTT01) is the accumulation of the number of LIN segments.Revision Date: 02/08/2017 Revision number: 6Vendor EDI 3Specifications3ANSI X12
Segment:Position:Loop:Level:Usage:Max Use:Purpose:Syntax Notes:Semantic Notes:ST Transaction Set Header010HeadingMandatory1To indicate the start of a transaction set and to assign a control number1The transaction set identifier (ST01) is used by the translation routines of theinterchange partners to select the appropriate transaction set definition (e.g., 810selects the Invoice Transaction t143NameTransaction Set IdentifierCodeCode uniquely identifying a Transaction SetAttributesMID3/3Planning Schedule withRelease CapabilityAlwaysST02329830Transaction Set ControlNumberIdentifying control number that must be unique within thetransaction set functional group assigned by the originatorfor a transaction setMAN4/9Data Element SummaryRevision Date: 02/08/2017 Revision number: 6Vendor EDI 4Specifications4ANSI X12
Segment:Position:Loop:Level:Usage:Max Use:Purpose:Syntax Notes:Semantic lwaysBFR08AlwaysBFR11BFR Beginning Segment for Planning Schedule020HeadingMandatory1To indicate the beginning of a planning schedule transaction set; whether a ship ordelivery based forecast; and related forecast envelope dates1 At least one of BFR02 or BFR03 is required.1 BFR02 is the identifying number for a forecast assigned by the orderer/purchaser.2 BFR06 is the forecast horizon start date: The date when the forecast horizon(envelope) begins.3 BFR07 is the forecast horizon end date: The date when the forecast horizon(envelope) ends.4 BFR08 is the date forecast generated: The date the forecast data was generated.5Use LIN05 for Purchase Order rather than BFR11 since there may be more than onePO on the 830.Data Element SummaryDataElement NameAttributes353Transaction Set Purpose CodeMID 2/2Code identifying purpose of transaction set04Change05Replace127Reference IdentificationXAN 1/30Reference information as defined for a particularTransaction Set or as specified by the ReferenceIdentification Qualifier328Release NumberXAN 1/30Number identifying a release against a PurchaseOrder previously placed by the parties involvedin the transaction675Schedule Type QualifierMID 2/2Code identifying the type of dates used whendefining a shipping or delivery time in aschedule or forecastDLDelivery BasedSHShipment Based676Schedule Quantity QualifierMID 1/1Code identifying the type of quantities usedwhen defining a schedule or forecastAActual Discrete Quantities373Forecast Horizon Start DateMDT 8/8Date expressed as CCYYMMDD373Forecast Horizon End DateODT 8/8Date expressed as CCYYMMDD373Generation DateMDT 8/8Date expressed as CCYYMMDD324Purchase Order NumberMAN 9/9Identifying number for Purchase OrderNumber assigned by PurchaserRevision Date: 02/08/2017 Revision number: 6Vendor EDI 5Specifications5ANSI X12
Segment:Position:Loop:Level:Usage:Max Use:Purpose:Syntax Notes:Semantic Notes:Comments:N1 Name240N1OptionalHeadingOptional1To identify a party by type of organization, name, and code1 At least one of N102 or N103 is required.2 If either N103 or N104 is present, then the other is required.123FNGUsageAlwaysRef.Des.N101AlwaysSee comment 2See comment 3AlwaysN102AlwaysN103AlwaysN104This segment, used alone, provides the most efficient method of providingorganizational identification. To obtain this efficiency the "ID Code" (N104) mustprovide a key to the table maintained by the transaction processing party.The N1*ST will be used at either the header level or at the detail level, but never atboth levels. If all parts in a transaction set have the same ship to destination, theheader level N1*ST will be used. If parts have different destinations, the detail levelsegment will be used within every LIN loop.N103 for N1*SU is mandatory to match whit the 856 that you return. If you do notsupply this on the 856 the GS segment will be usedData Element SummaryDataElement NameAttributes98Entity Identifier CodeM ID 2/3Code identifying an organizational entity, a physical location, property or anindividualMIMaterial Release IssuerSTShip ToSUSupplier/Manufacturer93NameX AN 1/60Free-form name66Identification Code QualifierX ID 1/2Code designating the system/method of code structure used for IdentificationCode (67)1D-U-N-S Number, Dun & Bradstreet01D-U-N-S Number, Dun & Bradstreet92Assigned by Buyer or Buyer’s Agent67Identification CodeX AN 2/80Code identifying a party or other codeSuppress internal dashes and spaces.This is normally your DUNS number can also be mutually definedRevision Date: 02/08/2017 Revision number: 6Vendor EDI 6Specifications6ANSI X12
Segment:Position:Loop:Level:Usage:Max Use:Purpose:Syntax Notes:PERAdministrative Communications Contact290N1HeaderOptional3To identify a person or office to whom administrative communications should be directed1 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 This segment is used only for the Ship-to.Semantic nal PER03Optional PER04Optional PER05Optional PER06Data Element SummaryDataElement NameAttributes366Contact Function CodeM ID 2/2Code identifying the major duty or responsibility of the person or group namedEXExpeditor93NameO AN 1/60Free-form name365Communications Number QualifierX ID 2/2Code identifying the type of communications numberTETelephone364Communications NumberX A/N 1/80Complete communications number including country or area code365Communications Number QualifierX ID 2/2Code identifying the type of communications numberFXFacsimile364Communications NumberX A/N 1/80Complete communications number including country or area codeRevision Date: 02/08/2017 Revision number: 6Vendor EDI 7Specifications7ANSI X12
Segment:Position:Loop:Level:Usage:Max Use:Purpose:Syntax Notes:Semantic Notes:Comments:FNGUsageLIN Item Identification350LINMandatoryDetailMandatory1To specify basic item identification data1 If either LIN04 or LIN05 is present, then the other is required.2 If either LIN08 or LIN09 is present, then the other is required.3 If either LIN12 or LIN13 is present, then the other is required.112LIN01 is the line item identificationSee the Data Dictionary for a complete list of IDs.LIN02 through LIN13 provide for six different product/service IDs for each item.Data Element SummaryDataElement NameAttributes235Product/Service ID QualifierM ID 2/2Code identifying the type/source of the descriptive number used inProduct/Service ID (234)BPBuyer's Part Number234Product/Service IDM AN 1/48Identifying number for a product or service235Product/Service ID QualifierX ID 2/2Code identifying the type/source of the descriptive number used inProduct/Service ID (234)POPurchase Order Number234Product/Service IDX AN 1/48Identifying number for a product or service235Product/Service ID QualifierX ID 2/2Code identifying the type/source of the descriptive number used inProduct/Service ID ysLIN05Optional -LIN06Optional -LIN07234Optional -LIN08235Optional -LIN09234Optional -LIN10235Optional Optional -LIN11LIN12234235ECEngineering Change LevelProduct/Service IDX AN 1/48Identifying number for a product or serviceProduct/Service ID QualifierX ID 2/2Code identifying the type/source of the descriptive number used inProduct/Service ID (234)VPVendor PartProduct/Service IDX AN 1/48Identifying number for a product or serviceProduct/Service ID QualifierX ID 2/2Code identifying the type/source of the descriptive number used inProduct/Service ID (234)RYModel YearProduct/Service IDX AN 1/48Product/Service ID QualifierX ID 2/2Code identifying the type/source of the descriptive number used inProduct/Service ID (234)PDOptional -LIN13234Part DescriptionProduct/Service IDRevision Date: 02/08/2017 Revision number: 6Vendor EDI 8SpecificationsXAN 1/488ANSI X12
Segment:Position:Loop:Level:Usage:Max Use:Purpose:Syntax Notes:Semantic Notes:Comments:FNGUsageAlwaysRef.Des.UIT01UIT Unit Detail360LINMandatoryDetailOptional1To specify item unit data1 if UIT03 is present, then UIT02 is required.UIT01 is a composite data element, C001, which contains 15 simple data elements.AIAG only utilizes the first component of the composite, data element 355. Thisimplementation guideline reflects that decision by substituting 355 for C001, whichis syntactically correct.1 The unit of measure in the SN103 element on the 856 for a given part should matchthe unit of measure in UIT01 for that part.Data Element SummaryDataElement NameAttributes355Unit or Basis for Measurement CodeM AN 2/2Code specifying the units in which a value is being expressed, or manner inwhich a measurement has been takenAny valid X12 code value except mutually defined: 'ZZ'Revision Date: 02/08/2017 Revision number: 6Vendor EDI 9Specifications9ANSI X12
Segment:Position:Loop:Level:Usage:Max Use:Purpose:PRS Part Release Status460LINMandatoryDetailOptional1To indicate the status of the part being ordered or forecast with respect to this materialrelease or planning documentSyntax Notes:Semantic Notes:Comments:FNGUsageOptional -Ref.Des.PRS01Data Element SummaryDataElement NameAttributes682Part Release Status CodeM ID 1/2Code identifying the status of the specific part number being released orforecast or being used in an engineering changeAny valid X12 code value.Revision Date: 02/08/2017 Revision number: 6Vendor EDI10Specifications10ANSI X12
Segment:Position:Loop:Level:Usage:Max Use:Purpose:Syntax Notes:Optional -Ref.Des.REF01REFReference Identification470LINMandatoryDetailOptional12To specify identifying information1 At least one REF02 is required.Comments:Data Element SummaryDataElement Name128Reference Identification QualifierCode qualifying the Reference IdentificationDKLFRLOptional -REF02127AttributesM ID 2/3Dock codeLine FeedReserve Line FeedReference IdentificationX AN 1/30Reference information as defined for a particular Transaction Set or asspecified by the Reference Identification QualifierRevision Date: 02/08/2017 Revision number: 6Vendor EDI11Specifications11ANSI X12
Segment:Position:Loop:Level:Usage:Max Use:Purpose:Syntax Notes:Semantic Notes:Comments:AlwaysRef.Des.ATH01AlwaysATH02See syntaxATH03See syntaxATH05ATH Resource Authorization550LINMandatoryDetailOptional20To specify resource authorizations (i.e., finished labor, material, etc.) in the planningschedule1 At least one of ATH02 or ATH03 is required.2 If ATH03 is present, then ATH05 is required.1 ATH02 is the resource authorization through date: The date through which the buyerauthorizes the seller to commit the resource defined in element ATH01.2 ATH03 is the current cumulative requirements quantity: The cumulative quantitythat has been authorized to date from the cumulative start date (ATH05) through theresource authorization through date (ATH02).3 ATH05 is the cumulative start date: The date where the cumulative quantity countstarts. This date might be the start date of a contract period, a calendar or fiscal year,or other.1 It is imperative that negotiations defining financial commitment have previouslyoccurred and are agreed to by both buyer and seller.Data Element SummaryDataElement NameAttributes672Resource Authorization CodeM ID 2/2Code identifying the resource which the buyer is authorizing the seller tocommit toFIFinished (Labor, Material, and Overhead/Burden)MTMaterialPQCumulative Quantity Required Prior to First SchedulePeriodNOTE: If the first FST is prior to today date then thatCumulative Quantity is added to the PQ CumulativeQuantity prior to subtracting the SHP 02 CumulativeQuantity the calculation to verify if you have a past dueamount.373DateX DT 8/8Date expressed as CCYYMMDD380Authorization Cum Required QuantityX R 1/15Numeric value of quantity373Required Ship DateX DT 8/8Date expressed as CCYYMMDDRevision Date: 02/08/2017 Revision number: 6Vendor EDI12Specifications12ANSI X12
Segment:Position:Loop:Level:Usage:Max Use:Purpose:Syntax Notes:Semantic Notes:Comments:N1 Name690LIN/N1OptionalDetailOptional1To identify a party by type of organization, name, and code1 At least one of N102 or N103 is required.2 If either N103 or N104 is present, then the other is aysN103AlwaysN104This segment, used alone, provides the most efficient method of providingorganizational identification. To obtain this efficiency the "ID Code" (N104) mustprovide a key to the table maintained by the transaction processing party.The N1*ST will be used at either the header level or at the detail level, but never atboth levels. If all parts in a transaction set have the same ship to destination, theheader level N1*ST will be used. If parts have different destinations, the detail levelsegment will be used.Data Element SummaryDataElement NameAttributes98Entity Identifier CodeM ID 2/3Code identifying an organizational entity, a physical location, property or anindividualSTShip To93NameX AN 1/60Free-form name66Identification Code QualifierX ID 1/2Code designating the system/method of code structure used for IdentificationCode (67)1D-U-N-S Number, Dun & Bradstreet67Identification CodeX AN 2/80Suppress internal dashes and spaces.Code identifying a party or other codeRevision Date: 02/08/2017 Revision number: 6Vendor EDI13Specifications13ANSI X12
Segment:N3 Address InformationPosition:Loop:Level:Usage:Max Use:Purpose:Syntax Notes:Semantic Notes:Comments:FNGUsageOptional -Ref.Des.N301Optional -N302710LIN/N1OptionalDetailOptional1To specify the location of the named partyData Element SummaryDataElement Name166 Address InformationAttributesM ID 1/55Address InformationO AN 1/55166Revision Date: 02/08/2017 Revision number: 6Vendor EDI14Specifications14ANSI X12
Segment:N4 Geographic LocationPosition:Loop:Level:Usage:Max Use:Purpose:Syntax Notes:Semantic Notes:Comments:FNGUsageOptional -Ref.Des.N401720LIN/N1OptionalDetailOptional1To specify the geographic location, e.g., city, state, of the named party1Data Element SummaryDataElement NameCity Name19MAttributesAN 2/30Optional -N402156State/ProvinceOID 1/2Optional -N403116Postal codeOID 3/15Optional -N40426Country CodeOID 2/3Revision Date: 02/08/2017 Revision number: 6Vendor EDI15Specifications15ANSI X12
Segment:Position:Loop:Level:Usage:Max Use:Purpose:Syntax T02AlwaysFST03AlwaysFST04See syntax&commentsFST05FST Forecast Schedule800LIN/FSTOptionalDetailOptional260To specify the forecasted dates and quantities1If FST03 equals "F" (indicating flexible interval), then FST04 and FST05 arerequired. FST04 would be used for the start date of the flexible interval and FST05would be used for the end date of the flexible interval.1 As qualified by FST02 and FST03, FST04 represents either a discrete forecast date,the first date of a forecasted bucket (weekly, monthly, quarterly, etc.) or the start dateof a flexible interval.2. Flex-N-Gate may send daily requirements.Data Element SummaryDataElement NameAttributes380QuantityM R 1/15Numeric value of quantity680Forecast QualifierM ID 1/1Code specifying the sender's confidence level of the forecast data or an actionassociated with a forecastCFirmDPlanning681Forecast Timing QualifierM ID 1/1Code specifying interval grouping of the forecastDDiscreteFFlexible Interval (from Date X through Date Y)MMonthly Bucket (Calendar Months)WWeekly Bucket373Forecast Begin DateM DT 8/8Date expressed as CCYYMMDD373Forecast End DateO DT 8/8Date expressed as CCYYMMDDRevision Date: 02/08/2017 Revision number: 6Vendor EDI16Specifications16ANSI X12
Segment:Position:Loop:Level:Usage:Max Use:Purpose:Syntax Notes:Semantic sSHP03AlwaysSHP04SHP Shipped/Received Information900LIN/SHPOptionalDetailOptional1To specify shipment and/or receipt information1 If SHP01 is present, then SHP02 is required.2 If SHP03 is present, then at least one of SHP04 or SHP05 is required.3 If SHP04 is present, then SHP03 is required.1 SHP04 is the date shipped, delivered, received, or the cumulative quantity start date(as qualified by SHP03).1 The SHP segment is used to communicate shipment, delivery, or receipt informationand may include discrete or cumulative quantities, dates, and times.Data Element SummaryDataElement Name673Quantity QualifierCode specifying the type of quantity01Discrete Quantity02Cumulative Quantity380QuantityNumeric value of quantity374Date/Time QualifierCode specifying type of date or time, or both date and time050Received051Cumulative Quantity Start373DateDate expressed as CCYYMMDDRevision Date: 02/08/2017 Revision number: 6Vendor EDI17SpecificationsAttribute
Revision Date: 02/08/2017 Revision number: 6 Vendor EDI Specifications 6 6 ANSI X12 version 4010 Segment: N1 Name Position: 240 Loop: N1 Optional Level: Heading Usage: Optional Max Use: 1 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 ei
