MA – BP Generate Audit Finalized

Mass Appraisal Generate Audit Finalized Batch Process

Release 6.1

Overview

The Mass Appraisal Audit Finalized batch process sets all Mass Appraisal Audit Information that meet the following criteria to Finalized:
The Status field of the Audit Records is set to Finalized.

The parcels are in the dataset, jurisdiction, neighborhood, or range of tax map numbers selected.

NOTE: Once records are finalized, they can no longer be modified, except with required permissions in alternate security.

Documentation

To view this information in pdf format, click on the following link:

BatchAuditFinalized.pdf

Business Rules for Finalized Records

When the Value Finalized option is selected on the MA – Audit Information form, a frozen record is automatically created. The first time the record is frozen, it is assigned Frozen ID -2. The next time, it is assigned Frozen ID -3, and so on.

Users can view frozen records by selecting the applicable year and Frozen ID in the History Panel, provided they have the required access permissions. Records from all Mass Appraisal forms can be viewed.

Access rights are required for viewing and modifying frozen records. These are defined in the OFD by selecting the Alternate type and then setting rights for the required Profile, Roles and users.

Related Information

Refer to the Govern OpenForms Designer (OFD) documentation for details.
Refer to the Mass Appraisal General Information documentation for further details on frozen records.

Prerequisites

Required Tables

The following tables are required for the Mass Appraisal Audit Pending batch process:

  • MA_APPRAISERS: This table lists the appraisers that can be selected for the audit.
  • NA_NAMES: This table lists all the name and address accounts in the deployment.
  • PC_PARCEL: This tables lists all the parcels in the deployment.
  • VT_USER.MAENTRY: This table lists the entry code that can be associated with an audit.
  • VT_USER.MA_AUDIT_REASON: This table lists the reasons for conducting the audit.
  • VT_USER.MA_AUDIT_STATUS: This table lists the Pending and Finalized status codes that are required for the audit.

Required Records

Ensure that the Mass Appraisal Audit Information records are up to date.
If you are running the process on a saved dataset, one must be created.

Related Batch Processes

The Mass Appraisal Audit Pending Batch Process is similar to the Audit Finalized batch process. It generates Mass Appraisal Audit Information records and sets the Status to Pending. These records can be modified or deleted. The finalized Audit Information records cannot be deleted, except by a user with authorized permissions.

Defining the MA Audit Information Form

The following new fields are now included in the MA Audit Information form. These are required for the MA Audit Finalized and MA Audit Pending batch processes.

Status
The Status field is automatically set to Pending when you run the MA Audit Pending batch process. In this state the form can be modified or even deleted. An appraiser can update the status field to Finalized. The MA Audit Finalized batch process selects the Finalized flag. At this point, the record can no longer be modified.
Audit Reason Code
The Audit Reason Code contains user defined values. When you run the MA Audit Pending batch process, you must select a reason code. This can be modified after the process is complete.

Creating Mass Appraisal Audits

You can use the Mass Appraisal Pending and Mass Appraisal Finalized batch processes, as follows, in order to facilitate the Mass Appraisal audit procedure.
Step 1
Receive the requirement to create a number of Mass Appraisal Audits.
Step 2
Run the Mass Appraisal Audit Pending batch process in order to create Mass Appraisal Audit Information records for parcels within any of the following:

  • A Saved Dataset
  • A Jurisdiction and Neighborhood
  • A Range of Tax Map Numbers

Result
The MA Audit Pending batch process updates the following fields on the MA Audit Information form:
Status: Sets the Status field to Pending.
Frozen ID: Sets the Frozen ID to 0. This indicates that the record is current and modifications can be made.
Sets the following fields as selected on the batch process form.

  • Entry Date
  • Appraiser
  • Entry Code
  • Source Code
  • Activity Code
  • Audit Reason Code

The record can be modified or deleted at this point.
Step 3
Perform audits on the parcels, update the Audit Information records, and set the Status field to Finalized.
Step 4
Run the MA Audit Finalized batch process in order to create a number of Mass Appraisal Audit Information records for parcels within any of the following:

  • A Saved Dataset
  • A Jurisdiction and Neighborhood
  • A Range of Tax Map Numbers

Result
The MA Audit Finalized batch process updates the following fields on the MA Audit Information form:
Status: Sets the Status field to Finalized.
Value Finalized: Selects the Value Finalized check box.
Frozen ID: The Frozen ID is set to a value starting with -2. This is updated for each audit performed/
Updates the following field as selected on the batch process form.
Entry Code
The record is frozen and cannot be modified, unless the user is granted the required access permissions. Typically, only supervisors have access to modify frozen records.

Defining the MA Audit Finalized Batch Process

There are no special requirements for the MA Audit Finalized batch process. It is set up as any other batch process in Govern OpenForms. You can create as many MA Audit Finalized batch processes as required.
To definethe batch process:

  1. Launch GNA.
  2. Select Editors > Batch Process Definition Editor.
  3. Select 101-ma-bp-008 > MA – Audit Finalized.
  4. Enter a Code, Short, and Long Description in order to uniquely identify the batch process.
  5. Select the Transaction tab.
  6. The Transaction Type and Transaction Mode can be set to any value, depending on how you want to run the batch process. Refer to the Govern Batch Scheduler guide for details.
  7. Complete the other parameters as required by your organization.
  8. Click Save.

