visteon corporation edi implementation guideline 830 planning schedule...

Visteon Corporation

EDI Implementation Guideline

830

Planning Schedule with Release Capability

X12 Version 004010

Visteon EDI Implementation Guide - 830 Transaction - Release for Production Material

ASC X12 - version 004010 Updated 9/11/2000 1

830 Planning Schedule with Release Capability

Functional Group ID=PS Introduction: This Draft Standard for Trial Use contains the format and establishes the data contents of the Planning Schedule with 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 to the transfer of forecasting/material release information between organizations. The planning schedule transaction may be used in various ways or in a combination of ways, such as: (1) a simple forecast; (2) a forecast with the buyer's authorization for the seller to commit to resources, such as labor or material; (3) a forecast that is also used as an order release mechanism, containing such elements as resource authorizations, period-to-date cumulative quantities, and specific ship/delivery patterns for requirements that have been represented in "buckets," such as 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. Notes: Heading: Pos. Seg. Req. Loop Notes and No. ID Name Des. Max.Use Repeat Comments M 010 ST Transaction Set Header M 1 M 020 BFR Beginning Segment for Planning Schedule M 1 Not Used 025 XPO Preassigned Purchase Order Numbers O >1 Not Used 040 CUR Currency O 1 D 050 REF Reference Identification O 12 Not Used 060 PER Administrative Communications Contact O 3 Not Used 070 TAX Tax Reference O 3 Not Used 080 FOB F.O.B. Related Instructions O 1 Not Used 090 CTP Pricing Information O 25 Not Used 100 SAC Service, Promotion, Allowance, or Charge

Information O 25

Not Used 110 CSH Sales Requirements O 1 Not Used 120 ITD Terms of Sale/Deferred Terms of Sale O 2 Not Used 130 DTM Date/Time Reference O 10 Not Used 140 PID Product/Item Description O 200 Not Used 150 MEA Measurements O 40 Not Used 160 PWK Paperwork O 25 Not Used 170 PKG Marking, Packaging, Loading O 25 Not Used 180 TD1 Carrier Details (Quantity and Weight) O 2 Not Used 190 TD5 Carrier Details (Routing Sequence/Transit

Time) O 12

Not Used 200 TD3 Carrier Details (Equipment) O 12 Not Used 210 TD4 Carrier Details (Special Handling, or

Hazardous Materials, or Both) O 5

Not Used 220 MAN Marks and Numbers O 10 LOOP ID - N1 200 Rec 230 N1 Name O 1



D 240 N2 Additional Name Information O 2 D 250 N3 Address Information O 2 D 260 N4 Geographic Location O 1 Not Used 270 REF Reference Identification O 12 Not Used 280 PER Administrative Communications Contact O 3 Not Used 290 FOB F.O.B. Related Instructions O 1 LOOP ID - LM >1 Not Used 300 LM Code Source Information O 1 Not Used 310 LQ Industry Code M 100 Detail: Pos. Seg. Req. Loop Notes and No. ID Name Des. Max.Use Repeat Comments

LOOP ID - LIN >1 M 010 LIN Item Identification M 1 Rec 020 UIT Unit Detail O 1 Not Used 021 DTM Date/Time Reference O 10 Not Used 030 CUR Currency O 1 Not Used 060 PO3 Additional Item Detail O 25 Not Used 070 CTP Pricing Information O 25 Not Used 080 PID Product/Item Description O 1000 Not Used 090 MEA Measurements O 40 Not Used 100 PWK Paperwork O 25 Not Used 110 PKG Marking, Packaging, Loading O 25 Not Used 120 PO4 Item Physical Details O 1 Not Used 130 PRS Part Release Status O 1 D 140 REF Reference Identification O 12 D 150 PER Administrative Communications Contact O 3 Not Used 170 SAC Service, Promotion, Allowance, or Charge

Information O 25

Not Used 180 ITD Terms of Sale/Deferred Terms of Sale O 2 Not Used 190 TAX Tax Reference O 3 Not Used 200 FOB F.O.B. Related Instructions O 1 Not Used 210 LDT Lead Time O 12 Not Used 220 QTY Quantity O >1 n1 Rec 230 ATH Resource Authorization O 20 Not Used 240 TD1 Carrier Details (Quantity and Weight) O 1 Not Used 250 TD5 Carrier Details (Routing Sequence/Transit

Time) O 12

Not Used 260 TD3 Carrier Details (Equipment) O 12 Not Used 270 TD4 Carrier Details (Special Handling, or

Hazardous Materials, or Both) O 5

Not Used 280 MAN Marks and Numbers O 10 Not Used 290 DD Demand Detail O 10 LOOP ID - SLN 100 Not Used 300 SLN Subline Item Detail O 1 Not Used 310 PID Product/Item Description O 1000 Not Used 315 NM1 Individual or Organizational Name O 10 LOOP ID - N1 200 Not Used 320 N1 Name O 1 Not Used 330 N2 Additional Name Information O 2 Not Used 340 N3 Address Information O 2 Not Used 350 N4 Geographic Location O 1 Not Used 360 REF Reference Identification O 12 Not Used 370 PER Administrative Communications Contact O 3



