All factors have the capability of having different values depending on some characteristic of an associated object such as an asset, or the asset billing address. For example, a factor used to levy a waste disposal fee would have a different rate depending on the waste management district associated with the asset’s address. Factors share a common structure, made up of the following tables:
A factor contains descriptive information and attributes that control how the factor may be used in the system.
A factor characteristic value defines each instance of a characteristic for which there is a unique value for a charge. In the waste management district example, a factor characteristic value would exist for each district that levied a waste management fee.
Each factor characteristic may have many factor values over time. To continue the example, waste management fees may vary from one revenue year to another.
Some factors don't need a characteristic. There are factors whose value does not differ based on a characteristic. For example, the values of a factor that levies a state wide asset related charge will not vary because of a specific asset attribute. However, because of the relational design of the system, every factor value must reference both a factor and a characteristic value in the database. The base product provides two factor business objects to support the different situations. The Simple Factor BO flattens the characteristic type and value to base values of ‘Not Applicable’, so that only the factor details and effective values need to be entered. The Characteristic Based Factor BO supports the maintenance of the complete factor, factor characteristic values and factor values relationship.
For more information about setting up characteristics, see Setting Up Characteristic Types & Their Values.
Copyright © 2007, 2016, Oracle and/or its affiliates. All rights reserved. Documentation build: 2.5.2016 10:21:45 [T1_1454696505000]