Report Parameters | |
---|---|
Payroll Bank Account | Mandatory, LOV Available This field allows you to indicate the bank account where the deposit will be made. |
Institution | Mandatory, Institution lexicon available This field allows you to indicate the financial institution where the deposit will be made. |
Version Number | Optional, Text This field allows you to indicate the version number of the deposit. |
EFT Originator ID | Mandatory, Text |
File Create Date | Mandatory, Date, LOV Available The date the file was created is indicated in this field. |
Due Date | Mandatory, Date, LOV Available The date the file is due is listed in this field. |
Institution ID | Mandatory, Text |
Short Name | Mandatory, Text |
From/To Pay Issue Date | Mandatory, Date, LOV Available These fields indicate the earliest and latest issue dates of the deposits that will qualify for this EFT. |
Interface Directory | Mandatory, Text Must be a directory on the data base server for which the current user (as signed onto the client’s network) has write capability. For example the entry ‘C:\TEMP’ accesses the ‘TEMP’ directory on the server, not the local directory for the computer terminal being used. |
File Name | Mandatory, Text Enter the name of the file that will be created in the interface directory specified. If you use the tokens MEX or DATE or TIME these will be replaced as noted in P2K_PU.FILE_NAME. Also supported is FILE which will replace the File Creation Number, which is a User Defined Field on the IPBA screen. |
Trial Run | Optional, Yes or No lexicon available//You may choose to run the report in a trial mode to see results <Yes> or in update mode <No>. |
Exception Level | Mandatory, Exception Level lexicon available This field defines the exception level (report messages) required. |
User Comments | Optional, Text This field holds the user-supplied comment which will appear in the header of all pages of the report. This is useful during testing phases to identify similar reports from each other. |
(RBC) Proc Centre | Optional, Text This field allows for the support of the RBC variation of the CPA1464 format. It is only needed by clients selecting the RBC Format. The definition of this field is provided in the specification supplied by RBC to the client. |
Additional File Header | Optional, Text This field is an optional extra file header which is a constant value. It is used only for RBC clients. Once populated, the text in this field will be the first record in the file. |
The UPDTB_CPA1464 will report any outstanding deposits that do not have this MEX_ID and meet the additional conditions of
- Having a status of "Deposit Issued" in the lexicon X_DEPOSIT_STATUS
- Having a Pay Issue Date less than the "From" date in the UPDTB_CPA1496 parameters.
There is no standard function to "undo" a UPDTB_CPA1464 that has been run in UPDATE mode. The UPDTB_CPA1464 will update MEX_ID column found on the P2K_PR_DEPOSITS table with the execution ID created when UPDTB_CPA1464 was processed. This prevents deposits that have already been sent to the bank from appearing in susequent runs of UPDTB_CPA1464.
A script can be used in situations where the file sent is rejected, or problems are identified after running the process.
Please note - '######' will be replaced by the MEX_ID from UPDTB_CPA1464.
First verify the number of records to be updated;
select count(mex_id) from p2k_pr_deposits where mex_id = '######'; /Once you have verified the number of records, the update script can be run;
UPDATE p2k_pr_deposits set mex_id = NULL where mex_id = '######'; /
Once the update script has been completed - commit the records;
COMMIT; /
Screen captures are meant to be indicative of the concept being presented and may not reflect the current screen design.
If you have any comments or questions please email the Wiki Editor
All content © High Line Corporation