Not Used 380 FOB F.O.B. Related Instructions O 1 LOOP ID - LM >1 Not Used 390 LM Code Source Information O 1 Not Used 400 LQ Industry Code M 100 LOOP ID - FST >1 Not Used 410 FST Forecast Schedule O 1 n2 Not Used 415 QTY Quantity O >1 Not Used 420 SDQ Destination Quantity O 50 LOOP ID - LM >1 Not Used 430 LM Code Source Information O 1 Not Used 440 LQ Industry Code M 100 LOOP ID - SDP 260 Must Use 450 SDP Ship/Delivery Pattern O 1 Must Use 460 FST Forecast Schedule O 260 LOOP ID - SHP 25 D 470 SHP Shipped/Received Information O 1 D 480 REF Reference Identification O 5 Summary: Pos. Seg. Req. Loop Notes and No. ID Name Des. Max.Use Repeat Comments Must Use 010 CTT Transaction Totals O 1 n3 M 020 SE Transaction Set Trailer M 1 Transaction Set Notes 1. QTY is used to specify supplemental quantities relevant to the forecast function. However, QTY is

not related to the actual forecast quantity in the FST segments. 2. At least one occurrence of segment FST is required, either in the FST loop or within the SDP loop.

These two loops are mutually exclusive. 3. Number of line items (CTT01) is the accumulation of the number of LIN segments. If used, hash

total (CTT02) is the sum of the values of the quantities (FST01) for each FST segment.



Segment: ST Transaction Set Header

Position: 010 Loop: Level: Heading Usage: Mandatory Max Use: 1 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: Example: ST~830~0032 ̂

Data Element Summary

Ref. Data Des. Element Name Attributes M ST01 143 Transaction Set Identifier Code M ID 3/3 Code uniquely identifying a Transaction Set 830 Planning Schedule with Release Capability M ST02 329 Transaction Set Control Number M AN 4/9 Identifying control number that must be unique within the transaction set

functional group assigned by the originator for a transaction set The value in this element must match the value in the element SE02.



Segment: BFR Beginning Segment for Planning Schedule

Position: 020 Loop: Level: Heading Usage: Mandatory Max Use: 1 Purpose: To indicate the beginning of a planning schedule transaction set; whether a ship

or delivery based forecast; and related forecast envelope dates Syntax Notes: 1 At least one of BFR02 or BFR03 is required. Semantic Notes: 1 If BFR01 contains the value "04" (Net Change), BFR09 is required. 2 BFR02 is the identifying number for a forecast assigned by the

orderer/purchaser. 3 BFR06 is the forecast horizon start date: The date when the forecast horizon

(envelope) begins. 4 BFR07 is the forecast horizon end date: The date when the forecast horizon

(envelope) ends. 5 BFR08 is the date forecast generated: The date the forecast data was

generated. 6 BFR09 is the date forecast updated: The date the forecast was updated with

"net change" data. (Used only when data element 353 in BFR01 contains the value "04", meaning net change.)

Comments: Notes: The intent of this segment is to provide information for the entire transaction. Some of

the information (e.g. quantity qualifier - element 05) may be overridden by segments later in the transaction. Example: BFR~00~~30000020~DL~C~20000731~20001001~20000709 ̂


Ref. Data Des. Element Name Attributes M BFR01 353 Transaction Set Purpose Code M ID 2/2 Code identifying purpose of transaction set 00 Original Used to show the first release after the annual

cumulative reset 01 Cancellation 02 Add 05 Replace Usual value for this transaction X BFR02 127 Reference Identification C AN 1/30 Reference information as defined for a particular Transaction Set or as

specified by the Reference Identification Qualifier >> BFR03 328 Release Number C AN 1/30 Number identifying a release against a Purchase Order previously placed by the

parties involved in the transaction Unique release number generated by Visteon's SAP system M BFR04 675 Schedule Type Qualifier M ID 2/2 Code identifying the type of dates used when defining a shipping or delivery

time in a schedule or forecast DL Delivery Based Delivery based planning numbers are used in the FST

segments of this transaction SH Shipment Based



Shipment based palnning numbers are used in the FST segments in this transaction.

M BFR05 676 Schedule Quantity Qualifier M ID 1/1 Code identifying the type of quantities used when defining a schedule or

forecast C Cumulative Quantities Cumulative quantities are used in the FST segments

except when specifically overridden in the FST segment.

M BFR06 373 Date M DT 8/8 Date expressed as CCYYMMDD Date from which the part quantity accumulation begins. D BFR07 373 Date O DT 8/8 Date expressed as CCYYMMDD Planning horizon end date - last Sunday of the period in the forecast. M BFR08 373 Date M DT 8/8 Date expressed as CCYYMMDD Date this release was issued. X BFR09 373 Date O DT 8/8 Date expressed as CCYYMMDD X BFR10 367 Contract Number O AN 1/30 Contract number D BFR11 324 Purchase Order Number O AN 1/22 Identifying number for Purchase Order assigned by the orderer/purchaser Contains the Purchase Order number for this release, when appropriate. X BFR12 783 Planning Schedule Type Code O ID 2/2 Code identifying type of planning schedule used Refer to 004010 Data Element Dictionary for acceptable code values. X BFR13 306 Action Code O ID 1/2 Code indicating type of action Refer to 004010 Data Element Dictionary for acceptable code values.



Segment: REF Reference Identification

Position: 050 Loop: Level: Heading Usage: Optional (Dependent) Max Use: 12 Purpose: To specify identifying information Syntax Notes: 1 At least one of REF02 or REF03 is required. Semantic Notes: 1 REF04 contains data relating to the value cited in REF02. Comments:

Notes: This segment is used to communicate general notes which apply to the entire transaction (when used with the H7 qualifier, and in this position) In other places in the transaction, the REF segment will convey different information. Example: REF~H7~~Generic Description^


Ref. Data Des. Element Name Attributes M REF01 128 Reference Identification Qualifier M ID 2/3 Code qualifying the Reference Identification H7 Standard Clause General Information -> REF01 will contain this value

when used to convey transaction level information. X REF02 127 Reference Identification C AN 1/30 Reference information as defined for a particular Transaction Set or as

