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

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

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
59 26-Nov-2021 10:22 37 KB khiggs to previous
58 26-Nov-2021 10:22 37 KB kparrott to previous | to last
57 26-Nov-2021 10:22 37 KB rforbes to previous | to last
56 26-Nov-2021 10:22 60 KB rforbes to previous | to last
55 26-Nov-2021 10:22 60 KB rforbes to previous | to last
54 26-Nov-2021 10:22 60 KB jmyers to previous | to last
53 26-Nov-2021 10:22 60 KB jmyers to previous | to last
52 26-Nov-2021 10:22 60 KB jmyers to previous | to last
51 26-Nov-2021 10:22 65 KB jmyers to previous | to last
50 26-Nov-2021 10:22 67 KB jmyers to previous | to last
49 26-Nov-2021 10:22 67 KB jmyers to previous | to last
48 26-Nov-2021 10:22 64 KB jmyers to previous | to last
47 26-Nov-2021 10:22 64 KB jmyers to previous | to last
46 26-Nov-2021 10:22 64 KB jmyers to previous | to last
45 26-Nov-2021 10:22 64 KB jmyers to previous | to last
44 26-Nov-2021 10:22 63 KB jmyers to previous | to last
43 26-Nov-2021 10:22 67 KB jmyers to previous | to last
42 26-Nov-2021 10:22 67 KB jmyers to previous | to last
41 26-Nov-2021 10:22 67 KB jmyers to previous | to last

Page References

Incoming links Outgoing links
UPPHF
UPPHF

Version management

Difference between version and

