BNCOVDFT – Benefit Coverage Defaults

System
Benefits (BN)
Prefix
BCD
Primary key
COMPANY, PLAN-TYPE, PLAN-CODE, COVER-TYPE, START-DATE, GROUP-NAME, COVERAGE-OPT
Fields
18
Updated by
41 programs
Referenced by
4 programs

BNCOVDFT is the Benefit Coverage Defaults table in Lawson Benefits (prefix BCD). It is indexed by COMPANY, PLAN-TYPE, PLAN-CODE, COVER-TYPE, START-DATE, GROUP-NAME, COVERAGE-OPT (BCDSET1); alternate indexes: BCDSET2, BCDSET3, BCDSET4 and BCDSET5. It is related 1:1 to BNCOVOPT, PERSGROUP, PLAN and PRSYSTEM. It is updated by BN100, BN101, BN102, BN103, BN105, BN145, BN15.1, BN17.1 and 33 more and referenced by BN215, BN220, HR55.1 and PRBN.1. The table has 18 fields, 5 indexes and 4 documented relations.

About BNCOVDFT

The Benefits Coverage Defaults defines which benefit options are currently valid for each employee group.

Fields (18)

Column = COBOL field name without the BCD- 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
#BCD-COMPANY PK
COMPANY		Numeric 4Contains the company number.BN17.1, BN17.2
#BCD-PLAN-TYPE PK
PLAN_TYPE		Alpha 2Indicates the default plan type.
  • HL Health
  • DN Dental
  • DI Disability
  • EL Employee Life
  • DL Dependent Life
  • DC Defined Contribution
  • DB Defined Benefit
  • VA Vacation
  • RS Spending Account
  • SB Savings Bond
  • SP Stock Purchase
BN17.1, BN17.2
#BCD-PLAN-CODE PK
PLAN_CODE		Alpha 4Contains the user-defined code that represents the benefit plan.BN17.1, BN17.2
#BCD-START-DATE PK
START_DATE		Numeric 8 (yyyymmdd)Contains the start date for the coverage options.BN17.1, BN17.2
#BCD-GROUP-NAME PK
GROUP_NAME		Alpha 10Contains the employee group for which the coverage option applies.BN17.1, BN17.2
#BCD-COVERAGE-OPT PK
COVERAGE_OPT		Numeric 2Contains the coverage option used at benefit entry.BN17.1, BN17.2
#BCD-COVERAGE-DFT
COVERAGE_DFT		Alpha 1Indicates whether this is default coverage.
  • Y Yes
  • N No
BN17.1, BN17.2
#BCD-ACTIVE-FLAG
ACTIVE_FLAG		Alpha 1Indicates if the coverage option is active for the group.
  • A Active
  • I Inactive
BN17.1, BN17.2
#BCD-COVER-TYPE PK
COVER_TYPE		Alpha 1Indicates if the coverage is for employees, retirees, or COBRA participants for each premium record.
  • E Employees
  • R Retirees
  • C COBRA
BN17.1, BN17.2
#BCD-STATUS
STATUS		Numeric 1Contains the employee status. If a Benefits Coverage Default record is added and no employee benefits exists or if BN105 (Plan Update) is updated, the status is updated. When PR140 (Earnings and Deductions Calculation) is run for a payment date, BN105 must also be run to update employee benefits if a record of - New Group, New Date; - Existing Group, New Date; or - Change Existing Record exists for any date before or on the payment date.
  • 0 New Group New Date
  • 1 Existing Group New Date
  • 2 Change existing record
  • 3 Updated
BN105, BN17.1, BN17.2
#BCD-RET-STATUS
RET_STATUS		Numeric 1Contains the retiree status. When PR180 (Manual Payment Print) is run for a payment date, BN105 must also be run to update employee benefits if a record of - New Group, New Date; - Existing Group, New Date; or - Change Existing Record exists for any date before or on the payment date.
  • 0 New Group New Date
  • 1 Existing Group New Date
  • 2 Change Existing Record
  • 3 Updated
