Skip to main content
Skip table of contents

PYHR - SUBMISCx

This common code adds functionality that will allow clients to control what is placed in the ABS Misc1-10 and SUB Misc1-10 fields when the STUTLF Action is run in the Sub Tracker subsystem. This function gives the users the flexibility to override what the STUTLF Action fills the ten absentee miscellaneous fields, ten substitute miscellaneous fields, and the position, account, and site fields with.

To turn this functionality on, common code PYHR/SUBMISC1 must be created to tell it what values to override and where to get the override values from the input file. If the common code is not set up, or if it is set up incorrectly, nothing will be overridden. If more than five fields are needed, PYHR/SUBMISC2 can set up to accommodate the extra fields. Both common codes work exactly the same.

See PYHR-SUBMISCx Setup for more information.
 

Code Category: PYHR
Code Value: SUBMISC1
Associated Codes: Range of Characters from flat file: The codes fields would hold the range of characters to be extracted from the 3rd-party flat file. For example: 45,65 means to take characters 45 through 65 and put them in the field designated by the corresponding Description field (described below).
Range Limitations:
a. Max Range length for Each IMPORT field:

ABS1-ABS10, SUB1-SUB10

33 long

POSN

31 long

ACCT

45 long

SITE

9 long

b. The Range must fall within the record length of the 3rd-party software input file:

SmartFindExpress

Delimited File - special case

Aesop

1085 characters

Associated Descriptions: These are the codes the user can use in the Description column and their meaning:

ABS1–ABS10

Override Absentee Misc 1, 2, 3… up to 10

SUB1–SUB10

Override Substitute Misc 1, 2, 3… up to 10

ABSSUB1–ABSSUB10

Override Absentee AND Substitute Misc 1, 2, 3..10

POSN

Override Position field

ACCT

Override Account field

SITE

Override Site field

A "U" in the very last character of the Description field indicates that the results should be upshifted before being placed in the appropriate field on IMPORT. This can be useful for "standardizing" data that may import in multiple different formats (e.g., sometimes all upper-case, other times mixed case, etc.).
Any errors encountered with the common code will be written to sub_error table when STUTLF is run. Use CDD Report ST1001 to view errors.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.