Understanding Minor Keys for Billing AAIs
You must specify at least one minor key for each billing AAI table that you set up. The minor key must include:
- Obj From (object from), Obj Thru (object through), Sub From (subsidiary from), and Sub Thru (subsidiary through)
Specifies the range of objects and subsidiaries to use to assign accounting rules. The object and subsidiary of the workfile transaction must be within the specified range to use this accounting rule. If you leave the object range blank, all objects are eligible for this rule. If you leave the subsidiary range blank, all subsidiaries are eligible for this rule.
The accounts that are selected by this range should be nonbillable accounts so that Contract and Service Billing does not process the resulting transactions again.
- Subledger and Sub Type (subledger type)
Specifies the subledger and subledger type to use to assign accounting rules. The subledger and subledger type of the workfile transaction must match these entries to use this accounting rule. If you leave the subledger and subledger type blank, all subledgers and types are eligible for this rule. If you enter a subledger, you must enter a subledger type; conversely, if you enter a subledger type, you must enter a subledger.
Note: When you set up this accounting rule for key type 1, the work order that you assign as the table key value will be supplied as the default value to the subledger with a subledger type W.- G/L Offset
Specifies the G/L offset to use to assign accounting rules. If you leave the G/L Offset field blank, all G/L offsets are eligible for this rule. The G/L offset of the workfile transaction is compared to this value, except for AAI number 4815 (Tax Liability), for which the system uses the G/L offset of the tax authorities that you set up in the tax rate area table.
- Component Code
Identifies the component code to use to assign accounting rules. You leave this field blank to enable base and component workfile transactions to use this accounting rule. You update this field with a valid component code to assign accounting rules to component workfile transactions that are different from the accounting rules that are set up for the base workfile transactions. When the system does not find a component code in the Billing AAI table that exactly matches the component workfile transaction, it uses the accounting rule that you set up for the base workfile transaction.
For example, if a base workfile transaction has three component workfile transactions, OVH (overhead), GA (general and administrative), and FEE (fees), and you want the OVH revenue that is assigned to an accounting rule to be different from that of the base or the other component workfile transactions, you would set up two accounting rules: one accounting rule with OVH entered in the Component Code field to process the OVH revenue, and another accounting rule with a blank component code to process the base, GA, and FEE workfile transactions.
- Burden Category
Identifies the burden category to assign accounting rules. The system uses burden categories to assign accounting rules in the same way as component codes. You can use a burden category or a component code, but not both. Examples of burden categories include FR, for fringe, and OV for overhead.
The system displays this field on the AAI Base Rule Revisions form only if you have selected the Burdening Used check box in the Billing Constants program (P48091).