specified by the Reference Identification Qualifier >> REF03 352 Description C AN 1/80 A free-form description to clarify the related data elements and their content Freeform text X REF04 C040 Reference Identifier O To identify one or more reference numbers or identification numbers as

specified by the Reference Qualifier X C04001 128 Reference Identification Qualifier M ID 2/3 Code qualifying the Reference Identification Refer to 004010 Data Element Dictionary for acceptable code values. X C04002 127 Reference Identification M AN 1/30 Reference information as defined for a particular Transaction Set or as

specified by the Reference Identification Qualifier X C04003 128 Reference Identification Qualifier C ID 2/3 Code qualifying the Reference Identification Refer to 004010 Data Element Dictionary for acceptable code values. X C04004 127 Reference Identification C AN 1/30 Reference information as defined for a particular Transaction Set or as


specified by the Reference Identification Qualifier



Segment: N1 Name

Position: 230 Loop: N1 Optional (Recommended) Level: Heading Usage: Optional (Recommended) 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 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. Notes: The N1 loop in the heading level is used to identify the release issuer (buyer), the seller

(supplier), the bill-to location, the ship-to location, and/or the ship-from location. NB. Leading zeroes inVisteon codes are essential. Examples: N1~BY~T BEYER~92~0000002020 ̂ N1~ST~~92~0004000047 ̂


Ref. Data Des. Element Name Attributes M N101 98 Entity Identifier Code M ID 2/3 Code identifying an organizational entity, a physical location, property or an

individual BT Bill-to-Party Used only if different from ship-to BY Buying Party (Purchaser) Used only if different from ship-to IC Intermediate Consignee SE Selling Party Used only if different than ship-from SF Ship From ST Ship To D N102 93 Name C AN 1/60 Free-form name >> N103 66 Identification Code Qualifier C ID 1/2 Code designating the system/method of code structure used for Identification

Code (67) 92 Assigned by Buyer or Buyer's Agent >> N104 67 Identification Code C AN 2/80 Code identifying a party or other code Will contain the Visteon location code assigned by Visteon's SAP system X N105 706 Entity Relationship Code O ID 2/2 Code describing entity relationship Refer to 004010 Data Element Dictionary for acceptable code values. X N106 98 Entity Identifier Code O ID 2/3 Code identifying an organizational entity, a physical location, property or an

individual Refer to 004010 Data Element Dictionary for acceptable code values.



Segment: N2 Additional Name Information

Position: 240 Loop: N1 Optional (Recommended) Level: Heading Usage: Optional (Dependent) Max Use: 2 Purpose: To specify additional names or those longer than 35 characters in length Syntax Notes: Semantic Notes: Comments:

Notes: This segment will be used only when necessary. It is most likely to be used for direct ship information, but not only for that. Example: N2~Attn - Receiving^


Ref. Data Des. Element Name Attributes M N201 93 Name M AN 1/60 Free-form name D N202 93 Name O AN 1/60 Free-form name



Segment: N3 Address Information

Position: 250 Loop: N1 Optional (Recommended) Level: Heading Usage: Optional (Dependent) Max Use: 2 Purpose: To specify the location of the named party Syntax Notes: Semantic Notes: Comments:

Notes: This segment will be used only when necessary. It is most likely to be used for direct ship information, but not only for that. Example: N3~North Side Delivery Door~473 Industrial Parkway ̂


Ref. Data Des. Element Name Attributes M N301 166 Address Information M AN 1/55 Address information D N302 166 Address Information O AN 1/55 Address information



Segment: N4 Geographic Location

Position: 260 Loop: N1 Optional (Recommended) Level: Heading Usage: Optional (Dependent) Max Use: 1 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.

Notes: This segment will be used only when necessary. It is most likely to be used for direct ship information, but not only for that. Example: N4~Columbus~OH~43002 ̂


Ref. Data Des. Element Name Attributes R N401 19 City Name O AN 2/30 Free-form text for city name D N402 156 State or Province Code O ID 2/2 Code (Standard State/Province) as defined by appropriate government agency Required for US and Canadian addresses. D N403 116 Postal Code O ID 3/15 Code defining international postal zone code excluding punctuation and blanks

(zip code for United States) Provided whenever available. D N404 26 Country Code O ID 2/3 Code identifying the country Used only for non-US addresses. X N405 309 Location Qualifier C ID 1/2 Code identifying type of location Refer to 004010 Data Element Dictionary for acceptable code values. X N406 310 Location Identifier O AN 1/30 Code which identifies a specific location



Segment: LIN Item Identification

Position: 010 Loop: LIN Mandatory Level: Detail Usage: Mandatory Max Use: 1 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: Used to specify Visteon part information. This segment begins the detail loop. The purchase order number can be included in this segment. NB. Leading zeros in part numbers are essential. Example: LIN~0001~BP~000000000004020106~PO~5500001971~PL~00010 ̂


Ref. Data Des. Element Name Attributes >> LIN01 350 Assigned Identification O AN 1/20 Alphanumeric characters assigned for differentiation within a transaction set This number, along with the release number, should be sent back to Visteon in

the 856 which the supplier creates upon shipment of the parts ordered. These numbers are used by the Visteon SAP system to properly match the supplier generated 856 to the appropriate release.

M LIN02 235 Product/Service ID Qualifier M ID 2/2 Code identifying the type/source of the descriptive number used in

Product/Service ID (234) BP Buyer's Part Number Visteon's part number or Visteon's customer's part

number follows. M LIN03 234 Product/Service ID M AN 1/48 Identifying number for a product or service Contains the Visteon supplied part number. Visteon part numbers are 18

characters long and leading zeroes are important. Part numbers supplied by Visteon customers may be a different length and contain imbedded special characters.

