SLSEGVALUE FILE
PL User Analysis Value
The Strategic Ledger User Analysis Value (SLSEGVALUE) file stores user
analysis values defined in SL00.1 (User Analysis Values). This stores the user
analysis name and description the value is defined for, the class associated
with the user analysis value, and the status.
If you delete a user analysis value, the existing user analysis record is
deleted. You can delete user analysis values using the Change form and Delete
line actions in SL00.1 or change the Allow Blank field in SL00.2 (Define User
Analysis) from Yes to No.
REFERENCED BY
SLBL.1 SLSE.1 MX202 MX223 SLVW.1
FIELD NAME DESCRIPTION/VALID VALUES UPDATED BY
SVL-SEGMENT Alpha 15
User Analysis The 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.
SVL-SEGMENT-VALUE Alpha 32
User Analysis Value The value for the user analysis.
SVL-DESCRIPTION Alpha 30 (Lower Case)
User Analysis The user analysis value description.
Description
If left blank, the user analysis value
identifier defaults.
SVL-SEGMENT-RULE Alpha 5
Class Type or select a class that identifies
the user analysis value. Use a class to
group user analysis values and to assign
specific user analysis values to an
account number.
You can associate the same user analysis
values in different user analysis by
defining the same class.
Use the Define feature to open SL00.4
(Define Value Class). Use this subform
to associate multiple classes with a
user analysis.
SVL-ACTIVE-STATUS Alpha 1
Status This field determines the status of the
user analysis. If you leave this field
blank, Active defaults which lets you
use this value in transactions.
You can select Inactive, which does not
let you use this value.
A = Active
I = Inactive
SVL-OBJ-ID Numeric 12
Object ID This is the object identifier. It is
used to relate commitments or posted
transactions back to the originating
subsystems. Each subsystem record that
is updated as a commitment or posted
transaction is assigned an object
identifier. The object identifier is
maintained in the subsystem files and in
the Activity Commitments Detail and
Activity Transaction files. The object
identifier is a unique key used to drill
back from Activity Management to the
subsystems.
SLSEGVALUE FILE INDEX
NAME KEY FIELDS DESCRIPTION / SUBSET CONDITION USED IN
SVLSET1 SEGMENT SLBL.1 SLSE.1
SEGMENT-VALUE
SVLSET2 SEGMENT-RULE KeyChange
SEGMENT
SEGMENT-VALUE
SVLSET3 OBJ-ID MX202 MX223
SLBL.1 SLVW.1
SLSEGVALUE FILE RELATIONS
ONE TO ONE RELATIONS
RELATION RELATED
NAME FILE INTEGRITY RULES / FIELD MATCH
Slsegment SLSEGMENT Required
SVL-SEGMENT -> SEG-SEGMENT
|
