ST402 – Generic Settlement Extract – Phase 3

NOTE: The specific fields with permissible entries to be filled in or left blank are listed below. Ignore fields that are not in the list next to the screens.

Figure 1. SY41 (TOP)

1. Job: Report name should always appear here. For example, ST402. 2. Server Name: Keep the server name that first appears. 3. Printer_Name: Select a valid printer or keep the displayed printer if one is present. 4. Jurisdiction: Enter your jurisdiction. 5. Tax Year: Enter the current Tax Year. 6. Spool File Name: Enter ST402.LIS to create the file in text format. 7. Beginning Date: Enter the Business Date to query phase 2 in STLGROUP. 8. Ending Date: Enter the Business Date to load phase 2 to 3 in STLGROUP. 13. FCU: Formatting code. Keep the default printer setting that is present when the screen appears. If blank, enter HPLL132 or enter DFLT. 17. PARAM1 ROLLTYPE: Enter a valid rolltype or leave blank to process all rolltypes defined in TEDUPLYR table. 18. PARAM2 FREQUENCY: Frequency at which Settlements are being run. User should look in STLSCHED, STLDIST, or STLMOD tables for their particular type of frequency. 21. PARAM5 UPDATE STLPARCEL (Y/N): Enter “Y” to update/create records in STLPARCEL table. Enter “N” or leave blank to avoid STLPARCEL. Note: STLPARCEL is a table that stores settlement data by parcel level.

Figure 2. SY 41 (BOTTOM)

Press [Submit Job]. The system will notify you when the report is finished.

SY27 SET UP

Version 4.0.21. Param5 added to indicate whether or not to write Settlement output to STLPARCEL table. For this logic to work, we need an entry in SEDIT table with the following entries:

Table Name = SETTLEMENT

Field1 = FREQ

Field2 = WHOCALC

Value1 = <Frequency> E.g.: D/M/Y/1/2

Value2 = <TX13 Whocalc> E.g.: TX13

TX43 SET UP

Version 4.0.21. Settlements logic modified to make it work even after the rollover. Currently Settlements run based on Taxyr (Dupyr) defined in Duplyr. So, if the Settlements are not run before the rollover, the process was not picking up all the unsettled records (part of them were sitting in Old Taxyr). Modified the Settlements logic not to look at Taxyr, when setup is defined in TECYCLE table. Also, the program uses the Duedate and Billdate defined in TECYCLE to determine the Taxyr to be written into STLGROUP, as it would be useful for clients using Oracle Financials system to balance their accounts.

For example, in Bernalillo county everything becomes delinquent as of July 1st and any payments they receive are considered delinquents. So when processing Settlements for July 1st to October 31st (before the rollover), there is no concept of Current. So when writing records into STLGROUP, new logic is used to determine the Taxyr:

SETUP in TECYCLE (TX43)

TAXYR -> Current TAXYR

ROLLTYPE -> '~'

CYCLE -> '~'

BILLDATE -> Current TAXYR Billdate. E.g.: '01-NOV-00'

DUEDATE -> Current TAXYR Duedate. E.g.: '31-JUL-00'

After which everything becomes Delinquent

Updated 7/25/2006