D LIN04 235 Product/Service ID Qualifier C ID 2/2



Code identifying the type/source of the descriptive number used in Product/Service ID (234)

PO Purchase Order Number Used when there is a PO number for this item. D LIN05 234 Product/Service ID C AN 1/48 Identifying number for a product or service Contains the Purchase Order number for the item. D LIN06 235 Product/Service ID Qualifier C ID 2/2 Code identifying the type/source of the descriptive number used in

Product/Service ID (234) PL Purchaser's Order Line Number Used when there is a purchase order line item number. D LIN07 234 Product/Service ID C AN 1/48 Identifying number for a product or service This will contain the PO line number when available. If available, it should be

returned in the ASN for this shipment. X LIN08 235 Product/Service ID Qualifier C ID 2/2 Code identifying the type/source of the descriptive number used in

Product/Service ID (234) Refer to 004010 Data Element Dictionary for acceptable code values. X LIN09 234 Product/Service ID C AN 1/48 Identifying number for a product or service X LIN10 235 Product/Service ID Qualifier C ID 2/2 Code identifying the type/source of the descriptive number used in






Product/Service ID (234) Refer to 004010 Data Element Dictionary for acceptable code values.



X LIN21 234 Product/Service ID C AN 1/48 Identifying number for a product or service X LIN22 235 Product/Service ID Qualifier C ID 2/2 Code identifying the type/source of the descriptive number used in





Product/Service ID (234) Refer to 004010 Data Element Dictionary for acceptable code values. X LIN31 234 Product/Service ID C AN 1/48 Identifying number for a product or service



Segment: UIT Unit Detail

Position: 020 Loop: LIN Mandatory Level: Detail Usage: Optional (Recommended) Max Use: 1 Purpose: To specify item unit data Syntax Notes: 1 If UIT03 is present, then UIT02 is required. Semantic Notes: Comments:

Notes: This segment indicates the unit of measure for all quantities relating to the line item. Example: UIT~PC^


Ref. Data Des. Element Name Attributes M UIT01 C001 Composite Unit of Measure M To identify a composite unit of measure (See Figures Appendix for examples

of use) M C00101 355 Unit or Basis for Measurement Code M ID 2/2 Code specifying the units in which a value is being expressed, or manner in

which a measurement has been taken Unit of Measure. Should be used on the ASNs returned for this part's

shipments. Refer to 004010 Data Element Dictionary for acceptable code values. X C00102 1018 Exponent O R 1/15 Power to which a unit is raised X C00103 649 Multiplier O R 1/10 Value to be used as a multiplier to obtain a new value X C00104 355 Unit or Basis for Measurement Code O ID 2/2 Code specifying the units in which a value is being expressed, or manner in

which a measurement has been taken Refer to 004010 Data Element Dictionary for acceptable code values. X C00105 1018 Exponent O R 1/15 Power to which a unit is raised X C00106 649 Multiplier O R 1/10 Value to be used as a multiplier to obtain a new value X C00107 355 Unit or Basis for Measurement Code O ID 2/2 Code specifying the units in which a value is being expressed, or manner in

which a measurement has been taken Refer to 004010 Data Element Dictionary for acceptable code values. X C00108 1018 Exponent O R 1/15 Power to which a unit is raised X C00109 649 Multiplier O R 1/10 Value to be used as a multiplier to obtain a new value X C00110 355 Unit or Basis for Measurement Code O ID 2/2 Code specifying the units in which a value is being expressed, or manner in

which a measurement has been taken Refer to 004010 Data Element Dictionary for acceptable code values. X C00111 1018 Exponent O R 1/15 Power to which a unit is raised X C00112 649 Multiplier O R 1/10 Value to be used as a multiplier to obtain a new value



X C00113 355 Unit or Basis for Measurement Code O ID 2/2 Code specifying the units in which a value is being expressed, or manner in

which a measurement has been taken Refer to 004010 Data Element Dictionary for acceptable code values. X C00114 1018 Exponent O R 1/15 Power to which a unit is raised X C00115 649 Multiplier O R 1/10 Value to be used as a multiplier to obtain a new value X UIT02 212 Unit Price C R 1/17 Price per unit of product, service, commodity, etc. X UIT03 639 Basis of Unit Price Code O ID 2/2 Code identifying the type of unit price for an item Refer to 004010 Data Element Dictionary for acceptable code values.




Position: 140 Loop: LIN Mandatory Level: Detail Usage: Optional (Dependent) Max Use: 12 Purpose: To specify identifying information Syntax Notes: 1 At least one of REF02 or REF03 is required. Semantic Notes: 1 REF04 contains data relating to the value cited in REF02. Comments:

Notes: Shows any relevant item level text. Example: REF~L1~~ITEM RELATED TEXT ̂


Ref. Data Des. Element Name Attributes M REF01 128 Reference Identification Qualifier M ID 2/3 Code qualifying the Reference Identification L1 Letters or Notes Used for item level notes. X REF02 127 Reference Identification C AN 1/30 Reference information as defined for a particular Transaction Set or as

specified by the Reference Identification Qualifier D REF03 352 Description C AN 1/80 A free-form description to clarify the related data elements and their content This description is most likely to be used when Visteon has received

information from one of its customers and wishes to pass it along to the supplier. It is unlikely that Visteon originated orders will contain any value here.

X REF04 C040 Reference Identifier O To identify one or more reference numbers or identification numbers as







Segment: PER Administrative Communications Contact

Position: 150 Loop: LIN Mandatory Level: Detail Usage: Optional (Dependent) 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:

Notes: This segment conveys interpersonal communication information. It does not show network or telecommunication contact information. It is used to convey a person's name and telephone number. Example: PER~EX~Ken Wido~TE~248-458-2002^


