The universal policy of each issue on a transaction can be overridden as
follows:
1. For each issue found, the financial audit process checks to see if a customer
specific policy record exists. If one exists and the FA_Policy field is not
Null, then the policy in the custom specific MDB is applied.
2. If the lookup into the custom specific MDB returns a Null, the financial audit
process checks to see if a vendor specific policy record exists. If one
exists and the FA_Policy field is not Null, then the policy in the vendor specific
MDB is applied.
3. If the lookup into the vendor specific MDB returns a Null, the financial audit
process checks to see if a universal policy record exists. If one exists and
the FA_Policy field is not Null, then the policy in the vendor specific MDB is
applied.
4. If no policy exist in these tables, an exception will be generated reporting
that no policy record was found and will recommend that one be added to at least
one of these tables.
Overriding the Universal Policy of Each Issue