Adding the MA Audit Finalized Batch Process to a Profile

In order to use the batch process in Govern OpenForms, you must add it to at least one Profile. You can add it to multiple Profiles.
To add the batch process to a Profile:

  1. Launch GNA.
  2. Select Editors > Profile Editor.
  3. Select the Profile that you want to use.
  4. Select the Links tab.
  5. Click Add in the Batch Process section to add open a secondary window.
  6. Select the batch process.
  7. Click Save.

Before Running the MA Audit Finalized Batch Process

Ensure that all MA Audit Information records are up to date in the dataset, jurisdiction and neighborhood, or range of tax map numbers that are selected.
To view the updated records.

  1. Launch Govern.
  2. Open a Profile that contains the MA Audit Information form.
  3. Perform a search to retrieve the required records.
  4. Select a record.
  5. Open the MA Audit Information form.
  6. Scroll to the required record.
  7. Ensure the following:
    The Status field is set to Finalized.
    The Finalized option is deselected.

The MA Audit Information record can still be modified at this point.

Running the MA Audit Finalized Batch Process

To run the batch process:

  1. Launch Govern.
  2. Open a Profile that contains the MA Audit Finalized batch process.
  3. Open the Batch Processing Explorer.
  4. Select the Mass Appraisal Audit Finalized batch process.
  5. Complete the Selection Criteria as follows.
    In the Parcels Selection section, do one of the following:
    Select All to create Pending Audit records for all parcels that do not have Audit records for the selected year.
    Select Saved Dataset and select a saved dataset from the drop-down list.
    Select Jurisdiction and select a jurisdiction and neighborhood from the drop-down lists.
    The jurisdictions and neighborhoods are year-based.
    Ensure that the correct year is entered in the Year field.
  6. Select Tax Map Number and enter a range of tax map numbers.
  7. Enter the year you are associating with the Audit records in the Year parameter.
  8. Select the entry code from the drop-down list (Table: VT_USR. MAENTRY).
  9. Click Save.

Viewing the MA Audit Finalized Log Files

The following information is logged and appears on the Processing tab of the MA Audit Finalized batch process in Govern. If you are scheduling the process to run at a later time, the information can be viewed on the Log Files of the Govern Scheduler.

Information: Starting Time: Displays the starting of the batch process
Parameter: UserId = Displays the name of the user who ran the process.
Parameter: BatchId = Displays the batch ID.
Information: Parameter: TransactionMode = Displays the transaction type, such as RollBackIfOneTransactionFails
Parameter: RunBatchAsync = Displays True or False according to whether the transaction type of the batch process is Synchronous or Asynchronous
Parameter: MaxNumberProcess = Displays the maximum number of records processed.
Parameter: AuditBatchID = Displays the Batch ID associated with the audit.
Parameter: SavedDataset Displays the name of the Saved Dataset.
Parameter: CanChooseSavedDatasets = Displays True or False according to whether the saved dataset option is selected.
Parameter: TaxMapStart Displays the starting tax map number in the range.
Parameter: TaxMapEnd: Displays the ending tax map number in the range.
Parameter: CanChooseTaxMapRange = Displays True or False according to whether the Tax Map Number options is selected.
Parameter: Jurisdiction = Displays the code for the jurisdiction.
Parameter: Neighborhood = Displays the code for the jurisdiction and neighborhood.
Parameter: CanChooseJurisdictionNeighborhood = Displays True or False according to whether the Jurisdiction option is selected.
Parameter: IsAllParcels = Displays True or False according to whether All is selected.
Parameter: YearId = The year the audit occurred.
Parameter: ValueFinalized = Displays True to indicate that the Value Finalized option is selected.
Parameter: EntryCode = The entry code selected for the Audit.
Parameter: EntryDate = The date of the audit.
Statistics: Total Records To Process = Displays the number of records in the batch.
Information: Statistics: Total Records Processed = Displays the total number of records processed.
Ending Time: Displays the time the batch process ended.

Viewing the Updated Record in Govern

Once the batch process is run, a new audit record is created with the status set to Pending for all parcel records that meet with the criteria.
To view the updated records.

  1. Launch Govern.
  2. Open a Profile that contains the MA Audit Information form.
  3. Perform a search to retrieve the required records.
  4. Select a record.
  5. Open the MA Audit Information form.
  6. Scroll to the required record.

 

 

101-ma-bp-008

 

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this.
Loading...

MA Modification Stamps – BRules

Mass Appraisal Modification Stamps – Business Rules

Release 6.1 [under review]

Overview

For system performance, business rules are applied to identify what needs to be reloaded and/or recomputed.
The appraisal detail records have a modification stamp that contain either:

  • date & time – the last time a computation was completed successfully
  • null value – the record needs to be recomputed do to a modification in the record or one of it’s dependencies

The master modification stamp table (single record) contains the date & time of when a change was made to parameters that can impact value.

MODIF STAMP vs LAST MODIFICATION date

  • The last modification date is updated ONLY when a physical change is made to a record, and only to this record.

