Reports & Documentation
Chapter 1 — Printouts

Test reports

Complete & Continue Next Lesson Learn More

LESSON INFO

Audience

  • Customer service and quality teams who need to provide customer-ready documentation.
  • Shipping/receiving supervisors who validate documentation completeness before release.
  • Admins responsible for report access and ensuring test data is trustworthy.

Prerequisites

  • Your user/role has permission to view the underlying test data and to generate printouts.
  • The inventory item(s) have test data recorded (chemistry/coating/mechanical, as applicable).
  • You know the customer context (customer name, PO, heat/lot, and any required customer references).

Skills you’ll build

  • Generate a Test Report (certificate of analysis) that is consistent and traceable.
  • Validate that report values match system test data before sending externally.
  • Troubleshoot common issues: missing fields, wrong item selection, and permission blocks.
  • Maintain audit-friendly behaviour (what was generated, from what data, by whom).

LESSON OUTLINE

Concept

  • A Test Report is a standardized, printable certificate of analysis generated from system test data.
  • The report provides:
    • Traceability to specific system records (item identity, heat/lot, specs).
    • Reduced manual retyping and formatting.
    • Permission controls on which users are able to generate/export report data.
    • The Test Report is read-only in Themis-Trace. Themis-Trace does not perform the underlying tests; it displays the latest stored test results for the item context.

Generate a Test Report for an inventory item in the Web App

  1. Locate the item:
    • Open Inventory → Inventory Items and search by Item ID, TTIN, heat/lot, or other known identifiers.
  2. Open the item record and confirm you have the correct item:
    • Facility
    • Customer
    • Product type
    • Heat / lot / melt (as applicable)
    • Grade/spec context (as applicable)
  3. Open the Documents menu.
  4. Select Test Report.
  5. Review the preview/output:
    • Confirm chemistry/coating/mechanical sections reflect the latest stored test data for the item context and show the correct units of measure.
    • Confirm optional customer fields (PO, customer references) are correct when present.
    • Expect blank fields when source data is missing (do not interpret missing data as 0).
  6. Export/print according to your site process:
    • Print for physical paperwork, or export to a file as required.

Export (Power BI embedded report)

  1. In the embedded report toolbar, select File.
  2. Select Export.
  3. Select Excel.
  4. Save the exported file.

Verification

  • For a known item with known test data:
    • Generate a Test Report.
    • Confirm the report includes the correct item identity and audit markers (timestamps/user) if present.
    • Optional: spot-check that key sections appear when populated (general fields, chemistry, coating, mechanical, and test dates if present).

COMMON QUESTIONS

    • Likely cause

      • Permissions are restricting your access.

    • Checks

      • Confirm your role has access to Printouts/Test Reports.

    • Fix

      • Ask an admin to enable the printout and/or grant permissions.

    • Likely cause

      • Test data is missing or not associated to the item/spec.

    • Checks

      • Open the item’s test data details and confirm results exist for the expected categories.

    • Fix

      • Correct/supply test data, then regenerate the report.

    • Likely cause

      • Wrong item selected, wrong customer references, or outdated test data.

    • Checks

      • Reconfirm item identity (heat/lot/spec) and customer fields.

    • Fix

      • Regenerate after correcting the source record(s); do not hand-edit the printed output without documenting the exception process.

    • Likely cause

      • The expected message type (EDI 863) is not supported for this workflow/customer integration.

      • EDI is not enabled for the current customer.

      • The workflow did not generate a transmission for this record, or the transmission failed / downstream processing is delayed.

    • Checks

      • Open the relevant record’s edit form and review the EDI Transmissions tab.

        • Confirm whether an outbound transmission exists for the timeframe you expected.

      • Confirm EDI is enabled for the current customer.

    • Fix

      • If no transmissions exist on the EDI Transmissions tab: escalate with the record identifier(s), customer, facility, and the date/time the workflow step completed.

      • If transmissions exist but the customer didn’t receive them: escalate with the transmission identifier(s) and timestamp(s).

      • If EDI isn’t enabled for the customer: have an admin enable/configure it via the Customers menu, then re-test.