SLGROUPDTL – User Analysis Group Detail

System
Strategic Ledger (SL)
Prefix
GRD
Primary key
SEGMENT-GROUP, SEGMENT
Fields
3
Updated by
1 program
Referenced by
5 programs

SLGROUPDTL is the User Analysis Group Detail table in Lawson Strategic Ledger (prefix GRD). It is indexed by SEGMENT-GROUP, SEGMENT (GRDSET1); alternate indexes: GRDSET2 and GRDSET3. It is related 1:1 to SLGROUPHDR and SLSEGMENT and 1:M to SLGROUPDTL, SLRELATHDR, SLSEGVALUE and SLTRANS. It is updated by SL01.1 and referenced by SL00.2, SL00.5, SL02.1, SLSE.1 and SLSR.1. The table has 3 fields, 3 indexes and 6 documented relations.

About SLGROUPDTL

The Strategic Ledger Group Detail (SLGROUPDTL) file stores user analysis group information defined in SL01.1 (User Analysis Group), including the user analysis order and user analysis size. User Analysis Groups are used to define a user analysis relation in SL02.1 (User Analysis Value Relation) and assign to a chart of accounts in GL00.2 (Define Chart). A user analysis group is a group of up to four user analysis for reports and inquiries. User Analysis Group header information is stored in the Strategic Ledger Group Header (SLGROUPHDR) file. You cannot remove a user analysis group from a chart or delete a user analysis group if transactions exist for the group in the General Ledger Transaction (GLTRANS) file.

Fields (3)

Column = COBOL field name without the GRD- 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
#GRD-SEGMENT-GROUP PK
SEGMENT_GROUP
Alpha 15A user analysis group is a combination of up to four user analysis for reports and analysis.SL01.1
#GRD-SEGMENT PK
SEGMENT
Alpha 15The name that identifies the user analysis. A user analysis is a flexible, user-defined element, much like an accounting unit, account, or attribute, that stores transaction information you can use for reports and analysis. You can use a user analysis to track multiple elements of business data.SL01.1
#GRD-SEGMENT-ORDER SET2
SEGMENT_ORDER
Numeric 2The order the user analysis are used in subsystems.SL01.1

Indexes (3)

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
GRDSET1
  1. SEGMENT-GROUP
  2. SEGMENT
PrimarySL00.2, SL00.5, SL01.1, SL01.2, SLSE.1, SLSR.1
GRDSET2
  1. SEGMENT-GROUP
  2. SEGMENT-ORDER
  3. SEGMENT
KeyChangeSL01.1, SL02.1
GRDSET3
  1. SEGMENT
  2. SEGMENT-GROUP
SL00.2

Relations

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

One to one (2) — lookups and parents

RelationTableRulesConditionField map
SlgrouphdrSLGROUPHDRRequired
GRD-SEGMENT-GROUP→SLH-SEGMENT-GROUP
SlsegmentSLSEGMENTRequired
GRD-SEGMENT→SEG-SEGMENT

One to many (4) — child tables

RelationTableRulesConditionField map
SlgroupdtlSLGROUPDTL
GRD-SEGMENT-GROUP→GRD-SEGMENT-GROUP
—→GRD-SEGMENT
SlrelathdrSLRELATHDR
GRD-SEGMENT-GROUP→SRH-SEGMENT-GROUP
—→SRH-RELATION
SlsegvalueSLSEGVALUE
GRD-SEGMENT→SVL-SEGMENT
—→SVL-SEGMENT-VALUE
SltransSLTRANS
GRD-SEGMENT-GROUP→SLT-SEGMENT-GROUP
—→SLT-POSTING-DATE
—→SLT-OBJ-ID

Programs

Updated by (1)

Referenced by (5)