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 415 changed 3 lines
- the data base tables available for User Calc are:
at company level: DEN/DLN/DDP/DDD/DUN/DGR/DGD/DGV
at employee level: EID/EPS/EEM/EAS/EASD/PPRU/PPRC
The data base tables available for User Calc are:
at company level: DEN/DLN/DDP/DDD/DUN/DGR/DGD/DGV
at employee level: EID/EPS/EEM/EAS/EASD/PPRU/PPRC
At line 420 changed one line
During the UPPHF run, you have the ability to update certain User Defined Fields (UDF) to indicate that the Interface file has been generated and mark the records as being processed.
During the UPPHF run, you have the ability to update certain User Defined Fields (UDF) to indicate that the Interface file has been generated and mark the records as being processed. You may reference these UDFs in [IDIF] to prevent the same information from being processed again.
At line 422 changed one line
You may reference these UDFs in [IDIF] to prevent the same information from being processed again.
On the [IDIF] screen, Record Type '92-Update Record' should be defined at the end of the [IDIF] definition
At line 424 changed 2 lines
On the [IDIF] screen, Record Type '92-Update Record' should be defined at the end of the [IDIF] definition
* the Variable Name should contain the UDF (xxx) that is to be updated or inserted,e.g. '320629 - UDF (PRN) (32)'
[UPPHF_09.JPG]
At line 426 added 2 lines
The Variable Name should contain the UDF (xxx) that is to be updated or inserted,e.g. '320629 - UDF (PRN) (32)'
At line 429 changed one line
The Derivation Expression field should contain the expression that is evaluated to the value to be updated for the UDF
The Derivation Expression field should contain the expression that is evaluated to the value to be updated for the UDF.
At line 432 changed one line
* multiple fields processing, DECODE, BYPASS, string manipulation, concatenation, function calls, etc.
*Multiple fields processing
*DECODE
*BYPASS
*String manipulation
*Concatenation
*Function calls, etc.
At line 443 changed one line
If the UDF is for a variable name that can be varied at the Pay Line level, then the UDF will be updated at each Pay Line level, e.g. 'UDF (DDD)', each pay line may point to a different department, therefore the UDF may be updated at the Pay Line level for that department
If the UDF is for a variable name that can be varied at the Pay Line level, then the UDF will be updated at each Pay Line level, e.g. 'UDF (DDD)', each pay line may point to a different department, therefore the UDF may be updated at the Pay Line level for that department.
At line 445 changed one line
Using the Returned Value of the derivation expression, UPPHF finds if the UDF already exists; if the UDF exists and the new value is different than the existed UDF value, it will be updated; if the UDF does not exist, it will be inserted
Using the Returned Value of the derivation expression, UPPHF finds if the UDF already exists:
*if the UDF exists and the new value is different than the existed UDF value, it will be updated
*if the UDF does not exist, it will be inserted
At line 461 changed one line
After UDFs are updated or inserted in UPPHF, the number of records updated for each Data Base table will be displayed on the UPPHF report
After UDFs are updated or inserted in UPPHF, the number of records updated for each Data Base table will be displayed on the UPPHF report.
At line 465 removed 52 lines
!!IDIF – Update Record
!IDIF – Update Record Set Up
- During the UPPHF run, user has ability to Update certain User Defined Fields (UDF) to indicate the Interface File has been generated and mark the records as being processed. User may reference these UDFs in IDIF to prevent the same information from being processed again.
- on IDIF screen, Record Type ’92-Update Record’ should be defined at the end of the IDIF definition
- the Variable Name should contain the UDF (xxx) that is to be Updated or Inserted, e.g. ‘320629 – UDF (PRN) (32)’
- the Constant Value field should contain the Name of the UDF, e.g UPPHF_CALPERS_PRN
- if this UDF name does not exist on the IMUF screen, UPPHF will create the UDF with this name on IMUF screen for the Data Base Table to be updated
- the Derivation Expression field should contain the Expression that is evaluated to the Value to be updated for the UDF
- the following Derivation Expression features can be used to derive the Value to be updated:
- multiple fields processing, DECODE, BYPASS, String manipulation, concatenation, function calls etc
- when UPPHF is run in non-Trial mode, Record Type ’92-Update Record’ will be processed at the appropriate levels to check if the UDF should be updated for the associated Data Base Tables
From above Example:
- Rec#500 Field#10 indicates to update ‘UDF (PRN)’, this will be processed at the end of each qualified Pay Run
- Rec#500 Field#20 indicates to update ‘UDF (PPH)’, this will be processed at the end of each qualified Pay Header
- Rec#500 Field#30 indicates to update ‘UDF (PPL)’, this will be processed at the end of each qualified Pay Line
- Rec#500 Field#40 indicates to update ‘UDF (EEM)’, this will be processed at the end of each qualified Pay Header
- Rec#500 Field#50 indicates to update ‘UDF (EASD)’, this will be processed at the end of each qualified Pay Line
- if the UDF is for a Variable Name that can be varied at the Pay Line level, then the UDF will be updated at each Pay Line level, e.g. ‘UDF (DDD)’, each Pay Line may point to a different Department, therefore the UDF may be updated at the Pay Line level for that Department
- using the Returned Value of the Derivation Expression, UPPHF finds if the UDF already exists; if the UDF exists and the new value is different than the existed UDF value, it will be Updated; if the UDF does not exist, it will be Inserted
- list of UDF supported in UPPHF from X_INF_VARIABLE_NAME are:
320606 – UDF (EID) (32)
320607 – UDF (EEM) (32)
320608 – UDF (EPS) (32)
320610 – UDF (EASD) (32)
320621 – UDF (DED) (32)
320623 – UDF (DDD) (32)
320624 – UDF (DLN) (32)
320626 – UDF (DUD) (32)
320628 – UDF (DGD) (32)
320629 – UDF (PRN) (32)
320630 – UDF (PPH) (32)
320631 – UDF (PPL) (32)
- after UDFs are Updated or Inserted in UPPHF, the Number of Records Updated for each Data Base Table will be displayed on the UPPHF report
- note that these Number of UDF Updated represents the number of times the Tables are being touched, these may not necessarily be the exact or unique number of UDF for that Table, e.g. UDF (EEM) may be touched 2 times if an employee has 2 Pay Headers to update the same EEM but with a different Value
At line 522 changed one line
A pay run's Pay Period End date or Pay Issue date must be on the day of or prior to the user specified ‘As of’ date.
A pay run's Pay Period End date or Pay Issue date must be on the day of or prior to the user specified 'As of' date.
This page (revision-59) was last changed on 26-Nov-2021 10:22 by khiggsTop