Tables and Fields

PARAMETERS Modification Stamp Table [ma_modif_stamp]

The modification stamps contain the date when changes were made to parameters that impact value.
Global fields:

  • [ALL_STAMP]
    • Updated when changes to basic parameters, general equalization factors between CAMA and Tax …
    • Updated after any changes in MA_TABLES ‘Sites’ or MA_PARM_SITE
  • [SITE_STAMP] same as [ALL_STAMP]
  • [VALUE_STAMP]
    • No longer used in version 6.1. Only the ALL_STAMP will be used.

Detail component fields:

  • [BLDG_STAMP] for buildings
  • [INC_STAMP] for income
  • [LAND_STAMP] for land
  • [MISC_STAMP] for miscellaneous structures
  • [SALE_STAMP] for comparable sales
  • [MRA_STAMP] for MRA
  • [PP_STAMP] for personal property (see roadmap)

Click here for the List of Parameters Tables when changed, updates the modification stamp flags of this table.

IMPORTANT NOTE: When there is a change in General Parameters, the stamps are NOT Flagged for recompute. When a change is made that impacts value, such as changing the Depreciation Year, it will be mandatory to do a FORCE batch compute.

DATA Modification Stamp fields [ma_xxx.modif_stamp]

Each detail appraisal component records has a modification stamp attribute that gets set to null when a change is made that requires the record or its dependencies to be recomputed.
Once the compute has when with an impact on value has a modification stamp field [MA_component.MODIF_STAMP]:
MA Master Property Value record [ma_master]

  • [VALUE_STAMP] Updates when the property has been computed successfully. Note: The VAUE_STAMP is no longer used in Version 6.1 since the MODIF_STAMP was added in MA_MASTER.
  • [MODIFICATION_STAMP]

All Appraisal Components [ma_xxx]

  • [MA_Site.MODIF_STAMP]
  • [MA_Bldg.MODIF_STAMP]
  • [MA_Land.MODIF_STAMP]
  • [MA_Misc.MODIF_STAMP]
  • [MA_Inc.MODIF_STAMP]
  • [MA_MRA.MODIF_STAMP]
  • [PP_ASSESSMENT.MODIF_STAMP]

Click here for the List of Tables Changes and their impact on the stamps.

Modification Stamps Business Rules

The modification stamp of a component record contains either:

  • The CURRENT DATE & time when last computed
    • The detail component modification stamp is set to the current date after the record has been successfully computed
    • Computation triggered on creation or modification or when running the Batch Compute
  • NULL
    • When one of it’s child (see Hierarchy) has been created, modified or deleted
    • When a record was rolled forward to a new year – to be tested

The modification stamp is not updated when:

  • Computation has not been completed
  • Computation was completed but not successful (values are set to zero)
    • Invalid or missing parameters
    • Invalid record values
    • Invalid expressions
    • Invalid mathematical operations (division by zero or missing parameters)
IMPORTANT NOTE: The Modification Stamps are set to null when a roll forward is made, however they are NOT computed. To be verified

Parent Child Stamps Update Hierarchy

General

When a change occurs (add, delete, mod) to a child entity, the parent modification stamp is set to null until successfully computed.
If all the property needs to be recomputed, the MA_MASTER.Modif_stamp attribute is set to null.

  • Property Control Changes (Jurisiction, Property type, neighborhood and income neighborhood) updates ALL
  • Component Child (ex: Building Area, Building Misc.Structures) updates Root entity Building Modif Stamp
  • Component Detail Record (ex: Building, Land, Misc.) updates
    • Component Detail Record linked to other Component Detail Record (ex: MRA or Income)
    • Component Detail Record linked to Site
  • Site Values (all)
  • Global Property Value
    • Property Value linked to
      • Building linking (verify impact)
      • Parcel linking (Distributes or receive)

Detail Record Linked To Income or MRA

Buildings, Land, Miscellaneous Structures and Personal Property (see roadmap) can be linked to MRA or INCOME records.
When a change occurs in a detailed record that is linked to another component, the following occurs:

  • [MA_xxx.MODIF_STAMP] is updated
  • [MA_xxx.MODIF_STAMP] of the linked component (MRA or Income detail and root entity)
  • [MA_SITE.MODIF_STAMP] of the linked component linked site
  • [MA_MASTER_MODIF_STAMP] of the property record

Detail Record part of a CAMA Parcel or Building Linking

Depends on the LINK TYPE

  • A parcel cannot receive and provide a value at the same time. Parcels having the MA_MASTER.exclude_from_roll = <> 0 are providing values to other parcels and therefore we should not further perform this step. However we need to reset the modif stamps to all linked parcels by performing the following SQL:
  • update ma_master set MODIF_STAMP = null where year_id = (current parcel year id) and frozen_id = (current parcel frozen id) and p_id = ( select malk.p_id from MA_LINKS_PERCENT malk, PC_PARCEL_LINKS lktype where malk.LINK_ID = lktype.LINK_ID and malk.P_ID = lktype.P_ID and year_id = (current parcel year id) and frozen_id = (current parcel frozen id) and MASTER_PID = -1 and malk.p_id <> (current parcel P_ID) and exists (select 0 from PC_PARCEL_LINKS pclk where pclk.LINK_ID = malk.LINK_ID and (MASTER_PID = 0 or master_PID is NULL) and P_ID = (current parcel P_ID)))
  • update ma_master set MODIF_STAMP = null where year_id = (current parcel year id)and frozen_id = (current parcel frozen id) and p_id <> (current parcel P_ID) and exists (select 0 from MA_LINKS_PERCENT where p_id = ma_master.p_id and year_id = ma_master.year_id and frozen_id = ma_master.frozen_id and LINK_ID = (select link_id from PC_PARCEL_LINKS where MASTER_PID = -1 and p_id = (current parcel P_ID)))

