EDI 142 Product Service Claim

Functional Group WA

X12M Supply Chain Subcommittee

This Draft Standard for Trial Use contains the format and establishes the data contents of the Product Service Claim Transaction Set (142) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to transmit the servicing organization, claimant, manufacturer, seller, and purchaser of the product. It can specify the product's current usage, date the product was sold, delivered, and placed in service as well as identify product model and serial numbers and serial numbers of any subassemblies. It can specify a malfunction or recall condition, service performed, labor, parts, and any other associated costs. It can show the costs of the repair and the date service was requested and when it was available to be placed back in service.

Heading

1. 010 · ST · Transaction Set Header · Max 1 · Mandatory

   To indicate the start of a transaction set and to assign a control number

2. 020 · BGN · Beginning Segment · Max 1 · Mandatory

   To indicate the beginning of a transaction set.

   BGN02 contains the warranty reference number. This could be a batch number for a group of claims. It will be used in LIN03 in the corresponding product service claim response transaction (141). BGN03 contains the product service claim transaction original creation date.

3. 025 · N9 · Reference Number · Max >1 · Optional

   To transmit identifying numbers and descriptive information as specified by the reference number qualifier

4. N1 Loop Mandatory Repeat 4

   1. 030 · N1 · Name · Max 1 · Mandatory

      To identify a party by type of organization, name and code

      The N1 loop identifies the sending party, usually the servicing organization, and the receiving party, usually the product's manufacturer. In addition, a third party, such as the product's distributor, can be identified. It is also possible to specify a secondary warranter such as a credit card issuer or a motor oil manufacturer.

   2. 040 · N2 · Additional Name Information · Max 2 · Optional

      To specify additional names or those longer than 35 characters in length

   3. 050 · N3 · Address Information · Max 3 · Optional

      To specify the location of the named party

   4. 060 · N4 · Geographic Location · Max 1 · Optional

      To specify the geographic place of the named party

   5. 070 · REF · Reference Numbers · Max 2 · Optional

      To specify identifying numbers.

      An independent servicing agency, usually identified as the sending party in the first iteration of the N1 loop, has a servicing contract with the manufacturer, usually the receiving party identified in the second iteration of the N1 loop. The REF segment in the N1 loop can contain the identity of this servicing contract between the two parties.

   6. 080 · PER · Administrative Communications Contact · Max 2 · Optional

      To identify a person or office to whom administrative communications should be directed

      The PER segment within the N1 loop of the heading area is used to refer to an individual for administrative purposes. It is not intended to be the one with whom technical issues would be discussed. The technical contacts would be contained in the PER segment within the N1 loops in the detail area. PER02 can be used to identify a person by name or job function or department.

Detail

