Quite apart from the main concern of your post, the comparison of hashes, another thing that comes to mind is that the sight of those serried ranks of lexical variables marching down the page makes my brain hurt. Not to go all sundialsvc4 on you, but this looks like a guaranteed, copper-bottomed MaintenanceNightmare™.

One approach to this type of organizational problem is to define constant sets of tags. These tags, which can be, e.g., strings, can then be used as hash keys, header lines (when concatenated together), etc. A tag set never changes its order once defined. They can be used with hash slices to assign to and extract data from hashes as an ordered set. E.g.:

c:\@Work\Perl\monks>perl -wMstrict -MData::Dump -le
"use constant INPUT_TAGS => (
   'Asset Name', 'Asset Application Id', 'Serial Number',
   'Asset Type', 'Activity Status',
   );
 ;;
 use constant OUTPUT_TAGS => (
   'Serial Number', 'Asset Type', 'Asset Name',
   );
 use constant OUTPUT_FORMAT => '%30s';
 ;;
 my $input_record =
   'Northwest Gammage Flocculator,AAI-123,SN9876,Flocculator,Taking Up
+ Space';
 ;;
 my %hash;
 @hash{ INPUT_TAGS() } = split ',', $input_record;
 dd \%hash;
 ;;
 print join ' | ', map sprintf(OUTPUT_FORMAT, $_),        OUTPUT_TAGS;
 print join ' | ', map sprintf(OUTPUT_FORMAT, $_), @hash{ OUTPUT_TAGS(
+) };
"
{
  "Activity Status"      => "Taking Up Space",
  "Asset Application Id" => "AAI-123",
  "Asset Name"           => "Northwest Gammage Flocculator",
  "Asset Type"           => "Flocculator",
  "Serial Number"        => "SN9876",
}

                 Serial Number |                     Asset Type |     
+                Asset Name
                        SN9876 |                    Flocculator |  Nor
+thwest Gammage Flocculator
[download]

Note that to disambiguate a constant list for use with a hash slice, the  () (subroutine invocation) operator must be used (update:  & could be used as well, e.g.  &INPUT_TAGS (update: but see choroba's pertinent comment here)) to prevent Perl from interpreting something like  INPUT_TAGS as a string.

Another point is that rather than using a naive split, it's almost always better to use Text::CSV_XS or Text::CSV for extracting CSV-ish data.

Update: Corrected small code example error.

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.