ebook img

Federal implementation guideline for electronic data interchange PDF

20 Pages·1998·0.82 MB·English
Save to my drive
Quick download
Download
Most books are stored in the elastic cloud where traffic is expensive. For this reason, we have a limit on daily download.

Preview Federal implementation guideline for electronic data interchange

NIST Special Publication 881-82 Federal Implementation Guideline Data Interchange for Electronic ASC X12 003040 Transaction Set 852 Product Activity Data (Revision 1) Implementation Convention Nisr DEPARTMENT OF COMMERCE U.S. Technology Administration National Institute of QC Standards and Technology 100 U57 ' . MO. 881 -82 1998 m he National Institute ofStandards and Technology was established in 1988 by Congress to "assist industry in -M. the developmentoftechnology neededto improveproductquality,tomodernizemanufacturingprocesses, . . . to ensure product reliability and to facilitate rapid commercialization ... ofproducts based on new scientific . . . discoveries." NIST, originally founded as the National Bureau of Standards in 1901, works to strengthen U.S. industry's competitiveness; advance science and engineering; and improve public health, safety, and the environment. One of the agency's basic functions is to develop, maintain, and retain custody of the national standards of measurement, and provide the means and methods for comparing standards used in science, engineering, manufacturing, commerce, industry, and education with the standards adopted or recognized by the Federal Government. As an agency of the U.S. Commerce Department's Technology Administration, NIST conducts basic and applied research in the physical sciences and engineering, and develops measurement techniques, test methods, standards, and related services. The Institute does generic and precompetitive work on new and advanced technologies. NIST's research facilities are located at Gaithersburg, MD 20899, and at Boulder, CO 80303. Major technical operating units and their principal activities are listed below. For more information contact the Publications and Program Inquiries Desk, 301-975-3058. Office of the Director Physics Laboratory • National Quality Program • Electron and Optical Physics • International and Academic Affairs • Atomic Physics • Optical Technology Technology Services • Ionizing Radiation • Standards Services • Time and Frequency' • Technology Partnerships • Quantum Physics' • Measurement Services • Technology Innovation Materials Science and Engineering Laboratory • Information Services • Intelligent Processing of Materials Advanced Technology Program • Ceramics • Economic Assessment • Materials Reliability' • Information Technology and Applications • Polymers • Chemical and Biomedical Technology • Metallurgy • Materials and Manufacturing Technology • NIST Center for Neutron Research • Electronics and Photonics Technology Manufacturing Engineering Manufacturing Extension Partnership Laboratory Program • Precision Engineering • Regional Programs • Automated Production Technology • National Programs • Intelligent Systems • Program Development • Fabrication Technology • Manufacturing Systems Integration Electronics and Electrical Engineering Laboratory Building and Fire Research Laboratory • Microelectronics • Law Enforcement Standards • Structures • Electricity • Building Materials • Semiconductor Electronics • Building Environment • Electromagnetic Fields' • Fire Safety Engineering • Electromagnetic Technology' • Fire Science • Optoelectronics' Information Technology Laboratory Chemical Science and Technology • Mathematical and Computational Sciences^ Laboratory • Advanced Network Technologies • Biotechnology • Computer Security • Physical and Chemical Properties^ • Information Access and User Interfaces • Analytical Chemistry • High Performance Systems and Services • Process Measurements • Distributed Computing and Information Services • Surface and Microanalysis Science • Software Diagnostics and Conformance Testing 'At Boulder, CO 80303. ^Some elements at Boulder, CO. NIST Special Publication 881-82 Federal Implementation Guideline for Electronic Data Interchange ASC X12 003040 Transaction Set 852 Product Activity Data (Revision 1) Implementation Convention Electronic Commerce Acquisition Program Management Office Standard Management Committee - Secretariat National Institute ofStandards and Technology MD Gaithersburg, 20899-0001 Editor: Dr. Jean-Philippe Favreau August 1998 DEPARTMENT OF COMMERCE U.S. William M. Daley, Secretary Technology Administration Gary R. Bachula, Acting Under Secretary for Technology National Institute ofStandards and Technology Raymond G. Kammer, Director Reports on Information Technology The National Institute of Standards and Technology (NIST)'s Information Technology Laboratory (ITL) develops standards and guidelines, provides technical assistance, and conducts research for computers and resources. As part of the overall federal effort to establish a single face to industry for conducting electronic commerce, ITL has been designated as the organization responsible for coordinating the development of Federal Implementation Conventions (ICs) for Electronic Data Interchange (EDI). ICs are defined by functional-area experts who create and select options from standard EDI Transaction Sets to yield the implementations to be used for practical EDI. These ICs are made available to federal agencies and industry by electronic means and this Special Publication Series. National Institute of Standards and Technology Special Publication 881-82 Natl. Inst. Stand. Technol. Spec. Publ. 881-82, 14 pages (Aug. 1998) CODEN: NSPUE2 U.S. GOVERNMENT PRINTING OFFICE WASHINGTON: 1998 852 Product Activity Data Functional Group ID= Introduction: This Draft Standard for Trial Use contains the format and establishes the data contents ofthe Product Activity Data Transaction Set (852) for use within the context ofan Electronic Data Interchange (EDI) environment. The transaction set can be used by a distributor, warehouse, orretailerto advise a trading partner ofinventory, sales, and other product activity information. Product activity data enables atrading partnerto plan and ship, or propose inventory replenishment quantities, for distribution centers, warehouses or retail outlets. The receiver ofthe transaction set will maintain some type ofinventory/product movement records for its trading partners to enable replenishment calculations based on dataprovidedby the distributor, warehouse or retailer. Notes: /. Organizations use thistransaction settoprovideassetbalanceandpointofsale information to vendors responsibleforreplenishingdistribution centers, warehousesorretailoutlets. 2. Use asingle occurrenceofthistransactionsettoreportassetbalanceandpointofsaleinformation to asingle vendorforasingledistribution center, warehouseorretailoutlet. Heading: Pos. Seg. Req. Loop Notesand No. ID Name Des. Max.Use Repeat Comments M MustUse 010 ST TransactionSetHeader 1 MustUse 020 XQ ReportingDate/Action M 1 MustUse 030 XPO PreassignedPurchaseOrderNumbers O >1 NotUsed 040 N9 ReferenceNumber 0 >1 NotUsed 050 PER AdministrativeCommunicationsContact 0 3 LOOPID-Nl 200 060 Nl Name 0 1 nl NotUsed 070 N2 AdditionalName Information 0 1 NotUsed 080 N3 Address Information 0 2 NotUsed 090 N4 GeographicLocation 0 1 NotUsed 100 FOB F.O.B. RelatedInstructions o 1 NotUsed 110 TD5 CarrierDetails(RoutingSequence/Transit o 1 Time) NotUsed 120 DTM Date/Time/Period 0 >1 NotUsed 130 N9 ReferenceNumber 0 >1 NotUsed 140 PER AdministrativeCommunicationsContact 0 3 Detail: Pos. Seg. Req. Loop Notesand No. ID Name Des. Max.Use Repeat Comments LOOP ID-LIN 999999 MustUse 150 LIN Item Identification O 1 NotUsed 160 CTP PricingInformation 0 25 Not Used 170 P04 Item Physical Details 0 1 Not Used 171 N9 ReferenceNumber 0 >1 003040F852 1 1 June 1998 NotUsed 175 AMT MonetaryAmount O 10 1,00PID-ZA 99 M MustUse 180 ZA ProductActivityReporting 1 n2 NotUsed 190 CTP PricingInformation 0 25 NotUsed 200 SDQ DestinationQuantity 0 >1 Summary: Pes. Seg. Req. Loop Notesand No. IB Name Des. Max.Use Reoeat Comments MustUse 210 CTT TransactionTotals 0 1 n3 M MustUse 220 SE TransactionSetTrailer 1 Transaction Set Notes The reporting location is required. The reporting location is specified explicitly in the Nl segment usingthe code RL in NlOl, or implicitly using the SDQ segment (Table 2) with the location data elements. They are mutually exclusive (the SDQ andthe Nl withNlOl containing RL). The quantity forthe item identified in the LIN segment is required. Quantity is specified either in the ZA segment (ZA02) or in the SDQ segment, but not in both. The number ofline items (CTTOl) is the accumulation ofthe number ofLIN segments. Hash total (CTT02) is not used inthis transaction set. When sending item and activity data inthe LIN loop, the CTT segment is required. 003040F852 2 June 1998 1 1 ST Segment: Transaction Set Header Position: 010 Loop: Level: Heading Usage: Mandatory Max Use: 1 Purpose: To indicate the start ofa transaction set and to assign a control number Syntax Notes: Semantic Notes: 1 The transaction set identifier (STOl) used bythe translation routines ofthe interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set). Comments: Data Element Summary Ref. Data Pes. Element Name Attributes M Must Use STOl 143 Transaction Set Identifier Code ID 3/3 Code uniquely identifying a Transaction Set 852 X12.52 Product Activity Data M Must Use ST02 329 Transaction Set Control Number AN 4/9 Identifying control numberthat must be unique within the transaction set functional group assigned bythe originator for atransaction set 003040F852 1 3 1 June 1998 Segment: Reporting Date/Action Position: 020 Loop: Level: Heading Usage: Mandatory Max Use: 1 Purpose: To specify reporting date and action to be taken Syntax Notes: Semantic Notes: 1 XQ02 is the reporting date. Ifreporting a date range, thenXQ02 is the start date and XQ03 is the end date. Comments: Data Element Summary Ref. Data Pes. Element Name Attributes M Must Use XQOl 305 Transaction Handling Code ID 1/1 Code designatingthe actionto be takenby all parties F Plan and Submit Suggested Purchase Order(s) G Plan Order(s) and Ship Product H Notification Only M Must Use XQ02 373 Date DT 6/6 (YYMMDD) Date Not Used XQ03 373 Date O DT 6/6 (YYMMDD) Date 003040F852 1 4 1 June 1998 XPO Segment: Preassigned Purchase Order Numbers Position: 030 Loop: Level: Heading Usage: Optional (Must Use) Max Use: >1 Purpose: To transmitpreassigned purchase ordernumbers Syntax Notes: 1 Ifeither XPO03 or XPO04 is present, then the other is required. Semantic Notes: 1 XPOOl is the preassigned purchase order number. Ifa range ofpurchase order numbers is to be transmitted, use XPOO1 for the first number and XPO02 as the ending number. Comments: 1 XPO03 and XPO04 specify the location that the purchase order numbers apply to. Data Element Summary Ref. Data Pes. Element Name Attributes Must Use XPOOl 324 Purchase Order Number M AN 1/22 Identifying number for Purchase Order assigned bythe orderer/purchaser Agencypreassignedpurchase ordernumber. There willbe a separate purchaseordernumberforeach warehousereceivinglocation. Not Used XPO02 324 Purchase Order Number O AN 1/22 Identifying number for Purchase Order assigned bythe orderer/purchaser Not Used XPO03 66 Identification Code Qualifier X ID 1/2 Code designatingthe system/method ofcode structure used for Identification Code (67) Not Used XPO04 67 Identification Code X AN 2/17 Code identifying a party or other code 003040F852 1 5 1 June 1998 . NX Segment: Name Position: 060 Loop: Nl Optional Level: Heading Usage: Optional Max Use: 1 Purpose: To identify a partybytype oforganization, name, and code N N Syntax Notes: 1 At least one of 102 or 103 is required. N N 2 Ifeither 103 or 104 is present, then the other is required. Semantic Notes: Comments: 1 This segment, used alone, provides the most efficient method ofproviding organizational identification. To obtain this efficiencythe "ID Code" (N104) must provide akey to the table maintained by the transaction processing party. N N N 2 105 and 106 further define the type ofentity in 101 Data Element Summary Ref. Data Pes. Element Name Attributes M Must Use NIDI 98 Entity Identifier Code ID 2/2 Code identifying an organizational entity, a physical location, or an individual RL Reporting Location Not Used N102 93 Name X AN 1/35 Free-form name Must Use N103 66 Identification Code Qualifier X ID 1/2 Code designating the system/method ofcode structure used for Identification Code (67) 1 D-U-N-S Number, Dun & Bradstreet 9 D-U-N-S+4, D-U-N-S Number with Four Character Suffix 10 Department ofDefense Activity Address Code (DODAAC) 54 Warehouse M4 Department ofDefense Routing Identifier Code (RIC) An integral and predeterminedparticipant in an established logistical system performing general logistic control, distribution, and storage functions Must Use N104 67 Identification Code X AN 2/17 Code identifying aparty or other code Enterthecodeapplicableto the warehousereportinglocation. O Not Used N105 706 Entity Relationship Code ID 2/2 Code describing entity relationship Not Used N106 98 Entity Identifier Code O ID 2/2 Code identifying an organizational entity, a physical location, or an individual 003040F852 1 6 I June 1998

See more

The list of books you might like

Most books are stored in the elastic cloud where traffic is expensive. For this reason, we have a limit on daily download.