This page (revision-73) was last changed on 29-Sep-2022 11:27 by Lilia Urtan

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

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
73 29-Sep-2022 11:27 13 KB Lilia Urtan to previous
72 26-Nov-2021 10:22 13 KB Karen Parrott to previous | to last
71 26-Nov-2021 10:22 13 KB Karen Parrott to previous | to last
70 26-Nov-2021 10:22 13 KB Karen Parrott to previous | to last
69 26-Nov-2021 10:22 13 KB mmcfarland to previous | to last
68 26-Nov-2021 10:22 13 KB mmcfarland to previous | to last
67 26-Nov-2021 10:22 13 KB kparrott to previous | to last
66 26-Nov-2021 10:22 13 KB kparrott to previous | to last
65 26-Nov-2021 10:22 13 KB kparrott to previous | to last
64 26-Nov-2021 10:22 13 KB kparrott to previous | to last
63 26-Nov-2021 10:22 11 KB kparrott to previous | to last
62 26-Nov-2021 10:22 11 KB khiggs to previous | to last
61 26-Nov-2021 10:22 10 KB mmcfarland to previous | to last

Page References

Incoming links Outgoing links
UPDISBV
UPDISBV

Version management

Difference between version and

At line 19 added 17 lines
!!!PREFERENCE REQUIRED FOR UPDISBV
UPAUDT ensures that all Vendor Items have the PPL reference Indo column populated with the Vendor Code.
The VENDOR MODULE preference must be set up on IMFN for the UPDISBV function. The valid values are UPVEND and UPDISBV.
* A value of UPDISBV will result in UPAUDT __NOT__ populating the Vendor Code lines.
* A value of UPVEND will result in UPAUDT populating the Vendor Code on the pay lines in IPPH.
* If the preference is not defined, UPAUDT will update the pay lines with a Vendor Code.
Clients who use UPDISBV __MUST__ define this preference with a value of UPDISBV so the Vendor Code is not populated on the pay lines. Failing to do so will cause UPDISBV not to function properly.
!!Set Up Instructions
# Set up the preference in IMFN for the UPVEND function. Enter VENDOR MODULE in the Preference field and UPDISBV in the Value field.
# Add a new batch and pay. Any existing pay headers that may have been processed through UPAUDT will not work properly.
At line 29 removed one line
[UPDISBV_01.JPG]
At line 47 added one line
At line 51 removed one line
[UPDISBV_02.JPG]
At line 69 added one line
At line 59 removed one line
!!!NEW PREFERENCE REQUIRED FOR UPDISBV
At line 61 removed one line
UPAUDT ensures that all Vendor Items have the PPL reference Indo column populated with the Vendor Code.
At line 63 removed 14 lines
There is a new Preference for the UPVEND function. Clients that use UPVEND __MUST__ set this preference.
The VENDOR MODULE preference must be set up in IMFN for the UPVEND function. The valid values are UPVEND and UPDISBV.
* A value of UPVEND will result in UPAUDT populating the Vendor Code on the pay lines in IPPH.
* A value of UPDISBV will result in UPAUDT __NOT__ populating the Vendor Code lines.
* If the preference is not defined, UPAUDT will update the pay lines with a Vendor Code.
Clients who use UPDISBV __MUST__ define this preference with a value of UPDISBV so the Vendor Code is not populated on the pay lines. Failing to do so will cause UPDISBV not to function properly.
!!Set Up Instructions
# Set up the preference in IMFN for the UPVEND function. Enter VENDOR MODULE in the Preference field and UPDISBV in the Value field.
# Add a new batch and pay. Any existing pay headers that may have been processed through UPAUDT will not work properly.
At line 81 changed one line
|Entity|Mandatory\\This field allows you identify the entity for which you wish to disburse a pay.
|Entity|Mandatory\\This field allows you identify the entity for which you wish to disburse a pay. This is used to filter the PPH records.
|Pay Run Number| Optional, Multiple, LOV Available, \\The pay run number of the pays to be selected. Multiple pay run numbers are allowed.
At line 89 changed one line
|Trial|Optional\\If YES, the Posted UDISBV UDF (for pay header in IPPH) will remain as 'N'.
|Trial|Optional\\If YES, the Posted UPVEND UDF (for pay header in IPPH) will remain as 'N'.
At line 115 changed 2 lines
In addition to the payment record, these particular direct deposits will have an ACH ‘Addenda Record’ sent along with the payment record. This event is triggered by the existence of any of the Child Support user fields listed below. The [UPDISBV] process therefore will not create this special addenda record unless the information needed is supplied in the [IPSN] form where the recurring deduction is maintained.
In addition to the payment record, these particular direct deposits will have an ACH ‘Addenda Record’ sent along with the payment record. This event is triggered by the existence of any of the Child Support user fields listed below. The [UPDISBV] process therefore will not create this special addenda record unless the information needed is supplied in the [IPSN] form where the recurring deduction is maintained.\\ \\
The UPDISBV report will show the Vendor and each payment with the associated ACH CHILD CARE ADDENDA field populated along with the amount for each employee. \\ \\
[{Image src='UPDISBV_ACHChildCare.jpg'}]
\\
At line 135 added one line
*Information in these User Fields will cause the UPDISBV to generate individual payments and show separately on the UPDISBV report
This page (revision-73) was last changed on 29-Sep-2022 11:27 by Lilia UrtanTop