Global and Site Changes

When a change is made to the site adjustments or to the fields that compose the site group description (i.e. site liability, site exemptions, etc.) or when a change is made in a component linked to the site, the following occurs:

  • [MA_SITE.MODIF_STAMP] of the detail record is updated
  • [MA_SITE.MODIF_STAMP] of the other site records with the same combination
  • [MA_MASTER_MODIF_STAMP.ALL_STAMP] of the property record

Other Entity Field Changes

Some changes made in other forms and business entities that can impact value will set the MA_MASTER.MODIF STAMP to Null.
Changes made to the fields that are used in the MA LINK GROUP lookup:

  • PC_PARCEL.Jurisdiction
  • PC_AREA.Neighborhood
  • PC_AREA.Income Neighborhood
  • PC_LEGAL.Property Type

Changes made to other custom fields used in expressions or queries that can impact value:

  • IMPORTANT: Currently, stamps are not updated.

 

 

101-ma-brules-modif_stamp

 

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this.
Loading...

101-ma-bp-001

Import APEX Sketch

Overview

 

What’s New

 

Technical Information

 

 

101-ma-bp-001

 

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this.
Loading...

MA Computation Batch Process

Mass Appraisal Computation Batch Process

Release 6.1

Overview

The Mass Appraisal computation batch program calculates the values for all the mass appraisal modules, Property, Site, Land, Buildings, MRA or FMV, Income, and Global. A separate batch process is available for the Mass Appraisal Sales module.

For details on Mass Appraisal Computation and Value Business Rules, see Valuation, MA Tables, Modification Stamps.

Computation by Neighborhood

Neighborhoods are filtered by jurisdiction. In order to run the batch process by neighborhood, you need to set up the Mass Appraisal User Validation Table by Jurisdiction.

To set up the Neighborhood table by jurisdiction.

  1. Launch GNA.
  2. Select Editors > User Validation Table Editor > Mass Appraisal.
  3. Select NBHD – Neighborhood.
  4. Select By Jurisdiction.

 

Running a Batch Process on a Saved Dataset

If you want to run a batch process on a group of parcels, such as parcels within a certain area or tax jurisdiction, you need to create and save a dataset. You can also use an existing dataset. In Govern, a dataset is a saved group of property records:

To create a new dataset:

  1. Launch Govern.
  2. Perform a search and load the parcel records that you want to include in the dataset to the treeview.
  3. Select the View menu.
  4. Enter a name for the dataset in the text box in the Data Sources section of the View menu.
  5. Click Save Dataset.

For further details on creating Datasets, refer to the Govern General Information documentation.

Accessing the Mass Appraisal Computation Batch Process

To access the Mass Appraisal Computation Batch Process in Govern:

  1. Launch Govern.
  2. Select a Profile that contains the Mass Appraisal Computation batch process.
  3. Select the Mass Appraisal Computation batch process.

Year: Enter the year for the computation. This is a required field.
By default, this field displays the year entered the last time that the process ran.

Parcels to Compute

Select one of following:

  • All

Select this option to run the process on all parcels that meet the other criteria.

  • Saved Dataset

Select this option to run the batch process on the selected dataset.

  • Jurisdiction / Neighorhood

The Neighborhood is optional. However, if you want to run the batch process on a specific neighborhood, you must select the Jurisdiction first.
Jurisdiction
Select a Jurisdiction to run the sales data computation on a specific jurisdiction.
Neighborhood
In order to select a neighborhood, you must select a Jurisdiction first. Select the Jurisdiction. Then, select the neighborhood from the Neighborhood drop-down list.

  • Tax Map Number

Enter a range of tax map numbers in the From and To parameters under Tax Map Number.

 

Computation Options

Select one of the following options.

  • All parcels that require a data update: Select this option to run the batch process on all records that are not up-to-date because they were modified before the parameters changed in GNA. These parcels have a modification date that is earlier than the parameter change.
  • All parcels that require a data update and a force compute: Select this option to run the batch process on all parcels that are not up-to-date and on all records for the selected modules. Then select the Mass Appraisal modules on which you want to run the computation:
    • All, Site, Miscellaneous Structures, MRA, Land, Building, Income, and Global.

 

Records to be processed:

  • Year selected: or all if none selected
  • Records (parcels) selected: all, saved named dataset (includes autosave dataset), jurisdiction, neighborhood
  • Record Frozen-id = zero (current)

