MVRS billing import
The MVRS Billing Import task allows you to import billing data from MVRS systems into IEE.
Note: The MVRS file format does not currently provide a field for Premise information. Only Account is available. If you use MVRS, create customer configuration against Accounts rather than Premises.
Note: MVRS Billing Import supports duplicate meters in the same MVRS billing import file.
Use the following procedure to configure a task template:
-
Go to System Operations > Task Management > Task Templates.
-
Use the dropdown menu to select the Task Type and Task Template. (Click Add to create a new task template. For more information, see Adding task templates.)
-
Configure the Task specific parameters. These parameters are defined after step 5 of this procedure.
-
Configure the Common task template parameters. For more information, see Task template parameters.
-
Click Save.
Task specific parameters:
File Mask
Defines a file extension or a partial file name that IEE uses to monitor import directories and create export files. Enter a file mask such as .xml when configuring an import or export task template. When a file arrives in the import directory, IEE automatically schedules the file for import if it matches the mask. IEE ignores files that do not match the file mask. When creating an export file, IEE appends this mask to the file name.
MDM Account Batch Size
Enter a whole number. This import parameter is a throttle for the rate at which IEE queries the database for customer configuration. For example, if IEE receives an Integrator file with 1000 accounts, its needs to do 1000 lookups. Setting the account batch size to 100 results in 10 round-trips to the database. This is more efficient than doing all 1000 lookups at once.
Processing Chunk Size
Defines the number of configuration entities processed by sub-tasks. IEE groups the data that was processed by the task into separate batches of the size you designate here. IEE considers the task completed when all child tasks are finished, and each has reported back to the parent tasks.
Chunk size is a parameter common to several task templates. The higher the chunk size value, the greater the portion of the total available work each IEE task runner performs. A smaller value means dividing the work between more concurrent task runners.
Chunk sizes that are too large overburden a few task runners, while other task runners sit idle. In extreme cases, overly large chunk sizes could result in system failure due to lack of available, allocated memory. Chunk sizes that are too small spawn many task runners that perform more initialization and shutdown than actual work. Both large and small extremes will cause delays in export processing.
When fine tuning chunk sizes, consider database resources, hardware requirements, daily processing levels, and processing windows. Adjust values over time, as hardware and networking conditions change.
Use EBCDIC Files
Determines whether to use Extended Binary Coded Decimal Interchange Code (EBCDIC) for import or export task templates. EBCDIC is an 8-bit character encoding used on IBM mainframes and AS/400s. Select True to use EBCDIC files. Select False to exclude EBCDIC files.
Import Directory
Defines the folder that IEE monitors for incoming files. IEE automatically schedules files that arrive in this directory for import. You define the paths to default import directories in the IEE System Administration workbench. When configuring the import directory parameter in an import task template, enter the file path to the directory that IEE monitors for import files specific to this task. This parameter supports standard IEE macros. Reference as ($ImportDirectory) when configuring a task.
Start CS Export on Success
Determines whether IEE automatically begins a collection system export upon completion of a successful import. Select True to automatically begin a collection system export upon completion of a successful import. Select False to disable the automatic export.
Custom Field Mapping Group
Defines mapping groups, which are useful if you have multiple Integrator or PremierPlus4 systems. You can create a custom field mapping for each system by creating a new mapping group. Import files have key fields in them, such as AccountNumber, RouteID, PremiseNumber, MeterNumber, and RegisterNumber. In a flat-file import such as PremierPlus4 or Integrator, these fields should appear in a specific place in the import file. Sometimes the IDs are not filled-in or are placed in a different location. IEE supports mapping those fields.
Click Edit to open the dialog box and modify the mappings.
Log File
Defines the file path and filename where IEE creates transaction logs. In task templates, enter the path to the directory where you want the task to place transaction logs.
Backup File
Defines the file path to a directory where IEE creates a backup file of the readings as it imports them to the database. Enter the directory path where IEE writes the backup reading files.
External System
Defines any external system to which IEE configuration data can be associated. In many places this parameter provides you with the dropdown menu to select from the external systems configured in the External System table.
Number of Consecutive Estimates
Defines the number of consecutive estimates to use. If the number of consecutive estimates exceeds the number you set for this parameter, override the preferred collection system (as indicated in the Collection System parameter.)
Valid Collection System for Must Read
A Find Best Read parameter for exports that specifies the collection system from which a read must originate in order to be considered a best read.
Observe Must Read Indicator
Determines whether to force IEE to observe the Must Read indicator for imported data. Select True to force IEE to observe this setting. Select False to override the Must Read indicator.
Owner of Import Tasks
Defines the user ID associated with a task. By default, this field populates with the user currently logged into IEE.
Earliest read date offset
Defines the number of days that IEE must subtract from "today" when an imported reading arrives without an associated earliest read date. Enter the number of days in whole numbers.
Scheduled read date offset
Defines the number of days that IEE must add to "today" when an reading arrives without an associated scheduled read date.
Contingency read date offset
Defines the number of days IEE adds to the current day (today), when importing read dates and a reading arrives without an associated contingency read date. Enter the number of days using a whole number.
Critical read date offset
Defines the number of days that IEE must add to "today" when a reading arrives without an associated critical read date. Enter the number of days in whole numbers. This is a read-dates parameter for imports.
Route Cycle Schedule lookup offset
Defines the number of days that IEE must add to "today" in order to shift which schedule IEE should use for route cycle billing. IEE determines route cycle billing dates (such as EarliestReadDate and WorkSetScheduledReadDate) from the ReadCycle that matches specific ReadCycleSchedule dates. Route Cycle Schedule Lookup Offset is a read dates parameter for imports.