Transcription
01/19/10Purchase Order Change Request - Buyer Initiated - 860860 Purchase OrderChange Request - BuyerInitiatedX12/V4010/860: 860 Purchase Order Change Request - Buyer InitiatedVersion: 1.0 FinalAuthor:Publication:Trading Partner:Notes:Seagate860v4010Seagate B2BAnsi X12 EDI 860 to beused with OEM,Distribution or Retailpartners.1 2012 Seagate Technology LLC. For internal use only
01/19/10Purchase Order Change Request - Buyer Initiated - 860Table of Contents860Purchase Order Change Request - Buyer Initiated. 3ISAInterchange Control Header . 5GSFunctional Group Header. 7STTransaction Set Header . 9BCH Beginning Segment for Purchase Order Change . 10CUR Currency . 12TAX Tax Reference . 13FOB F.O.B. Related Instructions . 14ITDTerms of Sale/Deferred Terms of Sale . 15TD5 Carrier Details (Routing Sequence/Transit Time) . 17N9Loop N9 . 18N9Reference Identification . 19MSG Message Text . 20N1Loop N1 . 21N1Name . 22N3Address Information. 23N4Geographic Location . 24PER Administrative Communications Contact . 25POC Loop POC . 26POC Line Item Change . 27PIDLoop PID . 30PIDProduct/Item Description . 31SCH Loop SCH . 32SCH Line Item Schedule . 33N9Loop N9 . 34N9Reference Identification . 35MSG Message Text . 36CTT Loop CTT . 37CTT Transaction Totals . 38SETransaction Set Trailer . 39GEFunctional Group Trailer . 40IEAInterchange Control Trailer . 41Seagate860v40102 2012 Seagate Technology LLC. For internal use only
01/19/10Purchase Order Change Request - Buyer Initiated - 860860Purchase Order Change Request Buyer InitiatedFunctional Group PCPurpose: This Draft Standard for Trial Use contains the format and establishes the data contents of the PurchaseOrder Change Request - Buyer Initiated Transaction Set (860) for use within the context of an Electronic DataInterchange (EDI) environment. The transaction set can be used to provide the information required for the customaryand established business and industry practice relative to a purchase order change. This transaction can be used: (1)by a buyer to request a change to a previously submitted purchase order or (2) by a buyer to confirm acceptance of apurchase order change initiated by the seller or by mutual agreement of the two parties.Not Defined:PosIdISAGSSegment NameInterchange ControlHeaderFunctional Group HeaderReqMMax Use1M1RepeatNotesUsageMust usePage5Must use7UsageMust useMust AXFOBITD240TD5LOOP ID - N9285N9290MSGLOOP ID - N1300N1320N3330N4350PERSegment NameReqTransaction Set HeaderMBeginning Segment forMPurchase Order ChangeCurrencyOTax ReferenceOF.O.B. Related InstructionsOTerms of Sale/DeferredOTerms of SaleCarrier Details (RoutingOSequence/Transit Time)Max Use11RepeatNotes1 1 edUsedUsedUsed21222324251000Reference IdentificationMessage TextOO11000NameAddress InformationGeographic LocationAdministrativeCommunications ContactOOOO12 1 1ReqMax UseO1200Detail:PosIdLOOP ID - POC010POCLOOP ID - PID050PIDSegment NameLine Item 3536Used1000Product/Item DescriptionO1LOOP ID - SCH295SCHLine Item ScheduleO1LOOP ID - N9320N9330MSGReference IdentificationMessage TextOO11000Seagate860v4010Repeat 120010003 2012 Seagate Technology LLC. For internal use only
01/19/10Purchase Order Change Request - Buyer Initiated - 860Summary:PosIdLOOP ID - CTT010CTT030SESegment NameTransaction TotalsTransaction Set TrailerReqMax UseOM11ReqMMMax Use11Repeat1NotesN3/010LN3/010UsageUsedMust usePage373839UsageMust useMust usePage4041Not Defined:PosIdGEIEASegment NameFunctional Group TrailerInterchange Control TrailerRepeatNotesNotes:3/010L3/010Number of line items (CTT01) is the accumulation of the number of POC segments. If used, hash total(CTT02) is the sum of the value of quantities ordered (POC03) for each POC segment.Number of line items (CTT01) is the accumulation of the number of POC segments. If used, hash total(CTT02) is the sum of the value of quantities ordered (POC03) for each POC segment.Seagate860v40104 2012 Seagate Technology LLC. For internal use only
01/19/10Purchase Order Change Request - Buyer Initiated - 860Interchange Control HeaderISAPos: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:RefISA01IdI01Element NameAuthorization Information QualifierReqMTypeIDMin/Max2/2UsageMust useDescription: Code to identify the type of information in the Authorization InformationCode00ISA02I02NameNo Authorization Information Present (No Meaningful Information in I02)Authorization InformationOAN10/10Not usedDescription: Information used for additional identification or authorization of the interchangesender or the data in the interchange; the type of information is set by the AuthorizationInformation Qualifier (I01)ISA03I03Security Information QualifierMID2/2Must useDescription: Code to identify the type of information in the Security InformationCode00ISA04I04NameNo Security Information Present (No Meaningful Information in I04)Security InformationOAN10/10Not usedDescription: This is used for identifying the security information about the interchange senderor the data in the interchange; the type of information is set by the Security Information Qualifier(I03)ISA05I05Interchange ID QualifierMID2/2Must useDescription: Qualifier to designate the system/method of code structure used to designate thesender or receiver ID element being qualifiedRecord Name: Header Position 72Example: edi interchange qualifierISA06I06Interchange Sender IDMAN15/15Must useDescription: Identification code published by the sender for other parties to use as the receiverID to route data to them; the sender always codes this value in the sender ID elementRecord Name: Header Position 2Example: edi interchange partner idISA07I05Interchange ID QualifierMID2/2Must useDescription: Qualifier to designate the system/method of code structure used to designate thesender or receiver ID element being qualifiedCode01ISA08I07NameDuns (Dun & Bradstreet)Interchange Receiver IDMAN15/15Must useDescription: Identification code published by the receiver of the data; When sending, it is usedby the sender as their sending ID, thus other parties sending to them will use this as a receivingID to route data to themUser Note 1: Seagate Production ISA ID:098533326Seagate Test ISA ID:IISA09I08Seagate860v4010098533326TSTInterchange DateM5DT6/6Must use 2012 Seagate Technology LLC. For internal use only
01/19/10Purchase Order Change Request - Buyer Initiated - 860Description: Date of the interchangeRecord Name: Header Position 74Example: trans date (YYNNDDHH24MI)ISA10I09Interchange TimeMTM4/4Must useMID1/1Must useDescription: Time of the interchangeRecord Name: Header Position 74Example: trans date (YYMMDDHH24MI)ISA11I10Interchange Control Standards IdentifierDescription: Code to identify the agency responsible for the control standard used by themessage that is enclosed by the interchange header and trailerCodeUISA12I11NameU.S. EDI Community of ASC X12, TDCC, and UCSInterchange Control Version NumberMID5/5Must useDescription: Code specifying the version number of the interchange control segmentsCode00400ISA13I12NameStandard Issued as ANSI X12.5-1997Interchange Control NumberMN09/9Must use1/1Must useDescription: A control number assigned by the interchange senderRecord Name: Header Position 86Example: interchange control numberISA14I13Acknowledgment RequestedMIDDescription: Code sent by the sender to request an interchange acknowledgment (TA1)Code0ISA15I14NameNo Acknowledgment RequestedUsage IndicatorMID1/1Must useDescription: Code to indicate whether data enclosed by this interchange envelope is test,production or informationCodePTISA16I15NameProduction DataTest DataComponent Element SeparatorM1/1Must useDescription: Type is not applicable; the component element separator is a delimiter and not adata element; this field provides the delimiter used to separate component data elements withina composite data structure; this value must be different than the data element separator and thesegment terminatorUser Note 1:Sample Data: ISA*00**00*12*XXXXXXXXXXX *01*098533326*100107*07353*U*00400*000008102*o*P* Seagate860v40106 2012 Seagate Technology LLC. For internal use only
01/19/10Purchase Order Change Request - Buyer Initiated - 860Functional Group HeaderGSPos:Max: 1Not Defined - MandatoryLoop: N/AElements: 8User Option (Usage): Must usePurpose: To indicate the beginning of a functional group and to provide control informationElement Summary:RefGS01Id479Element NameFunctional Identifier CodeReqMTypeIDMin/Max2/2UsageMust useDescription: Code identifying a group of application related transaction setsCodePCGS02142NamePurchase Order Change Request - Buyer Initiated (860)Application Sender's CodeMAN2/15Must useDescription: Code identifying party sending transmission; codes agreed to by trading partnersRecord Name: Header Position 37Example: edi group partner idGS03124Application Receiver's CodeMAN2/15Must useDescription: Code identifying party receiving transmission; codes agreed to by trading partnersUser Note 1: Seagate Production GS ID:098533326Seagate Test GS ID:GS04373098533326TSTDateMDT8/8Must useMTM4/8Must useDescription: Date expressed as CCYYMMDDGS05337TimeDescription: 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 senderRecord Name: Header Position 100Example: group control numberGS07455Responsible Agency CodeMID1/2Must useDescription: Code identifying the issuer of the standard; this code is used in conjunction withData Element 480CodeXGS08480NameAccredited Standards Committee X12Version / Release / Industry Identifier CodeMAN1/12Must useDescription: Code indicating the version, release, subrelease, and industry identifier of the EDIstandard being used, including the GS and GE segments; if code in DE455 in GS segment is X,then in DE 480 positions 1-3 are the version number; positions 4-6 are the release andsubrelease, level of the version; and positions 7-12 are the industry or trade associationidentifiers (optionally assigned by user); if code in DE455 in GS segment is T, then other formatsare allowedCode004010NameDraft Standards Approved for Publication by ASC X12 Procedures Review Boardthrough October 1997Semantics:Seagate860v40107 2012 Seagate Technology LLC. For internal use only
01/19/10Purchase Order Change Request - Buyer Initiated - 8601. 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.User Note 1:Sample X*004010 Seagate860v40108 2012 Seagate Technology LLC. For internal use only
01/19/10Purchase Order Change Request - Buyer Initiated - 860Transaction Set HeaderSTPos: 010Max: 1Heading - MandatoryLoop: N/AElements: 2User Option (Usage): Must usePurpose: To indicate the start of a transaction set and to assign a control numberElement Summary:RefST01Id143Element NameTransaction Set Identifier CodeReqMTypeIDMin/Max3/3UsageMust use4/9Must useDescription: Code uniquely identifying a Transaction SetRecord Name: Header Position 123Example: transaction typeCode860ST02329NamePurchase Order Change Request - Buyer InitiatedTransaction Set Control NumberMANDescription: Identifying control number that must be unique within the transaction set functionalgroup assigned by the originator for a transaction setRecord Name: Header Position 109Example: transaction control numberSemantics: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).User Note 1:Sample Data:Seagate860v4010ST*860*24786 9 2012 Seagate Technology LLC. For internal use only
01/19/10Purchase Order Change Request - Buyer Initiated - 860BCH Beginning Segment forPos: 020Max: 1Heading - MandatoryLoop: N/AElements: 6Purchase Order ChangeUser Option (Usage): Must usePurpose: To indicate the beginning of the Purchase Order Change Transaction Set and transmit identifying numbersand datesElement Summary:RefBCH01Id353Element NameTransaction Set Purpose CodeReqMTypeIDMin/Max2/2UsageUsedDescription: Code identifying purpose of transaction setRecord Name: H:428Example: cancel order flag (only if '01')Code01NameCancellationUser Note 1:Sending code '01' in BCH segment will cancel the entireorder.04BCH0292ChangePurchase Order Type CodeMIDDescription: Code specifying the type of Purchase OrderRecord Name: H:187Example: po typeUser Note 1: If your company sends codes other2/2Must usethan those specified,please consult Seagate's EDI person.CodeCPBCH03324NameChange to Purchase OrderPurchase Order NumberMAN1/22Must useDescription: Identifying number for Purchase Order assigned by the orderer/purchaserRecord Name: H:129Example: po numberBCH05327Change Order Sequence NumberOAN1/8UsedDescription: Number assigned by the orderer identifying a specific change or revision to apreviously transmitted transaction setRecord Name: Header Position 189Example: po change levelBCH06373DateMDTDescription: Date expressed as CCYYMMDDRecord Name: H:179Example: po dateUser Note 1: This is the date of the ChangeBCH10373DateODescription: Date expressed as CCYYMMDDRecord Name: Notes Position 11Example: custpo notesUser Note 1: This is the date of the original8/8Must use8/8UsedOrder.DTPurchase Order.Semantics:Seagate860v401010 2012 Seagate Technology LLC. For internal use only
01/19/101.2.3.4.Purchase Order Change Request - Buyer Initiated - 860BCH06 is the date assigned by the purchaser to purchase order.BCH09 is the seller's order number.BCH10 is the date assigned by the sender to the acknowledgment.BCH11 is the date of the purchase order change request.User Note 1:Sample ***20100103 11 2012 Seagate Technology LLC. For internal use only
01/19/10Purchase Order Change Request - Buyer Initiated - 860CUR CurrencyPos: 040Max: 1Heading - OptionalLoop: N/AElements: 2User Option (Usage): UsedPurpose: To specify the currency (dollars, pounds, francs, etc.) used in a transactionElement Summary:RefCUR01Id98Element NameEntity Identifier CodeReqMTypeIDMin/Max2/3UsageMust useDescription: Code identifying an organizational entity, a physical location, property or anindividualCodeBYCUR02100NameBuying Party (Purchaser)Currency CodeCID3/3UsedDescription: Code (Standard ISO) for country in whose currency the charges are specifiedRecord Name: Ship tos Position 27Example: local currency codeUser Note 1: Seagate assumes USD unless otherwise specified.Include local currency code if not USDSyntax 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.User Note 1:Sample Data:Seagate860v4010CUR*BY*USD 12 2012 Seagate Technology LLC. For internal use only
01/19/10Purchase Order Change Request - Buyer Initiated - 860Tax ReferenceTAXPos: 070Max: 1Heading - OptionalLoop: N/AElements: 2User Option (Usage): UsedPurpose: To provide data required for proper notification/determination of applicable taxes applying to the transactionor business described in the transactionElement Summary:RefTAX01Id325Element NameTax Identification NumberReqCTypeANMin/Max1/20UsageUsedDescription: Number assigned to a purchaser (buyer, orderer) by a taxing jurisdiction (state,county, etc.); often called a tax exemption number or certificate numberRecord Name: Shiptos Position 81Example: customer exemption numberUser Note 1: Tax id or tax exemption number.Include only if TAX12 '1'.TAX12441Tax Exempt CodeOID1/1UsedDescription: Code identifying exemption status from sales and use taxRecord Name: Shiptos Position 79Example: tax statusCode12NameYes (Tax Exempt)No (Not Tax Exempt)Syntax Rules:1.2.3.4.5.6.R0103 - At least one of TAX01 or TAX03 is required.P0203 - If either TAX02 or TAX03 is present, then the other is required.P0405 - If either TAX04 or TAX05 is present, then the other is required.P0607 - If either TAX06 or TAX07 is present, then the other is required.P0809 - If either TAX08 or TAX09 is present, then the other is required.P1011 - If either TAX10 or TAX11 is present, then the other is required.Comments:1. Tax ID number is, in many instances, referred to as a Tax Exemption Number. The paired (combined) use ofdata elements 309 and 310 provides for the designation of five taxing jurisdictions.2. TAX01 is required if tax exemption is being claimed.User Note 1:Sample Data: TAX*OR-55331*1 Seagate860v401013 2012 Seagate Technology LLC. For internal use only
01/19/10Purchase Order Change Request - Buyer Initiated - 860FOBF.O.B. Related InstructionsPos: 080Max: 1Heading - OptionalLoop: N/AElements: 3User Option (Usage): UsedPurpose: To specify transportation instructions relating to shipmentElement Summary:RefFOB01Id146Element NameShipment Method of PaymentReqMTypeIDMin/Max2/2UsageUsedDescription: Code identifying payment terms for transportation chargesRecord Name: Header Position 426Example: po freight termsCodeCCPCPPFOB02309NameCollectPrepaid but Charged to CustomerPrepaid (by Seller)Location QualifierOID1/2UsedOAN1/80RecommendedDescription: Code identifying type of locationRecord Name: Header Position 256Example: fob codeCodeDEORFOB03352NameDestination (Shipping)Origin (Shipping Point)DescriptionDescription: A free-form description to clarify the related data elements and their contentRecord Name: Header Position 286Example: fob descriptionUser Note 1: Seagate allows 30 characters for FOB03.Syntax Rules:1.2.3.4.C0302 - If FOB03 is present, then FOB02 is required.C0405 - If FOB04 is present, then FOB05 is required.C0706 - If FOB07 is present, then FOB06 is required.C0809 - If FOB08 is present, then FOB09 is required.Semantics:1.2.3.4.FOB01 indicates which party will pay the carrier.FOB02 is the code specifying transportation responsibility location.FOB06 is the code specifying the title passage location.FOB08 is the code specifying the point at which the risk of loss transfers. This may be different than the locationspecified in FOB02/FOB03 and FOB06/FOB07.User Note 1:Sample Data: FOB*CC*DE*PartnerHUB Seagate860v401014 2012 Seagate Technology LLC. For internal use only
01/19/10Purchase Order Change Request - Buyer Initiated - 860Terms of Sale/DeferredTerms of SaleITDPos: 130Max: 5Heading - OptionalLoop: N/AElements: 6User Option (Usage): UsedPurpose: To specify terms of saleElement Summary:RefITD01Id336Element NameTerms Type escription: Code identifying type of payment termsRecord Name: Header Position 800Example: pay terms type codeCode010203ITD02333NameBasicEnd of Month (EOM)Fixed DateTerms Basis Date CodeMDescription: Code identifying the beginning of the terms periodRecord Name: Header Postion 840Example: pay terms date codeCode3515ITD03338NameInvoice DateInvoice Receipt DateReceipt of GoodsTerms Discount PercentMRDescription: Terms discount percentage, expressed as a percent, available to the purchaser ifan invoice is paid on or before the Terms Discount Due DateRecord Name: Header Position 219Example: Pay terms discount percentITD05351Terms Discount Days DueMN01/3UsedDescription: Number of days in the terms discount period by which payment is due if termsdiscount is earnedRecord Name: Header Position 225Example: pay terms discount daysITD07386Terms Net DaysMN01/3UsedDescription: Number of days until total invoice amount is due (discount not applicable)Record Name: Header Position 228Example: pay terms net daysITD12352DescriptionOAN1/80UsedDescription: A free-form description to clarify the related data elements and their contentRecord Name: Header Position 880Example: pay terms descriptionSyntax Rules:1. L03040513 - If ITD03 is present, then at least one of ITD04, ITD05 or ITD13 is required.2. L08040513 - If ITD08 is present, then at least one of ITD04, ITD05 or ITD13 is required.3. L091011 - If ITD09 is present, then at least one of ITD10 or ITD11 is required.Semantics:Seagate860v401015 2012 Seagate Technology LLC. For internal use only
01/19/10Purchase Order Change Request - Buyer Initiated - 8601. ITD15 is the percentage applied to a base amount used to determine a late payment charge.Comments:1. If the code in ITD01 is "04", then ITD07 or ITD09 is required and either ITD10 or ITD11 is required; if the code inITD01 is "05", then ITD06 or ITD07 is required.User Note 1:Sample Data: ITD*01*3*1**5**30*****Net30 Seagate860v401016 2012 Seagate Technology LLC. For internal use only
01/19/10Purchase Order Change Request - Buyer Initiated - 860Carrier Details (RoutingSequence/Transit Time)TD5Pos: 240Max: 12Heading - OptionalLoop: N/AElements: 2User Option (Usage): UsedPurpose: To specify the carrier and sequence of routing and provide transit time informationElement Summary:RefTD501Id133Element NameRouting Sequence CodeReqOTypeIDMin/Max1/2UsageUsedDescription: Code describing the relationship of a carrier to a specific shipment movementCodeBTD505387NameOrigin/Delivery Carrier (Any Mode)RoutingXAN1/35UsedDescription: Free-form description of the routing or requested routing for shipment, or theoriginating carrier's identityRecord Name: Details Position 39Example: po carrierSyntax Rules:1.2.3.4.5.6.7.R0204050612 - At least one of TD502, TD504, TD505, TD506 or TD512 is required.C0203 - If TD502 is present, then TD503 is required.C0708 - If TD507 is present, then TD508 is required.C1011 - If TD510 is present, then TD511 is required.C1312 - If TD513 is present, then TD512 is required.C1413 - If TD514 is present, then TD513 is required.C1512 - If TD515 is present, then TD512 is required.Semantics:1. TD515 is the country where the service is to be performed.Comments:1. When specifying a routing sequence to be used for the shipment movement in lieu of specifying each carrierwithin the movement, use TD502 to identify the party responsible for defining the routing sequence, and useTD503 to identify the actual routing sequence, specified by the party identified in TD502.User Note 1:TD5*B****See Routing Guide Seagate860v401017 2012 Seagate Technology LLC. For internal use only
01/19/10Purchase Order Change Request - Buyer Initiated - 860Loop N9Pos: 285Repeat: 1000OptionalLoop: N9Elements: N/AUser Option (Usage): UsedPurpose: To transmit identifying information as specified by the Reference Identification QualifierLoop Summary:Pos285290IdN9MSGSeagate860v4010Segment NameReference IdentificationMessage TextReqOO18Max Use11000RepeatUsageUsedUsed 2012 Seagate Technology LLC. For internal use only
01/19/10Purchase Order Change Request - Buyer Initiated - 860Reference IdentificationN9Pos: 285Max: 1Heading - OptionalLoop: N9Elements: 2User Option (Usage): UsedPurpose: To transmit identifying information as specified by the Reference Identification QualifierElement Summary:RefN901Id128Element NameReference Identification QualifierReqMTypeIDMin/Max2/3UsageMust use1/30UsedDescription: Code qualifying the Reference IdentificationCodeZZN902127NameMutually DefinedReference IdentificationXANDescription: Reference information as defined for a particular Transaction Set or as specifiedby the Reference Identification QualifierSyntax Rules:1. R0203 - At least one of N902 or N903 is required.2. C0605 - If N906 is present, then N905 is required.Semantics:1. N906 reflects the time zone which the time reflects.2. N907 contains data relating to the value cited in N902.User Note 1:Messages or notes can be sent at either the header or line level.Sample Data: N9*ZZ*Instructions Seagate860v401019 2012 Seagate Technology LLC. For internal use only
01/19/10Purchase Order Change Request - Buyer Initiated - 860MSG Message TextPos: 290Max: 1000Heading - OptionalLoop: N9Elements: 1User Option (Usage): UsedPurpose: To provide a free-form format that allows the transmission of text informationElement Summary:RefMSG01Id933Element NameFree-Form Message TextReqMDescription: Free-form message textRecord Name: Notes Position 11Example: noteUser Note 1: Seagate allows 80TypeANMin/Max1/264UsageMust usecharacters for MSG01.Syntax Rules:1. C0302 - If MSG03 is present, then MSG02 is required.Semantics:1. MSG03 is the number of lines to advance before printing.Comments:1. MSG02 is not related to the specific characteristics of a printer, but identifies top of page, advance a line, etc.2. If MSG02 is "AA - Advance the specified number of lines before print" then MSG03 is required.User Note 1:Sample Data: MSG*PO note goes here Seagate860v401020 2012 Seagate Technology LLC. For internal use only
01/19/10Purchase Order Change Request - Buyer Initiated - 860Loop N1Pos: 300Repeat: 200MandatoryLoop: N1Elements: N/AUser Option (Usage): UsedPurpose: To identify a party by type of organization, name, and codeLoop egment NameNameAddress InformationGeographic LocationAdministrative Communications Contact21ReqOOOOMax Use12 1 1RepeatUsageUsedUsedUsedUsed 2012 Seagate Technology LLC. For internal use only
01/19/10Purchase Order Change Request - Buyer Initiated - 860NameN1Pos: 300Max: 1Heading - OptionalLoop: N1Elements: 4User Option (Usage): UsedPurpose: To identify a party by type of organization, name, a
Interchange (EDI) environment. The transaction set can be used to provide the information required for the customary and established business and industry practice relative to a purchase order change. This transaction can be used: (1) by a buyer to request a change to a previously submitted purchase order or (2) by a buyer to confirm acceptance .
![Change Management Process For [Project Name] - West Virginia](/img/32/change-20management-20process-2003-2022-202012.jpg)
