Policy Locations

Issues and policies can be owner_key specific, vendor specific, or universal. These issues can have policies defined in one of three places.

MDB
Description
Owner_Key MDB
This is an MDB that exists in the Owner_Key specific directory under the custom directory defined in the File_GRPS table. This MDB must have a name equal to the value contained in the Owner_Key on the freight bill followed by “.MDB”. If the value of Owner_Key is “001-0001”, then the MDB must be named “001-0001.MDB”. If any customer specific issues or policies exist, they should be placed inside a valid FA_Policy table structure inside of this MDB.
Vend_Labl MDB
This is an MDB that exists in the Owner_Key specific directory under the custom directory defined in the File_GRPS table. This MDB must have a name equal to the value contained in the Vend_Labl on the freight bill followed by “.MDB”. If the value of Vend_Labl is “ABCD”, then the MDB must be named “ABDC.MDB”. If any vendor specific issues or policies exist, they should be placed inside a valid FA_Policy table structure inside of this MDB. This table should not have any customer specific policies and should be the same for all instances of the same vendor for a specific release of the Class_Properties.
CLASSDEF.MDB
This is a universal MDB which exists in the default directory unless specified as otherwise in the File_GRPS and MDBs tables. This MDB must exist in the workgroup environment or the financial audit process will not function. Inside of this MDB is a valid FA_Policy table. This table contains the universal issues and policies and provide the default policies.

NOTE For the financial audit process to work, only the CLASSDEF.MDB must exist. The other MDBs and their FA_Policy tables need to exist only if you want to override a universal policy or add a new customer or vendor specific policy.

Related Topics

Financial Audit Classes Overview

Overview of the Financial Audit Process

Financial Issue Categories

Financial Action Policies

Financial Policy Application

Financial Policy Hierarchy

Policy Locations

Overriding the Universal Policy of Each Issue

FA_Policy Table Structure

Financial Audit Issue Variables

Carrier Audit Profile

Financial Audit Policy Classes

Execution Order of Classes

Universal FA_CODEs

MDB	Description
Owner_Key MDB	This is an MDB that exists in the Owner_Key specific directory under the custom directory defined in the File_GRPS table. This MDB must have a name equal to the value contained in the Owner_Key on the freight bill followed by “.MDB”. If the value of Owner_Key is “001-0001”, then the MDB must be named “001-0001.MDB”. If any customer specific issues or policies exist, they should be placed inside a valid FA_Policy table structure inside of this MDB.
Vend_Labl MDB	This is an MDB that exists in the Owner_Key specific directory under the custom directory defined in the File_GRPS table. This MDB must have a name equal to the value contained in the Vend_Labl on the freight bill followed by “.MDB”. If the value of Vend_Labl is “ABCD”, then the MDB must be named “ABDC.MDB”. If any vendor specific issues or policies exist, they should be placed inside a valid FA_Policy table structure inside of this MDB. This table should not have any customer specific policies and should be the same for all instances of the same vendor for a specific release of the Class_Properties.
CLASSDEF.MDB	This is a universal MDB which exists in the default directory unless specified as otherwise in the File_GRPS and MDBs tables. This MDB must exist in the workgroup environment or the financial audit process will not function. Inside of this MDB is a valid FA_Policy table. This table contains the universal issues and policies and provide the default policies.