Scribd Logo
Upload

Welcome to Scribd!

  • Faulty Tag

    Uploaded by

    Javier Begazo
    11 views1 page
    This document provides information for returning faulty goods. It includes fields for the customer name and contact information, product details like the bar code and goods description, and details of the fault like the date, phenomena, and category number. The reasons for repair are also listed, including warranty repairs, damage from deployment, transit, version upgrades, batch replacements, and other issues. Notes are provided about covering interfaces, analysis boards not being returned, using one fault tag per return category, and mandatory fields marked with an asterisk.

    Original Description:

    Original Title

    Faulty_Tag

    Copyright

    © © All Rights Reserved

    Available Formats

    XLSX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Report this Document
    This document provides information for returning faulty goods. It includes fields for the customer name and contact information, product details like the bar code and goods description, and details of the fault like the date, phenomena, and category number. The reasons for repair are also listed, including warranty repairs, damage from deployment, transit, version upgrades, batch replacements, and other issues. Notes are provided about covering interfaces, analysis boards not being returned, using one fault tag per return category, and mandatory fields marked with an asterisk.

    Copyright:

    © All Rights Reserved
    Download as XLSX, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    Download as xlsx, pdf, or txt
    11 views1 page

    Faulty Tag

    Uploaded by

    Javier Begazo
    This document provides information for returning faulty goods. It includes fields for the customer name and contact information, product details like the bar code and goods description, and details of the fault like the date, phenomena, and category number. The reasons for repair are also listed, including warranty repairs, damage from deployment, transit, version upgrades, batch replacements, and other issues. Notes are provided about covering interfaces, analysis boards not being returned, using one fault tag per return category, and mandatory fields marked with an asterisk.

    Copyright:

    © All Rights Reserved
    Download as XLSX, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    Download as xlsx, pdf, or txt
    of 1

    Faulty Tag

    *Customer’s Name : CLARO date :

    Address : AV. ARRIOLA 480, LA VICTORIA, LIMA - PERU


    Contact Person : STEVEN TORRES Contact Number : 997109236 Ticket:
    Fax: N/A

    Return Analysis
    Category*:
    Fault occurring
    Description of the fault Category No.*（分 Software Version* （软件
    Bom code (Bom 编码） Goods Description （产品描述） Bar Code* （条形码） Date*（故障日期 Site
    phenomena*（故障现象） 类号） 版本）
    ）

    Reasons for Repairing(Category No.):


    Category No. includes the following 8 types: F001— wear out damaged （◇In warranty Period ◇Out of Warranty Period ）, F002—deployment damaged, F003—intransit damaged, F004－Version upgrade, F005－batch replace, F007－overdue spare parts inspecting, F008—Othe

    Notes:
    1.For optical boards returned, the optical interface should be covered with the safety cap.
    2.As usually the analysis board will not be returned to you , if you have any special requirements , pls let us know .
    3.One Fault Tag should be adapted one return category , such as RMA / Return / Analysis .
    4.Please notice the mark "*" is the necessary content that you must fill in.

    You might also like