1. LX Loop Mandatory Repeat >1

   1. 010 · LX · Assigned Number · Max 1 · Mandatory

      To reference a line number in a transaction set.

      The LX loop represents an individual claim. Normally a claim will be for an independent product, assembly, subassembly, or component. However, a single claim also can be used for a group of similar products to be submitted to a single party.

   2. 020 · N9 · Reference Number · Max 1 · Mandatory

      To transmit identifying numbers and descriptive information as specified by the reference number qualifier

      N902 in the first or only occurrence of a N9 segment at this position in the LX loop must contain the reference number for all charges in this iteration of the LX loop.

   3. LIN Loop Mandatory Repeat >1

      1. 030 · LIN · Item Identification · Max 1 · Mandatory

         To specify basic item identification data.

         The LIN loop must be used to describe the product being serviced. The LIN segment contains 235-234 data element pairs that can be used to identify the product manufacturer (MF), model number (MN), serial number (SN), equipment identification number (EM), vehicle identification number (VV), model year (RY), etc.

      2. 040 · PID · Product/Item Description · Max >1 · Optional

         To describe a product or process in coded or free-form format

         The PID segment provides capability for further description of a product that cannot be described in an LIN segment. PID03 to PID05 can be used to described these features, such as the cab configuration of a vehicle.

      3. 045 · LOC · Location · Max 1 · Optional

         To describe the location in space and time of the axis of an item relative to an origin axis; euclidian geometry has been assumed with orthogonal axes; the sequence of axes has been chosen in the customary sequence of X, Y, and Z; however, it is possible to just use two dimensional space rather than three

         The LOC segment is used to describe the position of equipment within a structure or an assembly, subassembly, or part within a piece of equipment in space relative to an origin. For example, it could describe the location of a telephone switch within a building and of an individual circuit card within the switch by giving the position of a drawer within a rack within a switch.

      4. 050 · QTY · Quantity · Max 1 · Optional

         To specify quantity information.

         The QTY segment in the LIN loop reflects the quantity of items that do not have a serial number and are being serviced together under one repair order. For all items with a serial number, the value to be used is either explicitly or implicitly set to one. It also can specify the current service life such as miles, kilometers, or hours of the product being serviced.

      5. 060 · DTM · Date/Time Reference · Max >1 · Optional

         To specify pertinent dates and times

         The DTM segment could contain product related dates such as product delivery date (035), acceptance date (301), service requested (211), returned to customer (212), purchased (304), and manufacturer (094).

      6. 070 · REF · Reference Numbers · Max >1 · Optional

         To specify identifying numbers.

         The REF segment provides additional data about the product, its registration data and servicing environment that don't fit well within the LIN segment either because it requires too much extraneous data to be sent or the required codes are not available in the codes lists of the data elements within the LIN segment, but are available within the Reference Number Qualifier data element used in the REF segment.

      7. 080 · PER · Administrative Communications Contact · Max 1 · Optional

         To identify a person or office to whom administrative communications should be directed

         The PER segment lists the contact at the servicing location for technical questions regarding the repair or condition of the product. This could be the service manager or service technician.

      8. 090 · PSC · Product Service Contract · Max >1 · Optional

         To describe the conditions of a product service contract as in a warranty registration

         The PSC segment describes the status of the warranty, the type of warranty, recall notice, service bulletin, or service contract or other conditions for the product that could allow a service claim in effect at the time of service, if any. It also identifies the service contract number in PSC05. The PSC segment is used to describe the period of the warranty or service contract.

      9. 100 · SSS · Special Services · Max >1 · Optional

         To specify special conditions or services associated with the purchased product

         The SSS segment can be used to describe conditions such as carry-in or on-site service.

   4. N1 Loop Optional Repeat >1

      1. 110 · N1 · Name · Max 1 · Mandatory

         To identify a party by type of organization, name and code

         The N1 loop will be used to specify the parties involved with the item being serviced. It could be the registered owner (RW), the one who requested service (SQ), the one who is to be notified when the service has been completed (N1), the item's owner (OW), the initial dealer (ID), or any combination of them. The N1 loop is optional. If the product had been registered, the ownership data should already be available and can be accessed by the model and serial numbers that are placed in the LIN segment. The N1 loop also can be used to identify individuals in the service shop associated with this claim. For example, it could be used to identify the individual who received the item from the customer and wrote the repair order (OE). Another possible use for the N1 loop is to identify who pre-approved the claim. The N9 segment within the N1 loop would be used for the appropriate authorization number.

      2. 120 · N2 · Additional Name Information · Max 2 · Optional

         To specify additional names or those longer than 35 characters in length

      3. 130 · N3 · Address Information · Max 3 · Optional

         To specify the location of the named party

      4. 140 · N4 · Geographic Location · Max 1 · Optional

         To specify the geographic place of the named party

      5. 150 · N9 · Reference Number · Max 2 · Optional

         To transmit identifying numbers and descriptive information as specified by the reference number qualifier

      6. 160 · PER · Administrative Communications Contact · Max 2 · Optional

         To identify a person or office to whom administrative communications should be directed

         The PER segment in the N1 loop can give the communications contact information, such as telephone number, of an owner's representative (OS) who can supply additional information about the complaint.

   5. PRR Loop Mandatory Repeat >1

      1. 170 · PRR · Problem Report · Max 1 · Mandatory

         To describe a product condition when presented for service or a recall notice or a service bulletin

         The PRR loop describes the reported problem. It can be a product recall or service bulletin as well as a customer complaint. Each iteration of the PRR loop describes a single problem. The complaints should be in a coded format contained in PRR04 so that the transaction can be processed by a computer program. The PRR segment can have a code that describes the urgency or severity of the problem.

      2. 180 · LIN · Item Identification · Max 1 · Optional

         To specify basic item identification data.

         If necessary, the LIN segment describes the portion of the entire product causing the complaint. For example, it may be a subassembly or component. If more than one subassembly is having a problem, each would be identified in a separate PRR loop. The LIN segment contains 235-234 data element pairs that can be used to identify the product manufacturer (MF), model number (MN), and serial number (SN).

      3. 185 · LOC · Location · Max 1 · Optional

         To describe the location in space and time of the axis of an item relative to an origin axis; euclidian geometry has been assumed with orthogonal axes; the sequence of axes has been chosen in the customary sequence of X, Y, and Z; however, it is possible to just use two dimensional space rather than three

         The LOC segment is used to describe the position of equipment within a structure or an assembly, subassembly, or part within a piece of equipment in space relative to an origin. For example, it could describe the location of a telephone switch wihtin a building and of an individual circuit card within the switch by giving the position of a drawer within a rack within a switch.

      4. 190 · QTY · Quantity · Max 1 · Optional

         To specify quantity information.

         The QTY segment can specify the quantity of components or subassemblies that do not have a serial number and are being serviced together under one service order. For all items with a serial number the value to be used is either implicitly or explicitly set to one. The QTY segment can also specify the current service life of the component or subassembly, such as mileage or time. The equivalent information regarding the entire product should be contained in the QTY segment within the LIN loop.

      5. 200 · DTM · Date/Time Reference · Max 1 · Optional

         To specify pertinent dates and times

         The DTM segment can be used, for example, to report the time of the failure (302).

      6. 210 · MSG · Message Text · Max >1 · Optional

         To provide a free form format that would allow the transmission of text information.

         The MSG segment can be used to describe the customer's complaint. Non-standard complaints that can't be coded in PRR04 can be placed here. This, however, limits the possibility of having a computer completely process the claim.

      7. 220 · RC · Root Cause · Max 1 · Optional

         To specify the specific part responsible for a customer complaint in a request for service of a product and/or to describe the particular failure mechanism in a failing part or assembly

         The RC segment can specify the principle part involved in the failure in RC02. If a part number is specified in RC02, then the condition of the part must be included in either RC06 or RC07. Any free form description of the root cause should be included in RC08. The use of RC08 will probably require human analysis. It may be that a root cause is entitled only to fixed reimbursement.

      8. 230 · PER · Administrative Communications Contact · Max 1 · Optional

         To identify a person or office to whom administrative communications should be directed

         The PER segment lists the contact at the servicing location for technical questions regarding the repair condition of the component or subassembly.

      9. 240 · PSC · Product Service Contract · Max >1 · Optional

         To describe the conditions of a product service contract as in a warranty registration

         The PSC segment describes the status of the warranty, the type of warranty, recall notice, service bulletin, or service contract or other conditions for the assembly or subassembly that could allow a service claim in effect at the time of service, if any. If the assembly or subassembly has a separate service contract that is different than that for the entire product, it can be identified in PSC05.

      10. 250 · SSS · Special Services · Max >1 · Optional

          To specify special conditions or services associated with the purchased product

          The SSS segment can be used to describe conditions that pertain only to the assembly or subassembly.

      11. CID Loop Optional Repeat >1

          1. 260 · CID · Characteristic/Class ID · Max 1 · Mandatory

             To specify the general class or specific characteristic upon which test results are being reported or are to be taken

             The CID segment describes a particular portion of the product which has individual test specifications. For example, the tuner in a television set.

          2. 270 · TMD · Test Method · Max >1 · Optional

             To describe the nature of the test performed.

             The TMD segment specifies a code test procedure which will be used in the analysis of the customer's complaint.

          3. MEA Loop Optional Repeat >1

             1. 280 · MEA · Measurements · Max 1 · Mandatory

                To specify physical measurements or counts, including dimensions, tolerances, variances, and weights (See Figures Appendix for example of use of C001.)

                The MEA segment provides the results of any testing done before performing the service. Unless noted otherwise, this same test usually will be performed at the completion of the service activity. The preceding CID specifies the test conditions.

             2. 290 · DTM · Date/Time Reference · Max 1 · Optional

                To specify pertinent dates and times

                Some tests may require being run at various intervals of time. The time the separate tests were run is specified here.

             3. 300 · LIN · Item Identification · Max >1 · Optional

                To specify basic item identification data.

                The LIN segment can contain the identity of the test equipment, if significant.

   6. REP Loop Mandatory Repeat >1

      1. 310 · REP · Repair Action · Max 1 · Mandatory

         To specify the action that was taken or is to be taken in response to a service request

         The REP loop is used to describe the actions that were taken in servicing a problem. There can be a separate REP loop for each individual repair action, such as for each part replaced or individual adjustment. If this repair was the result of a service bulletin, then the bulletin number would be specified in REP03. A repair action can be identified in REP08 or REP09. For example, it could be the replacement of a part or assembly (RT), performing a calibration (CL), performing an alignment (AL), soldering a component (SD), etc. The repair action (REP08) should be in a coded format so that the transaction can be processed by a computer program. REP01 can be used to identify the repair action line number for use in the product service claim response in LIN09 to identify this individual repair action.

      2. 320 · REF · Reference Numbers · Max >1 · Optional

         To specify identifying numbers.

         If you want to refer to a problem or a repair listed earlier in the transaction, REF02 provides an identifier to the relevant PRR loop (PRR01) or to a relevant earlier REP loop (REP01). REF01 would contain the qualifier of "prior identifier". For example, if this is an REP loop to calibrate a circuit because a printed circuit board was replaced, REF02 would be used to refer to the REP loop where the printed circuit board was replaced. This also could be used to refer to a reported problem by referencing PRR01.

      3. 330 · N1 · Name · Max 2 · Optional

         To identify a party by type of organization, name and code

         The N1 segment provides an identifier to the individual or organization that authorized this particular repair.

      4. 340 · RC · Root Cause · Max 1 · Optional

         To specify the specific part responsible for a customer complaint in a request for service of a product and/or to describe the particular failure mechanism in a failing part or assembly

         The root cause, specified by the RC - Root Cause segment, is the ultimate reason why this particular repair action had to be performed. For example, a loose lubrication fitting could result in the loss of lubricant which caused an assembly to fail. The root cause of this particular repair action then would be the loose lubrication fitting.

      5. 350 · DTM · Date/Time Reference · Max >1 · Optional

         To specify pertinent dates and times

         The DTM segment specifies dates and, if necessary, times that are important to the service operations performed on the product. For example, it can include the time service was requested, when the product was presented for service, the actual repair start and stop times, and when the product was returned to the customer after the completion of the service. Such detailed time information could be vital if there was a service contract that had a penalty if the item was out of service for more than a specified period of time.

      6. 355 · LIN · Item Identification · Max >1 · Optional

         To specify basic item identification data.

         The LIN segment within the REP loop is intended to be used to specify the parts used in the service action. The manufacturer, model and serial number, location or product, etc. can be specified.

      7. 360 · MSG · Message Text · Max >1 · Optional

         To provide a free form format that would allow the transmission of text information.

         The MSG segment can be used to describe a non-standard repair action. This, however, limits the possibility of having a computer completely process the claim. The use of a standard repair action in REP08 rather than putting a reason in an MSG segment allows computer processing of the claim.

      8. MEA Loop Optional Repeat >1

         1. 370 · MEA · Measurements · Max 1 · Mandatory

            To specify physical measurements or counts, including dimensions, tolerances, variances, and weights (See Figures Appendix for example of use of C001.)

            The MEA loop is for any tests that are run at the completion of the repair to prove that the product is now able to operate within the specifications as given in the CID loop within the PRR loop above. The function of segments within this MEA loop are the same as in the MEA loop above.

         2. 380 · DTM · Date/Time Reference · Max 1 · Optional

            To specify pertinent dates and times

            This is used, for example, when time is significant in the test procedures.

         3. 390 · LIN · Item Identification · Max >1 · Optional

            To specify basic item identification data.

            The LIN segment can contain the identity of the test equipment, if significant.

      9. IT1 Loop Optional Repeat >1

         1. 400 · IT1 · Baseline Item Data (Invoice) · Max 1 · Mandatory

            To specify the basic and most frequently used line item data for the invoice and related transactions.

            The IT1 segment is used to specify a charge associated with the servicing of one item. For example, each of the individual parts or assemblies can be specified by part number. It also can list the labor operation number and the standard labor hours for this repair. Each occurrence of IT101 within a single transmission must be a unique alphanumeric string. Therefore, it is possible, but not required, to use sequential numbers as the identifier in IT101.

         2. 405 · LIN · Item Identification · Max >1 · Optional

            To specify basic item identification data.

            The LIN segment within the IT1 loop is intended to be used to specify the parts or supplies that are being charged against the service action.

         3. 410 · N1 · Name · Max >1 · Optional

            To identify a party by type of organization, name and code

            The N1 segment is the source of a purchased replacement part.

         4. 420 · N9 · Reference Number · Max >1 · Optional

            To transmit identifying numbers and descriptive information as specified by the reference number qualifier

            The N9 segment, if necessary, can contain the invoice number for the purchased replacement part. It refers back to the previous N1 segment which identified the source of the part.

         5. 430 · PRT · Part Disposition · Max 1 · Optional

            To specify the disposition of the removed part, subassembly or assembly

            The PRT segment specifies the actual or specified disposition of the replaced part identified by the IT1 loop.

         6. 440 · ITA · Allowance, Charge or Service · Max >1 · Optional

            To specify allowances, charges or services

            The ITA segment specifies summary charges for each REP loop. This can include any special service charges, a minimum labor charge, and miscellaneous charges.

   7. AMT Loop Optional Repeat 1

      1. 450 · AMT · Monetary Amount · Max 1 · Mandatory

         To indicate the total monetary amount.

         AMT01 contains the amount claimed for this LX loop. The AMT loop contains financial data for the entire claim. Of course, the transmission could have been composed of more than one claim. If so, table 3 will contain the summary financial data for the entire transaction.

      2. 460 · TXI · Tax Information · Max >1 · Optional

         To specify tax information.

         The TXI segment specifies the taxes, usually sales tax, for each of the taxing jurisdictions that can be involved in this particular claim.

      3. 470 · CUR · Currency · Max 1 · Optional

         To specify the currency (dollars, pounds, francs, etc.) used in a transaction

         One or the other of the CUR segments in table 2 or 3 can be used, but not both. In table 2, CUR represents the currency in a single iteration of the LX loop. In table 3, it represents the currency for the entire transaction. CUR segments will only be used if there are two different currencies involved in the claim. For example, the claim is being submitted to a firm in the United States and the work was done in Canada and the claim is to be paid in Canadian funds.

Summary

1. TDS Loop Optional Repeat 1

   1. 010 · TDS · Total Monetary Value Summary · Max 1 · Mandatory

      To specify the total invoice discounts and amounts

      The TDS loop in table 3 is used to accumulate the total costs and charges associated with all items being claimed in this single transaction. This loop is placed at the end rather than the beginning of the transaction to supply the grand total and to simplify processing the accumulated values.

   2. 020 · TXI · Tax Information · Max >1 · Optional

      To specify tax information.

      The TXI segment specifies the taxes, usually sales tax, for each of the taxing jurisdictions that can be involved in this entire transaction.

   3. 030 · CUR · Currency · Max 1 · Optional

      To specify the currency (dollars, pounds, francs, etc.) used in a transaction

      The currency used specifies that for the entire transaction these are the currency conversion rates. The CUR segment in this TDS loop should not be used if the CUR segment was used in one or more iterations of the preceding AMT loop. That would have indicated that some of the individual claims within this transaction were to be paid in one currency and others in another currency.

2. 040 · SE · Transaction Set Trailer · Max 1 · Mandatory

   To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments).