FA_Policy Table Structure

The structure of a valid FA_Policy table is as follows:

Heading
Description
FA_CODE
This field contains the label for a financial audit issue. These can be appended to any of the predefined issue variables from inside of any rules class that executes prior to the FA class. In addition to being set outside of the FA_Policy classes, most of these issues are automatically detected from inside of the financial audit classes. As these issues are discovered, they are stored into preset variables in File Express list format (e.g. [issue 1][issue 2]). This is a mandatory field and forms the first part of the primary key.
ORDINAL
This field can contain any valid number and is used to sort issue records with the same FA_Code in the order you want the FA_POLICY_EFF_EXPR to be evaluated. This is a mandatory field and forms the second part of the primary key.
FA_POLICY_EFF_EXPR
This field should contain a valid rules engine expression that returns True if this record is valid in the executing context. For records which have the same FA_CODE, these expressions are evaluated in the order of the ORDINAL number. The first record where the expression in this field returns True will be the record used for the field lookup being performed. If you do not have multiple records with the same FA_Code and the record is valid for every transaction that has the issue described by the FA_CODE, this field should contain the word True. This field can be used to limit a specific record to a list of carriers or to define different policies for different accessorial codes.
For example the expression {CString(AR_Service_Code) = "405"} would only return True if the accessorial service code as “405” a fuel surcharge.
FA_DESC
This field contains a textual description that describes the issue the FA_Policy record is meant to address.
FA_POLICY
This field determines what should be done as a result of the issue existing on the bill. The valid values for this field are; Pay_Billed, Pay_Rated, Deny, or Exception.
FA_EX_DESC
This field contains the user description which will be provided on the exception screen when this issue exists and at least one of the policies for one of the issues is Exception. It is important that this field contain as useful a description as possible. Even though the policy is not Exception, at least one of the FA_Policy tables should contain a description since the user is provided with all descriptions for all found issues when one of the issues has a policy of Exception.

If the contents of this field start with an equal sign (e.g. =“some text ” & {some expression}), then the contents are assumed to be an expression which is to be evaluated within the context of the current freight bill transaction and returns the description.
FA_VEND_REASON
This field contains the code which is to be sent to the vendor in a 820 or on a fax which defines the reason for an adjustment to the billed amount. This is normally a standard EDI code but can be any code that a vendor wants to receive in the vendor specific MDB.

If the contents of this field start with an equal sign (e.g. =“some text ” & {some expression}), then the contents are assumed to be an expression which is to be evaluated within the context of the current freight bill transaction and returns the reason.
FA_VEND_REASON_DESC
This field contains the free form text that you want to supply the vendor to describe an adjustment made to the billed amount. Due to some of the older EDI standards, this field or the results of this field should be limited to 34 characters.

If the contents of this field start with an equal sign (e.g. =“some text ” & {some expression}), then the contents are assumed to be an expression which is to be evaluated within the context of the current freight bill transaction and returns the reason.

NOTE When the financial audit process looks up fields 6-8, it will select the first non-Null value from the Customer, Vendor, and Universal tables respectively. For maintenance reasons, it is a good idea to only place values in the fields of the customer and vendor specific tables that are required to override the values provided in the universal table. This will allow easier maintenance when enhancements are or bug fixes are released.

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

Heading	Description
FA_CODE	This field contains the label for a financial audit issue. These can be appended to any of the predefined issue variables from inside of any rules class that executes prior to the FA class. In addition to being set outside of the FA_Policy classes, most of these issues are automatically detected from inside of the financial audit classes. As these issues are discovered, they are stored into preset variables in File Express list format (e.g. [issue 1][issue 2]). This is a mandatory field and forms the first part of the primary key.
ORDINAL	This field can contain any valid number and is used to sort issue records with the same FA_Code in the order you want the FA_POLICY_EFF_EXPR to be evaluated. This is a mandatory field and forms the second part of the primary key.
FA_POLICY_EFF_EXPR	This field should contain a valid rules engine expression that returns True if this record is valid in the executing context. For records which have the same FA_CODE, these expressions are evaluated in the order of the ORDINAL number. The first record where the expression in this field returns True will be the record used for the field lookup being performed. If you do not have multiple records with the same FA_Code and the record is valid for every transaction that has the issue described by the FA_CODE, this field should contain the word True. This field can be used to limit a specific record to a list of carriers or to define different policies for different accessorial codes. For example the expression {CString(AR_Service_Code) = "405"} would only return True if the accessorial service code as “405” a fuel surcharge.
FA_DESC	This field contains a textual description that describes the issue the FA_Policy record is meant to address.
FA_POLICY	This field determines what should be done as a result of the issue existing on the bill. The valid values for this field are; Pay_Billed, Pay_Rated, Deny, or Exception.
FA_EX_DESC	This field contains the user description which will be provided on the exception screen when this issue exists and at least one of the policies for one of the issues is Exception. It is important that this field contain as useful a description as possible. Even though the policy is not Exception, at least one of the FA_Policy tables should contain a description since the user is provided with all descriptions for all found issues when one of the issues has a policy of Exception. If the contents of this field start with an equal sign (e.g. =“some text ” & {some expression}), then the contents are assumed to be an expression which is to be evaluated within the context of the current freight bill transaction and returns the description.
FA_VEND_REASON	This field contains the code which is to be sent to the vendor in a 820 or on a fax which defines the reason for an adjustment to the billed amount. This is normally a standard EDI code but can be any code that a vendor wants to receive in the vendor specific MDB. If the contents of this field start with an equal sign (e.g. =“some text ” & {some expression}), then the contents are assumed to be an expression which is to be evaluated within the context of the current freight bill transaction and returns the reason.
FA_VEND_REASON_DESC	This field contains the free form text that you want to supply the vendor to describe an adjustment made to the billed amount. Due to some of the older EDI standards, this field or the results of this field should be limited to 34 characters. If the contents of this field start with an equal sign (e.g. =“some text ” & {some expression}), then the contents are assumed to be an expression which is to be evaluated within the context of the current freight bill transaction and returns the reason.