LSA Export Update

LSA Export Update
We are ready to update the export with our first round changes. The changes will be applied at 10:00 AM CDT today, Tuesday, April 16th. We will send out another announcement once it is complete. The update will include the following:
  • Flag 132 - HHType and HHAdultAge counts issue. {Sample Code Issue}
  • Flag 169 - RRH Housed Days {Sample Code/Export Specifications Issue}
  • Flags 27602/27662/27663/27664/27673/27674 - TH counts issue {Sample Code Issue}
  • Flag 27371 - CH persons in CH Only Beds {Sample Code/Export Specifications Issue}
  • Flags 25404/25410/25411 - Provider not listed in Geography.csv file {WellSky Code Issue}

The following potential issues in Sample Code have been reported to Abt by WellSky and other vendors:

  • ref_Population joins
  • Project-level vs project type counts
  • RRH Housed Days
  • ES/SH/TH client counts
  • Total Homeless Days counts
  • Bed night counts for some clients
  • Chronic Homeless definition
  • RelationshipToHoH3
  • System Path from prior qualifying exits
  • Households that change over time
  • Tracking Method in Where Clause
  • Geography Information Date type
  • HH Type
  • Double counting of days homeless
  • Date inserted is after Last Inactive
  • Veteran Client counts in summary procedure

We are still awaiting the revised Sample Code from HUD. HUD has announced that they have extended the LSA submission deadline date further and will announce a new submission date when they are ready. HUD anticipates the new deadline to be in early May. HUD does not anticipate that the HIC/PIT or SPM deadlines will change. HUD is keenly aware of CoC's concerns with respect to the LSA timeline as it relates to the CoC Competition, and they are taking into consideration the unexpected delays and upload issues.

For those that have reported errors that are resolved by this update we recommend sending a new file to Abt/HUD to receive an updated flag file. Abt recommends that our customers continue to review the non-vendor errors/warnings in their flag files to determine what fixes, if any, are needed and then resubmit the file to get the errors cleared. Abt does not recommend that customers wait for vendors to make their changes before fixing any non-vendor errors/warnings.

Please create a case in the Customer Community if you have further questions.