Contents Show
Changes made in this release of the software are detailed below.
Release 2.38.00 (2.38.xxxxx.xxxx).zip
Release 2.38.00 (2.38.xxxxx.xxxx) Source Code.zip
BatchProcessing_Core.zip
BatchProcessing_Core_Source Code.zip
v2.38.00_dfdd.zip
v2.38.00_webhelp_dfdd.zip
SPIRIT_Release_Notes_for_Version_2.38.00.pdf
A new version of the WIC EBT Middleware (WEM) software is available with this release. This version contains the following code updates:
WEM 2.5.2.2 Release:
Features Added:
Make the Unlock Card button reactivate a card [Offline Only].
WEM 2.5.2.3 Release:
Issues Fixed:
Soli credentials not passing through to WIC Direct.
WEM 2.5.2.4 Release:
Never released rolled into 2.5.2.5
WEM 2.5.2.5 Release:
Features Added:
Reorder issuance from begin date to end date for smart card
WEM 2.5.3.0 Release:
Features Added:
Update WEM to support pass through per file type via configuration.
Summary of changes with the new End of Month Command Line Batch Processing:
Below is a list of the processes available in End of Month Command Line Batch Processing.
CASELOAD COUNT, CASELOAD ENROLLMENT and CASELOAD REBATEITEMS insert information from the following records into the CASELOADCOUNT table:
Food instruments
Enrollment and reported participant data
Fully-breastfed infant participants
Mostly-breastfed infant participants (this function was added with Release 2.38.00)
Rebate items
VENDOR HIGHRISK DATA inserts redemption information into the REDEMPTIONHISTORY table. (Only the Redemption History table is included in the new End of Month Process.)
CASELOAD COUNT UNDUP inserts unduplicated participant information into the CASELOADCOUNTUNDUPSTATE, CASELOADCOUNTUNDUPFEDERAL, and CASELOADCOUNTUNDUPCALENDAR tables for the state, federal and calendar year respectively.
DUAL ENROLLMENT inserts dual enrollment participant information into the DUPLICATEENROLLPARTICIPATION table.
REDEMPTION RECONCILIATION inserts redemption reconciliation information into the REDEMPTIONRECONCILIATION table.
CDC FILES writes the CDC Pregnancy File and CDC Pediatric File to the output folder.
The table below includes business rules that can affect End of Month Command Line Batch Processing.
Business Rule CATEGORYID |
Business Rule DESCRIPTION |
MONTHEND_INCL_BANK_RECON |
option to include Bank Reconciliation processing |
MONTHEND_INCL_CASELOADCOUNTS |
option to include Caseload tables |
MONTHEND_INCL_CASELOADUNDUP_TBLS |
option to include Caseload Unduplicated tables |
MONTHEND_INCL_CDC_FILES |
option to include CDC files |
MONTHEND_INCL_DUALENROLLMENT_TBLS |
option to include Dual Enrollment processing |
MONTHEND_INCL_HIGHRISK_DATA |
option to include Redemption History table processing (Only the Redemption History table is included in the new End of Month Command Line Batch Processing.) |
MONTHEND_INCL_REDEMPRECON_TBL |
option to include Redemption Reconciliation table |
Below is a list of functions that were removed when the new End of Month Command Line Batch Processing was created with Release 2.38.00.
End of Month Processing screen
End of Month Checklist
All automated reporting functions
Required Processes
PARTICIPANT FORMULA
CASELOAD PROJECTION
EXTERNAL DUAL PARTICIPATION FILE
FINANCIAL REPORTS
HIGHRISK REPORTS
VENDOR HIGHRISK DATA (Only the Redemption History table is included in the new End of Month Process. All other vendor high risk processing was removed.)
Optional Processes
OPTIONAL CASELOAD REPORTS
OPTIONAL DIRECT DISTRIBUTION REPORTS
OPTIONAL NUTRITION REPORTS
OPTIONAL ENROLLMENT REPORTS
OPTIONAL FOOD INSTRUMENT REPORTS
OPTIONAL OPERATION REPORTS
OPTIONAL VENDOR REPORTS
These business rules no longer impact the End of Month Process.
Business Rule |
Description |
MONTHEND_INCL_CASELOADPROJECTION_TBL |
option to include Caseload Projection processing |
MONTHEND_INCL_CASELOAD_RPTS |
option to include Caseload reports |
MONTHEND_INCL_ENROLLMENT_RPTS |
option to include Enrollment reports |
MONTHEND_INCL_FINANCIAL_RPTS |
option to include Financial reports |
MONTHEND_INCL_FOODINSTRUMENT_RPTS |
option to include Food Instrument reports |
MONTHEND_INCL_HIGHRISK_RPTS |
option to include High Risk reports |
MONTHEND_INCL_NUTRITION_RPTS |
option to include Nutrition reports |
MONTHEND_INCL_OPERATION_RPTS |
option to include Operation reports |
MONTHEND_INCL_OPT_CASELOAD_RPTS |
option to include Caseload reports |
MONTHEND_INCL_OPT_DD_RPTS |
option to include Direct Distribution reports |
MONTHEND_INCL_OPT_ENROLLMENT_RPTS |
option to include Enrollment reports |
MONTHEND_INCL_OPT_FOODINSTRUMENT_RPTS |
option to include Food Instrument reports |
MONTHEND_INCL_OPT_NUTRITION_RPTS |
option to include Nutrition reports |
MONTHEND_INCL_OPT_OPERATION_RPTS |
option to include Operation reports |
MONTHEND_INCL_OPT_VENDOR_RPTS |
option to include Vendor reports |
MONTHEND_INCL_PARTICIPANTFORMULA_TBL |
option to include Participant Formula processing |
To test the new End of Month Command Line Batch Processing, it is recommended that state agencies/ITOs select one of the following options:
1. Test/Production Comparison
Prior to running production End of Month, backup the database.
Run production End of Month.
Refresh the test environment with the backup made above.
Upgrade SPIRIT to Release 2.38.00.
Run End of Month Command Line Batch Processing on the test environment.
Compare data between the production and the test environment with the following exceptions:
Participation data in the CASELOADCOUNT table for the End of Month Command Line Batch Processing will include mostly breastfed infants who are age birth to 1 month and have received no benefits.
Only the REDEMPTIONHISTORY table will update from the Vendor High Risk process from the End of Month Command Line Batch Processing. The remainder of the process will not run.
Reports will not be generated from the End of Month Command Line Batch Processing.
Optional processes will not run from the End of Month Command Line Batch Processing.
2. Test/Test Comparison
Determine a test environment that needs an End of Month run
Backup the database.
Run the test instance of End of Month.
Setup a second test instance and refresh that database with the backup made above.
Upgrade the second test instance to Release 2.38.00.
Run End of Month Command Line Batch Processing on the second test environment.
Compare data between the two test environments with the following exceptions:
Participation data in the CASELOADCOUNT table for the End of Month Command Line Batch Processing will include mostly breastfed infants who are age birth to 1 month and have received no benefits.
Only the REDEMPTIONHISTORY table will update from the Vendor High Risk process from the End of Month Command Line Batch Processing. The remainder of the process will not run.
Reports will not be generated from the End of Month Command Line Batch Processing.
Optional processes will not run from the End of Month Command Line Batch Processing.
For more information on the functionality of the new End of Month Command Line Batch Processing, see the End of Month Process topic.
With this release of the software, changes must be made manually to the EBTCONNECTIONINFO table to support new functionality in the SPIRIT WIC system.
UPC/PLU Redemption File
Ensure that valid file folder path values are specified within the following parameters of the EBTCONNECTIONINFO table of the SPIRIT database:
NOTE: The user running the batch must have access to the path and filename. |
i) Redemption Batch Timeout (RedemptionBatchTimeout)
This value controls the time-out period of the bulk insert of the initial records. The default for this value is 60 seconds. This value is required.
ii) Redemption Batch Record Count (RedemptionBatchRecordCount)
This value represents the maximum number of rows to bulk load during each part of a single transmission. The default for this value is 5000 rows. This value is required. If, for any reason, the batch record count isn't available, a default of 2000 rows is used.
iii) File Receive Path (FileReceivePath)
This value represents the folder location for the State UPC/PLU Redemption File used for processing. This value is required.
iv) File Archive Path (FileArchivePath)
This value represents the folder location for the archived State UPC/PLU Redemption File. This value is required.
v) Redeemed Benefits Filename (RedeemedBenefitsFileName)
This value provides a search pattern that will look for any files that start with the specified prefix. This value is required. When the value of the FILETYPE column is equal to "1" or "2", this value should match the file name format specified in the EBT processor ICD.
vi) Summer EBT Profile Number (SEBT_ProfileNum)
This value determines if Summer EBT processing is enabled. If the value is missing, or if the value is set to [999999999], then Summer EBT is disabled during redemption processing. This value is not required; however, to enable Summer EBT UPC/PLU Redemption File processing, a valid SEBT_ProfileNum value must exist for your state's environment. See the Profile Number section of the UPC/PLU Redemption File topic for more information.
vii) Summer EBT Receive File Path (SEBT_ReceiveFilePath)
This value represents the folder location for the UPC/PLU Redemption Files used for processing. This value is required only if Summer EBT processing is enabled.
viii) Summer EBT Archive File Path (SEBT_ArchiveFilePath)
This value represents the folder location for the archived UPC/PLU Redemption File. This value is required only if Summer EBT processing is enabled.
ix) WIC Program ID (WicProgramId)
This value is passed to the Header Record and the Trailer Record of the UPC/PLU Redemption File. This value is not required; therefore, no validation occurs on this parameter.
x) File Type (FileType)
This value represents the file type. This value is required. Valid values are as follows:
0 = JP Morgan
1 = WUMEI2014
2 = WUMEI2018
xi) EBT processor ICD Version (ICDVersion)
This value represents the EBT processor ICD Version to which this file complies, such as ICD.2014.2.5. This value is required when the value of the FILETYPE column in the EBTCONNECTIONINFO table is equal to "1" or "2".
xii) Universal Service Provider type (UniversalServiceProviderType)
This value represents the Universal Service Provider that generated the file. This value is required when the value of the FILETYPE column in the EBTCONNECTIONINFO table is equal to "1" or "2". Valid values are as follows:
0 = WUMEI (generic)
1 = WIC Direct
2 = S3 (Solutran)
3 = Conduent
xiii) WIC EBT host ID (WICEBTSystemID)
This value represents the WIC EBT host ID as per the EBT processor ICD. This value should match the file originator in the Header section of the file. This value is required when the value of the FILETYPE column in the EBTCONNECTIONINFO table is equal to "1" or "2".
xiv) WIC MIS System ID (WICMISSystemID)
This value represents the WIC MIS System ID as per the EBT processor ICD. This value should match the receiving institution ID in the file. This value is required when the value of the FILETYPE column in the EBTCONNECTIONINFO table is equal to "1" or "2".
xv) Redeemed File Type Extension (RedeemedBeneFileTypeExtension)
This value is used to add a file type extension to the file name when it is created in the FileSendPath and FileArchivePath. This value is required when the value of the FILETYPE column in the EBTCONNECTIONINFO table is equal to "1" or "2"and should match the file name format specified in the EBT processor ICD.
WIC Activity File
Ensure that valid file folder path values are specified within the following parameters of the EBTCONNECTIONINFO table of the SPIRIT database:
NOTE: The user running the batch must have access to the path and filename. |
i) WIC Activity Batch Timeout (WicActivityBatchTimeout)
This value is used to control the timeout period of the bulk insert of initial WIC activity records. The default for this value is 60 seconds. This value is required.
ii) WIC Activity Batch Record Count (WicActivityBatchRecordCount)
This value represents the maximum number of rows to bulk load during each part of a single transmission. The default for this value is 5000 rows. This value is required. If, for any reason, the batch record count isn't available, a default of 2000 rows is used.
iii) File Receive Path (FileReceivePath)
This value represents the folder location for the WIC Activity File used for processing. This value is required.
iv) File Archive Path (FileArchivePath)
This value represents the folder location for the archived WIC Activity File. This value is required.
v) WIC Activity Filename (WICActivityFileName)
This value represents the file name of the WIC Activity File. This value is required.
For more information about the syntax of the WICActivityFileName, refer to the file naming conventions section of the WIC Activity File topic.
vi) Summer EBT Profile Number (SEBT_ProfileNum)
This value is used to compare the profile number in the WIC Activity File. If both are same, then the Summer EBT row in the WIC Activity File is ignored and it is not saved in the SPIRIT database. This value is not required. See the Profile Number section of the WIC Activity File topic for more information.
vii) File Type (FileType)
This value represents the file type. This value is required. Valid values are as follows:
0 = JP Morgan
1 = WUMEI2014
2 = WUMEI2018
viii) EBT processor ICD Version (ICDVersion)
This value represents the EBT processor ICD Version to which this file complies, such as ICD.2014.2.5. This value is required when the value of the FILETYPE column in the EBTCONNECTIONINFO table is equal to "1" or "2".
ix) Universal Service Provider type (UniversalServiceProviderType)
This value represents the Universal Service Provider that generated the file. This value is required when the value of the FILETYPE column in the EBTCONNECTIONINFO table is equal to "1" or "2". Valid values are as follows:
0 = WUMEI (generic)
1 = WIC Direct
2 = S3 (Solutran)
3 = Conduent
x) WIC EBT host ID (WICEBTSystemID)
This value represents the WIC EBT host ID as per the EBT processor ICD. This value should match the file originator in the Header section of the file. This value is required when the value of the FILETYPE column in the EBTCONNECTIONINFO table is equal to "1" or "2".
xi) WIC MIS System ID (WICMISSystemID)
This value represents the WIC MIS System ID as per the EBT processor ICD. This value should match the receiving institution ID in the file. This value is required when the value of the FILETYPE column in the EBTCONNECTIONINFO table is equal to "1" or "2".
xii) WIC Daily Interface Reconciliation File Type Extension (WicActivityFileTypeExtension)
This value is used to add a file type extension to the file name when it is created in the FileSendPath and FileArchivePath. This value is required when the value of the FILETYPE column in the EBTCONNECTIONINFO table is equal to "1" or "2"and should match the file name format specified in the EBT processor ICD.
Expired Benefits File
Ensure that valid file folder path values are specified within the following parameters of the EBTCONNECTIONINFO table of the SPIRIT database:
NOTE: The user running the batch must have access to the path and filename. |
i) Expired Benefits Batch Timeout (ExpiredBenefitsBatchTimeout)
This value is used to control the timeout period of the bulk insert of initial records. The default for this value is 60 seconds. This value is required.
ii) Expired Benefits Batch Record Count (ExpiredBeneBatchRecordCount)
This value represents the maximum number of rows to bulk load during each part of a single transmission. The default for this value is 5000 rows. This value is required. If, for any reason, the batch record count isn't available, a default of 2000 rows is used.
iii) File Receive Path (FileReceivePath)
This value represents the folder location for the Expired Benefits File used for processing. This value is required.
iv) File Archive Path (FileArchivePath)
This value represents the folder location for the archived Expired Benefits File. This value is required.
v) Expired Benefits Filename (ExpiredBenefitsFileName)
This value represents the file name of the Expired Benefits File. This value is required.
For more information about the syntax of the ExpiredBenefitsFileName, refer to the file naming conventions section of the Expired Benefits File topic.
vi) Summer EBT Profile Number (SEBT_ProfileNum)
This value is used to compare the profile number in the Expired Benefits File. If both are same, then the Summer EBT row in the Expired Benefits File is ignored and it is not saved in the SPIRIT database. This value is not required. See the Profile Number section of the Expired Benefits File topic for more information.
vii) File Type (FileType)
This value represents the file type. This value is required. Valid values are as follows:
0 = JP Morgan
1 = WUMEI2014
2 = WUMEI2018
viii) EBT processor ICD Version (ICDVersion)
This value represents the EBT processor ICD Version to which this file complies, such as ICD.2014.2.5. This value is required when the value of the FILETYPE column in the EBTCONNECTIONINFO table is equal to "1" or "2".
ix) Universal Service Provider type (UniversalServiceProviderType)
This value represents the Universal Service Provider that generated the file. This value is required when the value of the FILETYPE column in the EBTCONNECTIONINFO table is equal to "1" or "2". Valid values are as follows:
0 = WUMEI (generic)
1 = WIC Direct
2 = S3 (Solutran)
3 = Conduent
x) WIC EBT host ID (WICEBTSystemID)
This value represents the WIC EBT host ID as per the EBT processor ICD. This value should match the file originator in the Header section of the file. This value is required when the value of the FILETYPE column in the EBTCONNECTIONINFO table is equal to "1" or "2".
xi) WIC MIS System ID (WICMISSystemID)
This value represents the WIC MIS System ID as per the EBT processor ICD. This value should match the receiving institution ID in the file. This value is required when the value of the FILETYPE column in the EBTCONNECTIONINFO table is equal to "1" or "2".
xii) WIC Benefits Purged File Type Extension (WICBenefitsPurgedFileTypeExt)
This value is used to add a file type extension to the file name when it is created in the FileSendPath and FileArchivePath. This value is required when the value of the FILETYPE column in the EBTCONNECTIONINFO table is equal to "1" or "2"and should match the file name format specified in the EBT processor ICD.
Category Subcategory File
Ensure that valid file folder path values are specified within the following parameters of the EBTCONNECTIONINFO table of the SPIRIT database:
NOTE: The user running the batch must have access to the path and filename. |
i) File Send Path (FileSendPath)
This value represents the folder location to which the Category/Sub-category File is sent. This value is required.
ii) File Archive Path (FileArchivePath)
This value represents the folder location for the archived Category/Sub-category File. This value is required.
iii) Cat/Subcat Filename (CatSubcatFileName)
This value represents the file name of the Category/Sub-category File. This value is required.
For more information about the syntax of the CatSubcatFileName, refer to the file naming conventions section of the Category/Sub-category File topic.
iv) Cat/Subcat Transaction Type (CatSubcatTransactionType)
This value is passed to the Header Record and the Trailer Record of the Category/Sub-category File. This value is required.
v) Cat/Subcat Transmit Date (CatSubcatLastTransmitDate)
This value is used to compare the MODIFYDTTM columns from the EBTFOODCATSUBCATEGORY table. This value is required.
vi) WIC Program ID (WicProgramId)
This value is passed to the Header Record and the Trailer Record of the Category/Sub-category File. This value is not required; therefore, no validation occurs on this parameter.
vii) File Type (FileType)
This value represents the file type. This value is required. Valid values are as follows:
0 = JP Morgan
1 = WUMEI2014
2 = WUMEI2018
viii) EBT processor ICD Version (ICDVersion)
This value represents the EBT processor ICD Version to which this file complies, such as ICD.2014.2.5. This value is required when the value of the FILETYPE column in the EBTCONNECTIONINFO table is equal to "1" or "2".
ix) Universal Service Provider type (UniversalServiceProviderType)
This value represents the Universal Service Provider that generated the file. This value is required when the value of the FILETYPE column in the EBTCONNECTIONINFO table is equal to "1" or "2". Valid values are as follows:
0 = WUMEI (generic)
1 = WIC Direct
2 = S3 (Solutran)
3 = Conduent
x) WIC EBT host ID (WICEBTSystemID)
This value represents the WIC EBT host ID as per the EBT processor ICD. This value should match the file originator in the Header section of the file. This value is required when the value of the FILETYPE column in the EBTCONNECTIONINFO table is equal to "1" or "2".
xi) WIC MIS System ID (WICMISSystemID)
This value represents the WIC MIS System ID as per the EBT processor ICD. This value should match the receiving institution ID in the file. This value is required when the value of the FILETYPE column in the EBTCONNECTIONINFO table is equal to "1" or "2".
xii) Cat/Subcat File Type Extension (CatSubcatFileTypeExtension)
This value is used to add a file type extension to the file name when it is created in the FileSendPath and FileArchivePath. This value is required when the value of the FILETYPE column in the EBTCONNECTIONINFO table is equal to "1" or "2"and should match the file name format specified in the EBT processor ICD.
Authorized Vendor File
Ensure that valid values are specified within the following parameters of the EBTCONNECTIONINFO table of the SPIRIT database:
NOTE: The user running the batch must have access to the path and filename. |
i) File Send Path (FileSendPath)
This value represents the folder location to which the Authorized Vendor File is sent. This value is required.
ii) File Archive Path (FileArchivePath)
This value represents the folder location for the archived Authorized Vendor File. This value is required.
iii) Vendor Filename (VendorFileName)
This value represents the file name of the Authorized Vendor File. This value is required. When the value of the FILETYPE column is equal to "1" or "2", this value should match the file name format specified in the EBT processor ICD.
For more information about the syntax of the VendorFileName, refer to the file naming conventions section of the Authorized Vendor File topic.
iv) Authorized Vendor Transaction Type (AuthorizedVendorTransactionType)
This value is passed to the Header Record and the Trailer Record of the Authorized Vendor File. This value is required.
v) WIC Program ID (WicProgramId)
This value is passed to the Header Record and the Trailer Record of the Authorized Vendor File. This value is not required; therefore, no validation occurs on this parameter.
vi) File Type (FileType)
This value represents the file type. This value is required. Valid values are as follows:
0 = JP Morgan
1 = WUMEI2014
2 = WUMEI2018
NOTE: If the system is using WEM (WIC EBT Middleware), the user will need to also configure the MIS Provider Type. Please refer to the WEM Configuration - MIS Clients section for additional configuration information. |
vii) EBT processor ICD Version (ICDVersion)
This value represents the EBT processor ICD Version to which this file complies, such as ICD.2014.2.5. This value is required when the value of the FILETYPE column in the EBTCONNECTIONINFO table is equal to "1" or "2".
viii) Universal Service Provider type (UniversalServiceProviderType)
This value represents the Universal Service Provider that generated the file. This value is required when the value of the FILETYPE column in the EBTCONNECTIONINFO table is equal to "1" or "2". Valid values are as follows:
0 = WUMEI (generic)
1 = WIC Direct
2 = S3 (Solutran)
3 = Conduent
ix) WIC EBT host ID (WICEBTSystemID)
This value represents the WIC EBT host ID as per the EBT processor ICD. This value should match the file originator in the Header section of the file. This value is required when the value of the FILETYPE column in the EBTCONNECTIONINFO table is equal to "1" or "2".
x) WIC MIS System ID (WICMISSystemID)
This value represents the WIC MIS System ID as per the EBT processor ICD. This value should match the receiving institution ID in the file. This value is required when the value of the FILETYPE column in the EBTCONNECTIONINFO table is equal to "1" or "2".
xi) Vendor File Type Extension (VendorFileTypeExtension)
This value is used to add a file type extension to the file name when it is created in the FileSendPath and FileArchivePath. This value is required when the value of the FILETYPE column in the EBTCONNECTIONINFO table is equal to "1" or "2"and should match the file name format specified in the EBT processor ICD.
Approved Product List (APL) File
Ensure that valid file folder path values are specified within the following parameters of the EBTCONNECTIONINFO table of the SPIRIT database:
NOTE: The user running the batch must have access to the path and filename. |
i) File Send Path (FileSendPath)
This value represents the folder location to which the Approved Product List (APL) File is sent. This value is required.
ii) File Archive Path (FileArchivePath)
This value represents the folder location for the archived Approved Product List (APL) File. This value is required.
iii) APL Filename (APLFileName)
This value represents the file name of the Approved Product List (APL) File. This value is required.
For more information about the syntax of the APLFileName, refer to the file naming conventions section of the Approved Product List (APL) File topic.
iv) APL Transaction Type (AplTransactionType)
This value is passed to the Header Record and the Trailer Record of the Approved Product List (APL) File.
v) APL Last Transmit Date (AplLastTransmitDate)
This value is used to compare the MODIFYDTTM columns from the EBTAUTHORIZEDUPC and EBTMAR tables. This value is required.
vi) WIC Program ID (WicProgramId)
This value is passed to the Header Record and the Trailer Record of the Approved Product List (APL) File. This value is not required; therefore, no validation occurs on this parameter.
vii) File Type (FileType)
This value represents the file type. This value is required. Valid values are as follows:
0 = JP Morgan
1 = WUMEI2014
2 = WUMEI2018
viii) EBT processor ICD Version (ICDVersion)
This value represents the EBT processor ICD Version to which this file complies, such as ICD.2014.2.5. This value is required when the value of the FILETYPE column in the EBTCONNECTIONINFO table is equal to "1" or "2".
ix) Universal Service Provider type (UniversalServiceProviderType)
This value represents the Universal Service Provider that generated the file. This value is required when the value of the FILETYPE column in the EBTCONNECTIONINFO table is equal to "1" or "2". Valid values are as follows:
0 = WUMEI (generic)
1 = WIC Direct
2 = S3 (Solutran)
3 = Conduent
x) WIC EBT host ID (WICEBTSystemID)
This value represents the WIC EBT host ID as per the EBT processor ICD. This value should match the file originator in the Header section of the file. This value is required when the value of the FILETYPE column in the EBTCONNECTIONINFO table is equal to "1" or "2".
xi) WIC MIS System ID (WICMISSystemID)
This value represents the WIC MIS System ID as per the EBT processor ICD. This value should match the receiving institution ID in the file. This value is required when the value of the FILETYPE column in the EBTCONNECTIONINFO table is equal to "1" or "2".
xii) WIC UPC/PLU (APL File) File Type Extension (UPCPLUFileTypeExtension)
This value is used to add a file type extension to the file name when it is created in the FileSendPath and FileArchivePath. This value is required when the value of the FILETYPE column in the EBTCONNECTIONINFO table is equal to "1" or "2"and should match the file name format specified in the EBT processor ICD.
Prior to upgrading to this release of the software, verify that the WEM outbox folder is empty. This folder can be identified by looking at the FILERECEIVEPATH column within the EBTCONNECTIONINFO table.
States/ITOs should run End of Day and End of Month processes in the following order:
Run the original End of Day Process - only required if your state's environment supports checks
Run the new End of Day Command Line Batch Processing
Run the new End of Month Command Line Batch Processing
The table below documents software enhancements included within this release of the software.
Enhancement# |
Primary Function |
Enhancement Detail |
||
ENH-493 |
Mostly Breastfed Infant Participants End of Month Processing |
The InsertInfantsMostlyBF stored procedure was added to the End of Month Command Line Batch Processing to count infants for participation who are substantially breastfeeding (aka partially or mostly breastfeeding), are age birth-1 month old, and have received no benefits. For more information, see the End of Month Command Line Batch Processing database changes, which include this enhancement. |
||
ENH-613 |
Dual Enrollment End of Month Processing |
R1: Ensure that the new EOM processes correctly and updates the appropriate records for the Dual Enrollment Table when business rule MONTHEND_INCL_DUALENROLLMENT_TBLS is set to Y. To accommodate the R1 requirement for this enhancement, the following functions were converted from in-line SQL code and views to new stored procedures which were added and distributed with this release of the software:
For more information, see the End of Month Command Line Batch Processing database changes, which include this enhancement. R2: The release notes should contain the name of any stored procedures used by EOM after these changes have been applied. To accommodate the R2 requirement for this enhancement, the following functions were converted from in-line SQL code and views to new stored procedures which were added and distributed with this release of the software:
For more information, see the End of Month Command Line Batch Processing database changes, which include this enhancement. R3: The legacy EOM process shall discontinue the processing of the Dual Enrollment Table. To accommodate the R3 requirement for this enhancement, changes to End of Month Processing for ENH-613 removed Dual Enrollment processing from the End of Month Process in the Scheduled Job Administration application module. With the 2.38.00 release of the SPIRIT WIC system,Dual Enrollment processing now occurs only during End of Month Command Line Batch Processing. R4: The new EOM shall not process the table if the business rule MONTHEND_INCL_DUALENROLLMENT_TBLS is set to N. To accommodate the R4 requirement for this enhancement, the new InsertIntoDuplicateEnrollParticipation stored procedure was added and distributed with this release of the software. If value of the MONTHEND_INCL_DUALENROLLMENT_TBLS business rule equals "N", the InsertIntoDuplicateEnrollParticipation stored procedure does not update the appropriate records. For more information, see the End of Month Command Line Batch Processing database changes, which include this enhancement. R5: All new processes will log information to the scheduled job log in a manner consistent with the original versions, however the order may be different since the job order may change during transition. To accommodate the R5 requirement for this enhancement, information is logged consistently in the SCHEDULEDJOBLOG table of the SPIRIT database. R6: Any prerequisite processes for either of these processes shall continue to run ahead of these processes in either legacy or the new EOM. To accommodate the R6 requirement for this enhancement, the prerequisite processes continue to run as intended: Processing in the BatchProcessor.dll for End of Month occurs in the following order: 1. Run the End of Month process
2. Write the CDC Files to Output Folders
R7: CDP shall document within the release notes that states will need to run their existing EOM prior to running the new EOM and compare the old results with the new. To accommodate the R7 requirement for this enhancement to test the new End of Month Command Line Batch Processing, it is recommended that state agencies/ITOs select one of the following options: 1. Test/Production Comparison
2. Test/Test Comparison
For more information on the functionality of the new End of Month Command Line Batch Processing, see the End of Month Process topic. |
||
ENH-616 |
Pediatric and Pregnancy CDC files End of Month Processing |
R1: Ensure that the new EOM processes correctly and creates the Pediatric and Pregnancy CDC files correctly when business rule MONTHEND_INCL_CDC_FILES is set to “Y” To accommodate the R1 requirement for this enhancement, the following functions were converted from in-line SQL code and views to new stored procedures which were added and distributed with this release of the software:
For more information, see the End of Month Command Line Batch Processing database changes, which include this enhancement. R2: The CDC files should continue to be in the same locations on the server as located with the old EOM. To accommodate the R2 requirement for this enhancement, the following stored procedures process files from the same locations as the existing End of Month Processing:
For more information, see the End of Month Command Line Batch Processing database changes, which include this enhancement. R3: The CDC files should continue to maintain the same naming convention as used in the old EOM. To accommodate the R3 requirement for this enhancement, the following stored procedures use the same naming conventions as the existing End of Month Processing:
For more information, see the End of Month Command Line Batch Processing database changes, which include this enhancement. R4: The CDC files should not timeout during EOM. To accommodate the R4 requirement for this enhancement, the following stored procedures were added to process CDC files during End of Month Command Line Batch Processing without timeouts.
For more information, see the End of Month Command Line Batch Processing database changes, which include this enhancement. R5: The release notes should contain the name of any stored procedures used by EOM after these changes have been applied. To accommodate the R5 requirement for this enhancement, the following functions were converted from in-line SQL code and views to new stored procedures which were added and distributed with this release of the software:
For more information, see the End of Month Command Line Batch Processing database changes, which include this enhancement. R6: The legacy EOM process shall discontinue the creation of the CDC files. To accommodate the R6 requirement for this enhancement, changes to End of Month Processing for ENH-616 removed Pediatric and Pregnancy CDC files processing from the End of Month Process in the Scheduled Job Administration application module. With the 2.38.00 release of the SPIRIT WIC system, Pediatric and Pregnancy CDC files processing now occurs only during End of Month Command Line Batch Processing. R7: The new EOM shall not create CDC files if business rule MONTHEND_INCL_CDC_FILES is set to N. To accommodate the R7 requirement for this enhancement, the following new stored procedures were added and distributed with this release of the software:
If value of the MONTHEND_INCL_CDC_FILES business rule equals "N", the new stored procedures do not update the appropriate records. For more information, see the End of Month Command Line Batch Processing database changes, which include this enhancement. R8: All new processes will log information to the scheduled job log in a manner consistent with the original versions, however the order may be different since the job order may change during transition. To accommodate the R8 requirement for this enhancement, information is logged consistently in the SCHEDULEDJOBLOG table of the SPIRIT database. R9: Any prerequisite processes for either of these processes shall continue to run ahead of these processes in either legacy or the new EOM. To accommodate the R9 requirement for this enhancement, the prerequisite processes continue to run as intended: Processing in the BatchProcessor.dll for End of Month occurs in the following order: 1. Run the End of Month process
2. Write the CDC Files to Output Folders
R10: CDP shall document within the release notes that states will need to run their existing EOM prior to running the new EOM and compare the old results with the new. To accommodate the R10 requirement for this enhancement to test the new End of Month Command Line Batch Processing, it is recommended that state agencies/ITOs select one of the following options: 1. Test/Production Comparison
2. Test/Test Comparison
For more information on the functionality of the new End of Month Command Line Batch Processing, see the End of Month Process topic. R11: The DFDD shall be updated appropriately to update the changes outlined within this change request document. To accommodate the R11 requirement for this enhancement, the SPIRIT WIC Detailed Functional Design Document (DFDD) was updated. For more information, see the DFDD changes for this enhancement. |
||
ENH-623 |
Redemption History Table End of Month Processing |
R1: Ensure that the new EOM processes correctly and updates the appropriate records for the RedemptionHistory table when business rule MONTHEND_INCL_HIGHRISK_DATA is set to Y. To accommodate the R1 requirement for this enhancement, the following functions were converted from in-line SQL code and views to new stored procedures which were added and distributed with this release of the software:
For more information, see the End of Month Command Line Batch Processing database changes, which include this enhancement. R2: The release notes should contain the name of any stored procedures used by EOM after these changes have been applied. To accommodate the R2 requirement for this enhancement, the following functions were converted from in-line SQL code and views to new stored procedures which were added and distributed with this release of the software:
For more information, see the End of Month Command Line Batch Processing database changes, which include this enhancement. R3: The legacy EOM process shall discontinue the processing of the high-risk vendor data. To accommodate the R3 requirement for this enhancement, changes to End of Month Processing for ENH-623 removed Redemption History Table processing from the End of Month Process in the Scheduled Job Administration application module. With the 2.38.00 release of the SPIRIT WIC system, Redemption History Table processing now occurs only during End of Month Command Line Batch Processing. R4: The new EOM shall not process the table if the business rule MONTHEND_INCL_HIGHRISK_DATA is set to N. To accommodate the R4 requirement for this enhancement, the new InsertRedemptionHistory stored procedure was added and distributed with this release of the software. If value of the MONTHEND_INCL_HIGHRISK_DATA business rule equals "N", the InsertRedemptionHistory stored procedure does not update the appropriate records. For more information, see the End of Month Command Line Batch Processing database changes, which include this enhancement. R5: All new processes will log information to the scheduled job log in a manner consistent with the original versions, however the order may be different since the job order may change during transition. To accommodate the R5 requirement for this enhancement, information is logged consistently in the SCHEDULEDJOBLOG table of the SPIRIT database. R6: Any prerequisite processes for either of these processes shall continue to run ahead of these processes in either legacy or the new EOD/EOM. To accommodate the R6 requirement for this enhancement, the prerequisite processes continue to run as intended: Processing in the BatchProcessor.dll for End of Month occurs in the following order: 1. Run the End of Month process
2. Write the CDC Files to Output Folders
R7: CDP shall document within the release notes that states will need to run their existing EOD/EOM prior to running the new EOD/EOM and compare the old results with the new. To accommodate the R7 requirement for this enhancement to test the new End of Month Command Line Batch Processing, it is recommended that state agencies/ITOs select one of the following options: 1. Test/Production Comparison
2. Test/Test Comparison
For more information on the functionality of the new End of Month Command Line Batch Processing, see the End of Month Process topic. |
||
ENH-625 |
Redemption Reconciliation Table End of Month Processing |
R1: Ensure that the new EOM processes correctly and updates the appropriate records for the Redemption Reconciliation Table. To accommodate the R1 requirement for this enhancement, the following functions were converted from in-line SQL code and views to new stored procedures which were added and distributed with this release of the software:
For more information, see the End of Month Command Line Batch Processing database changes, which include this enhancement. R2: The release notes should contain the name of any stored procedures used by EOM after these changes have been applied. To accommodate the R2 requirement for this enhancement, the following functions were converted from in-line SQL code and views to new stored procedures which were added and distributed with this release of the software:
For more information, see the End of Month Command Line Batch Processing database changes, which include this enhancement. R3: The legacy EOM process shall discontinue the processing of the Redemption Reconciliation Table. To accommodate the R3 requirement for this enhancement, changes to End of Month Processing for ENH-625 removed Redemption Reconciliation Table processing from the End of Month Process in the Scheduled Job Administration application module. With the 2.38.00 release of the SPIRIT WIC system, Redemption Reconciliation Table processing now occurs only during End of Month Command Line Batch Processing. R4: The new EOM shall not process the table if the business rule MONTHEND_INCL_REDEMPRECON_TBL is set to "N". To accommodate the R4 requirement for this enhancement, the new InsertIntoRedemptionReconciliation stored procedure was added and distributed with this release of the software. If value of the MONTHEND_INCL_REDEMPRECON_TBL business rule equals "N", the InsertIntoRedemptionReconciliation stored procedure does not update the appropriate records. For more information, see the End of Month Command Line Batch Processing database changes, which include this enhancement. R5: All new processes will log information to the scheduled job log in a manner consistent with the original versions, however the order may be different since the job order may change during transition. To accommodate the R5 requirement for this enhancement, information is logged consistently in the SCHEDULEDJOBLOG table of the SPIRIT database. R6: Any prerequisite processes for either of these processes shall continue to run ahead of these processes in either legacy or the new EOM. To accommodate the R6 requirement for this enhancement, the prerequisite processes continue to run as intended: Processing in the BatchProcessor.dll for End of Month occurs in the following order: 1. Run the End of Month process
2. Write the CDC Files to Output Folders
R7: CDP shall document within the release notes that states will need to run their existing EOM prior to running the new EOM and compare the old results with the new. To accommodate the R7 requirement for this enhancement to test the new End of Month Command Line Batch Processing, it is recommended that state agencies/ITOs select one of the following options: 1. Test/Production Comparison
2. Test/Test Comparison
For more information on the functionality of the new End of Month Command Line Batch Processing, see the End of Month Process topic. |
||
ENH-626 |
Rebate Items Data End of Month Processing |
R1: Ensure that the new EOM processes correctly and updates the appropriate records. To accommodate the R1 requirement for this enhancement, the following functions were converted from in-line SQL code and views to new stored procedures which were added and distributed with this release of the software:
For more information, see the End of Month Command Line Batch Processing database changes, which include this enhancement. R2: The release notes should contain the name of any stored procedures used by EOM after these changes have been applied. To accommodate the R2 requirement for this enhancement, the following functions were converted from in-line SQL code and views to new stored procedures which were added and distributed with this release of the software:
For more information, see the End of Month Command Line Batch Processing database changes, which include this enhancement. R3: The legacy EOM process shall discontinue the processing of Rebate Items Data. To accommodate the R3 requirement for this enhancement, changes to End of Month Processing for ENH-626 removed Rebate Items Data processing from the End of Month Process in the Scheduled Job Administration application module. With the 2.38.00 release of the SPIRIT WIC system, Rebate Items Data processing now occurs only during End of Month Command Line Batch Processing. R4: The new EOM shall not process the CaseloadCountRebateItems table if the business rule MONTHEND_INCL_CASELOADCOUNTS is set to N. To accommodate the R4 requirement for this enhancement, the new InsertIntoCaseLoadCountRebateItems stored procedure was added and distributed with this release of the software. If value of the MONTHEND_INCL_CASELOADCOUNTS business rule equals "N", the InsertIntoCaseLoadCountRebateItems stored procedure does not update the appropriate records. For more information, see the End of Month Command Line Batch Processing database changes, which include this enhancement. R5: All new processes will log information to the scheduled job log in a manner consistent with the original versions, however the order may be different since the job order may change during transition. To accommodate the R5 requirement for this enhancement, information is logged consistently in the SCHEDULEDJOBLOG table of the SPIRIT database. R6: Any prerequisite processes for either of these processes shall continue to run ahead of these processes in either legacy or the new EOD/EOM. To accommodate the R6 requirement for this enhancement, the prerequisite processes continue to run as intended: Processing in the BatchProcessor.dll for End of Month occurs in the following order: 1. Run the End of Month process
2. Write the CDC Files to Output Folders
R7: CDP shall document within the release notes what order States/ITOs needs to run existing and new EOD/EOM. To accommodate the R7 requirement for this enhancement, States/ITOs should run End of Day and End of Month processes in the following order:
|
||
ENH-627 |
Caseload Unduplicated Tables End of Month Processing |
R1: Ensure that the new EOM processes correctly and updates the appropriate tables (listed in Notes for TC1 in the Testing Criteria section above) when business rule MONTHEND_INCL_CASELOADUNDUP_TBLS is set to “Y”. To accommodate the R1 requirement for this enhancement, the following functions were converted from in-line SQL code and views to new stored procedures which were added and distributed with this release of the software:
For more information, see the End of Month Command Line Batch Processing database changes, which include this enhancement. R2: The release notes should contain the name of any stored procedures used by EOM after these changes have been applied. To accommodate the R2 requirement for this enhancement, the following functions were converted from in-line SQL code and views to new stored procedures which were added and distributed with this release of the software:
For more information, see the End of Month Command Line Batch Processing database changes, which include this enhancement. R3: The legacy EOM process shall discontinue the processing of the following tables.
To accommodate the R3 requirement for this enhancement, changes to End of Month Processing for ENH-627 removed Caseload Unduplicated Tables processing from the End of Month Process in the Scheduled Job Administration application module. With the 2.38.00 release of the SPIRIT WIC system, Caseload Unduplicated Tables processing now occurs only during End of Month Command Line Batch Processing. R4: The new EOM shall not process the (listed in Notes for TC1 in the Testing Criteria section above) if the business rule MONTHEND_INCL_CASELOADUNDUP_TBLS is set to N. To accommodate the R4 requirement for this enhancement, the new InsertCaseLoadCountUndupe stored procedure was added and distributed with this release of the software. If value of the MONTHEND_INCL_CASELOADUNDUP_TBLS business rule equals "N", the InsertCaseLoadCountUndupe stored procedure does not update the appropriate records. For more information, see the End of Month Command Line Batch Processing database changes, which include this enhancement. R5: All new processes will log information to the scheduled job log in a manner consistent with the original versions, however the order may be different since the job order may change during transition. To accommodate the R5 requirement for this enhancement, information is logged consistently in the SCHEDULEDJOBLOG table of the SPIRIT database. R6: Any prerequisite processes for either of these processes shall continue to run ahead of these processes in either legacy or the new EOD/EOM. To accommodate the R6 requirement for this enhancement, the prerequisite processes continue to run as intended: Processing in the BatchProcessor.dll for End of Month occurs in the following order: 1. Run the End of Month process
2. Write the CDC Files to Output Folders
R7: CDP shall document within the release notes what order States/ITOs needs to run existing and new EOD/EOM. To accommodate the R7 requirement for this enhancement, States/ITOs should run End of Day and End of Month processes in the following order:
|
||
ENH-629 |
Food Instrument Data (Participation) End of Month Processing |
R1: Ensure that the new EOM processes correctly and updates the appropriate records in the CASELOADCOUNT table. To accommodate the R1 requirement for this enhancement, the following functions were converted from in-line SQL code and views to new stored procedures which were added and distributed with this release of the software:
For more information, see the End of Month Command Line Batch Processing database changes, which include this enhancement. R2: The release notes should contain the name of any stored procedures used by EOM after these changes have been applied. To accommodate the R2 requirement for this enhancement, the following functions were converted from in-line SQL code and views to new stored procedures which were added and distributed with this release of the software:
For more information, see the End of Month Command Line Batch Processing database changes, which include this enhancement. R3: The legacy EOM process shall discontinue the processing of the food instrument data. To accommodate the R3 requirement for this enhancement, changes to End of Month Processing for ENH-629 removed Food Instrument Data processing from the End of Month Process in the Scheduled Job Administration application module. With the 2.38.00 release of the SPIRIT WIC system, Food Instrument Data processing now occurs only during End of Month Command Line Batch Processing. R4: The new EOM shall not process the option food instrument reports if the business rule MONTHEND_INCL_CASELOADCOUNTS is set to N. To accommodate the R4 requirement for this enhancement, the new InsertIntoCaseLoadCount stored procedure was added and distributed with this release of the software. If value of the MONTHEND_INCL_CASELOADCOUNTS business rule equals "N", the InsertIntoCaseLoadCount stored procedure does not update the appropriate records. For more information, see the End of Month Command Line Batch Processing database changes, which include this enhancement. R5: All new processes will log information to the scheduled job log in a manner consistent with the original versions, however the order may be different since the job order may change during transition. To accommodate the R5 requirement for this enhancement, information is logged consistently in the SCHEDULEDJOBLOG table of the SPIRIT database. R6: Any prerequisite processes for either of these processes shall continue to run ahead of these processes in either legacy or the new EOD/EOM. To accommodate the R6 requirement for this enhancement, the prerequisite processes continue to run as intended: Processing in the BatchProcessor.dll for End of Month occurs in the following order: 1. Run the End of Month process
2. Write the CDC Files to Output Folders
R7: CDP shall document within the release notes what order States/ITOs needs to run existing and new EOD/EOM. To accommodate the R7 requirement for this enhancement, States/ITOs should run End of Day and End of Month processes in the following order:
|
||
ENH-630 |
Enrollment Data and Reported Participant Data End of Month Processing |
R1: Ensure that the new EOM processes correctly and updates the appropriate records in the CaseloadCountEnrollment table. To accommodate the R1 requirement for this enhancement, the following functions were converted from in-line SQL code and views to new stored procedures which were added and distributed with this release of the software:
For more information, see the End of Month Command Line Batch Processing database changes, which include this enhancement. R2: The release notes should contain the name of any stored procedures used by EOM after these changes have been applied. To accommodate the R2 requirement for this enhancement, the following functions were converted from in-line SQL code and views to new stored procedures which were added and distributed with this release of the software:
For more information, see the End of Month Command Line Batch Processing database changes, which include this enhancement. R3: The legacy EOM process shall discontinue the processing of enrollment data. To accommodate the R3 requirement for this enhancement, changes to End of Month Processing for ENH-630 removed Enrollment Data and Reported Participant Data processing from the End of Month Process in the Scheduled Job Administration application module. With the 2.38.00 release of the SPIRIT WIC system, Enrollment Data and Reported Participant Data processing now occurs only during End of Month Command Line Batch Processing. R4: The new EOM shall not process the CaseloadCountEnrollment table if the business rule MONTHEND_INCL_CASELOADCOUNTS is set to N. To accommodate the R4 requirement for this enhancement, the new InsertIntoCaseLoadCountEnrollment stored procedure was added and distributed with this release of the software. If value of the MONTHEND_INCL_CASELOADCOUNTS business rule equals "N", the InsertIntoCaseLoadCountEnrollment stored procedure does not update the appropriate records. For more information, see the End of Month Command Line Batch Processing database changes, which include this enhancement. R5: All new processes will log information to the scheduled job log in a manner consistent with the original versions, however the order may be different since the job order may change during transition. To accommodate the R5 requirement for this enhancement, information is logged consistently in the SCHEDULEDJOBLOG table of the SPIRIT database. R6: Any prerequisite processes for either of these processes shall continue to run ahead of these processes in either legacy or the new EOD/EOM. To accommodate the R6 requirement for this enhancement, the prerequisite processes continue to run as intended: Processing in the BatchProcessor.dll for End of Month occurs in the following order: 1. Run the End of Month process
2. Write the CDC Files to Output Folders
R7: CDP shall document within the release notes what order States/ITOs needs to run existing and new EOD/EOM. To accommodate the R7 requirement for this enhancement, States/ITOs should run End of Day and End of Month processes in the following order:
|
||
ENH-638 |
Fully Breastfed Infant Participants End of Month Processing |
R1: Ensure that the new EOM processes correctly and updates the appropriate records in the CaseloadCount and CaseloadCountEnrollment tables when MONTHEND_INCL_CASELOADCOUNTS is set to Y. To accommodate the R1 requirement for this enhancement, the following functions were converted from in-line SQL code and views to new stored procedures which were added and distributed with this release of the software:
For more information, see the End of Month Command Line Batch Processing database changes, which include this enhancement. R2: The release notes should contain the name of any stored procedures used by EOM after these changes have been applied. To accommodate the R2 requirement for this enhancement, the following functions were converted from in-line SQL code and views to new stored procedures which were added and distributed with this release of the software:
For more information, see the End of Month Command Line Batch Processing database changes, which include this enhancement. R3: The legacy EOM process shall discontinue the processing of Fully Breastfed records. To accommodate the R3 requirement for this enhancement, changes to End of Month Processing for ENH-638 removed Fully Breastfed Infant Participants processing from the End of Month Process in the Scheduled Job Administration application module. With the 2.38.00 release of the SPIRIT WIC system, Fully Breastfed Infant Participants processing now occurs only during End of Month Command Line Batch Processing. R4: All new processes will log information to the scheduled job log in a manner consistent with the original versions, however the order may be different since the job order may change during transition. To accommodate the R4 requirement for this enhancement, information is logged consistently in the SCHEDULEDJOBLOG table of the SPIRIT database. R5: Exceptions shall be logged to the appropriate table. To accommodate the R5 requirement for this enhancement, information is logged consistently in the SCHEDULEDJOBLOG table of the SPIRIT database. R6: Any prerequisite processes for either of these processes shall continue to run ahead of these processes in either legacy or the new EOM. To accommodate the R6 requirement for this enhancement, the prerequisite processes continue to run as intended: Processing in the BatchProcessor.dll for End of Month occurs in the following order: 1. Run the End of Month process
2. Write the CDC Files to Output Folders
R7: CDP shall document within the release notes what order States/ITOs needs to run existing and new EOD/EOM. To accommodate the R7 requirement for this enhancement, States/ITOs should run End of Day and End of Month processes in the following order:
|
||
ENH-654 |
WIC Direct |
The enhancement requested for ENH-654 involves WIC Direct only. For information, see WIC Direct Release Notes with the change expected to release in July or August 2020. No SPIRIT database or Detailed Functional Design Document (DFDD) changes were required. |
||
ENH-655 |
WIC Direct |
The enhancement requested for ENH-655 involves WIC Direct only. For information, see the WIC Direct Release Notes, version 6.6.1.77. No SPIRIT database or Detailed Functional Design Document (DFDD) changes were required. |
The table below documents WUMEI-specific software enhancements included within this release of the software.
Enhancements |
||
Enhancement# |
Primary Function |
Enhancement Detail |
SPIRIT Web-12652 |
End of Day Process WIC UPC/PLU File |
The SPIRIT WIC system was modified as follows:
For more information, see the database changes for this enhancement. |
SPIRIT Web-12653 |
End of Day Process Authorized Vendor File |
The SPIRIT WIC system was modified as follows:
For more information, see the database changes for this enhancement. |
SPIRIT Web-12654 |
End of Day Process WIC Category/Sub-category File |
The SPIRIT WIC system was modified as follows:
For more information, see the database changes for this enhancement. |
SPIRIT Web-12655 |
End of Day Process UPC/PLU Redemption File |
The SPIRIT WIC system was modified as follows:
For more information, see the database changes for this enhancement. |
SPIRIT Web-12656 |
End of Day Process WIC Activity File |
The SPIRIT WIC system was modified as follows:
For more information, see the database changes for this enhancement. |
SPIRIT Web-12658 |
End of Day Process WIC Benefits Purge File |
The SPIRIT WIC system was modified as follows:
For more information, see the database changes for this enhancement. |
SPIRIT Web-142210 |
End of Day Process Authorized Vendor File |
The SPIRIT WIC system was modified to send the vendor's termination date if applicable, in the Authorized Vendor File. It now sends the DEACTBANKEFFECTIVEDATE value from the VENDORSTAMP table, if applicable. Otherwise, it sends the CONTRACTENDDATE value from the VENDOR table. This change applies to WUMEI file types only. For more information, see the DFDD Changes for this reported issue. |
Issue# |
Primary Function |
Issue Detail |
Issue Resolution |
CDP-402 |
Account Balance Report (Output) |
The user group requested clarification on the Account Balance Report (Output) regarding manual adjustments made in the processor web portal. |
The SPIRIT WIC Detailed Functional Design Document (DFDD) was modified based on comments from the user group in CDP-402. For more information, see the DFDD Changes for this reported issue. |
CDP-403 |
Void/Replace Benefits for EBT Account |
The user group requested clarification on the Benefits for Current Month data grid regarding shared benefits. |
The SPIRIT WIC The SPIRIT WIC Detailed Functional Design Document (DFDD) was modified based on comments from the user group in CDP-403. (DFDD) was modified based on comments from the user group in CDP-403. For more information, see the DFDD Changes for this reported issue. |
CDP-409 |
BatchProcessing_Core.zip Installation and Configuration EBTCONNECTIONINFO table |
The user group requested clarification to the BatchProcessing_Core.zip Installation and Configuration topic and EBTCONNECTIONINFO table information. |
The SPIRIT WIC Detailed Functional Design Document (DFDD) was not modified based on comments from the user group in CDP-409 because the requested change was documented in Release 2.36.00 in the BatchProcessing_Core.zip Installation and Configuration topic. The EBTCONNECTIONINFO table was modified. For more information, see the database changes for this reported issue. |
CDP-430 |
Authorized Vendor File |
The Authorized Vendor File produced by End of Day or manually through the Vendor Module truncates the Vendor Trade Name to 20 characters. |
The SPIRIT WIC system was modified to include up to 50 characters for the Vendor Trade Name in the Authorized Vendor File as part of the SPIRIT Web-12653 change. This change applies when the file type is WUMEI, where the value of the FILETYPE column is equal to "1" or "2" in the EBTCONNECTIONINFO table of the SPIRIT database. For more information, see the database changes and DFDD Changes for SPIRIT Web-12653. |
CDP-435 |
Adjust/Archive/Purge Process End of Day Process |
The End of Day Process does not set priority when an infant changes to a child category. |
The CheckChildFirstBirthday function was updated to correctly set the priority when an infant changes to a child category. For more information, see the database changes for this reported issue. No Detailed Functional Design Document (DFDD) changes were required. |
TMP-257 |
End of Month Process |
The End of Month Process does not drop all temporary tables from the database upon completion. |
The SPIRIT WIC system was modified to use SQL temporary database tables that automatically clean up in the new Run End of Month Command Line Batch Processing steps. For more information, see the End of Month Command Line Batch Processing database changes, which include this reported issue. No Detailed Functional Design Document (DFDD) changes were required. |
TMP-318 |
Demographics Permissions Matrix |
The user group requested clarification for feature ID 104. |
The SPIRIT WIC Detailed Functional Design Document (DFDD) was modified based on comments from the user group in TMP-318. For more information, see the DFDD Changes for this reported issue. |
TMP-340 |
Authorized Vendor File |
The Authorized Vendor File produced by End of Day or manually through the Vendor Module does not include the actual vendor store type. |
The SPIRIT WIC system was modified as follows:
For more information, see the DFDD Changes and database changes for this reported issue. |
The table below documents changes made to the SPIRIT WIC Detailed Functional Design Document (DFDD) for this release of the software.
|
Documentation Delivery Date: 07/24/2020