This page (revision-27) was last changed on 26-Nov-2021 10:22 by kparrott

This page was created on 26-Nov-2021 10:22 by KHanson

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
27 26-Nov-2021 10:22 8 KB kparrott to previous
26 26-Nov-2021 10:22 8 KB JMyers to previous | to last
25 26-Nov-2021 10:22 8 KB JAiken to previous | to last
24 26-Nov-2021 10:22 8 KB JMyers to previous | to last
23 26-Nov-2021 10:22 8 KB JEscott to previous | to last
22 26-Nov-2021 10:22 8 KB JEscott to previous | to last
21 26-Nov-2021 10:22 8 KB JEscott to previous | to last

Page References

Incoming links Outgoing links

Version management

Difference between version and

At line 1 changed 3 lines
[{TableOfContents }] <-- only if tabbed form
!!!GENERAL LEDGER SEGMENTS
[{Image src='IDGS.JPG' width='360' align='right' link='attach/IDGS/IDGS.JPG'}]
[{TableOfContents}]
!!!DEFINE GENERAL LEDGER SEGMENTS
At line 8 changed one line
The system may ‘validate’ each segment of distribution codes defined on the G/L Company (IDGC) form. You may do this by completing the G/L Segments (IDGS) form for all segments you wish to validate.
Note that if a single-segment distribution is being used, then no hyphens whatsoever should be present in the format.
At line 10 changed one line
Once you define these segments, Personality validates the distribution code via the Distribution Editor button for any forms that invoke this Distribution Editor. For example: Department (IDDP), Job (IDJB), Position (IDPS), Assignment (IEAS), Pay Transaction (IPTR), Pay Lines (IPPH), etc. The distribution button invokes the distribution editor to look-up and choose the appropriate segment codes.
The system may ‘validate’ each segment of distribution codes defined on the G/L Company ([IDGC]) form. You may do this by completing the G/L Segments (IDGS) form for all segments you wish to validate.
At line 12 added 4 lines
Once you define these segments, Personality validates the distribution code via the Distribution Editor button for any forms that invoke this Distribution Editor.
For example: Department ([IDDP]), Job ([IDJB]), Position ([IDPS]), Assignment ([IEAS]), Pay Transaction ([IPTR]), Pay Lines ([IPPH]), etc. The distribution button invokes the distribution editor to look-up and choose the appropriate segment codes.
At line 13 removed one line
‘Define General Ledger Segments’ Usage and Examples
At line 15 changed one line
General Ledger Segments data is stored in the [P2K_CM_GL_SEGMENTS] and the [P2K_CM_GL_SEGMENTS_VALUES] table.
General Ledger Segments data is stored in the [P2K_CM_GL_SEGMENTS] and the [P2K_CM_GL_SEGMENT_VALUES] table.
At line 19 changed 13 lines
[{Image src='IDGS_INPUT.JPG' width='360' align='right' link='attach/IDGS/IDGS_INPUT.JPG'}]
!!INPUT (SEGMENTS 1 THRU 10)
;[Start At | FIELD_START_BYTE]:This is the starting position of the segment. It does not count ‘-’ or ‘.’ as a position i.e. Distribution code: 1234-56-789
Segment 1starts at position 1
Segment 2 starts at position 5
Segment 3 starts at position 7
;[Length | VALUE_LENGTH]:This is the number of characters of the segment. i.e. Distribution code: 1234-56-789
Segment 1 starting at position 1 has a length of 4(1234)
Segment 2 starting at position 5 has a length of 2(56)
Segment 3 starting at position 7 has a length of 3(789)
;[Name | DESCRIPTION]:This field displays the name of the segment highlighted.
e.g. Company, Division, Department, Fund,
;[Prompt | FIELD_PROMPT]:When the Distribution Editor button is invoked on various forms (e.g. IDPP, IDPS, IDJB, IEAS, IPTR, IPPH, etc.), this value in this field is used as a side label for the segment to be entered.
----
!!Input (Segments 1 Thru 10) tab
;[Segment | SEGMENT_NUMBER]:This is the sequential order of the segments. Maximum of ten segments may be defined numbered between 1 through 10.
;:i.e. Distribution code: 1234-56-789
;:Segment 1 is digits 1234
;:Segment 2 is digits 56
;:Segment 3 is digits 789
;[Start At | FIELD_START_BYTE]:This is the starting position of the segment. It does not count ‘-’ or ‘.’ as a position
;:i.e. Distribution code: 1234-56-789
;:Segment 1starts at position 1
;:Segment 2 starts at position 5
;:Segment 3 starts at position 7
;[Length | VALUE_LENGTH]:This is the number of characters of the segment.
;:i.e. Distribution code: 1234-56-789
;:Segment 1 starting at position 1 has a length of 4(1234)
;:Segment 2 starting at position 5 has a length of 2(56)
;:Segment 3 starting at position 7 has a length of 3(789)
;[Name | DESCRIPTION]:This field displays the name of the segment highlighted. e.g. Company, Division, Department, Fund,
;[Prompt | FIELD_PROMPT]:When the Distribution Editor button is invoked on various forms (e.g. [IDDP], [IDPS], [IDJB], [IEAS], [IPTR], [IPPH], etc.), this value in this field is used as a side label for the segment to be entered.
At line 33 changed 3 lines
9 for a numeric
a for an alpha character
x for any alphanumeric character
;:9 for a numeric
;:a for an alpha character
;:x for any alphanumeric character
At line 38 changed one line
;[Journalized Fund | JOURNALIZE_FUND]:This optional toggle will indicate that this segment identifies the funds that are to be journalized and set up in the Define GL Funds (IDGF) form. This allows the application to distribute labor by fund based on grants, fellowships, etc. Please refer to the document GL Fund Distribution.
;[Journalized Fund | JOURNALIZED_FUND]:This optional toggle will indicate that this segment identifies the funds that are to be journalized and set up in the Define GL Funds (IDGF) form. This allows the application to distribute labor by fund based on grants, fellowships, etc. Please refer to the document GL Fund Distribution.
At line 40 changed 4 lines
;[Description | DESCRIPTION]:If desired, a description of the segment may be entered. This may aid users in determining the values they require.
If the Must Validate toggle is turned on, then this description will be shown on the list of values, as well as shown beside the value selected, on the Distribution Editor. If the Must Validate toggle is not on, then this description is not shown on the Distribution Editor.
!Section He[{Image src='ILDI_Tabname.JPG' width='360' align='right' link='attach/ILDI/ILDI_Tabname.JPG'}]
!!VALIDATE
;[Description | DESCRIPTION]:If desired, a description of the segment may be entered. This may aid users in determining the values they require. If the Must Validate toggle is turned on, then this description will be shown on the list of values, as well as shown beside the value selected, on the Distribution Editor. If the Must Validate toggle is not on, then this description is not shown on the Distribution Editor.
At line 45 changed one line
;[FieldName]:Definition
----
!!Validate tab
This section allows you to define the information that the segments or combinations of segments will be validated against.
These units must be numbered 11 and greater in order to be separate from the original GL segments.
!Validate Segments
You may set up validation for different combinations within the predefined segments. For example: You have defined your distribution mask as ????-??-??? (Division - Cost Center- Account). You would like to indicate that there are only certain accounts that work with certain cost centers.
Those cost centers are defined by the last three numbers in the cost center segment. Once those three numbers are defined, you will have a selection of accounts defined by the entire account segment.
Validation will be made for the digits in the 7th through 9th position in this code ????-??-???
If validation is required, you must FIRST turn the ‘Must Validate’ toggle ON in the ‘Input’ tab and then list all valid segments in the ‘G/L Valid Value’ field. The ‘Validate’ tab allows you to define the length of the portion to be validated. This could be either entire segments or other portions of segments.
The combinations of segments, or segment portions must be contiguous. That is, you cannot validate the combination of segment 3 and segment 7 together Even if no validation is needed, it is necessary that the Segment form be completed with the segment description. This allows users to have a more descriptive screen of information when using the distribution editor button in the Department, Job, Position, and Assignment forms, etc.
;[Validate Unit | GL_SEGMENT_NUMBER]:This is the sequential order of the validation units. These units must be numbered 11 and greater in order to be separate from the original GL segments. For example, if the original G/L segment is 1234-56-789, then possible units are:
;:Unit 11 is digits 123456
;:Unit 12 is digits 56789
;:Unit 13 is digits 345678
;[From | FIELD_START_BYTE]:This is the starting position of the unit. Characters such as ‘-’ or ‘.’ are NOT considered positions. For example, if the original G/L segment is 1234-56-789, then:
;:Unit 11 starts at position 1
;:Unit 12 starts at position 5
;:Unit 13 starts at position 3
;[Length | VALUE_LENGTH]:This is the number of characters in the unit. For example, if the original G/L segment is 1234-56-789, then:
;:Unit 11 starting at position 1 has a length of 6 (1234-56)
;:Unit 12 starting at position 5 has a length of 5 (56-789)
;:Unit 13 starting at position 3 has a length of 6 (34-56-78)
;[Validation Name | DESCRIPTION]:This field provides the name of the unit.
;[G/L Valid Value | GL_VALID_VALUE]:The actual valid unit value to be compared to what the user may be entering as a distribution code. For example, if the only valid value for a specific unit is 1235-6?-???, input 12356 in this field.
;[Description | DESCRIPTION]:If desired, a description of the unit may be entered. This may aid users in determining the values they require.
----
![Notes|Edit:Internal.IDGS]
[{InsertPage page='Internal.IDGS' default='Click to create a new notes page'}]