Transcription
830 Planning ScheduleX12 Vers. 4010: 830 Planning ScheduleAuthor:Trading Partner:Modified:Notes:Adam TenorioCSA Suppliers1/5/2017207 South West StreetAuburn, IN 4670[email protected]: 440.263.5616Fax: 260.927.3201
1/5/2017Planning Schedule with Release Capability - 830Table of Contents830. . .Planning Schedule with Release Capability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PH 1ISA. . .Interchange Control Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PH 3GS. . .Functional Group Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PH 5ST. . .Transaction Set Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PH 7. . .BFR Beginning Segment for Planning Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PH 8. .CUR Currency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PH 10. .PER Administrative Communications Contact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PH 11N1. .Loop Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PH 12N1. .Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PH 13N2. .Additional Name Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PH 14N3. .Address Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PH 15N4. .Geographic Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PH 16LIN. .Loop Item Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PH 17LIN. .Item Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PH 18UIT. .Unit Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PH 20PID. .Product/Item Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PH 21. .PER Administrative Communications Contact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PH 22. .ATH Resource Authorization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PH 23. .FST Loop Forecast Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PH 24. .FST Forecast Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PH 25. .SHP Loop Shipped/Received Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PH 27. .SHP Shipped/Received Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PH 28. .REF Reference Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PH 29. .CTT Transaction Totals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PH 30SE. .Transaction Set Trailer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PH 31GE. .Functional Group Trailer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PH 32IEA. .Interchange Control Trailer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PH 33CSA 830 4010.ecsiFor internal use only
1/5/2017Planning Schedule with Release Capability - 830830Planning Schedule with ReleaseCapabilityFunctional Group PSPurpose: This Draft Standard for Trial Use contains the format and establishes the data contents of the PlanningSchedule 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 practicerelative to the transfer of forecasting/material release information between organizations.The planning scheduletransaction may be used in various ways or in a combination of ways, such as: (1) a simple forecast; (2) a forecastwith the buyer's authorization for the seller to commit to resources, such as labor or material; (3) a forecast that isalso used as an order release mechanism, containing such elements as resource authorizations, period-to-datecumulative 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 purchaseorders, as required, because the order release capability eliminates the need for discrete generation of purchaseorders.Not Defined:PosIdSegment NameISAGSInterchange Control HeaderFunctional Group HeaderPosIdSegment Name010020STBFR040060CURPERTransaction Set HeaderBeginning Segment forPlanning ScheduleCurrencyAdministrativeCommunications ContactReqMax UseMM11RepeatNotesUsageReqMax UseMM11Must useMust useOO13Must useUsedOO12Must useUsedOO21UsedUsedReqMax UseMust useMust useHeading:LOOP ID - ional NameInformationAddress InformationGeographic LocationIdSegment NameDetail:PosLOOP ID - LIN010020080150LINUITPIDPER230ATHFSTItem IdentificationUnit DetailProduct/Item DescriptionAdministrativeCommunications ContactResource AuthorizationMOOO1110003O20UsageMust useMust useUsedUsedUsed 1Forecast ScheduleO1LOOP ID - SHPCSA 830 4010.ecsNotes 1LOOP ID - FST410RepeatN2/410LN2/410Must use251For internal use only
1/5/2017Planning Schedule with Release Capability - 830PosIdSegment ce IdentificationReqMax UseRepeatNotesUsageO1Must useO5UsedReqMax UseOM11ReqMax UseMM11Summary:PosIdSegment Name010020CTTSETransaction TotalsTransaction Set TrailerRepeatNotesUsageN3/010Must useMust useNotesUsageNot Defined:PosIdSegment NameGEIEAFunctional Group TrailerInterchange Control TrailerRepeatMust useMust useNotes:2/410L2/4103/010At least one occurrence of segment FST is required, either in the FST loop or within the SDP loop. Thesetwo loops are mutually exclusive.At least one occurrence of segment FST is required, either in the FST loop or within the SDP loop. Thesetwo loops are mutually exclusive.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.CSA 830 4010.ecs2For internal use only
1/5/2017Planning Schedule with Release Capability - 830ISA Interchange Control HeaderPos:Max: 1Not Defined - MandatoryLoop: N/AElements: 16User Option (Usage): Must usePurpose: To start and identify an interchange of zero or more functional groups and interchange-related controlsegmentsElement Summary:RefIdElement NameISA01I01Authorization Information QualifierReqTypeMin/MaxUsageMID2/2Must useDescription: Code to identify the type of information in the Authorization InformationCodeList Summary (Total Codes: 7, Included: 1)Code Name00ISA02I02No Authorization Information Present (No Meaningful Information in I02)Authorization InformationMAN10/10Must useDescription: Information used for additional identification or authorization of theinterchange sender or the data in the interchange; the type of information is set by theAuthorization Information Qualifier (I01)ISA03I03Security Information QualifierMID2/2Must useDescription: Code to identify the type of information in the Security InformationCodeList Summary (Total Codes: 2, Included: 1)Code Name00ISA04I04No Security Information Present (No Meaningful Information in I04)Security InformationMAN10/10Must useDescription: This is used for identifying the security information about the interchangesender or the data in the interchange; the type of information is set by the SecurityInformation Qualifier (I03)ISA05I05Interchange ID QualifierMID2/2Must useDescription: Qualifier to designate the system/method of code structure used to designatethe sender or receiver ID element being qualifiedCodeList Summary (Total Codes: 38, Included: 1)Code Name01ISA06I06Duns (Dun & Bradstreet)Interchange Sender IDMAN15/15Must useDescription: Identification code published by the sender for other parties to use as thereceiver ID to route data to them; the sender always codes this value in the sender IDelementISA07I05Interchange ID QualifierMID2/2Must useDescription: Qualifier to designate the system/method of code structure used to designatethe sender or receiver ID element being qualifiedCodeList Summary (Total Codes: 38, Included: 1)CSA 830 4010.ecs3For internal use only
1/5/2017Planning Schedule with Release Capability - 830Code Name01ISA08I07Duns (Dun & Bradstreet)Interchange Receiver IDMAN15/15Must useDescription: Identification code published by the receiver of the data; When sending, it isused by the sender as their sending ID, thus other parties sending to them will use this as areceiving ID to route data to themISA09I08Interchange DateMDT6/6Must useMTM4/4Must useMID1/1Must useDescription: Date of the interchangeISA10I09Interchange TimeDescription: Time of the interchangeISA11I10Interchange Control StandardsIdentifierDescription: Code to identify the agency responsible for the control standard used by themessage that is enclosed by the interchange header and trailerAll valid standard codes are used. (Total Codes: 1)ISA12I11Interchange Control Version NumberMID5/5Must useDescription: Code specifying the version number of the interchange control segmentsCodeList Summary (Total Codes: 14, Included: 2)Code Name00300 Standard Issued as ANSI X12.5-199200401 Draft Standards for Trial Use Approved for Publication by ASC X12 ProceduresReview Board through October 1997ISA13I12Interchange Control NumberMN09/9Must useDescription: A control number assigned by the interchange senderISA14I13Acknowledgment RequestedMID1/1Must useDescription: Code sent by the sender to request an interchange acknowledgment (TA1)CodeList Summary (Total Codes: 2, Included: 1)Code Name0ISA15I14No Acknowledgment RequestedUsage IndicatorMID1/1Must useDescription: Code to indicate whether data enclosed by this interchange envelope is test,production or informationCodeList Summary (Total Codes: 3, Included: 1)Code NamePISA16I15Production DataComponent Element SeparatorM1/1Must useDescription: Type is not applicable; the component element separator is a delimiter andnot a data element; this field provides the delimiter used to separate component dataelements within a composite data structure; this value must be different than the dataelement separator and the segment terminatorCSA 830 4010.ecs4For internal use only
1/5/2017Planning Schedule with Release Capability - 830Pos:GS Functional Group HeaderMax: 1Not Defined - MandatoryLoop: N/AElements: 8User Option (Usage): Must usePurpose: To indicate the beginning of a functional group and to provide control informationElement Summary:RefIdElement NameGS01479Functional Identifier CodeReqTypeMin/MaxUsageMID2/2Must useDescription: Code identifying a group of application related transaction setsCodeList Summary (Total Codes: 240, Included: 1)Code NamePSGS02142Planning Schedule with Release Capability (830)Application Sender's CodeMAN2/15Must useDescription: Code identifying party sending transmission; codes agreed to by tradingpartnersGS03124Application Receiver's CodeMAN2/15Must useDescription: Code identifying party receiving transmission; codes agreed to by tradingpartnersGS04373DateMDT8/8Must useTM4/8Must useDescription: Date expressed as CCYYMMDDGS05337TimeMDescription: Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, orHHMMSSD, or HHMMSSDD, where H hours (00-23), M minutes (00-59), S integerseconds (00-59) and DD decimal seconds; decimal seconds are expressed as follows: D tenths (0-9) and DD hundredths (00-99)GS0628Group Control NumberMN01/9Must useDescription: Assigned number originated and maintained by the senderGS07455Responsible Agency CodeMID1/2Must useDescription: Code identifying the issuer of the standard; this code is used in conjunctionwith Data Element 480CodeList Summary (Total Codes: 2, Included: 1)Code NameXGS08480Accredited Standards Committee X12Version / Release / Industry IdentifierCodeMAN1/12Must useDescription: Code indicating the version, release, subrelease, and industry identifier of theEDI standard being used, including the GS and GE segments; if code in DE455 in GSsegment is X, then in DE 480 positions 1-3 are the version number; positions 4-6 are therelease and subrelease, level of the version; and positions 7-12 are the industry or tradeassociation identifiers (optionally assigned by user); if code in DE455 in GS segment is T,then other formats are allowedCSA 830 4010.ecs5For internal use only
1/5/2017RefPlanning Schedule with Release Capability - 830IdElement NameReqTypeMin/MaxUsageCodeList Summary (Total Codes: 39, Included: 1)CodeName004010 Draft Standards Approved for Publication by ASC X12 Procedures Review Boardthrough October 1997Semantics:1. GS04 is the group date.2. GS05 is the group time.3. The data interchange control number GS06 in this header must be identical to the same data element in theassociated functional group trailer, GE02.Comments:1. A functional group of related transaction sets, within the scope of X12 standards, consists of a collection ofsimilar transaction sets enclosed by a functional group header and a functional group trailer.CSA 830 4010.ecs6For internal use only
1/5/2017Planning Schedule with Release Capability - 830Pos: 010ST Transaction Set HeaderMax: 1Heading - MandatoryLoop: N/AElements: 2User Option (Usage): Must usePurpose: To indicate the start of a transaction set and to assign a control numberElement Summary:RefIdElement NameST01143Transaction Set Identifier CodeReqTypeMin/MaxUsageMID3/3Must use4/9Must useDescription: Code uniquely identifying a Transaction SetCodeList Summary (Total Codes: 298, Included: 1)Code Name830ST02329Planning Schedule with Release CapabilityTransaction Set Control NumberMANDescription: Identifying control number that must be unique within the transaction setfunctional group assigned by the originator for a transaction setSemantics:1. The transaction set identifier (ST01) used by the translation routines of the interchange partners to select theappropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).CSA 830 4010.ecs7For internal use only
1/5/2017Planning Schedule with Release Capability - 830Pos: 020BFR Beginning Segment forMax: 1Heading - MandatoryPlanning ScheduleLoop: N/AElements: 9User Option (Usage): Must usePurpose: To indicate the beginning of a planning schedule transaction set; whether a ship or delivery basedforecast; and related forecast envelope datesElement Summary:RefIdElement NameBFR01353Transaction Set Purpose CodeReqTypeMin/MaxUsageMID2/2Must use1/30Must useDescription: Code identifying purpose of transaction setCodeList Summary (Total Codes: 65, Included: 1)Code Name05BFR02127ReplaceReference IdentificationXANDescription: Reference information as defined for a particular Transaction Set or asspecified by the Reference Identification QualifierBFR03328Release NumberXAN1/30Must useDescription: Number identifying a release against a Purchase Order previously placed bythe parties involved in the transactionBFR04675Schedule Type QualifierMID2/2Must useDescription: Code identifying the type of dates used when defining a shipping or deliverytime in a schedule or forecastCodeList Summary (Total Codes: 11, Included: 1)Code NameDLBFR05676Delivery BasedSchedule Quantity QualifierMID1/1Must useDescription: Code identifying the type of quantities used when defining a schedule orforecastCodeList Summary (Total Codes: 4, Included: 1)Code NameABFR06373Actual Discrete QuantitiesDateMDT8/8Must useDT8/8Must useDT8/8Must useAN1/22Must useDescription: Date expressed as CCYYMMDDBFR07373DateODescription: Date expressed as CCYYMMDDBFR08373DateMDescription: Date expressed as CCYYMMDDBFR11324CSA 830 4010.ecsPurchase Order NumberO8For internal use only
1/5/2017RefPlanning Schedule with Release Capability - 830IdElement NameReqTypeMin/MaxUsageDescription: Identifying number for Purchase Order assigned by the orderer/purchaserSyntax Rules:1. R0203 - At least one of BFR02 or BFR03 is required.Semantics:1.2.3.4.5.6.If BFR01 contains the value "04" (Net Change), BFR09 is required.BFR02 is the identifying number for a forecast assigned by the orderer/purchaser.BFR06 is the forecast horizon start date: The date when the forecast horizon (envelope) begins.BFR07 is the forecast horizon end date: The date when the forecast horizon (envelope) ends.BFR08 is the date forecast generated: The date the forecast data was generated.BFR09 is the date forecast updated: The date the forecast was updated with "net change" data. (Used onlywhen data element 353 in BFR01 contains the value "04", meaning net change.)CSA 830 4010.ecs9For internal use only
1/5/2017Planning Schedule with Release Capability - 830Pos: 040CUR CurrencyMax: 1Heading - OptionalLoop: N/AElements: 2User Option (Usage): Must usePurpose: To specify the currency (dollars, pounds, francs, etc.) used in a transactionElement Summary:RefIdElement NameCUR0198Entity Identifier CodeReqTypeMin/MaxUsageMID2/3Must useDescription: Code identifying an organizational entity, a physical location, property or anindividualCodeList Summary (Total Codes: 1312, Included: 1)Code NameZZCUR02100Mutually DefinedCurrency CodeMID3/3Must useDescription: Code (Standard ISO) for country in whose currency the charges are specifiedUser Note 1: ZZZ - As indicated on the Purchase OrderSyntax Rules:1.2.3.4.5.6.7.8.9.10.11.12.13.14.C0807 - If CUR08 is present, then CUR07 is required.C0907 - If CUR09 is present, then CUR07 is required.L101112 - If CUR10 is present, then at least one of CUR11 or CUR12 is required.C1110 - If CUR11 is present, then CUR10 is required.C1210 - If CUR12 is present, then CUR10 is required.L131415 - If CUR13 is present, then at least one of CUR14 or CUR15 is required.C1413 - If CUR14 is present, then CUR13 is required.C1513 - If CUR15 is present, then CUR13 is required.L161718 - If CUR16 is present, then at least one of CUR17 or CUR18 is required.C1716 - If CUR17 is present, then CUR16 is required.C1816 - If CUR18 is present, then CUR16 is required.L192021 - If CUR19 is present, then at least one of CUR20 or CUR21 is required.C2019 - If CUR20 is present, then CUR19 is required.C2119 - If CUR21 is present, then CUR19 is required.Comments:1. See Figures Appendix for examples detailing the use of the CUR segment.CSA 830 4010.ecs10For internal use only
1/5/2017Planning Schedule with Release Capability - 830Pos: 060PER AdministrativeMax: 3Heading - OptionalCommunications ContactLoop: N/AElements: 2User Option (Usage): UsedPurpose: To identify a person or office to whom administrative communications should be directedElement Summary:RefIdElement NamePER01366Contact Function CodeReqTypeMin/MaxUsageMID2/2Must useDescription: Code identifying the major duty or responsibility of the person or groupnamedPER0293NameOAN1/60UsedDescription: Free-form nameSyntax Rules:1. P0304 - If either PER03 or PER04 is present, then the other is required.2. P0506 - If either PER05 or PER06 is present, then the other is required.3. P0708 - If either PER07 or PER08 is present, then the other is required.CSA 830 4010.ecs11For internal use only
1/5/2017Planning Schedule with Release Capability - 830Pos: 230Loop NameRepeat: 200OptionalLoop: N1Elements: N/AUser Option (Usage): Must usePurpose: To identify a party by type of organization, name, and codeLoop Summary:PosIdSegment Name230240250260N1N2N3N4NameAdditional Name InformationAddress InformationGeographic LocationCSA 830 4010.ecs12ReqMax UseOOOO1221RepeatUsageMust useUsedUsedUsedFor internal use only
1/5/2017Planning Schedule with Release Capability - 830Pos: 230N1 NameMax: 1Heading - OptionalLoop: N1Elements: 4User Option (Usage): Must usePurpose: To identify a party by type of organization, name, and codeElement Summary:RefIdElement NameN10198Entity Identifier CodeReqTypeMin/MaxUsageMID2/3Must useDescription: Code identifying an organizational entity, a physical location, property or anindividualCodeList Summary (Total Codes: 1312, Included: 2)Code NameSTSUN10293Ship ToSupplier/ManufacturerNameXAN1/60Must useXID1/2Must useDescription: Free-form nameN10366Identification Code QualifierDescription: Code designating the system/method of code structure used for IdentificationCode (67)CodeList Summary (Total Codes: 215, Included: 2)Code Name192N10467D-U-N-S Number, Dun & BradstreetAssigned by Buyer or Buyer's AgentIdentification CodeXAN2/80Must useDescription: Code identifying a party or other codeSyntax Rules:1. R0203 - At least one of N102 or N103 is required.2. P0304 - If either N103 or N104 is present, then the other is required.Comments:1. This segment, used alone, provides the most efficient method of providing organizational identification. Toobtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transactionprocessing party.2. N105 and N106 further define the type of entity in N101.CSA 830 4010.ecs13For internal use only
1/5/2017Planning Schedule with Release Capability - 830N2 Additional Name InformationPos: 240Max: 2Heading - OptionalLoop: N1Elements: 1User Option (Usage): UsedPurpose: To specify additional names or those longer than 35 characters in lengthElement Summary:RefIdElement NameN20193NameReqTypeMin/MaxUsageMAN1/60Must useDescription: Free-form nameCSA 830 4010.ecs14For internal use only
1/5/2017Planning Schedule with Release Capability - 830Pos: 250N3 Address InformationMax: 2Heading - OptionalLoop: N1Elements: 1User Option (Usage): UsedPurpose: To specify the location of the named partyElement Summary:RefIdElement NameN301166Address InformationReqTypeMin/MaxUsageMAN1/55Must useDescription: Address informationCSA 830 4010.ecs15For internal use only
1/5/2017Planning Schedule with Release Capability - 830Pos: 260N4 Geographic LocationMax: 1Heading - OptionalLoop: N1Elements: 3User Option (Usage): UsedPurpose: To specify the geographic place of the named partyElement Summary:RefIdElement NameN40119City NameReqTypeMin/MaxUsageOAN2/30Must useOID2/2Must useDescription: Free-form text for city nameN402156State or Province CodeDescription: Code (Standard State/Province) as defined by appropriate governmentagencyN403116Postal CodeOID3/15Must useDescription: Code defining international postal zone code excluding punctuation andblanks (zip code for United States)Syntax Rules:1. C0605 - If N406 is present, then N405 is required.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.CSA 830 4010.ecs16For internal use only
1/5/2017Planning Schedule with Release Capability - 830Pos: 010Loop Item IdentificationRepeat: 1MandatoryLoop: LINElements: N/AUser Option (Usage): Must usePurpose: To specify basic item identification dataLoop Summary:PosIdSegment Name010020080150230410470LINUITPIDPERATHItem IdentificationUnit DetailProduct/Item DescriptionAdministrative Communications ContactResource AuthorizationLoop FSTLoop SHPCSA 830 4010.ecs17ReqMax UseMOOOOOO111000320RepeatUsage 125Must useMust useUsedUsedUsedMust useMust useFor internal use only
1/5/2017Planning Schedule with Release Capability - 830Pos: 010LIN Item IdentificationMax: 1Detail - MandatoryLoop: LINElements: 5User Option (Usage): Must usePurpose: To specify basic item identification dataElement Summary:RefIdElement NameLIN01350Assigned ption: Alphanumeric characters assigned for differentiation within a transaction setUser Note 1: If the line number sent, it must be sent back in the same format in the 856LIN02235Product/Service ID QualifierMID2/2Must useDescription: Code identifying the type/source of the descriptive number used inProduct/Service ID (234)CodeList Summary (Total Codes: 477, Included: 1)Code NameBPLIN03234Buyer's Part NumberProduct/Service IDMAN1/48Must use2/2Must useDescription: Identifying number for a product or serviceLIN04235Product/Service ID QualifierXIDDescription: Code identifying the type/source of the descriptive number used inProduct/Service ID (234)CodeList Summary (Total Codes: 477, Included: 1)Code NamePOLIN05234Purchase Order NumberProduct/Service IDXAN1/48Must useDescription: Identifying number for a product or serviceSyntax Rules:1.2.3.4.5.6.7.8.9.10.11.12.13.14.P0405 - If either LIN04 or LIN05P0607 - If either LIN06 or LIN07P0809 - If either LIN08 or LIN09P1011 - If either LIN10 or LIN11P1213 - If either LIN12 or LIN13P1415 - If either LIN14 or LIN15P1617 - If either LIN16 or LIN17P1819 - If either LIN18 or LIN19P2021 - If either LIN20 or LIN21P2223 - If either LIN22 or LIN23P2425 - If either LIN24 or LIN25P2627 - If either LIN26 or LIN27P2829 - If either LIN28 or LIN29P3031 - If either LIN30 or LIN31CSA 830 4010.ecsis present, then the other is required.is present, then the other is required.is present, then the other is required.is present, then the other is required.is present, then the other is required.is present, then the other is required.is present, then the other is required.is present, then the other is required.is present, then the other is required.is present, then the other is required.is present, then the other is required.is present, then the other is required.is present, then the other is required.is present, then the other is required.18For internal use only
1/5/2017Planning Schedule with Release Capability - 830Semantics:1. LIN01 is the line item identificationComments: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.CSA 830 4010.ecs19For internal use only
1/5/2017Planning Schedule with Release Capability - 830Pos: 020UIT Unit DetailMax: 1Detail - OptionalLoop: LINElements: 1User Option (Usage): Must usePurpose: To specify item unit dataElement Summary:RefIdElement NameUIT01C001Composite Unit of MeasureReqTypeMCompMin/MaxUsageMust useDescription: To identify a composite unit of measure(See Figures Appendix for examplesof use)UIT01-01355Unit or Basis for Measurement CodeMID2/2Must useDescription: Code (Standard ISO) for unit of measure specifying the units in which avalue is being expressed, or manner in which a measurement has been taken.User Note 1: Can use any valid X12 code. This is determined by the plant.CodeList Summary (Total Codes: 794, Included: 3)Code NameEALBPCEachPoundPieceSyntax Rules:1. C0302 - If UIT03 is present, then UIT02 is required.CSA 830 4010.ecs20For internal use only
1/5/2017Planning Schedule with Release Capability - 830Pos: 080PID Product/Item DescriptionMax: 1000Detail - OptionalLoop: LINElements: 2User Option (Usage): UsedPurpose: To describe a product or process in coded or free-form formatElement Summary:RefIdElement NamePID01349Item Description TypeReqTypeMin/MaxUsageMID1/1Must use1/80UsedDescription: Code indicating the format of a descriptionPID05352Desc
1/5/2017 Planning Schedule with Release Capability - 830 CSA_830_4010.ecs 1 For internal use only 830Planning Schedule with Release Capability Functional Group PS Purpose: This Draft Standard for Trial Use contains the format and establishes the data contents of the Planning Schedule with Release Capability Transaction Set
