GSE Integrations and Services 23.2 June Service Pack: Fixed Issues
This section describes the issues fixed with this release.
Why we fixed these issues: These issues were fixed to improve usability and to help ensure Encompass GSE Integrations & Services is operating as expected. The issues that are chosen to be fixed are based on the severity of their impact to clients and client feedback.
UCD
When uploading files to GNMA, the following error displayed:
Pool Issuer Loan Identifier is required.
To fix the issue, logic has been updated as follows:
-
If a value in field ULDD.X21 (Seller Loan ID) exists, then the following checks are executed:
-
Remove all special characters, if applicable. Per GNMA spec, this is an alphanumeric data point. The allowed characters are: ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789
-
If after removing the special characters, field ULDD.X21 exceeds 15 characters, then drop the remaining characters to make it 15. Example: field ULDD.X21 equals: 123456789-12345678. After removing the special character, it's now 12345678912345678. This is 17 alphanumeric characters now so we would drop the last 2 characters and export only 123456789123456
-
If after removing the special characters, field ULDD.X21 does not equal 15 alphanumeric characters, then add leading zeros to make it 15 characters. Example: field ULDD.X21 equals 123456789-12. After removing the special character, it's now 12345678912. This is only 11 alphanumeric characters, so we would need to add leading zeros to it and export 000012345678912
-
-
Once the above has been performed, send that value to LoanIdentifier and then send PoolIssuerLoan to LoanIdentifierType
-
Attributes:
-
LoanIdentifierType
-
LoanIdentifier
-
-
Enumeration: PoolIssuerLoan
-
Xpath: MESSAGE/DEAL_SETS/DEAL_SET/DEALS/DEAL/LOANS/LOAN/LOAN_IDENTIFIERS/LOAN_IDENTIFIER
-
Prior to this release, Ginnie Mae PDD export files were using UTF-8-BOM encoding instead of UTF-8, and as a result, files could not be uploaded to Ginnie Mae's SFPDM tool. To fix the issue, export files have been updated to UTF-8 encoding.
Closing 2.6 and Closing 2.6 Extended Export
When the borrower birth year was, or after, 2000, the Closing 2.6 Data Export from Encompass was converting the birth year from 2004 (for example) to 1904. This has been fixed so that the correct borrower birth year is now included in the export file.
Previous Section: Feature Enhancements |