Servicing Director Posting.txt File For UltraData Warning Error
warning duplicate G/L posting .txt file ! do you wish to continue ? 'Y/N'
Root Cause:
You have created a Servicing Director Posting.txt file, uploaded it to your UltraData host server, and when using UltraFis to run CU437 and import the file, you get the error.
The most common cause for this error is the Posting.txt file you are importing is not today's Posting.txt file, or is not a file with today's data. For example, if you did not upload a today's Posting.txt file, then yesterday's Posting.txt file will still be there on the UltraData host server with yesterday's data.
Workaround:
First, click No to the error message.
Next, have the user who ran the Servicing Director end of day Run All scheduled events review their steps. For more information about the problems with the end of day run all, search Knowledge Center with the keywords Servicing Director end of day run all.
IMPORTANT! Do not click on the Run All button. Do not choose to Run All scheduled events until troubleshooting this problem is completed, and you determine to move forward with the Run All scheduled events.
To have a new Posting.txt file with today's data for UltraData, all of the following is needed:
- The Servicing Director Current Transaction Posting date would have to be advanced to your next business day.
- The UltraData GL Export event must have completed successfully with the advanced transaction dates.
- The UltraData GL Export will create the Posting.txt file in the location you have defined in the event criteria. A file with a new Windows file date and time will be created containing new data records.
- This new Posting.txt file needs to be uploaded to the UltraData host server for import, typically by someone on-site running the GET.ILQ FTP commands.
If you cannot resolve the cause of having an old Posting.txt file, then submit a case through Case Management to contact support.
ArticleNumber:
000042416