Records to be calculated:

  • When the modification stamp of the record requires it (see Batch Processing below)
    • A change was made to Mass Appraisal Tables (different impact) after the component record was last computed
    • A component modification stamp is null (never computed or changes to characteristics or dependencies that require a compute)
    • A component modification stamp is less than the Component or Site parameters modification stamp
  • The force computation can be applied to all modules or to a specific one.

Batch Processing:

  • The batch program can be scheduled to run periodically. For instance, a process can be run every 3 minutes.
  • The transaction Mode “Roll Back If One Transaction Failed” is not supported. It will be “Continue If One Transaction Failed” by default
  • Refer to the Standard Batch Process details Batch Program Setup or Govern Scheduler for more details

 

Batch Execution

The batch program can be executed on demand or scheduled with Govern Scheduler.

During the execution, warning and error messages will be presented in the batch result grid.

  • On error, the parcel id will be displayed in the message
  • Double-click on the message to access the full text

Once completed, information will be displayed, that includes:

  • Parameters and Options used
  • Total number of records read
  • Total number of records processed

 

Batch Processing (technical)

Before Executing Subprocesses:

  • Select all parcel ID and frozen ID related to the year (or all year if none selected) the jurisdiction, or the neighborhood or the saved dataset if chosen.
  • When the Computation Options “All parcels that require a Data Update” is selected and the “Only Parcels with an empty modif stamp” is checked
    • The batch process will only return parcels without a modif stamp in MA_MASTER.
      • MA_MASTER.MODIF_STAMP = NULL

Execute Subprocess

  • For each computation, select all parcels with records for that component to compute
    • MA_MASTER.MODIF_STAMP = NULL
    • MA_“component”.MODIF_STAMP = NULL
    • MA_“component”.MODIF_STAMP less than MA_“component”.SITE_MODIF_STAMP
    • MA_“component”.MODIF_STAMP less than MA_MODIF_STAMP.”component”_STAMP
  • If the component does have a force compute option setup, select all component items to compute
  • Computation order:
    1. Compute site
    2. Compute miscellaneous
    3. Compute MRA
    4. Compute land
    5. Compute building
    6. Compute income
    7. Compute global

 

What’s New

  • 6.1 Final Compute and Transfer Records to tax is now a distinct batch program called Transfer to Tax (see road map).
  • 6.1 Final Compute Set History to Yes is now a distinct batch program called Close Year
  • 6.1 The batch computation will now process records set to History Only (prior to 6.1, they were not processed)

Troubleshooting

  • After changes, it is always best to compute for a single year and small dataset
  • The parcel ID is listed in the error message
  • Turning on the Govern Diagnostic Tool
  • Turning on the SQL Profiler Tool (system administrator)

 

See Also

 

 

101-ma-bp-002

 

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this.
Loading...

MA – Generate Pending Audit Batch Process

Mass Appraisal Generate Pending Audit Batch Process

Overview

The Mass Appraisal Audit Pending batch process automatically generates new MA Audit Information records in Govern OpenForms. While these records can be created manually, running the batch process can save time and increase the accuracy of the records

Records can be created for a:

  • Saved dataset
  • Jurisdiction and neighborhood
  • Range of tax map numbers

The MA Audit Pending batch process updates the following fields on the MA Audit Information form. Once the batch process is complete:

  • The Status field is set to Pending.
  • The Frozen ID is set to 0.

The following fields are updated as selected on the batch process form.

  • Audit Reason Code: This is a required field.
  • Appraiser
  • Entry Date: This is a required field.
  • Entry Code
  • Activity Code: This is a required field.
  • Source Code

You can select parcels from the batch process by jurisdiction or neighborhood within a range of tax map numbers, or in a saved dataset. Alternatively, you can crate audit records for all parcels. The fiscal year is required.

The Mass Appraisal Audit Pending batch process generates Audit Information user records in Govern OpenForms. The Status field is set to Pending once the process is run. These records can be modified or deleted, as any other record.

Documentation

To read this information in pdf format, click on the following link:

BatchAuditPending.pdf

Prerequisites

The following tables are required for the Mass Appraisal Audit Pending batch process:

  • MA_APPRAISERS: This table lists the appraisers that can be selected for the audit.
  • NA_NAMES: This table lists all the name and address accounts in the deployment.
  • VT_USER.MAENTRY: This table lists the entry code that can be associated with an audit.
  • VT_USER.MAINFSRC: This table lists the source codes associated with the Mass Appraisal audit.
  • VT_USER.MAACTV: This table lists the activity codes associated with the audit.
  • VT_USER.MA_AUDIT_REASON: This table lists the reasons for conducting the audit.

If you are running the process on a saved dataset, one must be created.

Related Forms

The Mass Appraisal Audit Information form is updated by the Mass Appraisal Audit Pending batch process. The Mass Appraisal Audit Finalized batch process can be run to create finalized MA Audit Information records from pending ones.

MA Audit Information User Form

The following new fields are now included in the MA Audit Information form. These are required for the MA Audit Pending and MA Audit Finalized batch processes.

  • Status: The Status field is automatically set to Pending when you run the MA Audit Pending batch process. In this state the form can be modified or even deleted. An appraiser can update the status field to Finalized. The MA Audit Finalized batch process selects the Finalized flag. At this point, the record can no longer be modified.
  • Audit Reason Code: The Audit Reason Code contains user defined values from the VT_USER.MA_AUDIT_REASON table. When you run the MA Audit Pending batch process, you must select a reason code. This can be modified after the process is complete.