BN105, BN17.1, BN17.2
#BCD-COBRA-STATUS
COBRA_STATUS		Numeric 1Contains the COBRA status. When PR180 (Manual Payment Print) is run for a payment date, BN105 must also be run to update employee benefits if a record of - New Group, New Date; - Existing Group, New Date; or - Change Existing Record exists for any date before or on the payment date.
  • 0 New Group New Date
  • 1 Existing Group New Date
  • 2 Change Existing Record
  • 3 Updated
BN105, BN17.1, BN17.2
#BCD-CREATE-DATE
CREATE_DATE		Numeric 8 (yyyymmdd)—BN17.1, BN17.2
#BCD-CREATE-TIME
CREATE_TIME		Numeric 6 (hhmmss)—BN17.1, BN17.2
#BCD-CREATE-USER-ID
CREATE_USER_ID		Alpha 10 (Lower Case)—BN17.1, BN17.2
#BCD-DATE-STAMP
DATE_STAMP		Numeric 8 (yyyymmdd)—BN17.1, BN17.2
#BCD-TIME-STAMP
TIME_STAMP		Numeric 6 (hhmmss)—BN17.1, BN17.2
#BCD-USER-ID
USER_ID		Alpha 10 (Lower Case)—BN17.1, BN17.2

Indexes (5)

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
BCDSET1
  1. COMPANY
  2. PLAN-TYPE
  3. PLAN-CODE
  4. COVER-TYPE
  5. START-DATE
  6. GROUP-NAME
  7. COVERAGE-OPT
PrimaryBN100, BN101, BN102, BN103, BN105, BN145, BN15.1, BN17.1 +22 more (list truncated in source)
BCDSET2
  1. COMPANY
  2. PLAN-TYPE
  3. PLAN-CODE
  4. COVER-TYPE
  5. START-DATE ↓
  6. GROUP-NAME
  7. COVERAGE-OPT
SubsetWhere (ACTIVE-FLAG = "A") And (COVERAGE-DFT = "Y")BN100, BN101, BN102, BN103, BN105, BN145, BN17.2, BN232 +22 more (list truncated in source)
BCDSET3
  1. COMPANY
  2. PLAN-TYPE
  3. PLAN-CODE
  4. COVERAGE-OPT
  5. COVER-TYPE
  6. START-DATE
  7. GROUP-NAME
BN17.1
BCDSET4
  1. COMPANY
  2. PLAN-TYPE
  3. PLAN-CODE
  4. COVER-TYPE
  5. START-DATE ↓
  6. GROUP-NAME
  7. COVERAGE-OPT
BN100, BN101, BN102, BN103, BN105, BN145, BN17.1, BN17.2 +22 more (list truncated in source)
BCDSET5
  1. COMPANY
  2. PLAN-TYPE
  3. PLAN-CODE
  4. COVER-TYPE
  5. GROUP-NAME
  6. START-DATE ↓
  7. COVERAGE-OPT
BN17.1, BN17.2

Relations

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

One to one (4) — lookups and parents

RelationTableRulesConditionField map
BncovoptBNCOVOPTRequired
BCD-COMPANY→COP-COMPANY
BCD-PLAN-TYPE→COP-PLAN-TYPE
BCD-PLAN-CODE→COP-PLAN-CODE
BCD-COVERAGE-OPT→COP-COVERAGE-OPT
PersgroupPERSGROUPNot Required
BCD-COMPANY→PRG-COMPANY
BCD-GROUP-NAME→PRG-GROUP-NAME
PlanPLANRequired
BCD-COMPANY→PLN-COMPANY
BCD-PLAN-TYPE→PLN-PLAN-TYPE
BCD-PLAN-CODE→PLN-PLAN-CODE
PrsystemPRSYSTEMRequired
BCD-COMPANY→PRS-COMPANY
Spaces→PRS-PROCESS-LEVEL

Programs

Updated by (41)

Referenced by (4)