my %hash
open FILE, "</path/to/your/data/file.csv";
while ( my $line = <FILE> ) {
  chomp $line;
  my ( $key, $data ) = split ";", $line;
  $hash{$key} = $data;
}
[download]

In a file named "shared-hash.dat":

my %hash = (
    '000001' => 'ITEM _First',
    '000002' => 'Item B',
    '000003' => 'House',
    '000004' => 'Service C',
    '000005' => 'Service X',
    '000006' => 'Service Z',
    '00007b' => 'Adjust Area',
    '020902' => 'Campus',
    '0sdc45' => 'Unit C',
    '000011' => 'Unit B',
    '0wed45' => 'Lower Level',
    '0ws456' => 'Cars',
    '02100m' => 'Numbers'
);
[download]

my %hash = do "shared-hash.dat";
[download]

If you need the programs to write back to the hash (and have those changes shared), you will have to do something a little more involved, but it didn't sound like that was the case from your description.

You want to create a module. You'll probably want to read perlmod first. Here's a very basic example to get you started (untested):

############################
# filename: MyFirstModule.pm

package MyFirstModule;

our %common_codes_hash = (
    '000001' => 'ITEM _First',
    '000002' => 'Item B',
    '000003' => 'House',
    # ....);

1;

__END__

########################
# filename: myscript1.pl

use MyFirstModule;

my $whatever = $MyFirstModule::common_codes_hash{$foo};

# ....

__END__
[download]

Later, you can get fancy by using Exporter to export your common data structures or functions into the script's namespace, and other things.

Update: changed the my to our (realized the error at the same time as snowcrash).

>   my %common_codes_hash = (....);
[download]

In the module, the file MyFirstModule.pm, %common_codes_hash should be declared with our instead of my. Otherwise it won't work if you put the module and script in two seperate files.

snowcrash

itīs a matter of taste, but i whouldnīt store data in modules but in datafiles, textfiles, databases etc.
modules are for sharing code, not data.

Except when modules are for sharing data (HTTP::Status, Unicode::CharName , etc)

Use DB_File or some other DBM module to create a DBM file that stores the hash on disk, then just have each script declare a hash and tie() it to the DBM file. Tying a hash changes its behavior; when you tie a hash to a DBM file, you can make the hash absorb the contents of the hash in the DBM file, make it so any changes to the hash also modify the hash in the DBM file, and other neat stuff depending on the DBM library.

This code here creates the hash and stores it the hash.dbm DBM file:

use DB_File;

my %hash;
tie (%hash, 'DB_File', 'hash.dbm', O_CREAT|O_RDWR) || die $!;
%hash=(
    '000001' => 'ITEM _First',
    '000002' => 'Item B',
    '000003' => 'House',
    '000004' => 'Service C',
    '000005' => 'Service X',
    '000006' => 'Service Z',
    '00007b' => 'Adjust Area',
    '020902' => 'Campus',
    '0sdc45' => 'Unit C',
    '000011' => 'Unit B',
    '0wed45' => 'Lower Level',
    '0ws456' => 'Cars',
    '02100m' => 'Numbers'
);
[download]

Afterwards, any script that wants to manipulate the hash in hash.dbm need only just tie() the DBM file for reading and writing, like this:

use DB_File;

my %hash
tie (%hash, 'DB_File', 'hash.dbm', O_RDWR) || die $!;
[download]

then modifying %hash will result in modifying the hash stored in hash.dbm.

If you want a hash in one script to be able to copy the contents of the hash in hash.dbm but not to actually modify it, then tie() the hash for reading only instead of for reading and writing:

my %hash
tie (%hash, 'DB_File', 'hash.dbm', O_RDONLY) || die $!;
[download]

now modifying %hash won't affect the hash stored in hash.dbm.

While less readable, Data::Dumper saves info in a Perl syntax but is part of the standard Perl install.

I think most end-user-type folks would generally prefer to edit YAML by hand rather than Perl.