Understand saved-part-number batch reports

The account NSN batch route and a separate legacy part-number cross report have different inputs and account scope. This reference distinguishes them; the detailed current account workflow is linked below.

How to reach this report reference

This article describes report output. In the application, begin at Search by NSN/NIIN, choose Create a Batch Report, and complete the Batch Reporting form. The output appears after Create Report. The form's Back returns to the preceding search page, but does not undo the saved-list replacement.

Current account NSN batch report

The current Create a Batch Report route accepts an account list of NSNs. Its historical report name mentions part numbers, but that name does not change the input into a commercial-part-number list. The batch input and report field guide explains every input, replacement effect, section selector and actual report-design column. It also distinguishes typed text from file input and explains the automatic Excel response.

The report uses the displayed labels documented in the batch input and report field guide. Some catalog fields, such as FIIG and INC, are not printed as report columns.

Submitting a new list replaces the account's saved list. Review the replacement behavior in the input guide before creating a report.

Part-number cross report

A separate legacy part-number report can show a saved Part Number, matched NSN, item Name, CAGE and Company Name. Its list is shared across accounts: uploading a new part-number list can replace the list another account is using. Avoid that legacy upload for customer work. Use the account-specific NSN batch workflow instead.

Example and release gate

A parts seller could compare a maintained list of exact part numbers with matched NSNs, then research each NSN's reference number, technical constraints and buying notice. The shared-list warning above applies to the legacy cross report.