Ref. Data Des. Element Name Attributes M PER01 366 Contact Function Code M ID 2/2 Code identifying the major duty or responsibility of the person or group named EX Expeditor General office exeditor. D PER02 93 Name O AN 1/60 Free-form name Contains Visteon contact's name or contact code. R PER03 365 Communication Number Qualifier C ID 2/2 Code identifying the type of communication number TE Telephone Visteon contact's telephone number follows, when

appropriate. R PER04 364 Communication Number C AN 1/80 Complete communications number including country or area code when

applicable Contains Visteon contact's telephone number when appropriate. X PER05 365 Communication Number Qualifier C ID 2/2 Code identifying the type of communication number Refer to 004010 Data Element Dictionary for acceptable code values. X PER06 364 Communication Number C AN 1/80 Complete communications number including country or area code when

applicable X PER07 365 Communication Number Qualifier C ID 2/2 Code identifying the type of communication number Refer to 004010 Data Element Dictionary for acceptable code values. X PER08 364 Communication Number C AN 1/80 Complete communications number including country or area code when

applicable X PER09 443 Contact Inquiry Reference O AN 1/20 Additional reference number or description to clarify a contact number



Segment: ATH Resource Authorization

Position: 230 Loop: LIN Mandatory Level: Detail Usage: Optional (Recommended) Max Use: 20 Purpose: To specify resource authorizations (i.e., finished labor, material, etc.) in the

planning schedule Syntax Notes: 1 At least one of ATH02 or ATH03 is required. 2 If ATH03 is present, then ATH05 is required. 3 If ATH04 is present, then ATH05 is required. Semantic Notes: 1 ATH02 is the resource authorization through date: The date through which

the buyer authorizes the seller to commit the resource defined in element ATH01.

2 ATH03 is the current cumulative requirements quantity: The cumulative quantity that has been authorized to date from the cumulative start date (ATH05) through the resource authorization through date (ATH02).

3 ATH05 is the cumulative start date: The date where the cumulative quantity count starts. This date might be the start date of a contract period, a calendar or fiscal year, or other.

Comments: 1 It is imperative that negotiations defining financial commitment have previously occurred and are agreed to by both buyer and seller.

2 ATH04 is the maximum cumulative requirements quantity: The maximum cumulative quantity that has been authorized to date from the cumulative start date (ATH05) through the resource authorization through date (ATH02). This is a high water mark. If the forecast decreases, the current cumulative requirements quantity also decreases, but the maximum cumulative requirements quantity does not decrease.

Notes: The quantity elements in this segment are always cumulative quantities. There will be at most one ATH~FI and one ATH~MT for each LIN. Examples: ATH~FI~20000828~49~~20000731 ̂ ATH~MT~20000903~75~~20000731 ̂


Ref. Data Des. Element Name Attributes M ATH01 672 Resource Authorization Code M ID 2/2 Code identifying the resource which the buyer is authorizing the seller to

commit to FI Finished (Labor, Material, and Overhead/Burden) Fabrication MT Material Raw Material only >> ATH02 373 Date C DT 8/8 Date expressed as CCYYMMDD Last day of the week (Sunday). >> ATH03 380 Quantity C R 1/15 Numeric value of quantity Cumulative quantity authorized through date in ATH02. X ATH04 380 Quantity O R 1/15 Numeric value of quantity R ATH05 373 Date C DT 8/8



Date expressed as CCYYMMDD Cumulative quantity start date. (Beginning of inventory start date.)



Segment: SDP Ship/Delivery Pattern

Position: 450 Loop: SDP Optional (Must Use) Level: Detail Usage: Optional (Must Use) Max Use: 1 Purpose: To identify specific ship/delivery requirements Syntax Notes: Semantic Notes: Comments: 1 The intent of this segment is to define the routine ship or delivery patterns,

as required, when order quantities are in "buckets", such as weekly, monthly. Ship/delivery patterns eliminate the need to transmit discrete quantities and dates for each required shipment or delivery. It is assumed that a "bucketed" quantity is to be divided equally by the ship/delivery pattern. For example, a weekly quantity of 100 with a delivery pattern of Monday and Wednesday would result in 50 to be delivered on Monday and 50 to be delivered on Wednesday.

Notes: Visteon does not specify shipment and delivery patterns in the 830. Other transactions are used for that information, or it is agreed upon with the supplier at contract time. This segment is included only because valid X12 syntax requires it to use the FST segment following. Example: SDP~Y~Y^


Ref. Data Des. Element Name Attributes M SDP01 678 Ship/Delivery or Calendar Pattern Code M ID 1/2 Code which specifies the routine shipments, deliveries, or calendar pattern Constant value 'Y'. Y None (Also Used to Cancel or Override a Previous

Pattern) M SDP02 679 Ship/Delivery Pattern Time Code M ID 1/1 Code which specifies the time for routine shipments or deliveries Constant value 'Y'. Y None (Also Used to Cancel or Override a Previous

Pattern) X SDP03 678 Ship/Delivery or Calendar Pattern Code O ID 1/2 Code which specifies the routine shipments, deliveries, or calendar pattern Refer to 004010 Data Element Dictionary for acceptable code values. X SDP04 679 Ship/Delivery Pattern Time Code O ID 1/1 Code which specifies the time for routine shipments or deliveries Refer to 004010 Data Element Dictionary for acceptable code values. X SDP05 678 Ship/Delivery or Calendar Pattern Code O ID 1/2 Code which specifies the routine shipments, deliveries, or calendar pattern Refer to 004010 Data Element Dictionary for acceptable code values. X SDP06 679 Ship/Delivery Pattern Time Code O ID 1/1 Code which specifies the time for routine shipments or deliveries Refer to 004010 Data Element Dictionary for acceptable code values. X SDP07 678 Ship/Delivery or Calendar Pattern Code O ID 1/2 Code which specifies the routine shipments, deliveries, or calendar pattern Refer to 004010 Data Element Dictionary for acceptable code values. X SDP08 679 Ship/Delivery Pattern Time Code O ID 1/1



