Transcription
IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONSSHIPPING SCHEDULE (862) TRANSACTION SETFCA USINFORMATION & COMMUNICATION TECHNOLOGY MANAGEMENTANSI ASC X12VERSION/RELEASE 002040CHRY
FCA US - Shipping Schedule862 Shipping ScheduleFunctional Group ID SSIntroduction:This standard provides the format and establishes the data contents of a shipping schedule transaction setwithin the context of an electronic data interchange (EDI) environment. The shipping schedule transaction setprovides the ability for a customer to convey precise shipping schedule requirements to a supplier, and isintended to supplement the planning schedule transaction set (830). The shipping schedule transaction set willsupersede certain shipping and delivery information transmitted in a previous planning schedule transaction,but it does not replace the 830 transaction set. The shipping schedule transaction set shall not be used toauthorize labor, materials or other resources.The use of this transaction set will facilitate the practice of Just In Time (JIT) manufacturing by providingthe customer with a mechanism to issue precise shipping schedule requirements on a more frequent basisthan with the issuance of a planning schedule transaction, e.g.daily shipping schedules versus weeklyplanning schedules. The shipping schedule transaction also provides the ability for a customer location toissue shipping requirements independent of other customer locations when planning schedule transactions areissued by a consolidated scheduling organization.Notes:With the launch of Common Ship/Delivery Schedule (CSDS), plants may establish ship and deliverywindows which do not necessarily differ by total transit time. In addition, window times within each dayand by day of the week may differ. FCA has changed the 862 format to provide transportation supplierswith both shipment based information and delivery based information to facilitate smooth, on-timedelivery to its plants. Please refer to Example 7 - Common SDS.The supplier or carrier should be aware of the following things when programming for thisimplementation guide- The date (FST04) and time (FST07) indicated in the FST segment represent when the supplier shouldSHIP the parts, not when the supplier should deliver the parts to FCA.- The elements BSS05 and BSS06 represent the horizon start and horizon end dates with a 30 calendarday schedule.- The resource authorization date (ATH02) is the day prior to the 30 calendar day schedule.- In the Beginning Segment - Shipping Schedule (BSS), a code value of '04' (Change) in the BSS01element will be issued for the transmission of requirement changes for selected part numbers only; a codevalue of '02' (Add) in the BSS01 element will be issued for adding new part numbers or shipmentrequirements sent in a previous 862 transaction; a code value of '03' (Delete) in the BSS01 element willbe issued for removing a part or shipment requirement sent on a previous 862 transaction. Data for otherpart numbers previously transmitted and not included in this transmission must be retained.04/17/2019 V/R 002040CHRY1FCA US
FCA US - Shipping Schedule- Daily adjustments will not be shown in the SHP segment but will be included in the Quantity element(ATH03) of the ATH segment to provide the net adjusted cum requirements. The adjustment no longerneeds to be calculated to provide net requirements.FCA US utilizes an accum based releasing (EDI 830 and 862) process, if your system takes the data andmakes a calculation, you should always know where you are.The calculation is:ATH03 Today’s FST01 (if there’s no requirement for ‘today’, use FST01 0 ) total amount that should have been shipped by the end of the day on which the EDI 830 was generated.SHP 02(Cumulative Quantity) The amount shipped to date ((CHAMPS YTD) if there’s no SHP 02segment, CHAMPS YTD 0) 051 99991230 99991231SHP 02, element 02 - (ATH03 Today’s FST01) status.If the status is 0, you have fulfilled the current requirement.If status is less than 0, you have not met the current requirement.If the status more than 0, you have shipped more than the current requirement.Metered Parts Kanban Ship Schedule (MSDS)The Metered Parts Kanban Ship Schedule (MSDS) is intended to enable the Split ASN process. The SplitASN process using Kanban is intended to allow an offsite faciility to receive full truckloads of materialfrom suppliers and meter the material to the plant using the MSDS. Material will arrive to the facility aday ahead of when it is to be delivered to the plant. Having projections available prior to the trucksarriving at the offsite facility will allow the trucks to be unloaded and split for the next day's shipments.DEVIATION TABLE FOR THE DETAIL AREA:1: The NTE segment is used to show the type of SDS part (test, information, or Just In Time).2: This PER segment will provide contact information for the specific part shown in the LIN segment.3. The DTM segment was added to the JIT loop in order to facilitate more flexible shipment/deliveryrequirements as part of the Common SDS (CSDS) Rewrite.NOTE: Through this document, 'USER STATUS' and 'USER ATTRIBUTES' refer to the FCAimplementation.Notes about the format of this implementation guide:1. The requirements contained herein have not changed, with the exception of anything that may appear inthe History of Changes section below.2. The term 'Base Status' refers to the requirements as defined by the ASC X12 Standards Organization.3. The terms 'User Status' and 'User Attributes' refer to FCA requirements.4. Data segment sequence tables for each hierarchical level will no longer be presented at the beginning ofeach hierarchical level. The data segment sequence tables for each hierarchical level will now be presented atthe beginning.5. Segment Syntax and Semantic notes as defined by ASC X12 will now be included where in the 'old'format they were not.04/17/2019 V/R 002040CHRY2FCA US
FCA US - Shipping Schedule6. Element Description as defined by ASC X12 will now be included where in the 'old' format they were not.7. Many comments that relate to a particular code value will now appear underneath the code valuedescription, where previously the comments would appear to the right.History of Changes:01/13/2004:Add comments and example (8) for Metered Parts Kanban SDS.03/01/2004:Add comments and example (9) for Customer EDI.09/30/2004:Add functionality for (new example) Assembly Kanban: add PO4 segment, add codes to REF segment07/19/2005:Add code 'A' (Immediate) to forecast qualifier (FST02) for Kanban.08/04/2005:Add N1 loop for plant extension ship to locations08/20/2006:Add transportation mode 'I' to both TD5 segments04/11/2007:Add requirements and example (8) for Web Based Module Ordering (WBMO)11/15/2007:Transition to Chrysler LLC with removal of references to Daimler09/21/2010:Name change from Chrysler LLC to ChryslerUpdated Address10/20/2010:Minor Edits10/30/2014:Removed requirements and example for Web Based Module Ordering (WBMO).This Is No Longer Supported03/31/2015:Detail - NTE02 Added New Local Code 'I'Name Change To FCA US03/10/2017:Detail - REF01 Added Note to Qualifier 'RL'01/14/2019Detail - Corrected reference of '04000KB' to '04000'KN'04/17/2019 V/R 002040CHRY3FCA US
FCA US - Shipping Schedule04/17/2019:Added Notes for Accum uideM7020BSSBeginning Segment for ShippingScheduleMM030DTMDate/Time/PeriodONot Used10040NTENote/Special InstructionFNot Used100043REFReference NumbersONot Used 1045PIDProduct/Item DescriptionONot Used 1NameTransaction Set HeaderUserStatusMMax.Use1Notes andComments1LOOP ID - N19LoopRepeat200050N1NameO1060N2Additional Name InformationONot Used2070N3Address InformationONot Used1080N4Geographic LocationONot Used1090REFReference NumbersONot Used12100PERAdministrative CommunicationsContactONot Used3110FOBF.O.B. Related InstructionsONot Used1Detail:PageNo.Pos.No.Seg.ID11010LINItem IdentificationO14020UITUnit DetailM15030NTENote/Special InstructionO116040PERAdministrative CommunicationsContactO617050PO4Item Physical DetailsO060PKGMarking, Packaging, LoadingO070REFReference NumbersO080SDPShip/Delivery PatternO19BaseGuideNameLOOP ID - LINUserStatusMax.UseM1 1Not Used 112Not Used1200081N1Name082N2Additional Name InformationONot Used2083N3Address InformationONot Used2084N4Geographic LocationONot Used1085REFReference NumbersONot Used12086PERAdministrative CommunicationsContactONot Used3088FOBF.O.B. Related InstructionsONot Used1OLOOP ID - FST04/17/2019 V/R 002040CHRYNotes andComments1LOOP ID - N120LoopRepeat1000011004FCA US
FCA US - Shipping Schedule21090FSTForecast tination QuantityO120JITJust-In-Time ScheduleO130REFReference ource AuthorizationO1Not Used999999LOOP ID - JIT24961Not Used500LOOP ID - SHP283010150SHPShipped/Received InformationO160REFReference NumbersONot Used121170TD1Carrier Details (Quantity and Weight)ONot Used1175TD5Carrier Details (RoutingSequence/Transit Time)O180TD3Carrier Details (Equipment)O1Not action Totals34020SETransaction Set Trailer04/17/2019 V/R atNotes andComments1FCA US
FCA US - Shipping ScheduleSegment:Position:Loop:Level:Usage:Max Use:Purpose:Syntax Notes:Semantic Notes:Comments:Business Rules:Notes:ST Transaction Set Header010HeadingMandatory1To indicate the start of a transaction set and to assign a control number1The transaction set identifier (ST01) is intended for use by the translationroutines of the interchange partners to select the appropriate transaction setdefinition (e.g., 810 selects the invoice transaction set).Variable Name: STSTThe transaction set control number (ST02) in this header must match thetransaction set control number (SE02) in the transaction set trailer (SE).Example:ST 862 910601111Data Element SummaryRef.Des.ST01DataElement Name143Transaction Set Identifier CodeCode uniquely identifying a Transaction Set862ST02329BaseAttributesM ID 3/3UserAttributesMM AN 4/9MX12.37 Shipping ScheduleTransaction Set Control NumberAN 9/9Identifying control number assigned by the originator for a transaction set.A unique control number (Same as SE02).04/17/2019 V/R 002040CHRY6FCA US
FCA US - Shipping ScheduleSegment:Position:Loop:Level:Usage:Max Use:Purpose:Syntax Notes:Semantic Notes:Comments:Notes:BSS Beginning Segment for Shipping Schedule020HeadingMandatory1To indicate the beginning of a shipping schedule.1 At least one of BSS07 or BSS08 is required.123Use BSS02 to indicate a document number.Use BSS03 to indicate the date of this document.Use BSS05 to indicate the schedule horizon start date (the date when theschedule begins.)4 Use BSS06 to indicate the schedule horizon end date (the date when theschedule ends.)5 BSS08 is the identifying number for a forecast assigned by theorderer/purchaser.This segment indicates whether the schedule is shipment or kanban based.The BSS01 element shows what action is to be taken with this transaction inregard to previous shipping schedules.Example:BSS 05 910601111 910603 SH 910603 910702 9106011-11Data Element SummaryRef.Des.BSS01DataElement Name353Transaction Set Purpose CodeBaseAttributesM ID 2/2UserAttributesMCode identifying purpose of transaction set02AddBSS0212703Delete04Change05ReplaceReference NumberM AN 1/30 MAN 6/30Reference number or identification number as defined for a particular TransactionSet, or as specified by the Reference Number Qualifier.The schedule issue date in YYDDDHHMM formatFor KANBAN, the schedule issue date will be in YYMMDD format.BSS03373DateDate (YYMMDD)M DT 6/6MM ID 2/2MCurrent date.BSS04675Schedule Type Qualifier04/17/2019 V/R 002040CHRY7FCA US
FCA US - Shipping ScheduleCode identifying the type of dates used when defining a shipping or delivery time in aschedule or forecastBSS05373KBKanban SignalSHShipment BasedDateM DT 6/6MM DT 6/6MNotUsedDate (YYMMDD)First day of the thirty calendar day schedule.For KANBAN, the current date.BSS06373DateDate (YYMMDD)Last day of the thirty calendar day schedule.For KANBAN, the current date.BSS07328Release NumberC AN 1/30BSS08127Reference NumberC AN 1/30AN 6/30Reference number or identification number as defined for a particular TransactionSet, or as specified by the Reference Number Qualifier.Same as BSS02.BSS09367Contract NumberO AN 1/30NotUsedBSS10324Purchase Order NumberO AN 1/22NotUsedBSS11676Schedule Quantity QualifierO ID 1/1NotUsed04/17/2019 V/R 002040CHRY8FCA US
FCA US - Shipping ScheduleSegment:Position:Loop:Level:Usage:Max Use:Purpose:Syntax Notes:Semantic Notes:Comments:Notes:N1 Name050N1OptionalHeadingOptional1To 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.1This segment, used alone, provides the most efficient method of providingorganizational identification. To obtain this efficiency the "ID Code" (N104)must provide a key to the table maintained by the transaction processing party.Three iterations of the N1 loop in the heading area will be used to identify theShipping Schedule Issuer, the Release Supplier, and the Ship To location. TheUltimate Destination (MA) is not used within the Shipping Schedule.Example:N1 SI 92 04000N1 SU 92 10167ABN1 ST 92 09106N1 SF 92 10167ACRef.Des.N101Data Element SummaryDataBaseElement NameAttributes98Entity Identifier CodeM ID 2/2Code identifying an organizational entity or a physical location.SFShip FromSIShipping Schedule IssuerSTShip ToSUSupplier/ManufacturerN10293NameC AN 1/35N10366Identification Code QualifierC ID 1/2UserAttributesMNotUsedCode designating the system/method of code structure used for Identification Code(67)92N10467Assigned by BuyerIdentification CodeC ID 2/17ID 5/17Code identifying a party.For FCA issued schedules:If N101 'SI', this contains '04000' FCA Assembly Division; For KANBAN, thiselement will contain '04000KN'; For Metered Parts Kanban, this element willcontain '04000MK';If N101 'ST', the FCA assigned receiving plant code;04/17/2019 V/R 002040CHRY9FCA US
FCA US - Shipping ScheduleIf N101 'SU', the FCA assigned supplier code of the release supplier. For MeteredParts Kanban, this will be the supplier code or pool point location;If N101 'SF', the FCA assigned supplier code of the ship-from location;For Customer EDI schedules where FCA is the supplier:If N101 'SI', the FCA assigned code for the trading partner issuing the schedule;If N101 'ST', the FCA assigned code for the ship to location;If N101 'SU', the FCA assigned supplier code of the release supplier. ForCustomer EDI, '04006';04/17/2019 V/R 002040CHRY10FCA US
FCA US - Shipping ScheduleSegment:Position:Loop:Level:Usage:Max Use:Purpose:Syntax Notes:Semantic Notes:Comments:Notes:LIN Item Identification010LINOptionalDetailOptional1To specify basic item identification data1 If LIN04 is present, then LIN05 is required.2 If LIN06 is present, then LIN07 is required.3 If LIN08 is present, then LIN09 is required.4 If LIN10 is present, then LIN11 is required.5 If LIN12 is present, then LIN13 is required.6 If LIN14 is present, then LIN15 is required.7 If LIN16 is present, then LIN17 is required.8 If LIN18 is present, then LIN19 is required.9 If LIN20 is present, then LIN21 is required.10 If LIN22 is present, then LIN23 is required.11 If LIN24 is present, then LIN25 is required.12 If LIN26 is present, then LIN27 is required.13 If LIN28 is present, then LIN29 is required.14 If LIN30 is present, then LIN31 is required.123See the Data Dictionary for a complete list of ID's.LIN01 is the line item identificationLIN02 through LIN31 provide for fifteen (15) different product/service ID'sfor each item. For Example: Case, Color, Drawing No., UPC No., ISBN No.,Model No., SKU.This is a mandatory segment and is used to identify the part number.Clarification on the specification of part number:When FCA issues the schedule:- BP FCA part numberWhen FCA receives the schedule:- BP Customer part number- VP FCA part numberExamples:LIN BP 04080192AALIN BP BUYERPART VP VENDORPART (Customer EDI)Ref.Des.LIN01Data Element SummaryDataElement Name350Assigned Identification04/17/2019 V/R 002040CHRY11BaseAttributesO AN 1/6UserAttributesNotUsedFCA US
FCA US - Shipping ScheduleLIN02235Product/Service ID QualifierM ID 2/2MCode identifying the type/source of the descriptive number used in Product/ServiceID (234)BPLIN03234Buyer's Part NumberProduct/Service IDM AN 1/30MAN 8/30Identifying number for a product or serviceFCA part number.LIN04LIN05235234Product/Service ID QualifierO ID 2/2Code identifying the type/source of the descriptive number used in Product/ServiceID (234)For KANBAN use only.JNJob NumberVPVendor's (Seller's) Part NumberProduct/Service IDIdentifying number for a product or serviceC AN 1/30AN 8/30If LIN04 'JN', for KANBAN use only: KANBAN Job Number;If LIN04 'VP', for Customer EDI only: FCA part number.LIN06235Product/Service ID QualifierO ID 2/2Code identifying the type/source of the descriptive number used in Product/ServiceID (234)For KANBAN use only.JSLIN07234Job Sequence NumberProduct/Service IDC AN 1/30Identifying number for a product or serviceFor KANBAN use only: KANBAN Job Sequence NumberLIN08235Product/Service ID QualifierO ID 2/2NotUsedLIN09234Product/Service IDC AN 1/30NotUsedLIN10235Product/Service ID QualifierO ID 2/2NotUsedLIN11234Product/Service IDC AN 1/30NotUsedLIN12235Product/Service ID QualifierO ID 2/2NotUsedLIN13234Product/Service IDC AN 1/30NotUsedLIN14235Product/Service ID QualifierO ID 2/2NotUsedLIN15234Product/Service IDC AN 1/30NotUsed04/17/2019 V/R 002040CHRY12FCA US
FCA US - Shipping ScheduleLIN16235Product/Service ID QualifierO ID 2/2NotUsedLIN17234Product/Service IDC AN 1/30NotUsedLIN18235Product/Service ID QualifierO ID 2/2NotUsedLIN19234Product/Service IDC AN 1/30NotUsedLIN20235Product/Service ID QualifierO ID 2/2NotUsedLIN21234Product/Service IDC AN 1/30NotUsedLIN22235Product/Service ID QualifierO ID 2/2NotUsedLIN23234Product/Service IDC AN 1/30NotUsedLIN24235Product/Service ID QualifierO ID 2/2NotUsedLIN25234Product/Service IDC AN 1/30NotUsedLIN26235Product/Service ID QualifierO ID 2/2NotUsedLIN27234Product/Service IDC AN 1/30NotUsedLIN28235Product/Service ID QualifierO ID 2/2NotUsedLIN29234Product/Service IDC AN 1/30NotUsedLIN30235Product/Service ID QualifierO ID 2/2NotUsedLIN31234Product/Service IDC AN 1/30NotUsed04/17/2019 V/R 002040CHRY13FCA US
FCA US - Shipping ScheduleSegment:Position:Loop:Level:Usage:Max Use:Purpose:Syntax Notes:Semantic Notes:Comments:Notes:UIT Unit Detail020LINOptionalDetailMandatory1To specify item unit dataThis is a mandatory segment and indicates the unit of measure for all quantitiesrelating to the line item.Example:UIT EAData Element SummaryRef.Des.UIT01DataElement Name355Unit or Basis for Measurement CodeCode identifying the basic unit of measurement.EABaseAttributesM ID 2/2UserAttributesMEachUIT02212Unit PriceC R 1/14NotUsedUIT03639Basis of Unit Price CodeO ID 2/2NotUsed04/17/2019 V/R 002040CHRY14FCA US
FCA US - Shipping ScheduleSegment:Position:Loop:Level:Usage:Max Use:Purpose:Syntax Notes:Semantic Notes:Comments:Notes:NTE Note/Special Instruction030LINOptionalDetailOptional1To transmit information in a free-form format, if necessary, for comment or specialinstruction1The NTE segment permits free-form information/data which, under ANSI X12standard implementations, is not machine processable. The use of the NTEsegment should therefore be avoided, if at all possible, in an automatedenvironment.This segment is used to provide part information: if the part is a Just In Timepart or test part. Not used for Kanban.Only 1 NTE segment would be created for a particular part.Note: This segment will be eliminated in the future.Examples:NTE LIN TNTE LIN JRef.Des.NTE01Data Element SummaryDataBaseUserElement NameAttributesAttributes363Note Reference CodeO ID 3/3Code identifying the functional area or purpose for which the note appliesLINNTE023Line ItemFree Form MessageM AN 1/60MAN 1/1Free-form textIRILC RoutesJJust In TimeSSupplier InformationTPart In Test ModeIndicated part is in test mode. Supplier should not ship.04/17/2019 V/R 002040CHRY15FCA US
FCA US - Shipping ScheduleSegment:Position:Loop:Level:Usage:Max Use:Purpose:Syntax Notes:Semantic Notes:Comments:Notes:PER Administrative Communications Contact040LINOptionalDetailOptional6To identify a person or office to whom administrative communications should bedirected1 If PER03 is present, then PER04 is required.This segment is used to convey information about the contact person.Examples:PER EX CONTACT USING PLANT TE 3139565741PER EX DON LAWES TE 3139561107Ref.Des.PER01Data Element SummaryDataElement Name366Contact Function CodeBaseAttributesM ID 2/2UserAttributesMCode identifying the major duty or responsibility of the person or group namedEXExpeditorPER0293NameFree-form nameO AN 1/35AN 1/19The name of the contact person.PER03365Communication Number QualifierO ID 2/2Code identifying the type of communication numberTEPER04364TelephoneCommunication NumberC AN 7/256AN10/256Complete communications number including country or area code when applicableThe telephone number of the contact person.PER05365Communication Number QualifierO ID 2/2Code identifying the type of communication numberPER06364Communication NumberO AN 7/256Complete communications number including country or area code when applicable04/17/2019 V/R 002040CHRY16FCA US
FCA US - Shipping ScheduleSegment:Position:Loop:Level:Usage:Max Use:Purpose:Syntax Notes:Semantic Notes:Comments:PO4 Item Physical Details050LINOptionalDetailOptional 1To specify the physical qualities, packaging, weights, and dimensions relating to theitem1 If PO402 is present, then PO403 is required.2 If PO405 is present, then at least one of PO406 or PO407 is required.3 If PO408 is present, then PO409 is required.4 If PO413 is present, then at least one of PO410 PO411 or PO412 is required.12PO403 - The "Unit of Measure Code" (Element #355) in this segment position isfor purposes of defining the pack (PO401) /size (PO402) measure whichindicates the quantity in the inner pack unit. Example: If the carton contains 2412-Ounce packages, it would be described as follows: Element 356 24;Element 357 12; Element 355 OZ.PO410 defines the unit of measure for PO408, PO409, and PO410.Data Element SummaryRef.Des.PO401DataElement Name356PackNumber of inner pack units per outer pack unitBaseAttributesO N0 1/6UserAttributesNotUsedPO402357SizeO R 1/8PO403355Unit or Basis for Measurement CodeC ID 2/2Code identifying the basic unit of measurement.PO404103Packaging CodeO ID 5/5NotUsedPO405187Weight QualifierO ID 1/2NotUsedPO406384Gross Weight per PackC R 1/9NotUsedPO407355Unit or Basis for Measurement CodeC ID 2/2NotUsedPO408385Gross Volume per PackO R 1/9NotUsedPO409355Unit or Basis for Measurement CodeC ID 2/2NotUsedPO41082LengthC R 1/6NotUsedPO411189WidthC R 1/8Not04/17/2019 V/R 002040CHRY17FCA US
FCA US - Shipping ScheduleUsedPO41265HeightC R 1/6NotUsedPO413355Unit or Basis for Measurement CodeC ID 2/2NotUsed04/17/2019 V/R 002040CHRY18FCA US
FCA US - Shipping ScheduleSegment:Position:Loop:Level:Usage:Max Use:Purpose:Syntax Notes:Semantic Notes:Comments:Notes:REF Reference Numbers070LINOptionalDetailOptional12To specify identifying numbers.Used to identify the receiving dock, line feed, or drop point of the Ship Tolocation.Examples:REF DK MAINREF LF 0001REF RL 25H1Data Element SummaryRef.Des.REF01DataElement Name128Reference Number QualifierCode qualifying the Reference Number.BaseAttributesM ID 2/2DKDock NumberLFAssembly Line Feed LocationM1Material Storage LocationRLReserve Assembly Line Feed LocationUserAttributesMDrop ZoneRUREF02127Route NumberReference NumberM AN 1/30MAN 1/8Reference number or identification number as defined for a particular TransactionSet, or as specified by the Reference Number Qualifier.The FCA assigned name for the location described in REF01.For Assembly Kanban:If REF01 'RL', the bay within the plant (i.e. nearest pole);If REF01 'LF', the station;If REF01 'RU', the internal plant route;If REF01 'M1', the material storage location;REF03352Description04/17/2019 V/R 002040CHRYO AN 1/8019NotUsedFCA US
FCA US - Shipping ScheduleSegment:Position:Loop:Level:Usage:Max Use:Purpose:Syntax Notes:Semantic Notes:Comments:Notes:N1 Name081N1OptionalDetailOptional1To 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.1This segment, used alone, provides the most efficient method of providingorganizational identification. To obtain this efficiency the "ID Code" (N104)must provide a key to the table maintained by the transaction processing party.This N1 will be used only for those suppliers that should ship to a plant extension.The N1 loop in the detail area is used to identify physical locations for ShipFrom, Ship To and the FCA plant for which the material is ultimately intended.The Ship To location will usually be the FCA plant or a plant extension.These values must be echoed back to FCA in the ASN (856). If these codes arenot accurate, contact your buyer.Example:N1 ST 92 04010 (FCA plant or plant extension)Data Element SummaryRef.Des.N101DataBaseElement NameAttributes98Entity Identifier CodeM ID 2/2Code identifying an organizational entity or a physical location.STUserAttributesMShip ToN10293NameC AN 1/35N10366Identification Code QualifierC ID 1/2NotUsedCode designating the system/method of code structure used for Identification Code(67)92N10467Assigned by BuyerIdentification CodeC ID 2/17Code identifying a party.04/17/2019 V/R 002040CHRY20FCA US
FCA US - Shipping ScheduleSegment:Position:Loop:Level:Usage:Max Use:Purpose:Syntax Notes:Semantic Notes:Comments:Notes:FST Forecast Schedule090FSTOptionalDetailOptional1To specify the forecasted dates and quantities1 If either FST06 or FST07 is present, then the other is required.2 If either FST08 or FST09 is present, then the other is required.1As qualified by FST02 and FST03, FST04 represents either a discrete forecastdate, the first date of a forecasted bucket (weekly, monthly, quarterly, etc.) orthe start date of a flexible interval.2 If FST03 - "F" (indicating flexible interval), then FST04 and FST05 arerequired. FST04 would be used for the start date of the flexible interval andFST05 would be used for the end date of the flexible interval.3 FST06 - To qualify time in FST07. The purpose of the FST07 element is toexpress the specific time of day in a 24-hour clock, to satisfy "just-in-time"requirements. As an alternative, the ship/delivery pattern segment (SDP) may beused to define an approximate time, such as "AM" or "PM".One FST segment represents one of the thirty calendar days for FCA plants.Examples:FST 100 C D 910303 010 0800FST 100 C D 910322FST 0 C D 910323FST 1366 D D 910325FST 360 D D 910326 010 0800Data Element SummaryRef.Des.FST01DataElement Name380QuantityBaseAttributesM R 1/10UserAttributesMR 1/8Numeric value of quantityCumulative quantity for the day.FST02680Forecast QualifierM ID 1/1Code specifying the sender's confidence level of the forecast data.AMImmediateFor Kanban only: will be used for Hot Pick List Immediate/Emergency requirements.FST03681CFirmDPlanningForecast Timing QualifierM ID 1/1MCode specifying interval grouping of the forecastDDiscrete04/17/2019 V/R 002040CHRY21FCA US
FCA US - Shipping ScheduleFST04373DateM DT 6/6MDate (YYMMDD)If FST03 'D', the day the parts are scheduled for shipment.FST05373DateFST06374Date/Time QualifierC ID 3/3Code specifying type of date or time, or both date and time010FST07337O DT 6/6NotUsedRequested ShipTimeC TM 4/4Time expressed in 24-hour clock time (HHMMSS) (Time range: 000000 through235959)Requested ship time.FST08128Reference Number QualifierC ID 2/2NotUsedFST09127Reference NumberC AN 1/30NotAN 7/30Used04/17/2019 V/R 002040CHRY22FCA US
FCA US - Shipping ScheduleSegment:Position:Loop:Level:Usage:Max Use:Purpose:Syntax Notes:Semantic Notes:Comments:Notes:DTM To specify pertinent dates and times1 At least one of DTM02 or DTM03 is required.For Common SDS, the segment will be used for delivery date and time when onlyone shipment for the day.Example:DTM 002 930730 0930 CTData Element SummaryRef.Des.DTM01DataBaseElement NameAttributes374Date/Time QualifierM ID 3/3Code specifying type of date or time, or both date and time002DTM02373UserAttributesMDelivery RequestedDateC DT 6/6Date (YYMMDD)Date qualified by DTM01.DTM03337TimeC TM 4/4Time expressed in 24-hour clock time (HHMMSS) (Time range: 000000 through235959)DTM04623Time CodeCode identifying the time.O ID 2/2CDCentral Daylight TimeCTCentral Time04/17/2019 V/R 002040CHRY23FCA US
FCA US - Shipping ScheduleSegment:Position:Loop:Level:Usage:Max Use:Purpose:Syntax Notes:Semantic Notes:Comments:Notes:JIT Just-In-Time Schedule120JITOptionalDetailOptional1To identify the specific shipping/delivery time in terms of a 24-hour clock and theassociated quantity.The JIT loop is used when there are more than one shipment for the dayspecified in the FST. All times are Eastern Time.Used by Metered Parts Kanban.Not used by (traditional) Kanban.Example:JIT 100 0800Data Element SummaryRef.Des.JIT01DataElement Name380QuantityBaseAttributesM R 1/10UserAttributesMNumeric value of quantityQuantity to be shipped.JIT02337TimeM TM 4/4MTime expressed in 24-hour clock time (HHMMSS) (Time range: 000000 through235959)Time of Shipment in 24 hour clock (HHMM).04/17/2019 V/R 002040CHRY24FCA US
FCA US - Shipping ScheduleSegment:Position:Loop:Level:Usage:Max Use:Purpose:Syntax Notes:Semantic Notes:Comments:Ref.Des.DTM01DTM To spec
requirements sent in a previous 862 transaction; a code value of '03' (Delete) in the BSS01 element will be issued for removing a part or shipment requirement sent on a previous 862 transaction. Data for other part numbers previously transmitted and not included in this transmission must be retained. 04/17/2019 V/R 002040CHRY 1 FCA US
