| Version: | D |
|---|---|
| Release: | 01A |
| Contr. Agency: | UN |
| Revision: | 1 |
| Date: | 2000-10-26 |
| SOURCE: | D2 Purchasing (SWG) |
|
For general information on UN standard message types see UN Trade Data Interchange Directory, UNTDID, Part 4, Section 2.3, UN/ECE UNSM General Introduction |
|
This message also occurs in the following versions of this standard: D00A, D00B, D01A, D01B, D01C, D02A, D02B, D03A, D03B, D04A, D04B |
This specification provides the definition of the Repair call message (RPCALL) to be used in Electronic Data Interchange (EDI) between trading partners involved in administration, commerce and transport.
A message sent by a manufacturer or a call centre with information addressed to servicing and repair centres with details of appliances requiring repair or service. The information provided by the manufacturer or a call centre may include, details of the appliance, symptoms and faults, service history and previous repairs, parts already replaced, location where the appliance it is to be found as well as contact details.
The Repair call message may be used for both national and international applications. It is based on universal practice related to administration, commerce and transport, and is not dependent on the type of business or industry.
The RPCALL message can be used to inform service and repair centres on one or more repair calls that are proposed by a manufacturer or a call centre.
The message may contain the following information relating to the appliance and its location:
The PROSRV message may be used to respond to the manufacturer or call centre indicating the details of the interventions.
See UNTDID, Part 4, Chapter 2.3 UN/ECE UNSM - General Introduction, Section 1.
See UNTDID, Part 4, Chapter 2.3 UN/ECE UNSM - General Introduction, Section 2.
This section should be read in conjunction with the segment table which indicates mandatory, conditional and repeating requirements.
The following guidelines apply to the whole message and are intended to facilitate the understanding and implementation of the message:
All specified dates/times should be in the format 'ccyymmdd'/'hhmm' unless all parties involved in the transaction agree that there is a functional requirement for an alternative format. Periods should be specified as whole numbers representing the required period as indicated in the format qualifier (weeks, months, etc.).
Where a choice of code or text is given, the code element should be used wherever possible.
Conditional data that is not required in the message should not be included.
Care must be taken that the segment qualifier in dependent segments does not conflict with the segment qualifier of the trigger segment of a group.
Free text information within the message should be avoided as this inhibits automatic processing.
Information to be provided in the Header section:
A service segment starting and uniquely identifying a message. The message type code for the Repair call message is RPCALL.
Note: Repair call messages conforming to this document must contain the following data in segment UNH, composite S009:
| Data element | 0065 | RPCALL |
| 0052 | D | |
| 0054 | 01A | |
| 0051 | UN |
A segment by which the sender must uniquely identify the message by means of its type, number and, when necessary, its function.
A segment specifying general dates and, when relevant, times related to the whole message. The segment must be included at least once to identify the message date.
A group of segments giving references and where necessary, their dates, relating to the whole message e.g. contract number.
A segment identifying the reference by its number and where appropriate a line number within a document.
A segment specifying the date/time related to the reference.
A group of segments identifying the parties and any associated information.
A segment identifying names and addresses of the parties, in coded or clear form, and their functions relevant to the message. Identification of the manufacturer or call centre and repair centre is mandatory for the message. It is recommended that where possible only the coded form of the party identification should be specified e.g. the manufacturer and repair centre are known to each other, thus only the coded identification is required.
A group of segments giving references only relevant to the specified party rather than the Repair call.
A segment identifying the reference by its number and where appropriate a line number within a document.
A segment specifying the date/time related to the reference.
A group of segments giving contact details of the specific person or department within the party identified.
A segment to identify a person or department, and their function, to whom communications should be directed.
A segment to identify a communications type and number for the contact specified.
Information to be provided in the Detail section:
0150 Segment group 5: DOC-DTM-FTX-SG6 A group of segments providing details of a individual repair call.
A segment to identify an individual repair call for an appliance.
A segment specifying date/time/period details relating to the repair call.
A segment with free text information relating to the repair call in coded or clear form, used when additional information is needed but cannot be accommodated within other segments. In computer to computer exchanges such text will normally require the receiver to process this segment manually.
A group of segments providing identification and a description of the line items within the group. This segment group may be repeated.
A segment identifying the line item by the line number and additionally identifying the appliance requiring service or repair.
A segment providing additional identification to the product specified in the line item segment, e.g. model number, serial number.
A segment to further describe the product. This segment should be used for products that cannot be fully identified by a product code or article number.
A segment specifying date/time/period details relating to the line item only, e.g. date of failure of product.
A segment indicating special conditions related the product, e.g. home repair or repair centre repair.
A group of segments giving references and where necessary, their dates, relating to the line item.
A segment identifying the reference by its number and where appropriate a line number within a document.
A segment specifying the date/time related to the reference.
A group of segments identifying the parties with associated information relevant to the line item only.
A segment identifying names and addresses of the parties, in coded or clear form, and their functions relevant to the line item. It is recommended that where possible only the coded form of the party identification should be specified. The product owner or location address details may have to be clearly specified, preferably in structured format.
A group of segments giving contact details of the specific person or department within the party identified.
A segment to identify a person or department, and their function, to whom communications should be directed.
A segment to identify a communications type and number for the contact specified.
A group of segments providing product characteristic details.
A segment to identify characteristics related to the problem, service or repair of the product e.g. defects, repair characteristics.
A segment to specify common product characteristic by value in either coded form or in free format.
A segment with free text information, in coded or clear form, used when additional characteristic information is needed but cannot be accommodated within other segments. In computer to computer exchanges such text will normally require the receiver to process this segment manually.
Information to be provided in the Summary section:
A segment by which control totals may be provided by the sender for checking by the receiver.
A service segment ending a message, giving the total number of segments in the message (including the UNH & UNT) and the control reference number of the message.
| ALI | Additional information | |
| BGM | Beginning of message | |
| CAV | Characteristic value | |
| CCI | Characteristic/class id | |
| CNT | Control total | |
| COM | Communication contact | |
| CTA | Contact information | |
| DOC | Document/message details | |
| DTM | Date/time/period | |
| FTX | Free text | |
| IMD | Item description | |
| LIN | Line item | |
| NAD | Name and address | |
| PIA | Additional product id | |
| RFF | Reference | |
| UNH | Message header | |
| UNT | Message trailer |
| ├─UNH Message header | ×1 | (M) |
| ├─BGM Beginning of message | ×1 | (M) |
| ├─DTM Date/time/period | ×99 | (M) |
| ├─Segment Group 1 | ×9999 | (C) |
| │─├─RFF Reference | ×1 | (M) |
| │─└─DTM Date/time/period | ×99 | (C) |
| ├─Segment Group 2 | ×999 | (C) |
| │─├─NAD Name and address | ×1 | (M) |
| │─├─Segment Group 3 | ×99 | (C) |
| │─│─├─RFF Reference | ×1 | (M) |
| │─│─└─DTM Date/time/period | ×9 | (C) |
| │─└─Segment Group 4 | ×99 | (C) |
| │───├─CTA Contact information | ×1 | (M) |
| │───└─COM Communication contact | ×9 | (C) |
| ├─Segment Group 5 | ×99999 | (C) |
| │─├─DOC Document/message details | ×1 | (M) |
| │─├─DTM Date/time/period | ×9 | (C) |
| │─├─FTX Free text | ×9 | (C) |
| │─└─Segment Group 6 | ×99999 | (C) |
| │───├─LIN Line item | ×1 | (M) |
| │───├─PIA Additional product id | ×99 | (C) |
| │───├─IMD Item description | ×99 | (C) |
| │───├─DTM Date/time/period | ×99 | (C) |
| │───├─ALI Additional information | ×9 | (C) |
| │───├─Segment Group 7 | ×999 | (C) |
| │───│─├─RFF Reference | ×1 | (M) |
| │───│─└─DTM Date/time/period | ×9 | (C) |
| │───├─Segment Group 8 | ×999 | (C) |
| │───│─├─NAD Name and address | ×1 | (M) |
| │───│─└─Segment Group 9 | ×9 | (C) |
| │───│───├─CTA Contact information | ×1 | (M) |
| │───│───└─COM Communication contact | ×9 | (C) |
| │───└─Segment Group 10 | ×9999 | (C) |
| │─────├─CCI Characteristic/class id | ×1 | (M) |
| │─────├─CAV Characteristic value | ×99 | (C) |
| │─────└─FTX Free text | ×99 | (C) |
| ├─CNT Control total | ×99 | (C) |
| └─UNT Message trailer | ×1 | (M) |