Code which specifies the time for routine shipments or deliveries Refer to 004010 Data Element Dictionary for acceptable code values.



Segment: FST Forecast Schedule

Position: 460 Loop: SDP Optional (Must Use) Level: Detail Usage: Optional (Must Use) Max Use: 260 Purpose: To specify the forecasted dates and quantities Syntax Notes: 1 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. Semantic Notes: 1 If FST03 equals "F" (indicating flexible interval), then FST04 and FST05

are required. FST04 would be used for the start date of the flexible interval and FST05 would be used for the end date of the flexible interval.

Comments: 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 date of a flexible interval.

2 FST06 qualifies the time in FST07. The purpose of the FST07 element is to express 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 be used to define an approximate time, such as a.m. or p.m.

Notes: This segment shows cumulative quantities for all discrete forecast qualifiers (FST02 = 'D'). For strike protection (FST02 = 'S') and firm orders (FST02 = 'C', rarely used) this segment will show net quantities. Examples: FST~10~D~W~20000807 ̂weekly forecast FST~50~D~F~20000731~20001001 ̂monthly forecast


Ref. Data Des. Element Name Attributes M FST01 380 Quantity M R 1/15 Numeric value of quantity Normally this is cumulative quantity. It is net quantity only when FST02= "S"

or "C". M FST02 680 Forecast Qualifier M ID 1/1 Code specifying the sender's confidence level of the forecast data or an action

associated with a forecast C Firm D Planning S Strike Protection M FST03 681 Forecast Timing Qualifier M ID 1/1 Code specifying interval grouping of the forecast D Discrete Used for Strike Protection only. F Flexible Interval (from Date X through Date Y) Monthly forecast. W Weekly Bucket (Monday through Sunday) Weekly forecast M FST04 373 Date M DT 8/8 Date expressed as CCYYMMDD For flexible intervals (FST03="F"), this is the cumulative quantity start date.

For weekly intervals (FST03="W"), this is the week start date (Monday). For strike protection (FST03="D"), this is the strike protection date.

D FST05 373 Date O DT 8/8 Date expressed as CCYYMMDD



For flexible intervals, this is the period ending date (Sunday). It is not used for weekly or discrete intervals.

D FST06 374 Date/Time Qualifier C ID 3/3 Code specifying type of date or time, or both date and time 002 Delivery Requested 010 Requested Ship D FST07 337 Time C TM 4/8 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)

Shipment or delivery time when used. X FST08 128 Reference Identification Qualifier C ID 2/3 Code qualifying the Reference Identification Refer to 004010 Data Element Dictionary for acceptable code values. X FST09 127 Reference Identification C AN 1/30 Reference information as defined for a particular Transaction Set or as

specified by the Reference Identification Qualifier X FST10 783 Planning Schedule Type Code O ID 2/2 Code identifying type of planning schedule used Refer to 004010 Data Element Dictionary for acceptable code values.



Segment: SHP Shipped/Received Information

Position: 470 Loop: SHP Optional (Dependent) Level: Detail Usage: Optional (Dependent) Max Use: 1 Purpose: To specify shipment and/or receipt information Syntax Notes: 1 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. 4 If SHP05 is present, then SHP03 is required. Semantic Notes: 1 SHP04 is the date shipped, delivered, received, or the cumulative quantity

start date (as qualified by SHP03). 2 SHP06 is the cumulative quantity end date. Comments: 1 The SHP segment is used to communicate shipment, delivery, or receipt

information and may include discrete or cumulative quantities, dates, and times.

2 If SHP01 equals "02", "07", "08", "09", or "10" (indicating cumulative quantities), then SHP04 and SHP06 are required to identify the start and end dates of the quantity count.

Notes: This is based on the last ASN received and processed by Visteon's SAP system. The cumulative quantity is equal to the cumulative receipts plus the in-transit quantities through the last ASN received and processed by Visteon's SAP system. Example: SHP~01~10~011~20000803~~20000803 ̂net quantity from last ASN SHP~02~10~011~20000731~~20000803 ̂cum quantity from last ASN


Ref. Data Des. Element Name Attributes >> SHP01 673 Quantity Qualifier O ID 2/2 Code specifying the type of quantity 01 Discrete Quantity Discrete quantity shipped or delivered (depends on

whether the ASN was for a shipment or delivery based transaction).

02 Cumulative Quantity Cumulative quantity shipped or delivered (depends on

whether the ASN was for a shipment or delivery based transaction).

>> SHP02 380 Quantity C R 1/15 Numeric value of quantity >> SHP03 374 Date/Time Qualifier C ID 3/3 Code specifying type of date or time, or both date and time 011 Shipped 035 Delivered >> SHP04 373 Date C DT 8/8 Date expressed as CCYYMMDD Shipped/delivery date for discrete quantities.

Beginning inventory date for cumulative quantities. X SHP05 337 Time C TM 4/8 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) D SHP06 373 Date O DT 8/8 Date expressed as CCYYMMDD If present, this is the date of the last shipment/delivery processed. X SHP07 337 Time O TM 4/8 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)




Position: 480 Loop: SHP Optional (Dependent) Level: Detail Usage: Optional (Dependent) Max Use: 5 Purpose: To specify identifying information Syntax Notes: 1 At least one of REF02 or REF03 is required. Semantic Notes: 1 REF04 contains data relating to the value cited in REF02. Comments:

Notes: Shows the last ASN number received and processed by Visteon's SAP system. It will follow the SHP segment with '01' in SHP01. There will only be one of these segments in the SHP loop. Example: REF~SI~11.010.080-V123~Area V123 ̂


Ref. Data Des. Element Name Attributes M REF01 128 Reference Identification Qualifier M ID 2/3 Code qualifying the Reference Identification SI Shipper's Identifying Number for Shipment (SID) A unique number (to the shipper) assigned by the shipper

to identify the shipment >> REF02 127 Reference Identification C AN 1/30 Reference information as defined for a particular Transaction Set or as

specified by the Reference Identification Qualifier Contains last shipment ID number (ASN number) processed. D REF03 352 Description C AN 1/80 A free-form description to clarify the related data elements and their content This description is most likely to be used when Visteon has received

information from one of its customers and wishes to pass it along to the supplier. It is unlikely that Visteon originated orders will contain any value here.

X REF04 C040 Reference Identifier O To identify one or more reference numbers or identification numbers as



specified by the Reference Identification Qualifier X C04005 128 Reference Identification Qualifier C ID 2/3 Code qualifying the Reference Identification Refer to 004010 Data Element Dictionary for acceptable code values.



X C04006 127 Reference Identification C AN 1/30 Reference information as defined for a particular Transaction Set or as




Segment: CTT Transaction Totals

Position: 010 Loop: Level: Summary Usage: Optional (Must Use) Max Use: 1 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. Notes: Contains hash totals for forecast quantities (FST01) in this transaction set.

Example: CTT~1~150 ̂


Ref. Data Des. Element Name Attributes M CTT01 354 Number of Line Items M N0 1/6 Total number of line items in the transaction set Count of the number of LIN segments in this transaction. R CTT02 347 Hash Total O R 1/10 Sum of values of the specified data element. All values in the data element will

be summed without regard to decimal points (explicit or implicit) or signs. Truncation will occur on the left most digits if the sum is greater than the maximum size of the hash total of the data element. Example: -.0018 First occurrence of value being hashed. .18 Second occurrence of value being hashed. 1.8 Third occurrence of value being hashed. 18.01 Fourth occurrence of value being hashed. --------- 1855 Hash total prior to truncation. 855 Hash total after truncation to three-digit field.

Hash total of quantities released. This is the sum of the FST01 elements. If the hash total overflows the element size, the high order digits are truncated and the low order digits are used.

X CTT03 81 Weight C R 1/10 Numeric value of weight X CTT04 355 Unit or Basis for Measurement Code C ID 2/2 Code specifying the units in which a value is being expressed, or manner in

which a measurement has been taken Refer to 004010 Data Element Dictionary for acceptable code values. X CTT05 183 Volume C R 1/8 Value of volumetric measure X CTT06 355 Unit or Basis for Measurement Code C ID 2/2 Code specifying the units in which a value is being expressed, or manner in

which a measurement has been taken Refer to 004010 Data Element Dictionary for acceptable code values. X CTT07 352 Description O AN 1/80 A free-form description to clarify the related data elements and their content



Segment: SE Transaction Set Trailer

Position: 020 Loop: Level: Summary Usage: Mandatory Max Use: 1 Purpose: To indicate the end of the transaction set and provide the count of the

transmitted segments (including the beginning (ST) and ending (SE) segments) Syntax Notes: Semantic Notes: Comments: 1 SE is the last segment of each transaction set.

Notes: Example: SE~22~0032 ̂

Data Element Summary Ref. Data Des. Element Name Attributes M SE01 96 Number of Included Segments M N0 1/10 Total number of segments included in a transaction set including ST and SE

segments M SE02 329 Transaction Set Control Number M AN 4/9 Identifying control number that must be unique within the transaction set

functional group assigned by the originator for a transaction set The value in this element must match the value in the element ST02.


ASC X12 - version 004010 1 Updated 8/11/2000

Visteon Corporation EDI Transaction: 830

Planning Schedule EDI Version: X12 004010

Example #1: 830 Planning Schedule with a consignment material

EDI FLAT FILE FORMAT DETAILED DESCRIPTION

ST~830~0032 ̂ Transaction 830 BFR~00~~30000020~DL~C~20000731~20001001~20000709^

New scheduling agreement, which is delivery(DL) based. Quantities are cumulative (C). Part quantity accumulation start date is 07/31/2000. Last day of the week of last segment 10/01/2000. Release issue date is 07/09/2000.

REF~H7~~Generic Description^ Notes relevant to the transaction N1~BY~T BEYER~92~0000002020 ̂ Buying party is 0000002020 N1~SF~Vendor~92~0000010081 ̂ Ship From vendor 0000010081 N1~ST~3PL/OE-Groveport Ohio Warehouse~92~0004000047 ̂

Ship to location 0004000047

LIN~0001~BP~000000000004020106~PO~5500001971~PL~00010^

Buyers part number 000000000004020106, under purchase order 5500001971, for PO line item 10

UIT~PC^ Unit of measure is piece (PC) REF~L1~~ITEM RELATED TEXT^ Item related notes PER~EX~Ken Wido~TE~248-458-2002^ Visteon Contact is Ken Wido at phone number 248-458-2002 ATH~FI~20000828~49~~20000731 ̂ The finished quantity of 49 is authorized through 08/28/00, with a

start date of 07/31/00. ATH~MT~20000903~75~~20000731 ̂ The material quantity of 75 is authorized through 09/03/00, with a