For details, see Mass Appraisal Audit Information.

Related Batch Processes

The MA Audit Finalized Batch Process is similar to the MA Audit Pending batch process. It generates finalized Mass Appraisal Audit Information records for existing MA Audit Information records with the Status set to Finalized. The MA Audit Finalized batch process selects the Finalized option and updates the Entry Code as set on the batch process. The finalized Audit Information records cannot be deleted, except by a user with authorized permissions.
For details, see Mass Appraisal Audit Finalized.

Business Rules for the MA Audit Pending Batch Process

The MA Audit Pending batch process creates new MA Audit Information records for all Mass Appraisal records that:

  • Match the Selection Criteria
  • Do not have a current MA Audit Information recording with Frozen ID 0
  • Are in the Fiscal Year selected

Creating Mass Appraisal Audits

You can use the Mass Appraisal Pending and Mass Appraisal Finalized batch processes, as follows, in order to facilitate the Mass Appraisal audit procedure. None of these steps are required.

Step 1
Receive the requirement to create a number of Mass Appraisal Audit Information records on parcels within any of the following:
  • A Saved Dataset
  • A Jurisdiction and Neighborhood
  • A Range of Tax Map Numbers
Step 2
Run the Mass Appraisal Audit Pending batch process in order to create Mass Appraisal Audit Information records.:
Result
The MA Audit Pending batch process updates the following fields on the MA Audit Information form:
Status: Sets the Status field to Pending.
Frozen ID: Sets the Frozen ID to 0. This indicates that the record is current and modifications can be made.
It updates the following fields on the user form as selected on the batch process form.
  • Entry Date
  • Appraiser
  • Entry Code
  • Source Code
  • Activity Code
  • Audit Reason Code
The record can be modified or deleted at this point.
Step 3
Perform audits on the parcels, update the Audit Information records, and set the Status field to Finalized.
Step 4
Run the MA Audit Finalized batch process in order to create a number of Mass Appraisal Audit Information records for parcels within any of the following:
Result
The MA Audit Finalized batch process updates the following fields on the MA Audit Information form:
  • Status: Sets the Status field to Finalized.
  • Value Finalized: Selects the Value Finalized check box.
  • Frozen ID: The Frozen ID is set to a value starting with -2. This is updated for each audit performed/
Updates the following field as selected on the batch process form.
Entry Code
The record is frozen and cannot be modified, unless the user is granted the required access permissions. Typically, only supervisors have access to modify frozen records.

Defining the MA Audit Pending Batch Process

There are no special requirements for the MA Audit Pending batch process. It is set up as any other batch process in Govern OpenForms. You can create as many MA Audit Pending batch processes as required.

To configure the batch process:

  1. Launch GNA.
  2. Select Editors > Batch Process Definition Editor.
  3. Select 101-ma-bp-007 – MA – Audit Pending.
  4. Enter a Code, Short, and Long Description in order to uniquely identify the batch process.
  5. Select the Transaction tab.
    The Transaction Type and Transaction Mode can be set to any value, depending on how you want to run the batch process. Refer to the Govern Batch Scheduler guide for details.
  6. Complete the other parameters as required by your organization.
  7. Click Save.

Adding the MA Audit Pending Batch Process to a Profile

In order to use the batch process in Govern OpenForms, you must add it to at least one Profile. You can add it to multiple Profiles.

To add the batch process to a Profile:

  1. Launch GNA.
  2. Select Editors > Profile Editor.
  3. Select the Profile that you want to use.
  4. Select the Links tab.
  5. Click Add in the Batch Process section to add open a secondary window.
  6. Select the batch process.
  7. Click Save.

Running the MA Audit Pending Batch Process

To run the batch process:
Open the Batch Program:

  1. Launch Govern.
  2. Open a Profile that contains the MA Audit Pending batch process.
  3. Open the Batch Processing Explorer.
  4. Select the Mass Appraisal Audit Pending batch process.

Complete the Parameters:

  1. Complete the Selection Criteria as follows.In the Parcels to Compute, do one of the following:
    Select All to create Pending Audit records for all parcels with Aduit records that do not have a do not have a status..
    Select Saved Dataset and select a saved dataset from the drop-down list.
  2. Select Jurisdiction and select a jurisdiction and neighborhood from the drop-down list.
  3. Select Tax Map Number and enter a range of tax map numbers.
  4. Enter the year you are associating with the Audit records in the Year parameter.
  5. Click on the calendar icon and select the date of the audit.
  6. Select the Appraiser who is responsible for the audit from the Appraiser drop-down list.
  7. Select the entry code from the drop-down list (Table: VT_USR. MAENTRY).
  8. Select the source code from the drop-down list (Table: VT_USR. MAINFSRC).
  9. Select the activity code from the drop-down list (Table: VT_USER. MAACTV).
  10. Select the reason for the audit from the Audit Reason drop-down list (Table: VT_USR.MA_AUDIT_REASON).

