Product: X12 EDI
Transaction: 841
Article Link:
841 - Specifications/Technical Information
FUNCTIONAL GROUP=SP
This X12 Transaction Set contains the format and establishes the data contents of the Specifications/Technical Information Transaction Set (841) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to transmit or request specifications or technical information between trading partners. It can be used to transmit engineering change and engineering change requests. It can also be used to allow EDI trading partners the ability to exchange a complete or partial technical description of a product, process, service, etc. over the same path as any other EDI transaction. The detail area can include graphic, text, parametric, tabular, image, spectral, or audio data. A transmission includes identification information to assist the receiver in interpreting and utilizing the information included in the transaction.
Further action as a consequence of the receipt and initial processing of the specification or other technical data may or may not require human intervention. The transmission and receipt of the data may require private agreement between the trading partners to automate the receipt of the data.
The total transaction must be in the general form of all ASC X12 transactions so that an EDI computer system will be able to automatically recognize it as a Specification/Technical Information Transaction Set and pass it on for processing of the data itself. The transaction set is not media dependent.
The detail area of the Specification/Technical Information Transaction Set provides a structure which allows for the exchange of a variety of specification information. For example, if the transaction contains information describing a complete assembly, it would be necessary to include the assembly model, the models for each of the individual parts, and the associated specifications. In the case of a process it may be necessary to transmit the specification of the product along with the specifications of the process and raw materials. This transaction set can also be linked to other transaction sets.
This transaction set is not limited to a specific transmission protocol and uses other standards as applicable where they do not conflict with these requirements for specification transaction.
SCHEMA
ST
Segment | Name | Position |
ST | Transaction Set Header | 0100 |
SPI
Segment | Name | Position |
SPI | Specification Identifier | 0200 |
RDT | Revision Date/Time | 0300 |
NTE | Note/Special Instruction | 0400 |
X1 | Export License | 0500 |
X2 | Import License | 0600 |
X7 | Customs Information | 0700 |
AMT | Monetary Amount Information | 0800 |
REF
Segment | Name | Position |
REF | Reference Information | 0900 |
DTM | Date/Time Reference | 1000 |
PER | Administrative Communications Contact | 1100 |
N1
Segment | Name | Position |
N1 | Party Identification | 1200 |
N2 | Additional Name Information | 1300 |
N3 | Party Location | 1400 |
N4 | Geographic Location | 1500 |
REF | Reference Information | 1600 |
PER | Administrative Communications Contact | 1700 |
HL
Segment | Name | Position |
HL | Hierarchical Level | 0100 |
SPI
Segment | Name | Position |
SPI | Specification Identifier | 0200 |
RDT | Revision Date/Time | 0300 |
PRR | Problem Report | 0330 |
PRT | Part Disposition | 0340 |
PRS | Part Release Status | 0350 |
LIN | Item Identification | 0400 |
PER | Administrative Communications Contact | 0460 |
MSG | Message Text | 0500 |
N1
Segment | Name | Position |
N1 | Party Identification | 0510 |
N2 | Additional Name Information | 0520 |
N3 | Party Location | 0530 |
N4 | Geographic Location | 0540 |
PER | Administrative Communications Contact | 0550 |
N9 | Extended Reference Information | 0560 |
PID
Segment | Name | Position |
PID | Product/Item Description | 0600 |
PKD | Packaging Description | 0650 |
QTY | Quantity Information | 0700 |
MEA | Measurements | 0740 |
UIT | Unit Detail | 0750 |
LOC | Location | 0760 |
PWK | Paperwork | 0770 |
PKG
Segment | Name | Position |
PKG | Marking, Packaging, Loading | 0780 |
MEA | Measurements | 0790 |
REF
Segment | Name | Position |
REF | Reference Information | 0800 |
DTM | Date/Time Reference | 0900 |
PER | Administrative Communications Contact | 1000 |
LX
Segment | Name | Position |
LX | Transaction Set Line Number | 1030 |
LIN | Item Identification | 1050 |
TMD | Test Method | 1070 |
MEA | Measurements | 1100 |
PSD | Physical Sample Description | 1120 |
SPS | Sampling Parameters for Summary Statistics | 1140 |
DTM | Date/Time Reference | 1200 |
REF | Reference Information | 1300 |
EFI
Segment | Name | Position |
EFI | Electronic Format Identification | 1400 |
BIN | Binary Data Segment | 1600 |
CID
Segment | Name | Position |
CID | Characteristic/Class ID | 1700 |
UIT | Unit Detail | 1800 |
TMD | Test Method | 1900 |
PSD | Physical Sample Description | 2000 |
CSS | Conditional Sampling Sequence | 2010 |
SPS | Sampling Parameters for Summary Statistics | 2100 |
MSG | Message Text | 2200 |
MEA
Segment | Name | Position |
MEA | Measurements | 2300 |
DTM | Date/Time Reference | 2400 |
REF | Reference Information | 2500 |
STA
Segment | Name | Position |
STA | Statistics | 2600 |
DTM | Date/Time Reference | 2700 |
REF | Reference Information | 2800 |
CSF
Segment | Name | Position |
CSF | Conditional Sampling Frequency | 2820 |
LS | Loop Header | 2830 |
CID
Segment | Name | Position |
CID | Characteristic/Class ID | 2840 |
MEA | Measurements | 2850 |
STA | Statistics | 2860 |
LE | Loop Trailer | 2870 |
EFI
Segment | Name | Position |
EFI | Electronic Format Identification | 2900 |
BIN | Binary Data Segment | 3100 |
SE
Segment | Name | Position |
SE | Transaction Set Trailer | 0100 |
COMMENTS
Notes |
|
2/0100 | To be meaningful, at least one of the SPI, PID, REF, MEA, EFI or CID loops must be present with each occurrence of the HL loop. |
2/2010 | The sampling sequence specified in the CSS segment will take precedence over any other sampling rate (PSD03, PSD09, SPS06, CSF02, and CSF03) from the point the CSS01 event occurs until the specified sequence is completed. |
2/2010 | If no other sampling is specified, then only the sampling indicated in this segment is performed when the CSS01 event occurs. |
2/2820 | The sampling rate specified is the CSF segment. It would take precedence over the normal sampling rate specified in PSD03 while the conditions of the CSF segment are satisfied, but would NOT take precedence over the sampling sequence activated by the proposed CSS segment. |
2/2820 | If no other sampling rate is specified, then the only sampling indicated in the CSF segment is performed while the CSF conditions are met. Sampling will cease when the conditions are no longer met. |
2/2820 | Conditional values specified in DE 740 (Range Minimum) will be interpreted as "greater than or equal to this value." Values specified in DE 741 (Range Maximum) will be interpreted to mean "less than or equal to this value." |
2/2840 | Either the MEA segment or the STA segment must occur, but not both. |
Comments |
|
2/0330 | The PRR segment contains the reason for an engineering change. |
2/0340 | The PRT segment is used to describe what should be done with the parts or assemblies specified in the preceding SPI segment. |
2/0350 | The PRS segment is used to tell the current status of the parts specified in the SPI segment required to make the change. |
2/0400 | The repeated pairs of 234 and 234 data elements in the LIN segment can be used to list where this modified part or assembly is used. |
2/1700 | The CID segment may be used to define either a general class of properties, such as physical properties, or an individual property within a class. The CID loop allows the user the ability to define specifications such as the properties of the item or class, the environmental conditions under which the specifications apply, the test methods to be used, and other parameters related to properties within the current HL hierarchical level. |
2/2820 | Repetitions of the CSF loop allow several frequency changes (and the conditions that would trigger those changes) to be specified. |
2/2820 | If the conditions are such that several CSF values are activated at the same time, the value with the highest sampling rate shall prevail. |
2/2840 | The CID loop within the CSF loop is used to specify the conditions that will trigger activation of the conditional value in the CSF segment. |
2/2840 | Repetitions of the CID loop will have an implied logical AND between the conditions set in each iteration. |
2/2850 | The elements of the CID segment identify the conditional property. If the property is a measurement from within the manufacturing process of a plant environment, rather than the product, the segment also identifies the location where the measurements are to be observed. |
2/2860 | If the condition is based on single test measurements, the MEA segment is used to specify the units of measure, and the open or closed numeric range of the conditional test. |
rev 12/10/2024