DeleteBaseReallocationRules

Delete Billing AAI Base and Reallocation rules

Minor Business Rule

Object Name: N48S0095

Parent DLL: CCRIN

Location: Client/Server

Language: NER

Functional Description

Purpose
This Named Event Rule will perform the necessary deletes from the F48S95 (Billing AAI's) and the
F4090 (AAI Record Types) files depending on the directive issued from the calling application.

Setup Notes and Prerequisites
You will need to specify 1 of the following 5 directives:

"1" - Delete all Base and Reallocation Rules (F48S95) associated with the AAI Table
Number. Also, delete the AAI Record Type (F4090) representing the AAI Table
Number.

Required parameters are:

• AAI Table Number

"2" - Delete all Base and Reallocation Rules (F48S95) associated with a given
Table Number, Table Key Type, Table Key Value, Beginning Effective Date, and
Ending Effective Date.

Required parameters are:

• AAI Table Number
• Table Key Type
• Table Key Value
• Beginning Effective Date
• Ending Effective Date

"3" - Delete the selected Base Rule and all the associated Reallocation Rules (F48S95).

Required parameters are:

• AAI Table Number
• Table Key Type
• Table Key Value
• Beginning Effective Date
• Ending Effective Date
• Unique Key Identifier

"4" - Delete the selected Reallocation Rule (F48S95).

Required parameters are:

• Unique Key Identifier

"5" - Delete all the Reallocation Rules associated with a Base Rule (F48S95).

Required parameters are:

• Parent Unique Key identifier*

* Parent Unique Key Identifier - This field will carry the same value
found in the Unique Key ID for it's associated parent Base Rule. This
field will be used in replace of the Unique Key ID when locating associated
Reallocation Rules.

Special Logic

Technical Specification
Main Program

If BF Directive is equal to "1"
F48S95.Delete
BF AAITableNumber = TK Number - AAI Table Number
F4090.Delete
BF AAITableNumber = TK Number - AAI Table Number
Else
IF BF Directive is equal to "2"
F48S95.Delete
BF AAITableNumber = TK Number - AAI Table Number
BF TypeOfKey = TK Key Type
BF TableKey = TK Table Key
BF DateBeginningEffective = TK Date - Beginning Effective
BF DateEndingEffective = TK Date - Ending Effective
Else
If BF Directive is equal to "3"
F48S95.Delete
BF AAITableNumber = TK Number - AAI Table Number
BF TypeOfKey = TK Key Type
BF TableKey = TK Table Key
BF DateBeginningEffective = TK Date - Beginning Effective
BF DateEndingEffective = TK Date - Ending Effective
BF UniqueKeyIDInternal = TK Unique Key ID (Internal)
Else
If BF Directive is equal to "4"
F48S95.Delete
BF UniqueKeyIDInternal = TK Unique Key ID (Internal)
Else
If BF Directive is equal to "5"
F48S95.Delete
BF UniqueKeyIDInternal = TK Unique Key ID (Internal)
End If
End If
End If
End If
End If

Data Structure

D48S0095 - Delete Billing AAI Base and Reallocation rules

Parameter Name	Data Item	Data Type	Req/Opt	I/O/Both
AAITableNumber	ANUM	MATH_NUMERIC	OPT	INPUT
You will need to specify 1 of the following 5 directives: "1" - Delete all Base and Reallocation Rules (F48S95) associated with the AAI Table Number. Also, delete the AAI Record Type (F4090) representing the AAI Table Number. ab ab Required parameters are: • AAI Table Number "2" - Delete all Base and Reallocation Rules (F48S95) associated with a given Table Number, Table Key Type, Table Key Value, Beginning Effective Date, and Ending Effective Date. ab Required parameters are: • AAI Table Number • Table Key Type • Table Key Value • Beginning Effective Date • Ending Effective Date "3" - Delete the selected Base Rule and all the associated Reallocation Rules (F48S95). ab Required parameters are: • AAI Table Number • Table Key Type • Table Key Value • Beginning Effective Date • Ending Effective Date • Unique Key Identifier "4" - Delete the selected Reallocation Rule (F48S95). ab Required parameters are: • Unique Key Identifier "5" - Delete all the Reallocation Rules associated with a Base Rule (F48S95). Required parameters are: • Parent Unique Key identifier*
TypeOfKey	TYKY	char	OPT	INPUT
A code that the system uses in combination with the table key to locate and validate the source and workfile transactions against the various tables and user defined codes in the Service Billing and Contract Billing systems. Valid key type codes and their related tables or user defined codes are: 1 Work order number - Work Order Master File (F4801) 2 JDE Consulting Service Type - User Defined Code (00/W7) 3 Contract number - Contract Master (F5201) 4 Parent contract number - Contract Master (F5201) 5 Customer - Address Book Master (F0101) 6 Job or business unit - Business Unit Master (F0006) 7 Job class - User Defined Code (00/11) 8 Company - Company Constants (F0010) 9 Default When you choose a key type, observe the following guidelines: o You cannot use the key types for contract number (3) or parent contract number (4) with the Tax Derivation and G/L Offset & Retainage tables. o You cannot use the key type for company (8) with the G/L Offset and Retainage tables. o You can use the default key type (9) with the Billing AAI Information table (F48S95) and the Billing Rate / Mark up Table (F48096) only.
TableKey	TKEY	char	OPT	INPUT
A value that the system uses in combination with the key type to locate and validate workfile transactions against the various tables in the Service Billing and Contract Billing systems. The value that you enter in the Key Type field determines the valid values for the Table Key field. For example, if you specify the key type for work order number (1), you must enter a valid work order number from the Work Order Master File table (F4801) in the Table Key field. The key type that you specify also controls the search window that you access from the Table Key field when you use the search button. For example, when you select Key Type 1, you can use the search button for the Table Key field to access the Work Order Search window. With Key Type 2, you access the User Defined Codes window for work order class.
DateBeginningEffective	EFTB	JDEDATE	OPT	INPUT
The date that an address, item, transaction, or table record becomes active. The meaning of this field differs, depending on the program. For example, the effective date could represent the following: o When a change of address becomes effective. o When a lease becomes effective. o When a price becomes effective. o When the currency exchange rate becomes effective. o When a tax rate becomes effective.
DateEndingEffective	EFTE	JDEDATE	OPT	INPUT
The date on which the item, transaction, or table becomes inactive, or through which you want transactions to appear. This field is used generically throughout the system. It could be a lease effective date, a price or cost effective date, a currency effective date, a tax rate effective date, or whatever is appropriate.
UniqueKeyIDInternal	UKID	MATH_NUMERIC	OPT	INPUT
This field is a unique number used to identify a record in a file.
Directive	EV01	char	OPT	INPUT
An option that specifies the type of processing for an event.

Related Functions

None

Related Tables

None