start date of 07/31/00. SDP~Y~Y^ Constant; segment required by X12 syntax. FST~10~D~W~20000807 ̂ Cum quantity of 10 is planned for the week starting on 08/07/00 FST~20~D~W~20000814 ̂ Cum quantity of 20 is planned for the week starting on 08/14/00



FST~30~D~W~20000821 ̂ Cum quantity of 30 is planned for the week starting on 08/21/00 FST~40~D~W~20000828 ̂ Cum quantity of 40 is planned for the week starting on 08/28/00 FST~50~D~F~20000731~20001001 ̂ Cum quantity of 50 is planned for the month ending 10/01/00 SHP~01~10~011~20000711~~20000711 ̂ Discrete quantity of 10 was shipped 07/11/2000 and transaction was

processed the same day. REF~SI~11.010.080-V123~Area V123 ̂ The last shipment number (ASN number) processed was 11.010.080-

V123 CTT~1~150 ̂ Transaction hash totals SE~22~0032 ̂ Trailer record -number of segments within this transaction set and

transaction set control number.





Example #2: 830 Planning Schedule with a non-consignment material


ST~830~0022 ̂ Transaction 830 BFR~00~~30000021~DL~C~20000731~20000917~20000609 ̂ Add scheduling agreement, which is delivery(DL) based.

Quantities are cumulative (C). Part quantity accumulation start date is 07/31/00 . Last day of the week of last segment 09/17/00 . Release issue date is 06/09/00 .

REF~H7~~Generic Description^ Overall transaction related notes N1~BY~T BEYER~92~0000002020 ̂ Buying party is 0000002020 N1~SF~Vendor~92~0000010081 ̂ Ship From vendor 0000010081 N1~ST~Exel/Visteon Aftermarket Warehouse~92~0000002020 ̂ Ship to location 0000002020 LIN~0001~BP~000000000004020121~PO~5500001965~PL~0010 ̂ Buyers part number 000000000004020121, under purchase order

5500001965, PO line item 10 UIT~PC^ Unit of measure is piece (PC) REF~L1~~ITEM RELATED TEXT^ Item related notes PER~EX~Ken Wido~TE~248-458-2002^ Visteon Contact is Ken Wido at phone number 248-458-2002 ATH~FI~20000828~49~~20000731 ̂ The finished quantity of 49 is authorized through 08/28/00, with a

start date of 07/31/00. ATH~MT~20000903~75~~20000731 ̂ The material quantity of 75 is authorized through 09/03/00, with a

start date of 07/31/00. SDP~Y~Y^ Constant; segment required by X12 syntax. FST~34~D~W~20000807 ̂ Cum quantity of 34 is planned for the week starting on 08/07/00 FST~40~D~W~20000814 ̂ Cum quantity of 40 is planned for the week starting on 08/14/00



FST~48~D~W~20000821 ̂ Cum quantity of 48 is planned for the week starting on 08/21/00 FST~54~D~W~20000828 ̂ Cum quantity of 54 is planned for the week starting on 08/28/00 FST~55~D~W~20000904 ̂ Cum quantity of 55 is planned for the week starting on 09/04/00 FST~56~D~W~20000911 ̂ Cum quantity of 56 is planned for the week starting on 09/11/00 SHP~01~10~011~20000605~~20000605 ̂ Discrete quantity of 10 was shipped 06/05/2000 REF~SI~11.010.081-V888~Area V888 ̂ The last shipment number processed was 11.010.080-V888 CTT~1~287 ̂ Transaction hash totals SE~23~0022 ̂ Trailer record -number of segments within this transaction set and






Example #3: 830 Planning Schedule with a non-consignment material


ST~830~0038 ̂ Transaction 830 BFR~00~~30000023~DL~C~20000601~20000903~20000616 ̂ Add scheduling agreement, which is delivery(DL) based. Quantities are

cumulative (C). Party quantity accumulation start date is 06/01/00 . Last day of the week of last segment 09/03/00 . Release issue date is 06/16/00 .

REF~H7~~Generic Description^ Notes related to the overall transaction N1~BY~Visteon~92~VIS1 ̂ Buying party is VIS1 N1~SF~Vendor~92~0000010081 ̂ Ship From vendor 10081 N1~ST~3PL/OE-Groveport Ohio Warehouse~92~0000012046 ̂

Ship to plant 0000012046

LIN~0001~BP~000000000004020122~PO~5500001965~PL~0010^

Buyers part number 000000000004020122, under purchase order 5500001965, line item number 0010

UIT~PC^ Unit basis is by piece (PC) PER~EX~Ken Wido~TE~248-458-2002^ Visteon Contact is Ken Wido at phone number 248-458-2002 ATH~FI~20000630~40~~20000601 ̂ The finished quantity of 40 is authorized through 06/30/00, with a start

date of 06/01/00. ATH~MT~20000901~75~~20000601 ̂ The material quantity of 55 is authorized through 09/01/00, with a start

date of 06/01/00. SDP~Y~Y^ Constant; segment required by X12 syntax. FST~20~D~W~20000605 ̂ Cum quantity of 20 is planned for a week from start date of 06/05/00 to

06/11/00 FST~26~D~W~20000612 ̂ Cum quantity of 26 is planned for a week from start date of 06/12/00 to

06/18/00










09/03/00 SHP~01~55~011~20000528~~20000529 ̂ Discrete quantity of 55 was shipped on 05/28/2000 and last ASN was

processed 05/29/00 REF~SI~11.010.080-V965~Area V965 ̂ The last shipment number processed was 11.010.080-V965 CTT~1~359 ̂ Transaction hash totals SE~25~0038 ̂ Trailer record -number of segments within this transaction set and


visteon corporation edi implementation guideline 830 planning schedule...

Documents