Run the Program

  1. Do one of the following:
    Click Run to run the batch process immediately.
    Click Schedule to run the batch process at a later time.

Viewing the MA Audit Log Files

The following information is logged and appears on the Processing tab of the MA Audit Information batch process in Govern. If you are scheduling the process to run at a later time, the information can be viewed on the Log Files in the Govern Schedule

Parameter: ReasonCode = The Reason Code selected for the batch Process.
Parameter: BatchProcessType = The name of the batch process.
Parameter: Appraiser = The name of the appraiser who is responsible for the audit.
Parameter: EntryDate = The date of the audit.
Parameter: EntryCode = The entry code selected for the Audit.
Parameter: Activity = The activity code selected for the audit.
Parameter: SourceCode = The source code selected for the audit.
Parameter: ValueFinalized = Displays True or False according to whether the Value Finalized option is selected or deslected.
Parameter: YearId = The year the audit occurred.
Parameter: IsAllParcels = Displays True or False according to whether All is selected.
Parameter: CanChooseJurisdictionNeighborhood = Displays True or False according to whether the Jurisdiction option is selected.
Parameter: Jurisdiction = Displays the code for the jurisdiction.
Parameter: Neighborhood = Displays the code for the jurisdiction and neighborhood.
Parameter: CanChooseTaxMapRange = Displays True or False according to whether the Tax Map Number options is selected.
Parameter: TaxMapStart Displays the starting tax map number in the range.
Parameter: TaxMapEnd: Displays the ending tax map number in the range.
Parameter: CanChooseSavedDatasets = Displays True or False according to whether the saved dataset option is selected.
Parameter: SavedDataset Displays the name of the Saved Dataset.
Parameter: AuditBatchID = Displays the Batch ID associated with the audit.
Parameter: MaxNumberProcess = Displays the maximum number of records processed.
Parameter: RunBatchAsync = Displays True or False according to whether the transaction type of the batch process is Synchronous or Asynchronous
Information: Parameter: TransactionMode = Displays the transaction type, such as ContinueIfOneTransactionFail
Parameter: BatchId = Displays the batch ID.

Viewing the Updated Record in Govern

Once the batch process is run, a new audit record is created with the status set to Pending for all parcel records that meet with the criteria.
To view the updated records.

  1. Launch Govern.
  2. Open a Profile that contains the MA Audit Information form.
  3. Perform a search to retrieve the required records.
  4. Select a record.
  5. Open the MA Audit Information form.
  6. Scroll to the required record.

 

 

101-ma-bp-007

 

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this.
Loading...

 

Standard Feature – Sequential Batch Process

Standard Feature – Sequential Batch Process

Version 6.0 and Version 6.1

Overview

Available in Release 6.0 and 6.1

A standard feature that is available in version 6.0 and 6.1 of the Scheduler Console is sequential batch process scheduling. This feature may be configured to allow users to execute multiple batch processes without human interaction. This feature is convenient for launching batch processes during periods where there is less impact on users accessing the network. As an example, these sequenced batch processes could be initiated and set to run overnight, over a weekend, or through the extended periods of a holiday.

The Sequential Batch Process feature allows users to configure a list of Schedules in order to create a linked sequence of Batch Processes in the Govern New Administration (GNA). As each batch process is successfully completed, i.e. no errors generated, it will automatically initiate the next pre-configured batch process in the user defined sequence.

NOTE: Sequential Batch Processes are initiated, and monitored in the Govern Scheduler (SC). The status of the execution of each batch process is displayed through the console of the Govern Batch Scheduler application.

Example of a Sequential Batch Process

The following is an example of a possible Sequential Batch Process. The example will demonstrate a basic batch process that, upon successful completion, will initiate two (2) child batch processes. Each of the two child processes will in turn trigger other processes, and so on. Refer to the example below.

Example

  1. Batch process A is configured to run daily.
  2. When Batch process A ends it will initiate batch processes B and C
  3. Batch process B initiates batch processes D and E
  4. Batch process E initiates batch process G
  5. Batch process C initiates batch process F
  6. Batch process F initiates batch process H

All batch processes B, C, D, E, and F are configured to be triggered upon successful completion.

https://kb.harrisgovern.com/wp-content/uploads/2019/01/Sequential_Flowchart00.png

Configuration

Read More...

Sequential batch processes are configured in the Govern New Administration (GNA). Preview and execution of the batch processes are presented in the Govern Scheduler.

For further detail Govern batch process scheduling, refer to the Govern Schedule user guide for details (106-gs-all-GovernScheduler.60.pdf).

 

https://kb.harrisgovern.com/wp-content/uploads/2019/01/Sequential_Flowchart01.png

Govern New Administration (GNA)

To configure Sequential Batch processes it will be necessary to first create a new batch process or use an existing one. You would next need to create a schedule for that Batch Process. This batch process will then be configured to, upon completion, trigger the next batch process in the sequence.

TIP: When planning sequential batch processes, it is recommended that a flowchart of sorts is sketched out to use as a guide to visualize your setup. In addition, as each schedule is associated with a batch process, the batch process used should also be noted.

 

