Speed Net Ver 3.1.2 Release Version on 29/01/2011

The same is uploaded into the PTC’s FTP site. The Release has the following contents

Speed Net 3.1.2 Client Setup
1.Database Upgrades Folder containing POSPCC and POSPCCBackup Scripts to be executed
in Database Workshop For Sites Module.
2. Database Workshop For Sites ( Latest) Module to do the DB Upgradation.
3. DB Exl Scripts folder contains POSPCC>Exl and POSPCCBackup.Exl files which should be
run in the Script Tool.exe.
4. Script Tool.Exe
5. Net ver 3.1.2 ( Release Version) ReadMe ( This File)
6. Release_Document_of_SpeedNet_3.1.2. ( To be provided to all Operating Offices)
7. SpeedNet Communication 3.1.2
8. SpeedNet Server 3.1 ( There is no change in this version)
9. Collection Agent Booking Module with Read Me

Download

Meghdoot Updates 28-01-2011

This release primarily is due to the introduction of the new services, and partly to respond with the bugs reported in various modules, To realize the full benefits all the post offices should migrate to this new release in Toto. Particularly they should not attempt to upgrade only few modules leaving behind others. Impact of this release on Meghdoot Modules This release will have impact on the following modules of Meghdoot:
1) Point of Sale 2) Postman
3) e-Payment 4) Treasury
5) AccountsMIS 6) Schedule

Download Software Download Readme

Negative List up to 31-10-2010

Download Negative List Upto 31-10-2010

DB Analyzer dated 20-09-2010

Download DB Analyzer Dated 20-09-2010
1. Provision to update PAN Card details for SCS accounts
2. Database Discrepancies - SCS - List of SCS accounts with SI option
3. Separate LoT for NREGS / IGNOAPS / IGNWPS / IGNDPS
4. Reports in connection with AML - Reports for SB, MIS, TD, SCS, NSC and KVP deposits/opening and withdrawals/closure transactions are available under 'Income tax report' option.
5. List of Branch offices
6. List of Accounts BO wise
7. Provision to modify agent license expiry date is made available in 'RD Accounts - Agent-wise' option

Account PBS Updated 14-09-2010

Problem of eMO payment report is rectified in schedule module

Download Account PBS 14-09-2010

DB Analyzer dated 02-09-2010

Download Latest DB Analyzer Dated 02-09-2010

Latest Account Exe Dated 28-07-2010

Download Account. Exe Dated 28-07-2010
A latest accfix.exe and Account.exe for solving the problem of duplicate records shown in Increment Register is available below.Download and upgrdate the account database by running accountsfix.exe, replace the accounts exe.

DBAnalyzer Dated 26-07-2010

Download DB Analyzer dated 26-07-2010

Recent additions in DBAnalyzer >> Reports
1. Reports in connection with AML - Reports for SB, MIS, TD, SCS, NSC and KVP deposits/opening and withdrawals/closure transactions are available under 'Income tax report' option.
2. List of Branch offices
3. List of Accounts BO wise
4. Provision to modify agent license expiry date is made available in 'RD Accounts - Agent-wise' option

Negitive List Upto 30-06-2010

Download Negitive List Corrected upto 30-06-2010

Service Pack 4 of Point of Sale

Download Service Pack 4 of POint of Sale

Sub Account Day End Problem

Sub Account Day End Problem

1. Please Download this attached file and run with script tool executor ..

2. after this .. pl. execute the query mentioned below in SQL Query Analyzer ...

execute treasury..update_megh66_accountheads_bydate '010610'

Pl. also check ..the option 'Convert Temporary Fields' under tools menu through supervisory login ..

If the missing heads are listed, then make them permanent ...

During the course you may need to perform undo day's work .. perform day end and day begin once again ..

Temporary Solution- Click Here

Negitive List

Download Negitive List Corrected upto 31-05-2010

Negitive List Updated

Download Negitive List Corrected upto 30-04-2010

Sanchay Post S.O to H.O Data Transfer

SO to HO data transfer (regular, without bridge) problems and solutions:------------------------------------------------------------------------

1.How to reset the sequence number to 1 at SO? Use the option ‘DBAnalyzer >> Data Transfer >> SO - HO Data Transfer’ before doing day-end on the day data transfer is to be commenced. Select only the schemes for which data transfer is planned to be commenced. Files with sequence number 1 will be generated during day end for the initialised schemes. This option has to be executed only once at a SO for any scheme. This should not be done if transfer of data from SO to HO has already been performed for this SO through Sanchay Post.

2. How to reset the sequence number to 1 at HO for a SO? Use the option ‘DBAnalyzer >> Data Transfer >> HO - SO Data Transfer’ before doing day end on the day data transfer is to be commenced. Use this option for the SO for which data transfer from HO is planned to be commenced. Files with sequence number 1 will be generated during day end for the initialised SO, if any data is available. This option has to be executed only once for a SO.

3. What are the preparatory steps for commencement of SO to HO data transfer? The following points are to be ensured:a. POCode at HO & SO should be the same. If not, at SO use DBAnalyzer to change code.b. Include HO name in SOs (Using PO Name & Address Form) in a separate row.c. Designate the nodes for ‘Day end’. Files are generated in the node in which day end is performed.d. Check whether the fields ‘Name’ / ‘City’ / ‘Pincode’ are not blank for the schemes in which datatransfer is to be commenced.e. Rectify the discrepancies listed in DBAnalyzer.

4. Files for data transfer are not generated at SO in the designated system and folder and cannot be regenerated. Wait for ‘day-end completed successfully’ message. If this is not done files will not be generated and cannot be regenerated also. File creation for HO is the last task performed during day end and if the day end process is ended abruptly due to user intervention or otherwise, file creation for SO will not happen. If Files are not generated at SO for some schemes then check ‘Initialisation >> PO Name & Address’ form and ensure that the scheme is selected in ‘Set Scheme Computerisation Status’ option.

5. Files generated at SO are without extension and hence cannot be imported at HO HO name and code to be initialized in SO. Include HO name in SOs (Using PO Name & Address Form) in a separate row

6. 'Data does not belong to [soname]’ message displayed while importing data. Select the file again and retry Logout and login to SOSB module and retry Ask SO to re-generate the file & resend. If this problem persists, it could be due to OS mismatch (XP / Vista / Windows 2003). Re-generate file in a different system at SO or import the file in a different system at HO.

7. RD bulk posting data not transferred. RD bulk data gets transferred only if Bulk posting is done before generation of the file (before day-end).

Meghdoot 6.6 Service Pack 2 dated 07-05-2010

Download Meghdoot 6.6 SP2