Transcription
EDI Implementation GuideProgress Energy CompanyElectronic Data Interchange860 Implementation GuideVersion 4010September 18, 2006
EDI Implementation GuideIExplanation of Guide1.0 IntroductionProgress Energy Company is committed to continually improving its businessoperations by reducing costs and improving business processes. Electronic DataInterchange (EDI) is one means of maintaining this commitment to ourshareholders and customers.Progress Energy invites its trading partners to commit to this on-going, continualprocess improvement by exchanging applicable business documents with PGNvia EDI. EDI can provide significant document processing savings while alsoincreasing the accuracy of exchanged business information.This “Progress Energy EDI Implementation Guide” has been created to facilitatethe implementation of an EDI interface between PGN and its trading partners.Please refer to it as necessary when implementing EDI with PGN and for ongoing, day-to-day EDI activity with PGN.2.0 Utility Industry GroupProgress Energy believes in using industry wide “best practices” and is amember of the Utility Industry Group (UIG). The function of the UIG is to“represent Electric and Combination Utilities, Gas Utilities, and their suppliers, fortheir Electronic Data Interchange business needs as an Industry Action Group”.The “Utility Industry Groups Implementation Guideline for Electronic DataInterchange” is the primary guideline used by PGN for implementing andconducting EDI. This guideline adheres to the ANSI X.12 version 4010standards and specifically addresses EDI within the utility industry.September 14, 2006Page 2
EDI Implementation GuideII.Progress Energy Purchase Order Change Mapping RequirementsOverview860 transactions will be extracted from our Passport Purchasing Applications.Progress Energy will send the entire revised purchase order, not just thechanges.Progress Energy has defined the specific 860 purchase order change datavalues and qualifications required for exchanging business documents via EDI.These values and qualifications adhere to the ANSI X.12 standard and to theUIG Implementation Guide. These detailed mappings provide our tradingpartners with the expected data values and exchange rules required to definemapping specifications and perform EDI with PGN.The detailed specifications provided here list only those segments and elementsapplicable to Progress Energy's outbound 860 Purchase Order Changedocument. Note that the “Value/Description” column specifies the values andspecific requirements associated with that element. In some cases the valuesmay digress from the UIG standard but will always adhere to the overall ANSIX12 standard. For example, the UIG standard may indicate that a certainelement is not normally used in the utility industry. In some cases, PGN hasidentified a need to use such an element. If so, this will be indicated in the“Value/Description” column.Functional AcknowledgmentsFunctional Acknowledgment transactions (997's) must be returned for each 860purchase order change transaction sent out by PGN. Response detail should beat the transaction ‘ST’ level. The AK1 and AK9 segments (one per purchaseorder group), as well as the AK2 and AK5 segments (one per purchase ordertransaction), must be returned with each functional acknowledgment. AK3 andAK4 segment data should not be sent.September 14, 2006Page 3
EDI Implementation ransaction Set HeaderBeginning Segment for Purchase Order ChangeReference IdentificationAdministrative Communications ContactF.O.B. Related InstructionsTerms of Sale/Deferred Terms of SaleCarrier Details (Routing Sequence/Transit Time)MMOOOOOMax. UseLoopRepeat1LOOP ID - N91000N9Reference IdentificationO1MSGMessage -----------------------------------------------N1 NameON3 Address InformationON4 Geographic XDTMSCHLine Item DataProduct/Item DescriptionPaperworkReference IdentificationAllowance, Charge or ServiceTax ReferenceDate/Time ReferenceLine Item ScheduleMOOOOOOOMax. UseLoopRepeatLOOP ID - N91000N9Reference IdentificationO1MSGMessage 3N4NameAddress InformationGeographic LocationOOOAMTMonetary AmountOSeg.IDNameReq.Des.CTTAMTTransaction TotalsMonetary AmountOOSummarySeptember 14, 2006Max. UseLoopRepeatPage 4
EDI Implementation GuideSESeptember 14, 2006Transaction Set TrailerMPage 5
EDI Implementation GuideInterchange Control HeaderSegment ID ISAFunction-Identifies start of an interchangeProvides ANSI version for segmentsIdentifies sending and receiving partiesProvides date and time transmission was createdDefines data element separator and segment terminator forthis transmissionProvides control number which should match controlnumber on Interchange Control Trailer (IEA segment) toensure transmission is complete- Requests an interchange acknowledgment (if applicable)- Indicates whether this transmission contains test orproduction dataRefDesigRefNumData Element TitleISA00n/aSegment alifierID(2)‘00' - No authorizationinformation A03I03SecurityInformationQualifierID(2)‘00' - No securityinformation 05Interchange IDQualifierID(2)‘ZZ' – Mutually DefinedISA06I06InterchangeAN(15)PGN’s Sender DUNS #’s:September 14, 2006Type(Size)Value/Description’ - blanks’ - blanksPage 6
EDI Implementation GuideRefDesigRefNumData Element TitleType(Size)Sender IDValue/Description‘006997217' Production‘006997217W’ TestISA07I05Interchange IDQualifierID(2)Code used is dependenton the format ofreceiver’s DUN’s #.ISA08I07InterchangeReceiver IDAN(15)Receiver’s DUNS numberISA09I08Submit DateDT(6)YYMMDDISA10I09Submit TimeTM(4)HHMMISA11I10Interchange CtrlStandards IDID(1)‘U’ - U.S. EDI X12, TDCC,ISA12I11InterchangeVersion IDID(5)‘004010'ISA13I12InterchangeControl Number(must match theIEA segmentcontrol D(1)‘0' - No ISAacknowledgmentrequested (seeFunctional Groupacknowledgment)ISA15I14Test IndicatorID(1)‘T’ - Test Data‘P’ - Production DataISA16I15Sub-elementSeparatorAN(1)HEX 5F (logical ‘not’sign)n/an/aSegmentAN(1)HEX 15 (non keyboardSeptember 14, 2006Page 7
EDI Implementation GuideRefDesigRefNumData Element TitleTerminatorSeptember 14, 2006Type(Size)Value/Descriptioncharacter)Page 8
EDI Implementation GuideFunctional Group HeaderSegment ID GSFunctionTo identify the beginning of a group of related transactionsets (e.g. purchase orders) and to provide control informationRefDesignRefNumData Element TitleGS00n/aSegment IDID(2)‘GS’GS01479Functional IDID(2)‘PC’ Purchase OrderRelated InstructionsGS02142ApplicationSender’s CodeID(2/12)‘006997217' - Production‘006997217W’ - TestGS03124ApplicationReceiver’s CodeID(2/12)DUNS numberGS0530Data InterchangeDateDT(6)YYMMDDGS0628Data InterchangeTimeTM(4)HHMMGS07455ResponsibleAgency CodeID(½)‘X’ - ANSIGS08480Version NumberID(1/12)‘004010' - ANSI version oftransaction setsegments.September 14, 2006Type(Size)Value/DescriptionPage 9
EDI Implementation GuideTransaction Set HeaderSegment ID STFunctionTo indicate the start of a transaction setTo identify the type of transaction (e.g. purchase order)To provide a control number which should match the controlnumber on the transaction set trailer (see SE segment)Type(Size)RefDesignRefNumData Element TitleST00n/aSegment IDID(2)‘ST’ST01143Transaction Set IDCodeID(3)‘860' - Purchase OrderChangeST02329Transaction SetControl NumberID(9)Originator generatedsequential controlnumber to matchcontrol number on SEsegment (at end)September 14, 2006Value/DescriptionPage 10
EDI Implementation GuideBeginning Segment for Purchase Order ChangeSegment ID BCHLevelHeaderFunctionTo identify the beginning of a purchase order changetransaction set and transmit identifying numbers and dates.RefDesignRefNumBCH00Data Element TitleType(Size)Value/DescriptionSegment IDID(3)‘BCH’BCH01353Transaction SetPurpose CodeID(2)‘04’ – ChangeBCH0292Purchase OrderTypeID(2)‘RL’ - Release order‘SA’- Stand alone orderBCH03324Purchase OrderNumberAN(8)Eight character POnumber.BCH04328Release #AN(5)Sequential release # insystem for blanket PO’s.BCH05327Change OrderSequence NumberAN(3)Revision NumberBCH06373Purchase OrderDateAN(8)CCYYMMDDSeptember 14, 2006Page 11
EDI Implementation GuideHeader Reference Segment for Purchase OrderSegment ID REFLevelHeaderFunctionTo provide Progress Energy legal company definitionRefDesignRefNumREF00Data Element TitleType(Size)Value/DescriptionSegment IDID(3)‘REF’REF01128ReferenceNumber QualifierID(2)‘ZZ' – Mutually DefinedREF02127ReferenceIdentificationAN(30)Not UsedREF03352DescriptionAN(80)Freeform Description.Legal definition of thecompany and itssubsidiaries.September 14, 2006Page 12
EDI Implementation GuideAdministrative Communications Contact Segment for Purchase OrderSegment ID PERLevelHeaderFunctionTo identify a person or office to whom administrativecommunications should be directedRefDesignRefNumPER00Data Element TitleType(Size)Value/DescriptionSegment IDID(3)‘PER’PER01366Contact FunctionCodeID(2)‘BD' - Buyer Name orDept.PER0293NameAN(35)Buyer ID(2) ‘-’ BuyernamePER03365CommunicationNumber QualifierID(2)‘TE’ - TelephonePER04364CommunicationNumberAN(12)Buyer telephone numberPER05365CommunicationNumber QualifierID(2)FX - FacsimilePER06364CommunicationNumberAN(12)Buyer Fax number orblank if no numberPER07365CommunicationNumber QualifierID(2)EM - EmailPER08364CommunicationNumberAN(40)Buyer Email AddressSeptember 14, 2006Page 13
EDI Implementation GuideF.O.B. Related Instructions for Purchase OrderSegment ID FOBLevelHeaderFunctionTo specify transportation instructions relating to shipmentRefDesignRefNumFOBData Element TitleType(Size)Value/DescriptionSegment IDID(3)‘FOB’FOB01146ShipmentMethod CodeID(2)Any valid code per ANSIX.12 standard. Defaultsto ‘DF’ - Defined byBuyer and Seller’ if novalue or an invalid valueis passed from PGN’sinternal application.FOB02309Location QualifierID(2)‘ZZ’ – Mutually DefinedFOB03352DescriptionID(80)FOB DescriptionFOB06309Location QualifierID(2)‘ZZ’ – Mutually DefinedFOB07352DescriptionID(80)FOB PointSeptember 14, 2006Page 14
EDI Implementation GuideTerms of Sale/Deferred Terms of Sale for Purchase OrderSegment ID ITDLevelHeaderFunctionTo specify the terms of saleRefDesignRefNumITD00Data Element TitleType(Size)Value/DescriptionSegment IDID(3)‘ITD’ITD01336Terms Type CodeID(2)‘08' - Basic Discount‘05' - No DiscountavailableITD02333Terms Basis DateCodeID(2)‘5' - Invoice ReceiptDate is the date towhich the terms applyITD03338Terms Discount %R(6)Invoice Terms PercentITD04n/an/an/aNot UsedITD05351Terms DiscountDaysN0(3)Max days for whichdiscount is applicableITD06n/an/an/aNot UsedITD07386Terms Net DaysN0(3)Max days until netamount is dueSeptember 14, 2006Page 15
EDI Implementation GuideCarrier Details (Routing Sequence/Transit Time) for Purchase OrderSegment ID TD5LevelHeaderFunctionTo specify the carrier, sequence of routing and to providetransit time informationRefDesignRefNumTD500Data Element TitleType(Size)Value/DescriptionSegment IDID(3)‘TD5’TD501n/an/an/aNot UsedTD50266IdentificationCode QualifierID(2)‘2' - Standard CarrierAlpha CodeTD50367IdentificationCodeAN(17)Freeform methoddescription (PGN uses 30characters but will betruncated to 17).Example might be‘Truck’.TD504throughTD512n/an/an/aNot UsedSeptember 14, 2006Page 16
EDI Implementation GuideHeader Level Reference Identification for Purchase OrderSegment ID N9LevelHeaderFunctionTo provide identifying informationRefDesignRefNumN900Data Element TitleType(Size)Value/DescriptionSegment fierID(3)ZZ – Mutually DefinedN902127ReferenceIdentificationAN(20)PO Instructions or POHeader CommentsSeptember 14, 2006Page 17
EDI Implementation GuideHeader Level Message Text for Purchase OrderSegment ID MSGLevelHeaderFunctionTo provide PO header commentsRefDesignRefNumMSG00MSG01September 14, 2006933Data Element TitleType(Size)Value/DescriptionSegment IDID(3)‘MSG’Free FormMessage TextAN(60)PO Instructions or POHeader CommentsPage 18
EDI Implementation GuideVendor Name for the Purchase OrderSegment ID N1LevelHeaderFunctionTo identify the Vendor locationThis segment begins an ‘N’ loop which also includes N3 andN4 segments (N2 is not used).RefDesignRefNumN100Data Element TitleType(Size)Value/DescriptionSegment IDID(2)‘N1’N10198Entity ID CodeID(2)‘VN’ - VendorN10293NameAN(30)Vendor contact nameN10366ID Code QualifierID(2)'ZZ' - Mutually DefinedN10467ID CodeAN(2)Internal vendor codeand suffixSeptember 14, 2006Page 19
EDI Implementation GuideVendor Information for the Purchase OrderSegment ID N2LevelHeaderFunctionTo provide the vendor address nameRefDesignRefNumN200N201September 14, 200693Data Element TitleType(Size)Value/DescriptionSegment IDID(2)‘N2”Additional NameID(30)Freeform Address NamePage 20
EDI Implementation GuideVendor Information for the Purchase OrderSegment ID N3LevelHeaderFunctionTo provide the next two lines of the vendor street addressRefDesignRefNumN300Data Element TitleType(Size)Value/DescriptionSegment IDID(2)‘N3”N301166Additional NameID(30)Freeform address line 2Standard place for streetaddressN302166Additional NameID(30)Freeform address line 3Standard place foradditional informationSeptember 14, 2006Page 21
EDI Implementation GuideVendor Information for the Purchase OrderSegment ID N4LevelHeaderFunctionTo provide the vendor addressRefDesignRefNumN400Data Element TitleType(Size)Value/DescriptionSegment IDID(2)‘N4’N40119City NameAN(18)CityN402156State CodeID(2)Standard State CodeN403116Postal CodeID(5)Zip CodeN40426Country CodeID(2)Country CodeSeptember 14, 2006Page 22
EDI Implementation GuideBill to Name for the Purchase OrderSegment ID N1LevelHeaderFunctionTo identify the location to bill items on the purchase orderThis segment begins an ‘N’ loop which also includes N3 andN4 segments (N2 is not used).RefDesignRefNumN100Data Element TitleType(Size)Value/DescriptionSegment IDID(2)‘N1’N10198Entity ID CodeID(2)‘BT’ - Bill-to partyN10293NameAN(30)Bill-to NameN10366ID Code QualifierID(2)'ZZ' - Mutually DefinedN10467ID CodeAN(2)Company Code:01 - Carolina Power & Light02 - Carofund03 - Carofinancial04 - Capitan05 - Carohome06 - Powerhouse Square20 - Progress Energy Ventures21 - Richmond22 - CP&L Synfules23 - Progress GENCO Ventures24 - Rowan25 - Effingham26 - DeSoto Co. Generating27 - JV Finance28 - Anson Co Power29 - Tuscarora Power30 - Monroe Power31 - Cumberland Co. Power50 - NCNG Corp.September 14, 2006Page 23
EDI Implementation GuideRefDesignRefNumData Element TitleType(Size)Value/Description51 - NCNG Rnergy52 - Cape Fear Energy53 - NCNG Pine Needle54 - NCNG Cardinal Pipeline55 - Eastern NCNG60 - FPC Utility Corp.61 - Electric Fuels62 - Progress Telecom63 - Florida Progress Corp.64 - Progress Capital Holding65 - PCH-Prog. Energy Corp.80 - Caronet85 - SRS97 - Purchase Acting Consol.98 - PGN Service Co.99 - Progress Energy INC.September 14, 2006Page 24
EDI Implementation GuideBill to Address Information for the Purchase OrderSegment ID N3LevelHeaderFunctionTo provide the first two lines of the bill to street addressRefDesignRefNumN300Data Element TitleType(Size)Value/DescriptionSegment IDID(2)‘N3”N301166Additional NameID(30)Freeform address line 1Standard place for siteLocation DescriptionN302166Additional NameID(30)Freeform address line 2Standard place for streetaddressSeptember 14, 2006Page 25
EDI Implementation GuideBill to Address Information for the Purchase OrderSegment ID N4LevelHeaderFunctionTo provide the bill to addressRefDesignRefNumN400Data Element TitleType(Size)Value/DescriptionSegment IDID(2)‘N4’N40119City NameAN(18)CityN402156State CodeID(2)Standard State CodeN403116Postal CodeID(5)Zip CodeSeptember 14, 2006Page 26
EDI Implementation GuideLine Item ChangeSegment ID POCLevelDetailFunctionTo specify changes to a line itemRefDesignRefNumPOC00Data Element TitleType(Size)Value/DescriptionSegment Purchase Order LineNumberPOC02670Change CodeID(2)‘AI’ – New Line‘CA’ – Change to Line‘DI’ – Cancel Line‘NC’ – No ChangePOC03330Quantity OrderedR(9)Quantity Ordered.PGN’s internal quantityfield is 13 digits. Ifquantity is greater than9 digits, then no quantityvalue will be sentresulting in an error forthe corresponding lineitem.POC04671Quantity Left toReceiveR(9)POC05355Unit or Basis forMeasureID(2)Unit of Measure-POC06212Unit PriceR(14)Unit PricePOC07235Product/ServiceID(2)‘BP’ - Buyer’s PartSeptember 14, 2006Page 27
EDI Implementation GuideRefDesignRefNumData Element TitleType(Size)ID rviceAN(30)Part NumberPOC09throughPOC27n/an/an/aNot UsedSeptember 14, 2006Page 28
EDI Implementation GuideProduct/Line Item Description for the Purchase Order Line ItemSegment ID PIDLevelDetailFunctionTo describe a product or process in coded or free-formformatRefDesignRefNumPID00Data Element TitleType(Size)Value/DescriptionSegment IDID(3)‘PID'PID01349Line ItemDescription TypeID(2)‘F’ - Free ‘HZ’ - Nuclear safetyrelated‘NH’ - Nuclear nonsafetyrelated‘ ’ - Non-nuclearrelatedPID03 –PID04n/an/an/aNot UsedPID05752ProductDescriptionAN(50)Short ProductDescription.September 14, 2006Page 29
EDI Implementation GuidePaperwork for Purchase OrderSegment ID PWKLevelDetailFunctionTo provide purchasing specification codes. Please referenceTrading Partner Agreement for full specification.RefDesignRefNumPWK00Data Element TitleType(Size)Value/DescriptionSegment IDID(3)‘PWK’PWK01755Report TypeCodeID(2)PJ – tandards andProcedures DocumentName, - (dash), RevisionNumber. For example:PO STANDARD TERMS &CONDITIONS – rev. 006September 14, 2006Page 30
EDI Implementation GuideDetail Reference Segment for Purchase Order Line ItemSegment ID REFLevelDetailFunctionTo provide identifying numbers associated with a Line ItemSeven manufacturer part numbers can be providedRefDesignRefNumREF00Data Element TitleType(Size)Value/DescriptionSegment IDID(3)‘REF’REF01128ReferenceNumber QualifierID(2)‘MF’ - Manufacturer’sPart NumberREF02127ReferenceNumberAN(24)Manufacture’s PartNumberREF03352ReferenceDescriptionAN(10)Short Manufacturer’sPart Number DescriptionSeptember 14, 2006Page 31
EDI Implementation GuideAllowance, Charge or ServiceSegment ID SACLevelDetailFunctionTo specify allowances, charges or servicesRefDesignRefNumSAC00Data Element TitleType(Size)Value/DescriptionSegment IDID(3)‘SAC’SAC01248Allowance orCharge IndicatorID(1)‘A’ – Allowance‘C’ – ChargeSAC021300Special Chargeor AllowanceCodeID(4)B020 – Cert. ofConformanceB050 – Cert. ofComplianceB940 – Cutting ChargeC040 - Delivery ChargeC400 - DocumentationChargeC490 – Drum DepositC870 – Expediting FeeD240 – FreightD270 – Fuel SurchargeD500 – Handling ChargeD540 – Hazmat ChargeG210 – Reel ChargeG470 – Restocking ChargeH680 – Government TaxH700 – County TaxH770 – State TaxI000 – Testing ChargeI110 – Tooling ChargeSeptember 14, 2006Page 32
EDI Implementation GuideRefDesignRefNumData Element TitleType(Size)Value/DescriptionZZZZ – Misc. ChargesSAC05610Allowance orCharge TotalAmountN2(9)Rate * QuantitySAC08118RateR(9)PriceSAC09355Unit of MeasureCodeID(2)Unit of Measure onAN(80)DescriptionSeptember 14, 2006Page 33
EDI Implementation GuideTax Reference for Purchase OrderSegment ID TAXLevelDetailFunctionTo specify the tax information for a purchase order line itemRefDesignRefNumTAX00Data Element TitleType(Size)Segment IDID(3)Value/Description‘TAX’TAX01325Tax IdentificationNumberAN(20)TAX02309Location QualifierID(2)PS – 5 Digit Zip CodeTAX03310Location IdentifierAN(30)Zip CodeTAX04TAX11n/an/an/aNot UsedTAX12441Tax Exempt CodeID(1)‘1’ – Tax Exempt‘2’ – Not Tax ExemptSeptember 14, 2006Page 34
EDI Implementation GuideDate/Time Reference for Purchase Order Line ItemSegment ID DTMLevelDetailFunctionTo Specify pertinent dates and timesRefDesignRefNumDTM00Data Element TitleType(Size)Value/DescriptionSegment 106' - Required By Date‘075' - Promised byDelivery n/an/aNot UsedSeptember 14, 2006Page 35
EDI Implementation GuideLine Item Schedule for Purchase Order Line ItemSegment ID SCHLevelDetailFunctionTo specify the delivery date at the line item levelRefDesignRefNumSCH00Data Element TitleType(Size)Value/DescriptionSegment 355Unit of MeasureCodeID(2)UOM CodeSCH05374Date QualifierID(3)‘106' - Required By Date‘075' - Promised byDelivery (AFT)SCH06373DateDT(8)CCYYMMDDSeptember 14, 2006Page 36
EDI Implementation GuideDetail Level Reference Identification for Purchase OrderSegment ID N9LevelDetailFunctionTo provide identifying informationRefDesignRefNumN900Data Element TitleType(Size)Value/DescriptionSegment fierID(3)ZZ – Mutually DefinedN902127ReferenceIdentificationAN(20)PO Line CommentsSeptember 14, 2006Page 37
EDI Implementation GuideDetail Level Message Text for Purchase OrderSegment ID MSGLevelDetailFunctionTo provide PO header commentsRefDesignRefNumMSG00MSG01September 14, 2006933Data Element TitleType(Size)Value/DescriptionSegment IDID(3)‘MSG’Free FormMessage TextAN(60)PO Line CommentsPage 38
EDI Implementation GuideShip to Location & Name for the Purchase OrderSegment ID N1LevelDetailFunctionTo identify the location to ship items on the purchase orderThis segment begins an ‘N’ loop which also includes N3 andN4 segments (N2 is not used).RefDesignRefNumN100Data Element TitleType(Size)Value/DescriptionSegment IDID(2)‘N1’N10198Entity ID CodeID(2)‘ST’ - Ship-to partyN10293NameAN(25)Ship-to NameN10366ID Code QualifierID(2)‘ZZ’ – Mutually DefinedN10467ID CodeAN(3)Ship to codeSeptember 14, 2006Page 39
EDI Implementation GuideShip to Address Information for the Purchase OrderSegment ID N3LevelDetailFunctionTo provide the first two lines of the ship to street addressRefDesignRefNumN300Data Element TitleType(Size)Value/DescriptionSegment IDID(2)‘N3”N301166Additional NameID(25)Freeform address line 1Standard place for siteLocation DescriptionN302166Additional NameID(25)Freeform address line 2Standard place for streetaddressSeptember 14, 2006Page 40
EDI Implementation GuideShip to Address Information for the Purchase OrderSegment ID N4LevelDetailFunctionTo provide the ship to addressRefDesignRefNumN400Data Element TitleType(Size)Value/DescriptionSegment IDID(2)‘N4’N40119City NameAN(18)CityN402156State CodeID(2)Standard State CodeN403116Postal CodeID(5)Zip CodeSeptember 14, 2006Page 41
EDI Implementation GuideMonetary Amount for Purchase Order Line ItemSegment ID AMTLevelDetailFunctionTo indicate the total monetary amount of the line itemRefDesignRefNumAMT00Data Element TitleType(Size)Value/DescriptionSegment IDID(3)‘AMT’AMT01522Amount QualifierCodeID(2)‘1' - Line Item TotalAMT02782MonetaryAmountR(13)Monetary Amount forLine ItemSeptember 14, 2006Page 42
EDI Implementation GuideTotal Line Items for Purchase OrderSegment ID CTTLevelSummaryFunctionControl count of line items on the purchase orderRefDesignRefNumCTT00Data Element TitleType(Size)Value/DescriptionSegment IDID(3)‘CTT’CTT01354Number of LineItemsN0(6)Count of line items onpurchase orderCTT02throughCTT07n/an/an/aNot UsedSeptember 14, 2006Page 43
EDI Implementation GuideTotal Amount for Purchase OrderSegment ID AMTLevelSummaryFunctionTotal cost amount of the purchase orderRefDesignRefNumAMT00Data Element TitleType(Size)Value/DescriptionSegment IDID(3)‘AMT’AMT01522Amount QualifierCodeID(2)‘TT’ - Total ry Amount forLine ItemSeptember 14, 2006Page 44
EDI Implementation GuideTransaction Set TrailerSegment ID SEFunctionTo indicate the end of the transaction setTo provide the count of the transmitted segments (includingthe beginning (ST) and ending (SE) segments)RefDesignRefNumData Element TitleSE00n/aSegment IDID(2)SE0196Number ofIncludedSegmentsN0(10)SE02329Transaction SetControl NumberID(9)September 14, 2006Type(Size)Value/Description‘SE’Originator generatedsequential controlnumber to matchcontrol number on STEsegment (in beginning)Page 45
860 transactions will be extracted from our Passport Purchasing Applications. Progress Energy will send the entire revised purchase order, not just the changes. Progress Energy has defined the specific 860 purchase order change data values and qualifications required for exchanging business documents via EDI.
