Army · SSN history

374 Title not stated in source

Appendix I lists Army SSN 374 as deleted and suggests substitute codes 348, 505, 581, 583, 714, 815, 821, 825, 826, 835 and 848. These are suggested alternatives, not a documented merger or an automatic reassignment to any one specialty.

Codes named in this history

Codes without a directory match

  • 348 stated by the source. No directory or archive record matches.
  • 505 stated by the source. No directory or archive record matches.
  • 581 stated by the source. No directory or archive record matches.
  • 583 stated by the source. No directory or archive record matches.
  • 714 stated by the source. No directory or archive record matches.
  • 815 stated by the source. No directory or archive record matches.
  • 821 stated by the source. No directory or archive record matches.
  • 825 stated by the source. No directory or archive record matches.
  • 826 stated by the source. No directory or archive record matches.
  • 835 stated by the source. No directory or archive record matches.
  • 848 stated by the source. No directory or archive record matches.

Documented history

Title not stated in source

The deletion date is not stated. June 30, 1945 is the publication date of Change 2, not an established effective date for deleting SSN 374.

  • The table does not name SSN 374's specialty or describe its duties.
  • The record does not specify which suggested substitute applied to an individual.
Source extraction notes

Appendix I lists deleted SSN 374 with suggested substitutes 348, 505, 581, 583, 714, 815, 821, 825, 826, 835, 848. The table does not print the deleted specialty title, so the neutral title placeholder is used. The row-level deletion date is unstated. The citation dates Change 2 to 30 June 1945; that publication date is not an effective deletion date.

Source documents (1)

Reviewed September 23, 2026 against references 1 and 2.

Historical information is drawn from the sources linked above. Classification dates are not personal service dates. Spot an error? Let us know.