Using the example flowchart of schedules, i.e. A, B, C, D, E, and F, we will say that Batch Process A is associated with Schedule A.  Batch Process B will be associated with Schedule B, and so on.

Parent Schedule

With our flowchart drawn out for our example, we will say that the Batch Process A schedule will be called Schedule_A. Schedule A is also the parent batch process that will trigger all subsequent processes. As the parent process its configuration is different from all subsequent processes.

Creating the Parent Schedule

To create the first schedule called Schedule A in the GNA…

  1. On the GNA ribbon, click Editors (tab) > Batch Process Definition Editor.
  2. In the Batch Process Definition Editor select the batch process that will be the parent.
  3. On the Batch Process Definition tab, either select an existing batch process, or click Create a new item to create a batch process.
  4. Click to select the Scheduling sub tab.
  5. Click Add.
  6. The form to configure the schedule is displayed.
NOTE: If the batch process requires parameters to be configured, this must be completed first. The save action is required before you can schedule the batch process.
  1. Click to select the Schedule
  2. Enter a Name, and a Description.
NOTE: Name and Description are required parameters; you will not be able to save without completing them.
  1. In the Settings group below, set a frequency for the schedule; select One time, Day, Week, or Month. Additional settings allow you to specify a Start Date, and expiration date, i.e. Expires on:. For our example, this will be a one time schedule so select One time.
NOTE: As this is the first batch process, the option for Triggered should not be selected.
  1. Click Save Changes on the Schedule.
  2. Click the Close button [X] in the upper right hand corner to close the form.

Creating the Child Schedule

Configuring B and C

Referring back to our flowchart, we see that the Children batch processes, B, and C, are at the same level and are triggered by batch process A. We will need to configure Schedule B to trigger batch process D, and E. Batch process C will trigger batch process F. As batch processes B and C are both at the same level, they will be run simultaneously.

To create any Children schedules, e.g. Schedule B, C, and all other subsequent processes…

  1. On the GNA Batch Process Definition Editor, click to select the batch process that will be designated as Schedule B.
  2. On the Batch Process Definition tab, click to select the Scheduling sub tab.
  3. Click Add to display the Schedule
  4. If the batch process requires parameters to be configured, this must be completed first. The save action is required before you can schedule the batch process.
  5. Select the Schedule
  6. Enter a Name and a Description for the schedule; for our example we will use Schedule B, and “Schedule B triggered by Schedule A” for the Name and Description:

We now need to specify that Schedule B is to be triggered by the successful completion of the batch process that is attached to Schedule A.

  1. In the Settings group, click the Triggered radio button.
  2. In the Parent group, select the batch process for Schedule A from the combo box, i.e. Batch Process A.
  3. Select the Schedule; the combo box will display Schedule A.
NOTE: If the batch process is also associated with other schedules, they will also be listed. It is important that you select the correct schedule.
  1. On the Schedule tab, click Save Changes, to save the setup.
  2. Click the [X] in the upper left hand of the form to close the form.

Configuring Sequential Schedules D and E

Referring back to the workflow sketch, we see that Schedule C / Batch Process C is at the same level as Schedule B, it will be necessary to select the batch process that will be associated with Schedule C. For the Parent you will specify Schedule A. For the configuration, it will be necessary to repeat all steps for configuring a Child Schedule; see above steps. Schedule D / Batch Process D and Schedule E / Batch Process E are triggered by Batch Process B, and should be configured accordingly.

Govern Scheduler Console Preview and Execution

Viewing the setup in Govern Scheduler

When complete the final sequential batch processes can be seen in the Govern Scheduler group of the Govern Scheduler console. Looking at the interface, we can see that Schedule A is at the top of the list as the parent process. Schedule B and Schedule C are at the same level, both have their sub processes which they will trigger. Schedule D and Schedule E will be triggered by Schedule B, and Schedule F is triggered by Schedule C. Finally Schedule G is triggered by Schedule E, and Schedule F triggers Schedule H.

If a Batch Process fails…

During execution of the batch processes, if a batch process in the sequence fails, all subsequent children processes in that chain will not be executed. For example, if Batch Process B for Schedule B fails to execute, it will need to be corrected. After rectifying the error with the process, it will be necessary to execute Batch Process B again. After which all subsequent processes will then be triggered. It is not necessary to execute the entire process flow again, i.e. Schedule A.

Executing the Batch Process

To execute the Batch Processes in the Scheduler Console

  1. Click to select the process in the console.
  2. Click Execute.
NOTE: Refer to the Govern Scheduler user guide for additional configuration details, and running Batch Processes.

Business Rules

Deletions of Processes in Batch Scheduler and GNA

In the Batch Scheduler or in GNA, trying to delete a schedule with Child schedules will generate an error message. This message will indicate that in order to proceed, you must first delete the child schedules before you can delete the parent.

Deleting Parent Schedules in the Batch Scheduler

An error will be generated when attempting to delete parent schedules that are linked to sub schedules, i.e. schedules that they trigger.

Documentation

Click to view the .PDF document detailing this feature. (101-std-fea-046_SequentialBatchProcesses.pdf)

 

 

101-std-fea-046

 

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this.
Loading...