CONTRDETL – Contribution Schedule Detail

System
Benefits (BN)
Prefix
CND
Primary key
COMPANY, PLAN-TYPE, PLAN-CODE, START-DATE, GROUP-NAME, BEGIN-YEAR-PCT
Fields
18
Updated by
11 programs
Referenced by
29 programs

CONTRDETL is the Contribution Schedule Detail table in Lawson Benefits (prefix CND). It is indexed by COMPANY, PLAN-TYPE, PLAN-CODE, START-DATE, GROUP-NAME, BEGIN-YEAR-PCT (CNDSET1); alternate indexes: CNDSET2. It is related 1:1 to BNCOMPANY, PRSYSTEM, PERSGROUP and PLAN and 1:M to PREMIUM. It is updated by BN00.1, BN15.1, BN18.1, BN18.2, BN18.3, BN18.4, BN18.5, BN18.6 and 3 more and referenced by BN100, BN101, BN102, BN103, BN105, BN215, BN245, BN31.1 and 21 more. The table has 18 fields, 2 indexes and 5 documented relations.

About CONTRDETL

The Contribution Schedule Detail file contains the contribution limits and company match information. This file is the detail file associated with the plan's Contribution Schedule Header file.

Fields (18)

Column = COBOL field name without the CND- prefix, hyphens → underscores. Derived fields are computed by the application and are not stored. PK = primary key (present in every index); SETn = leading/alternate key of that index.

Field / columnTypeDescription & valuesUpdated by
#CND-COMPANY PK
COMPANY		Numeric 4Contains the company number.BN15.1, BN19.3, BN19.4
#CND-PLAN-TYPE PK
PLAN_TYPE		Alpha 2Contains the benefit plan type.
  • HL Health
  • DN Dental
  • DI Disability
  • EL Life
  • DL Dependent Life
  • DC Defined Contribution
  • DB Defined Benefit
  • VA Vacation
  • RS Spending Account
  • SB Savings Bond
  • SP Stock Purchase
BN15.1, BN19.3, BN19.4
#CND-PLAN-CODE PK
PLAN_CODE		Alpha 4Contains the code that represents a defined contribution plan.BN15.1, BN19.3, BN19.4
#CND-GROUP-NAME PK
GROUP_NAME		Alpha 10Contains the employee group name.BN15.1, BN19.3, BN19.4
#CND-START-DATE PK
START_DATE		Numeric 8 (yyyymmdd)Contains the start date for this particular schedule of contributions.BN15.1, BN19.3, BN19.4
#CND-BEGIN-YEAR-PCT PK
BEGIN_YEAR_PCT		Numeric 3If match limit schedules are used, this field contains the beginning years of service for the detail record. If match percent schedules are used, this field contains the beginning percent for the detail record.BN15.1, BN19.3, BN19.4
#CND-EMP-PRE-PCT
EMP_PRE_PCT		Signed 5.2Contains the pre-tax contribution limit for all employees in the particular range of years of service.BN15.1, BN19.3, BN19.4
#CND-EMP-POST-PCT
EMP_POST_PCT		Signed 5.2Contains the employee after-tax contribution limit for all employees in the particular range of years of service.BN15.1, BN19.3, BN19.4
#CND-EMP-TOT-PCT
EMP_TOT_PCT		Signed 9.2Contains the total percent contribution for the detail record. Total pre-tax and after tax contributions cannot exceed this limit.BN15.1, BN19.3, BN19.4
#CND-MATCH-PCT
MATCH_PCT		Signed 5.2Contains the company match percent. The value of this field is used to determine the EDM-NEXT-AMOUNT when the system creates the company match deduction in the Employee Deduction file as the EDM-NEXT-AMOUNT.BN100, BN101, BN102, BN103, BN105, BN15.1, BN19.3, BN19.4 +22 more
#CND-PCT-MATCHED
PCT_MATCHED		Signed 5.2If match limit schedules are used, this field contains the percent to be matched. The value of this field is determines EDM-PCT-AMOUNT is used when the system creates the company matching deduction in the Employee Deduction file.BN15.1, BN19.3, BN19.4
#CND-MAX-MATCH
MAX_MATCH		Signed 11.2Contains the maximum company matching contribution as a flat dollar amount. This field is used to determine the EDM-BALANCE-AMT when the system creates the company matching deduction in the Employee Deduction file. If there is a maximum match amount, the deduction is set up as a descending deduction (EDM-BALANCE-TYPE = D).BN15.1, BN19.3, BN19.4
#CND-CREATE-DATE
CREATE_DATE		Numeric 8 (yyyymmdd)—BN15.1, BN19.3, BN19.4
#CND-CREATE-TIME
CREATE_TIME		Numeric 6 (hhmmss)—BN15.1, BN19.3, BN19.4
#CND-CREATE-USER-ID
CREATE_USER_ID		Alpha 10 (Lower Case)—BN15.1, BN19.3, BN19.4
#CND-DATE-STAMP
DATE_STAMP		Numeric 8 (yyyymmdd)—BN15.1, BN19.3, BN19.4
#CND-TIME-STAMP
TIME_STAMP		Numeric 6 (hhmmss)—BN15.1, BN19.3, BN19.4
#CND-USER-ID
USER_ID		Alpha 10 (Lower Case)—BN15.1, BN19.3, BN19.4

Indexes (2)

Keys are listed in index order; ↓ marks a descending key. Every documented Lawson index is unique unless flagged Duplicates; Subset indexes carry a Where condition.

IndexKeysFlagsConditionUsed in
CNDSET1
  1. COMPANY
  2. PLAN-TYPE
  3. PLAN-CODE
  4. START-DATE
  5. GROUP-NAME
  6. BEGIN-YEAR-PCT
PrimaryBN00.1, BN100, BN101, BN102, BN103, BN105, BN15.1, BN18.1 +22 more (list truncated in source)
CNDSET2
  1. COMPANY
  2. PLAN-TYPE
  3. PLAN-CODE
  4. START-DATE
  5. GROUP-NAME
  6. BEGIN-YEAR-PCT ↓
BN100, BN101, BN102, BN103, BN105, BN245, BN31.1, BN31.2 +19 more

Relations

Relationship map — 1:1 lookups/parents on the left, 1:M children on the right (up to 14 each)
BNCOMPANYPRSYSTEMPERSGROUPPLANPREMIUMCONTRDETL

One to one (4) — lookups and parents

RelationTableRulesConditionField map
CompanyBNCOMPANYRequired
CND-COMPANY→BNC-COMPANY
Company NamePRSYSTEMRequired
CND-COMPANY→PRS-COMPANY
Spaces→PRS-PROCESS-LEVEL
PersgroupPERSGROUPNot Required
CND-COMPANY→PRG-COMPANY
CND-GROUP-NAME→PRG-GROUP-NAME
PlanPLANRequired
CND-COMPANY→PLN-COMPANY
"DC"→PLN-PLAN-TYPE
CND-PLAN-CODE→PLN-PLAN-CODE

One to many (1) — child tables

RelationTableRulesConditionField map
PremiumPREMIUM
CND-COMPANY→PRE-COMPANY
CND-PLAN-TYPE→PRE-PLAN-TYPE
CND-PLAN-CODE→PRE-PLAN-CODE
—→PRE-COVER-TYPE
—→PRE-START-DATE
—→PRE-GROUP-NAME

Programs

Updated by (11)

Referenced by (29)