BONDBENSEQ – Savings Bond Sequence

System
Benefits (BN)
Prefix
BBS
Primary key
COMPANY, EMPLOYEE, PLAN-CODE, START-DATE, BOND-SEQ-NBR
Fields
8
Updated by
3 programs
Referenced by
2 programs

BONDBENSEQ is the Savings Bond Sequence table in Lawson Benefits (prefix BBS). It is indexed by COMPANY, EMPLOYEE, PLAN-CODE, START-DATE, BOND-SEQ-NBR (BBSSET1); alternate indexes: BBSSET2. It is related 1:1 to SBBEN, BENEFIT, BNCOMPANY, EMPLOYEE and PRSYSTEM and 1:M to BONDBENIF and PLAN. It is updated by BN48.2, HR11.1 and PA115 and referenced by BN140 and BN248. The table has 8 fields, 2 indexes and 9 documented relations.

About BONDBENSEQ

The Savings Bond Sequence file contains the sequence used to purchase bonds for each employee and savings bond plan. The sequence record defines the owner, co-owner, and beneficiaries used to purchase a savings bond.

Fields (8)

Column = COBOL field name without the BBS- 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
#BBS-COMPANY PK
COMPANY		Numeric 4Contains the company number.BN48.2
#BBS-EMPLOYEE PK
EMPLOYEE		Numeric 9Contains the employee number.BN48.2
#BBS-PLAN-CODE PK
PLAN_CODE		Alpha 4Contains the user-defined code that represents a savings bond plan.BN48.2
#BBS-START-DATE PK
START_DATE		Numeric 8 (yyyymmdd)Contains the date the sequence is in effect. When BN140 (Savings Bond Update) is run, it uses the sequence in effect to determine the order for the bonds.BN48.2
#BBS-BOND-SEQ-NBR PK
BOND_SEQ_NBR		Numeric 2Contains the sequence in which the employee wants to purchase bonds.BN48.2
#BBS-OWNER
OWNER		Alpha 3Contains the owner name to be used on the bond.BN48.2
#BBS-CO-OWNER
CO_OWNER		Alpha 3Contains the co-owner name to be used on the bond.BN48.2
#BBS-BNFC-NBR
BNFC_NBR		Alpha 3 Occurs 12 Times ×12Contains the beneficiary to be used on the bond. Up to 12 beneficiaries can be used.BN48.2

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
BBSSET1
  1. COMPANY
  2. EMPLOYEE
  3. PLAN-CODE
  4. START-DATE
  5. BOND-SEQ-NBR
PrimaryBN140, BN248, BN48.2, HR11.1, PA115
BBSSET2
  1. COMPANY
  2. EMPLOYEE
  3. PLAN-CODE
  4. START-DATE
  5. BOND-SEQ-NBR ↓
BN140, BN248, BN48.2

Relations

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

One to one (7) — lookups and parents

RelationTableRulesConditionField map
BeneficiariesSBBENNot Required
BBS-COMPANY→SBB-COMPANY
BBS-EMPLOYEE→SBB-EMPLOYEE
BBS-BNFC-NBR→SBB-BNFC-NBR
BenefitBENEFITNot Required
BBS-COMPANY→BEN-COMPANY
BBS-EMPLOYEE→BEN-EMPLOYEE
"SB"→BEN-PLAN-TYPE
BBS-PLAN-CODE→BEN-PLAN-CODE
BBS-START-DATE→BEN-START-DATE
BncompanyBNCOMPANYRequired
BBS-COMPANY→BNC-COMPANY
Co OwnerSBBENNot Required
BBS-COMPANY→SBB-COMPANY
BBS-EMPLOYEE→SBB-EMPLOYEE
BBS-CO-OWNER→SBB-BNFC-NBR
EmployeeEMPLOYEERequired
BBS-COMPANY→EMP-COMPANY
BBS-EMPLOYEE→EMP-EMPLOYEE
HrcompanyPRSYSTEMRequired
BBS-COMPANY→PRS-COMPANY
Spaces→PRS-PROCESS-LEVEL
OwnerSBBENNot Required
BBS-COMPANY→SBB-COMPANY
BBS-EMPLOYEE→SBB-EMPLOYEE
BBS-OWNER→SBB-BNFC-NBR

One to many (2) — child tables

RelationTableRulesConditionField map
BondBONDBENIF
BBS-COMPANY→BON-COMPANY
BBS-EMPLOYEE→BON-EMPLOYEE
BBS-PLAN-CODE→BON-PLAN-CODE
BBS-START-DATE→BON-START-DATE
—→BON-BOND-NBR
PlanPLANRequired
BBS-COMPANY→PLN-COMPANY
—→PLN-PLAN-TYPE
—→PLN-PLAN-CODE

Programs

Updated by (3)

Referenced by (2)