At line 215 changed one line
;Sort Sequence:Specifies the Sort Sequence for this Record #, Field #\\ \\Use for Record # with Record Type = 'Detail Record' only\\ \\For Record # with Record Type = 'Detail Level 1' to 'Detail Level 5', it uses the same Sort from Record Type = 'Detail Record' so that the Detail Level n records are followed after the 'Detail Record'\\e.g. Interface File need to sort by: Department, Employee First Name, Last Name\\- Then for the Fld# entry that specify 'Department', enter sort sequence: 100\\- For the Fld# that specify 'Employee First Name', enter sort sequence: 150\\-For the Fld# that specify 'Employee Last Name', enter sort sequence: 200\\ \\All Sort sequences must be entered on entries with the same Record Number\\ \\Sort Sequence is not supported for XML file format because xml file may specify many different Record # to generate xml begin and end tags and the xml tags are not able to sort along with the data.\\ \\Sort Sequence is not supported if the IDIF format contains 'Pay Header Begin' or 'Pay Header Summary' because the Sorting of the Detail Record cannot carry it's associated Header/Summary Record
;Sort Sequence:Specifies the Sort Sequence for this Record #, Field #\\ \\Use for Record # with Record Type = 'Detail Record' only\\ \\For Record # with Record Type = 'Detail Level 1' to 'Detail Level 5', it uses the same Sort from Record Type = 'Detail Record' so that the Detail Level n records are followed after the 'Detail Record' e.g. Interface File need to sort by: Department, Employee First Name, Last Name\\- Then for the Fld# entry that specify 'Department', enter sort sequence: 100\\- For the Fld# that specify 'Employee First Name', enter sort sequence: 150\\- For the Fld# that specify 'Employee Last Name', enter sort sequence: 200\\ \\All Sort sequences must be entered on entries with the same Record Number\\ \\Sort Sequence is not supported for XML file format because xml file may specify many different Record # to generate xml begin and end tags and the xml tags are not able to sort along with the data.\\ \\Sort Sequence is not supported if the IDIF format contains 'Pay Header Begin' or 'Pay Header Summary' because the Sorting of the Detail Record cannot carry it's associated Header/Summary Record
At line 245 added 14 lines
;Constant Value:If Variable Name = 'Constant Value', this field specifies the Constant Value to be used\\ \\If Variable Name = 'User Calc', this field specifies the User Calc Name\\ \\If Variable Name = 'UDF (xxx)', this field specifies the User Defined Field Name\\ \\If Variable Name = 'Statistics Amt', this field specifies the Statistics Code\\ \\If Variable Name = 'Element', this field specifies the Element Code\\ \\If Variable Name = 'Total Value', this field specifies the Rec# and Field # of the Detail Records to be totaled\\e.g. Record # 50 Field 70 is to be totaled and Total option = 'Calculate Total', then the Trailer record can report the 'Total Value', Constant value should be 5070
;Print Zero Rule:Applicable to Numeric field only, use for Record Type = 'Detail Record'\\ \\If amount is zero, this field indicates to include this amount in the interface file or not\\e.g. if the field is from 'Element Amount' and the amount is zero, the user may not want to report this amount.\\ \\If all numeric amounts are zero within one Record# and the Print Zero Rule are set to 'Do not Print zerosÃ' for each field, then this entry will not be reported on interface file.\\ \\Lexicon X_PRINT_ZERO_RULE
|00 | Not Specified
|01 | Print Zero Amounts
|02| Don't Print Zeros
;XML Tag option:Applicable to XML file, if Variable Name = 'XML begin Tag'or 'XML end Tag', this field option indicates if the XML Tag should be written.\\ \\Lexicon X_XML_TAG_OPTION
|00 | Not Specified
|01 | Optional, omit tag if null
|02| Mandatory, always write
;Accum Option:Applicable to Numeric field only, use for Record Type = 'Detail Record'\\ \\Indicate if this Record #, Field # amount should be accumulated or not\\e.g. if the field is a 'Pay Number' or 'Check Number', then do not accumulate.\\ \\If field is 'Element Value' or 'PC Amount', then you may want to accumulate to avoid writing too much detail per element or per pay component.
;Total Option:Applicable to Numeric field only, use for Record Type = Detail Record, Detail Leveln\\ \\Indicate if this Record #, Field # amount should be totaled for Header or Trailer record\\e.g. if the field is a 'FTE' or 'Rate of Pay', then do not totaled.\\ \\If field is 'Statistics Amount' or 'User Calc Amount', then you may want to calculate the total for Trailer record\\ \\Lexicon X_TOTAL_OPTION
|00 | Not Specified
|01 | Calculate Total
;Derivation Expression:Specifies the derivation expression for the Variable name.\\ \\This derivation expression will apply to the result of the Variable name before format mask.\\ \\The user may use RTRIM(~) to remove trailing blanks before comparing the entire string because the data may contain blanks that are not visible at the end.\\ \\Please refer to following Derivation Expression processing
At line 246 changed 7 lines
Constant Value - if Variable Name = ‘Constant Value’, this field specifies the Constant Value to be used
- if Variable Name = ‘User Calc’, this field specifies the User Calc Name
- if Variable Name = ‘UDF (xxx)’, this field specifies the User Defined Field Name
- if Variable Name = ‘Statistics Amt’, this field specifies the Statistics Code
- if Variable Name = ‘Element’, this field specifies the Element Code
- if Variable Name = ‘Total Value’, this field specifies the Rec# and Field # of the Detail Records to be totaled
e.g. Record # 50 Field 70 is to be totaled and Total option = ‘Calculate Total’, then the Trailer record can report the ‘Total Value’, Constant value should be 5070
!BYPASS Capability
On IDIF Derivation expression, user may decode the Variable Name using the ~ character and return the word 'BYPASS' to bypass the Detail record entry that are with certain criteria
At line 254 changed 3 lines
Print Zero Rule - applicable to Numeric field only, use for Record Type = ‘Detail Record’
- if amount is zero, this field indicates to include this amount in the interface file or not
- e.g. if the field is from ‘Element Amount’ and the amount is zero, the user may not want to report this amount
The 'BYPASS' criteria can be set up for Record Type = 'Qualify record', 'Detail record', and should not be used for Header and Trailer records
At line 258 changed 5 lines
- if all numeric amounts are zero within one Record# and the Print Zero Rule are set to ‘Do not Print zeros’ for each field, then this entry will not be reported on interface file
- lexicon X_PRINT_ZERO_RULE
00 – Not Specified
01 – Print Zero Amounts
02 – Don’t Print Zeros
If the return value of any IDIF Record Number/Field Number = 'BYPASS', then this Detail record will be bypassed and will not be written to the Interface file
At line 264 changed 5 lines
XML Tag option - applicable to XML file, if Variable Name = ‘XML begin Tag’or ‘XML end Tag’, this field option indicates if the XML Tag should be written
- lexicon X_XML_TAG_OPTION
00 – Not Specified
01 – Optional, omit tag if null
02 – Mandatory, always write
Example:
*To include only Departments start with 'P' on interface file:\\decode(rtrim(substr(~,1,1)),'P',~,'BYPASS')
*To include only Departments ends with 'C' on interface file:\\decode(substr(~,length(rtrim(~)),1),'C','BYPASS',~)
*To bypass Cost Centers that has '????' in second segments:\\decode(SUBSTR(~,5,4),'????','BYPASS',SUBSTR(~,5,4))
*To include Journal Entries with Account Numbers over 40000 in segment 5:\\decode(greatest('40000',substr(~,16,5)),'40000','BYPASS',substr(~,16,5))
At line 270 removed 42 lines
Accum Option - applicable to Numeric field only, use for Record Type = ‘Detail Record’
- indicate if this Record #, Field # amount should be accumulated or not
- e.g. if the field is a ‘Pay Number’ or ‘Check Number’, then do not accumulate
- if field is ‘Element Value’ or ‘PC Amount’, then you may want to accumulate to avoid writing too much detail per element or per pay component
Total Option - applicable to Numeric field only, use for Record Type = Detail Record, Detail Leveln
- indicate if this Record #, Field # amount should be totaled for Header or Trailer record
- e.g. if the field is a ‘FTE’ or ‘Rate of Pay’, then do not totaled
- if field is ‘Statistics Amount’ or ‘User Calc Amount’, then you may want to calculate the total for Trailer record
- lexicon X_TOTAL_OPTION
00 – Not Specified
01 – Calculate Total
Derivation Expression - specifies the derivation expression for the Variable name
- this derivation expression will apply to the result of the Variable name before format mask
- the user may use RTRIM(~) to remove trailing blanks before comparing the entire string because the data may contain blanks that are not visible at the end
- please refer to following Derivation Expression processing
!BYPASS capability
- on IDIF Derivation expression, user may decode the Variable Name using the ~ character and return the word ‘BYPASS’ to bypass the Detail record entry that are with certain criteria
- the ‘BYPASS’ criteria can be set up for Record Type = ‘Qualify record’, ‘Detail record’, and should not be used for Header and Trailer records
- if the return value of any IDIF Record Number/Field Number = ‘BYPASS’, then this Detail record will be bypassed and will not be written to the Interface file
- Example:
- to include only Departments start with ‘P’ on interface file:
decode(rtrim(substr(~,1,1)),'P',~,'BYPASS')
- to include only Departments ends with ‘C’ on interface file:
decode(substr(~,length(rtrim(~)),1),'C','BYPASS',~)
- to bypass Cost Centers that has ‘????’ in second segments:
decode(SUBSTR(~,5,4),'????','BYPASS',SUBSTR(~,5,4))
- to include Journal Entries with Account Numbers over 40000 in segment 5:
decode(greatest('40000',substr(~,16,5)),'40000','BYPASS',substr(~,16,5))
At line 314 changed one line
- when UPPHF is run with Interface Level = ‘Pay Headers + Pay Lines’, user may want to BYPASS the current Pay Line and continue to process the next Pay Line
When UPPHF is run with Interface Level = 'Pay Headers + Pay Lines', you may want to BYPASS the current pay line and continue to process the next pay line.
At line 316 changed one line
- when a Pay Line (ppl) is being processed, all the associated Pay Line Details (ppld) are processed one at a time until all ppld are finished
When a Pay Line (ppl) is being processed, all the associated Pay Line Details (ppld) are processed one at a time until all ppld are finished.
At line 318 changed one line
- the following BYPASS capabilities are available at the Pay Line level:
The following BYPASS capabilities are available at the Pay Line level:
;BYPASS:Bypass current ppld, will go to process next ppld\\ \\Usually BYPASS should be used for Qualify Records and is also used for other Record Types, this BYPASS also works in ppl
;BYPASS-1-PPL:Bypass current ppld, will go to process next ppld\\ \\When Interface Level = 'Pay Headers + Pay Lines', you should use 'BYPASS-1-PPL' instead of just 'BYPASS' for clarification
;BYPASS-ALL-PPL:Bypass all ppl and ppld from this point onward, will go to process Pay Amounts\\ \\The Pay Amounts will subtract the amounts that have been processed by ppld so far
;BYPASS-TO-PPL:Bypass all ppl, ppld, Pay Amounts from this point onward\\ \\Will go to process Pay Header Summary
At line 320 removed 12 lines
BYPASS - bypass current ppld, will go to process next ppld
- usually BYPASS should be used for Qualify Records and is also used for other Record Types, this BYPASS also works in ppl
BYPASS-1-PPL - bypass current ppld, will go to process next ppld
- when Interface Level = ‘Pay Headers + Pay Lines’, user should use ‘BYPASS-1-PPL’ instead of just ‘BYPASS’ for clarification
BYPASS-ALL-PPL - bypass all ppl and ppld from this point onward, will go to process Pay Amounts
- the Pay Amounts will subtract the amounts that have been processed by ppld so far
BYPASS-TO-PPL - bypass all ppl, ppld, Pay Amounts from this point onward
- will go to process Pay Header Summary
At line 287 added one line
INSERT GRAPHIC
At line 335 removed one line
This page (revision-59) was last changed on 26-Nov-2021 10:22 by khiggsTop