BNCYCLE – This database table is used for the Web Benefit Enrollment processing.

System
Benefits (BN)
Prefix
BCY
Primary key
COMPANY, CYCLE-PLAN, EFFECT-DATE, CYCLE-FREQ
Fields
12
Updated by
1 program
Referenced by
2 programs

BNCYCLE is the This database table is used for the Web Benefit Enrollment processing. table in Lawson Benefits (prefix BCY). It is indexed by COMPANY, CYCLE-PLAN, EFFECT-DATE, CYCLE-FREQ (BCYSET1); alternate indexes: BCYSET2. It is related 1:1 to PRSYSTEM and 1:M to BNCYCDTL. It is updated by BS06.1 and referenced by BS10.1 and BS15.1. The table has 12 fields, 2 indexes and 2 documented relations.

About BNCYCLE

This database table is used for the Web Benefit Enrollment processing. It contains the header information of a Cycle Plan and is used with the BNCYCDTL table that contains the Remaining Cycles for specific Begin and End Dates.

Fields (12)

Column = COBOL field name without the BCY- 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
#BCY-COMPANY PK
COMPANY		Numeric 4Company needs to exist in the PRSYSTEM table.BS06.1
#BCY-CYCLE-PLAN PK
CYCLE_PLAN		Alpha 4Contains the user-defined code that represents a Cycle Plan. A Cycle Plan determines the remaining cycle values for the web benefit enrollment task to use to display and create the correct costs for mid year enrollments into spending account type plans.BS06.1
#BCY-EFFECT-DATE PK
EFFECT_DATE		Numeric 8 (yyyymmdd)Effective Date of Cycle PlanBS06.1
#BCY-DESCRIPTION
DESCRIPTION		Alpha 30 (Lower Case)This field displays the cycle plan description.BS06.1
#BCY-PER-END-DATE
PER_END_DATE		Numeric 8 (yyyymmdd)First Cycle Period End Date used to automatically generate Begin and End Date Ranges and Remaining Cycle values.BS06.1
#BCY-CYCLE-FREQ PK
CYCLE_FREQ		Numeric 1Same frequencies as employee's pay frequency values. Used to automatically generate Cycle Begin and End Date Ranges and Remaining Cycle values.
  • 1 Weekly
  • 2 Bi-weekly
  • 3 Semi-monthly
  • 4 Monthly
  • 6 Nonstandard Semi-monthly
BS06.1
#BCY-CREATE-DATE
CREATE_DATE		Numeric 8 (yyyymmdd)—BS06.1
#BCY-CREATE-TIME
CREATE_TIME		Numeric 6 (hhmmss)—BS06.1
#BCY-CREATE-USER-ID
CREATE_USER_ID		Alpha 10 (Lower Case)—BS06.1
#BCY-DATE-STAMP
DATE_STAMP		Numeric 8 (yyyymmdd)—BS06.1
#BCY-TIME-STAMP
TIME_STAMP		Numeric 6 (hhmmss)—BS06.1
#BCY-USER-ID
USER_ID		Alpha 10 (Lower Case)—BS06.1

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
BCYSET1
  1. COMPANY
  2. CYCLE-PLAN
  3. EFFECT-DATE
  4. CYCLE-FREQ
PrimaryBS06.1
BCYSET2
  1. COMPANY
  2. CYCLE-PLAN
  3. EFFECT-DATE ↓
  4. CYCLE-FREQ
BS10.1, BS15.1

Relations

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

One to one (1) — lookups and parents

RelationTableRulesConditionField map
CompanyPRSYSTEMRequired
BCY-COMPANY→PRS-COMPANY
Spaces→PRS-PROCESS-LEVEL

One to many (1) — child tables

RelationTableRulesConditionField map
Cycle DetailsBNCYCDTLDelete Cascades
BCY-COMPANY→BCC-COMPANY
BCY-CYCLE-PLAN→BCC-CYCLE-PLAN
BCY-EFFECT-DATE→BCC-EFFECT-DATE
BCY-CYCLE-FREQ→BCC-CYCLE-FREQ
—→BCC-CYCLE-END-DATE

Programs

Updated by (1)

Referenced by (2)