RATES Data Table ColumnsΒΆ

REQ SM COLUMN NAME TYPE UC VALIDATE | DEFAULT| JUST NOTE
– – – – – – – – – – – – Keys
M S GROUP A U     L12 [1]
M S SERVICE A U VT=SERVICES   L8  
– – – – – – – – – – – – Identification
C S ACCOUNT A U VT=ACCOUNTS   L12  
M S APPLIED LC U Rate Application Codes   L4  
C A CALENDAR_KEY A U     L20 [6]
– – – – – – – – – – – – Reference
M S ACTIVITY LC U Transaction Activity Codes   L12  
O S PER LC U Rating and Value Per Unit   L4 [2]
O AM QTY_METHOD A       L4 [3]
O AM PAYER_METHOD A       L20 [3]
– – – – – – – – – – – – Rate Calculation
O A DESCRIPTION A U     T40  
M A RATE_TYPE LC U Rate Type Codes   L4  
M S FACTOR N   (MD4)   R8  
O S SURCHARGE N   (MD4)   R8  
O S ITEM_MIN N   (MD2)   R8 [5]
O NM RATE N   (MD4)   R8 [4]
O NM QUANTITY N   (MD2)   R8 [4]
O NM MINIMUM N   (MD2)   R8 [4]
M AM BILL_UOM LC U Units of Measure   L4  

LEGEND:

REQ
O = optional
M = mandatory
P = pair required
C = conditional
SM
S = single valued
M = multiple values
A = associated (array member)
COLUMN NAME (not case specific)
TYPE
A = alpha
N.n = numeric with decimals
B = boolean
D = datetime
U = UUID
LC = list of codes
SK = key sequence
S = sequence
U Key values and codes are uppercase
VALIDATE
links refer to code validation lists
Tablenames (uppercase) refer to verifiles
(‘values’) list allowed entries
DEFAULT a value default
JUST
Justify (L)eft, (C)enter, (R)ight, (T)ext
n = characters to show

Note

  1. Entries of type list code (TYPE=LC) are validated against the associated linked code option list.
  2. Entries with a paired requirement (REQ=P) are required when the associated paired entry or code is specified.
[1]Group entries are either GLOBAL, an account identifier, or a user-assigned value. For GLOBAL, the account identifier is blank and protected. Account groups fill and protect the account entry. The account on user-assigned groups may be blank or an account identifier. All rates in a group must have the same entry for ACCOUNT.
[2]PER lists may be filtered by activity to show differing choices.
[3](1, 2) QTY_OBJECT and PAYER_OBJECT represent coded methods which would return values for the quantity or the payer. The payer may be different from the account.
[4](1, 2, 3) Rates may be single, multiple with breaks, or tiered as described in the billing documentation.
[5]Where charges are calculated for a multi-line activity, a minimum charge for the total transaction may apply.
[6]Calendar values and associated operations are described in articles in billing documentation.