Friday, 26 October 2012
Sunday, 30 September 2012
UPDATE 6 FOR SPEEDNET
SpeedNet Version 3.1.2 Update 6 Release dated 29/09/2012
Index: I. Purpose of Release II. Prerequisites III. Upgradation Procedure IV. Feedback/Error Reporting I. Purpose of Release: 1. Revision of Domestic Speed Post tariff w.e.f 01.10.2012 vide BD Dte lr.no. 57-06/2011-BD&MD (pt) dated 21.09.2012. 2. Restructuring of Speed Post Discount structure vide BD Dte lr.no. 57-03/2012-BD&MD dated 24.09.2012. 3. Inclusion of 'South Africa' in the list of countries for Speed Post booking as per new EMS Standard Agreement between South Africa and India Post communicated vide Dte (GB) lr.no. 38-6/2010-DA dated 17.08.2012. 4. Revision in the method of calculation of taxes and their rounding off communicated vide BD Dte lr.no. 57-0/2011-BD&MD dated 21.09.2012. As per the latest communication, Service Tax, Edn. Cess and Higher Edn. Cess are to be rounded off together to the nearest rupee value instead of the current method of rounding up to the next higher rupee value. 5. New Speednet Communication (C#.Net) module, which will replace the old Speednet Communication (VB 6.0). II. Pre-requisites: 1. Hardware: Min. Pentium IV CPU with 2GHz speed, 1GB RAM and 500 MB free Hard Disk space. 2. OS: Min. Windows XP SP2 or higher. 3. Database: Min. SQL Server 2000 or higher. 4. Application Software: a) Speednet Server Version 3.1. b) Speednet Client Version 3.1.2 Release date: 15/12/2011. 5. Other Requirements: a) .Net Framework 2.0 or higher. III. Upgradation Procedure: Steps to Upgrade: 1. Upgrade the databases first. 2. Uninstall the old Speednet Communication and Install the new Speednet Communication. 3. Upgrade to the Speednet client application. Note: The sequence of upgradation should be followed strictly else you cannot log in to Speednet. 1. Database Upgradation: a) Take full backup of existing Databases i.e., POSPCC and POSPCCBackup b) Ensure that SpeedNet is not in use in any system at the time of upgradation. c) Run the EXL Scripts available in 'DB Exl Scripts Folder' using ScriptTool.exe and check the contents of Log folder for details of upgradation and errors, if any. 2. SpeedNet Communication Module: a) Ensure that SpeedNet is not in use in any system at the time of upgradation. b) Copy the contents of Message, RXD and TXD Folders to any other location. c) Uninstall the existing Communication Module using options available under Control Panel -->Add Remove Programs option. d) Install the new Speednet Communication Module. Note: i) If .Net 2.0 Framework is not available, stop here, install .Net 2.0 Framework and then proceed with step (d). ii) Default Installation path:- C:\Program Files\EMSClient. iii) Do not forget to update the communication path in Speednet Client under Supervisor -->Master --> Environment --> Folder Paths. e) Run the communication and complete the configuration. 3. SpeedNet Client Upgradation: On successful upgradation of DBs and Communication Module - do the Client updation. a) Copy & overwrite the Speednet.exe, BNPLDataCorrection.exe, TBNPL.snt and 4 DLLs viz., BNPL.dll, CollectionAgent.dll, EMSDelivery.dll and SpeedLib.dll from the upgradation folder to the Speednet folder in all client systems. b) Register the 4 DLLs. c) Run BNPLDataCorrection.exe once, before using Speednet. d) Run Speednet Client, check Login and confirm version updates in the Login form, Date & Time form, About form and Reports. IV. Feedback/Error Reporting: Please provide your feedback or report the errors by sending a mail to support@ceptmysore.net with the following subject: 'Speednet Version 3.1.2 - update 6 Dated: 29/09/2012 - Feedback/Error - Details. Centre for Excellence in Postal Technology, PTC Campus, Mysore -
Download patch form here
Saturday, 29 September 2012
Update-4 to Meghdoot 7.0 (Point of Sale)
ntroduction:
As per CGM, BD & Mktg Directorate, New Delhi letter no. 57-06/2011-BD&MD (pt) dated 21.09.2012, Speed Post tariff has been revised w.e.f. 01-10-2012. Further it is clarified by PA Wing of Postal Directorate vide Letter No.PA/BK-I/Service Tax/2012-13/D-6029 dated 19-9-2012 that Service tax and education cess has to be rounded off as a single component to the nearest rupee, instead of round upwards.
Based on the afore said two orders, modifications to Point of Sale application have been done. Further the wnx.dll also has been modified and the updated version is made available.
Hence this release.
Pre
‐requisites:
Update-3 to Meghdoot 7.0 released on 17.09.2012 which is also available in ftp site at url ftp://ftp.ptcinfo.org/Meghdoot7/Updates/
Contents :
Update
‐4 for Point Of Sale
contains the following:
1
|
Point of Sale exe
|
2
|
WNX.dll
|
Friday, 28 September 2012
Wednesday, 26 September 2012
Tuesday, 25 September 2012
Saturday, 22 September 2012
eMO Invoicing Problem in Update 3.0
Errors : unable to invoice eMOs either to Postman Beat or BOs or Window due to the following error:
"Error number: -2147217900
Couldn't find stored procedure 'dbo.Dly_select_EmoforIssuing to Postman/BOs/Window"
Download
"Error number: -2147217900
Couldn't find stored procedure 'dbo.Dly_select_EmoforIssuing to Postman/BOs/Window"
Download
Monday, 17 September 2012
Update 3 to Meghdoot 7.0 released
Center for Excellence in Postal Technology is constantly making efforts to bring in comfort at Post offices in implementing various Departmental software.
The expectations of the customers are rapidly changing. To meet the changing requirements of the customers Department is making efforts to upgrade the existing products or introducing new products. This update takes care of all the upgrades and new products being introduced by the Department.
The most salient features of this update are
i). Customized installer for upgrading Meghdoot to update-3.
ii). Online acceptance of fee for entrance examination.
iii). Disabling booking of Registered letters without barcode.
iv). Offline booking of WNX articles.
v). e-Money order Compilation
vi). MNOP implementation in Rnet.
Detailed information is furnished below about each change implemented in the software.
General Manager,
Center for Excellence in Postal Technology,
Mysore.
Detailed information about each change implemented in the software
Reason for release: Update-3 to Meghdoot 7.0 is being released in order to implement major changes in most of the Meghdoot modules besides provision of some other minor changes and rectifying the erros/bugs brought to the notice of CEPT till now.
Who has to Upgrade: Update-3 has to be implemented by all the Computerized Post Offices in the Country.
Pre-requisite: Update-1 to Meghdoot version 7.0 released by CEPT on 05.12.2011.
Detailed Release document containing Installation procedure and the modifications done in each module is also available the release document. The Software containing UPDATE-3 TO MEGHDOOT 7.0 can be downloaded from 15.09.2012.
friday, 15 th
September, 2012
Update-3 to Meghdoot 7.0
Release Document
Centre for Excellence in Postal Technology,
Mysore 570010
september 15
Contents:
Brief Description
Pre-Requisite
th
Installer Application
UPDATE-3 TO MEGHDOOT 7.0
General Instructions for up-gradation
Detailed up-gradation procedure
New features/modifications
Annexure
1. Brief Description
This document acts as an upgrade guide for upgrading all Meghdoot applications from to corresponding
update-3 version. The Update-3 to Meghdoot 7.0 consolidates following applications:
Installer Application
Point of Sale(including Despatch)
eMO
ePayment
pstman
MO Compilation
Accounts
AccountsPBS (Schedules)
Sub Accounts
Treasury
acountsMIS
R Net Communication (For Post Offices)
R Net Communication (For MBC/BPCs)
R Net (For RMS Offices)
Pincode
Page 2 of 28
September 15
2. Pre-Requisite
UPDATE-3 TO MEGHDOOT 7.0
The pre-requisite for Update-3 is Update-1 to Meghdoot version 7.0 released by CEPT on 05.12.2011,
which is available on ftp site at location
ftp://ftp.ptcinfo.org/Meghdoot7/Updates/
Installer Application
An Installer application is developed in order to automate the process of Up-gradation in Smaller Post
offices. The salient features of Installer application are:
It upgrades all the database scripts one by one
It copies the exe files and dll files to the respective application path
It registers the dll files with the system.
Procedure to use the Installer application:
It has to be copied to the machine along-with the update-3 folder.
The Checkbox "Server" has to be selected, if it is a server machine. In such a case, database
scripts will be executed one by one.
The application paths of all the Meghdoot modules installed in that machine have to be
provided.
Click on OK to start the up-gradation process. If any error occurs while execution, please send
the Log file created by the application to CEPT, Mysore and the procedure for manual up-
gradation as mentioned in Point-5 below may be followed.
As it is machine specific application, its use will be more in smaller Post Offices where all the
applications are operated in one or two systems. In bigger offices, where exclusive systems are
available for independent modules, the normal manual up-gradation process may be followed. The
process of automatic up-gradation of all the modules over the network will be released in the next
version of the Installer application.
Page 3 of 28
September 15 th , 2012
UPDATE-3 TO MEGHDOOT 7.0
4. General Instructions for Up-gradation
Ensure that Up-gradation is carried out after Day End in all modules.
Ensure that the office is upgraded with Update-1 to Meghdoot Version 7.0 dated 05.12.2011.
Ensure that backups of all databases and mdb files are taken and securely preserved.
Ensure 100% successful running of the database up-gradation. If any error occurs while
executing any exl file, please send the log file to CEPT Help Desk (
Support@ceptmysore.net
The up-gradation folder contains the following sub folders:
DatabaseScripts folder containing the exl files to be run to upgrade the databases •
Applications folder containing the executable file(s)/Dll files, which are to be copied to the
application folders by replacing the existing ones •
Support Folder containing Pincode application and other support documents.
Detailed Procedure for the following major modifications in this update, is furnished at the end
of this document. The same may be brought to the notice of all concerned officials
Offline Transmission of WNX Transactions as Annexure I
Collection of Online Examination Fee through ePayment system as Annexure II
eMO Issue/Paid returns (incorporated in MO Compilation module) as Annexure III
Please upgrade the applications in the following order:
eMO
emo
ePayment
ePayment Point of Sale
Point of Sale
Despatch
Dspatch
Sub Accounts
Sb Accounts
reasury
reasury
Postman
Postman
AccountsMIS
AccountsMIS
R Net Communication
R Ne
t Communication
MO Compilation
MO Compilation
Accounts
Accounts
AcountsPBS
AccountsPBS
Page 4 of 28
September 15
UPDATE-3 TO MEGHDOOT 7.0
5. Detailed Upgradation Procedure (Please follow the order mentioned below strictly)
eMO
eMO
top eMO and eMO Client applications.
Ensure that other emo related applications viz., Point of Sale, Postman etc; are not running.
Run emo_1.exl, eMO_2.exl, eMO_3.exl, eMO_4.exl, one by one, using Script Tool
Replace existing emo.exe and emoclient.exe available in respective installation paths
with the new versions provided
ePayment
Stop ePayment application.
Ensure that other ePayment related applications are not running.
Upgrade eCounter database by running eCounter_1.exl, eCounter_2.exl and eCounter_3.exl
using script tool.
Replace the existing ePaymentClient.exe with the new ePaymentClient.exe in ePayment
Client installation path.
Point of Sale and Despatch
Point of Sale and Despatch
Run the script Counter.exl and Counte_1.exl using Script Tool.
Replace the existing PointOfSale.exe with the new PointOfSale.exe in Point Of Sale Client
installation path. Replace the existing Despatch.exe with the new Despatch.exe in the installation path.
Copy the WNX.DLL to the Point Of Sale Client installation path and register the DLL.
Copy the ClientSoftware folder to the C drive of each client system and share the folder.
Copy the WNXMasterdata folder to the server.
Sub Accounts
Sub Accounts Run the script SUBACCOUNTS.exl using Script Tool.
Replace the existing SubAccounts.exe with the new SubAccounts.exe in SubAccounts Client
installation path.
Page 5 of 28 September 15
Treasury
Treasury
UPDATE-3 TO MEGHDOOT 7.0
Run the scripts Treasury_1.exl, Treasury_2.exl using Script Tool.
Replace the existing Treasurer.exe with the new Treasurer.exe in Treasurer Client
Postman
Postman
installation path.
Replace existing Postman.exe with new one.
Replace existing EMODelivery.dll with new one.
Replace existing EVPDelivery.dll with new one.
Register both EMODelivery.dll and EVPDelivery.dll
Run Postman.exl with script tool.
AccountsMIS Client (DET)
Replace existing Meghdoot Accounts MIS Client.exe with new one.
Replace the ServerObject.dll and AccountMISClient.dll with the new ones.
R Net Communication for Post Offices
Stop the R Net communication Client.
Ensure that the Counter and Postman database up-gradation is over successfully.
Take the backup of Old communication Client.
Replace the R Net communication exe with the new one.
Run the R Net communication exe.
If any error is reported, please send the mail to support@ceptmysore.net with error screen
shot and Log, TXD and RXD folders.
MO Compilation ( for Head Post Offices only)
MO Compilation ( for Head Post Offices only)
Replace existing MOCompilation.exe with newone.
Run MOCompilation.exl with script tool.
Login as MO Compilation Supervisor and go to My Office Environment menu option and
provide all required details and click on ‘OK’ button to save entries.
Page 6 of 28
UPDATE-3 TO MEGHDOOT 7.0
Accounts ( for Head Post Offices only)
Accounts ( for Head Post Offices only)
Copy AccountsFix folder to Desktop.
Run AccountsFix.exe available therein.
eplace the existing Accounts.exe with the new one
ountsPBS ( for Head Post Offices only)
AccountsPBS ( for Head Post Offices only)
the new Schedule.exe and replace the old exe with the new exe in the same location.
Run the Schedule.exl with script tool.
Run NICPLI.exl with script tool
6. New Features/Modifications done in this Update-3
Point of Sale
Option for booking WNX Transactions offline.
VP booking facility to Registered News Papers.
Option for uploading bulk Service eMOs.
ervice tax updation for Speed Post.
Service tax updation for NPS.
Validation for PLI and RPLI transactions.
Provision for acceptance of PLI and RPLI premium containing Paisa.
Rectified the error in PLI Transaction with Cheque.
Rectified the error in Statistical Report.
Provision for configuring the office as Mail Business Centre/Business Processing Centre.
Generation of Unique Receipt Number for Collection of Online Examination Fee.
From now onwards, all Registered Letter category articles have to be booked with Barcode
only .
Page 7 of 28
September 15
Despatch
Despatch
UDATE-3 TO MEGHDOOT 7.0
Closing of more than one bag to the same destination in same despatch.
Rectified the error while bulk uploading of Special Journal articles.
Rectified the error in Bundle Report & save to bundle option.
After preparing HVMO list, in order to include it in REGB bag please select "Include HVMO
List".
In Post Offices, provision made to close registered bags only to concern L1 or L2 offices.
In BPC/MBCs, provision made to close bags to any post office/L1 Office/L2 Office in the
country
Only one operator of despatch module can be able to despatch the bags whose configuration
need to be done in the following option.
Despatch -> Supervisor -> Master ->Bags Despatch User.
Provision made to despatch all the registered bags closed which is in the following option
Despatch -> Operator -> Prepare -> Despatch Bags.
Provision made to close more than one bag and bundle for same office and concern reports
has been changed.
Login info displaying in the menu item in order to identify who has been logged in.
Allowing only valid pin code in Redirected, Special Journal detailed booking and bulk
upload (text & excel).
Rectified the Collation error while preparing the HVMO List.
While preparing the bundle / bag, in the search option of article
a. Rectified the issue blinking against some other article in case of article not found.
b. Provision made to scroll the list automatically to the selected article.
Rectified the BPC abstract problem.
Rectified the binary truncation error while uploading the special journal articles through excel
file.
Page 8 of 28
eMO
UPDATE-3 TO MEGHDOOT 7.0
Flush data option provided for eMO Administrator for flushing of old Bulk payee data in
addition to flushing of Booking data to backup database so as to enhance the performance
of eMO module. The Procedure for flushing old data is:
Stop all the emo and emo realted applications.
•
Take the backup of the emo database
•
Login as Administrator. Only for first time you have to create backup database to flush old
emo data.
Give the cut off date since installation of emo 2008
Data may be moved for month by month, if data is more it should be done for day to day
basis (for some dates)
Once Data for 5-6 months is moved please shrink the database both emo and emobackup,
so that efficiency of shrinking will be more
eMO Client module will transmit eMO compilation data to central server
ePayment
Collection of Examination Fee through ePayment system has been introduced. The detailed
procedure for this scheme is furnished under Annexure II.
SP COD Biller creation : While creating the SPCOD biller in ePayment Website, please select
Biller Type as "SPCOD" and then put tick mark in the check box "Whether eVP/SPCOD Biller".
Sub Accounts
The following new Account Heads for SPCOD Delivery receipts and payments have been added
Account head Description Category ReceiptorPayment
spcodcollection SPCODCollection General Receipts
spcodfee SPCOD Fee General Receipts
spcodpayments SPCOD Payments General Payments
Provision made for upload of eMO related files received along with Daily Accounts.
Separate classification of amounts related to IEMO Paid in Summaries/Cash Account etc.,
Fixed the problem related to SQL 2005 – "Transaction context in use by another session"
Page 9 of 28
September 15
Treasury
UPDATE-3 TO MEGHDOOT 7.0
Provision for payment of SPCOD Collections to the SPCOD Billers through the Option Treasurer
–Payments—SPCOD Payments.
Report of SPCOD Payments made to the SPCOD Billers is provided through the Option
Treasurer – Reports –SPCOD Payment.
Classification of amounts of SPCOD collection after payment under ‘SPCOD Payments’,
‘SPCOD Fee’, Taxes etc., in Summaries/Daily Account as like ‘EBill Payments’,
‘EBillCommission’ .
Separate classification of ‘SPCODCollection’ made through Postman towards delivery of
SPCOD articles at the Delivery Office in Summaries/Daily Account.
Generation of Text file for EMO issue along with Other Daily Account files at Sub Office for the
purpose of eMO Compilation at Head Office.
Generation of Text file for EMO Paid along with Other Daily Account files at Sub Office for the
purpose of eMO Compilation at Head Office.
Separate classification of Foreign MOs Paid (IFS) through Postman under the Head of Account
‘IEMOPaid’ in Summaries/ Daily Account.
Provision for capturing the details of MTCN Number, Name of the Payee while making
payments towards ‘WUMTS’ through the Option Treasurer—Payments--Other payments for
transfer of WU Transactions Data through Accounts MIS for reconciliation/pairing work.
Pensioner’s Name column added in the ‘Pensions Paid’ Report at Sub Offices in Treasury.
Provision for Handling the NPS invalid transactions for Refund to the subscribers at Mysore
HO. (Released and deployed at Mysore HO with Update 2 for Meghdoot 7.0)
Page 10 of 28
Postman
UPDATE-3 TO MEGHDOOT 7.0
Delivery of Speed Post COD (SP COD) articles through Postman module. Please go through
complete SOP released by Directorate on SP COD scheme.
Provision for Receipt of Bag
Generation of Bag Receipt and Bag Opening message
Generating the messages for eVPP articles for the purpose of RNet tracking
Accounts
Option provided for dumping monthly data for calculation of Income tax.
Calculation of Income Tax as per new rates.
GDS details such as Date of Joining, Date of Birth and PRAN Number are being captured for
the purpose of detailed reports.
Error of Incorrect balance and Installment in GPF sanction has been solved.
AccountsPBS
PLI-RPLI cursor problem while generation of CSV file rectified
Data entry/fetching/Preparation of schedules for Ebillers which are inactivated in ECOUNTER
has been rectified. (Earlier unable to prepare the schedule for inactivated Ebillers)
EB commn digit problem rectified (fractions allowed in commn )
EMO issue over flow error rectified
EMO paid over flow error rectified
In PLI RPLI Policy Numbers, slashes or hyphens is not allowed continuously. For eg -- or // are
not allowed.
Under Modification of policy numbers in PLI / RPLI Premium -Operators are allowed to
Modify the Policy numbers (earlier only selection was allowed.)
Page 11 of 28
UPDATE-3 TO MEGHDOOT 7.0
Search option is provided in Modify option of PLI/RPLI policy numbers. The operator can type
one or two digits of policy numbers and click on search and select the Number if already
exists.
Problem in net amount, renewal amount, first year premium is corrected in view option..
Policy Premium amounts in fraction are accepted e.g. 48.50 is accepted as premium
AccountsMIS (DET)
Identification of Fake Reporting offices at CEPT Central Server.
Generation of new file for the Western Union Money Transactions happened in the Project
Arrow office.
Transmission of Western Union Money Transactions file to CEPT Central Server
RNet Communication
Transmission of WNX articles booked through Point of Sale to WNX Server.
BPC/MBC selection option.
Rectified ‘trxcheck.log’ problem.
Blocking frequent requests from R Net communication to central server. Therefore, a
minimum of half an hour time lap should be there between two successive requests to Central
Server. However, this will not apply for transmission of transactional data to/from central
server.
MO Compilation
eMO Compilation (Issue and Paid returns) facility has been incorporated in MO Compilation
module from this version onwards. Therefore, the modifications done to incorporate eMO
returns are explained in detailed below
Page 12 of 28
September 15
PDATE-3 TO MEGHDOOT 7.0
•
Only offices identified as WNX Booking Centres need to follow the following procedure.
•
AirwayBill configuration and Piece Id Configuration need to be done as per the series
allotted to each office by WNX.
Hither to the WNX transactions are being booked and transmitted online, by connecting to WNX
server for each activity. As this process is taking too much time for booking of each WNX
Transaction, the process of booking has been made offline.
Now onwards, booking of WNX transactions will happen in locally like any other counter
transaction and the booked data will be transmitted Communication to WNX server. For
initializing the new process, please follow the below procedure:
Select the option ‘WNX Configuration’ through Supervisor--> Configure option and click
on ‘Update Service’.(This can be done from the Server machine)
After clicking on Update service, Select the browse button and browse to the
WNXMasterData folder.
A message "WNXMaster updation is in progress…" will appear. Click on OK button and
wait for the completion of master data updation.
Airway bill configuration need to be done through Supervisor --> Configure --> WNX
Configuration --> AirwayBill
Configuration need to be done with the Airway bill series and Piece Id Series applicable
to each office. These details will be supplied by WNX.
Select the option 'World Net Express' through Operator --> ForeignMail --> Airmail for doing
WNX Transactions.
Rest of the procedure remains unchanged.
UPDATE-3 TO MEGHDOOT 7.0
ection of Examination Fee through ePayment System
The biller should be created in e-Payment web site by selecting the Biller Type as
'EXAMINATION FEE'.
Unique receipt number of 14 digits will be generated through Point of Sale module.
No transaction cancellation facility in Point of sale.
The transaction data will be transmitted to e-Payment central server during the next call of e-
Payment Client for downloading to the biller. (Without waiting for Point of sale Submit account
and Supervisor verification).
Biller download format should be configured in e-Payment web site for required periodicity.
Transaction data will be downloaded to biller periodically containing the unique receipt number.
Full transaction data will be transmitted to e-Payment server only after submit account and
supervisor verification as per ePayment system and sent for payment to office of payment.
Page 14 of 28tember 15
UPDATE-3 TO MEGHDOOT 7.0
Procedure for using eMO options in in MO Comilation
The new features include:
1.
Background
2.
Fetch Local eMO Data
3.
eMO Issue Data – HO
4.
eMO Paid Data – HO
5.
eMO Tally with HO Summary
6.
Error Report - eMO Tally with HO Summary
7.
Fetch SO eMO Data
8.
eMO Issue Data –SO
9.
eMO Paid Data – SO
10.
eMO Tally with SO Summary
11.
Error Report - eMO Tally with SO Summary
12.
eMO Issue Returns
13.
eMO Paid Returns
Each feature given above is explained in detail in the document.
TO MEGHDOOT 7.0
New background of MO Compilation application is as follows.
2.
Fetch Local eMO Data
UPDATE-3 TO MEGHDOOT 7.0
This option can be used to fetch local emo issue and paid details to MO Compilation application based
on the date range provided and options selected.
Page 17 of 28
3.
eMO Issue Data - HO
UPDATE-3 TO MEGHDOOT 7.0
Instead of fetching data, there is provision to enter eMO issue details of the local office. Operator has to
select HO Date and enter eMO value, commission, total number of eMOs, first PNR number and last PNR
number of the day. In case any eMOs were cancelled on the day, that entry also should be made after
checking "Error Entry" option.
In addition to data entry, provision has been provided for viewing, modifying and deleting the data.
The screenshot is given below.
September 15
4.
eMO Paid Data - HO
UPDATE-3 TO MEGHDOOT 7.0
There is option to enter details of eMO paid in the local office. Select HO date and enter total value of
eMOs paid and number of eMOs paid on the date. In case any error entry is there, it can be entered in
the space provided.
There is provision to view, modify and delete paid details also. Please see below given screenshot.
5.
eMO Tally with HO Summary
UPDATE-3 TO MEGHDOOT 7.0
One new feature in MO Compilation is tallying eMO data with HO summary. The eMO issue and paid
details of local office should be tallied with HO Summary. Tallying should be done for each HO date for
which data is entered before taking returns report.
UPDATE-3 TO MEGHDOOT 7.0
6.
Error Report – eMO Tally with HO Summary
In case any difference between the data entered in MO Compilation and that in HO Summary, an error
report will get displayed. Screenshot of one sample report is given below. of 28
September 15
7.
Fetch eMO SO Data
th
, 2012
UPDATE-3 TO MEGHDOOT 7.0
This feature helps to fetch eMO issue and paid details of attached Sub Offices. Operator has to select Ho
Date, SO name, date range and options. The emo issue or paid details of selected SO for given date
range will be fetched and entered to MO compilation application with selected HO date.
Page 22 of 28
September 15
th
8.
eMO Issue Data – SO
, 2012
UPDATE-3 TO MEGHDOOT 7.0
There is data entry option to enter emo issue details of an attached sub office. Operator has to select
HO date, SO name, SO date and has to enter total eMO value, commission, total number of eMOs, first
and last PNR numbers of the day.
There is provision to view, modify and delete the data entered.
Please see below screenshot. Yesterday’s last PNR number is shown as "0" because no data was entered
for an earlier date.
Page 23 of 28
September 15
9.
eMO Paid Data - SO
th
, 2012
UPDATE-3 TO MEGHDOOT 7.0
This option helps to do data entry of eMO paid details of an attached sub office. There are options to
view, modify and delete paid details. Please see below screenshot.
Page 24 of 28
September 15
th
, 2012
10.
eMO Tally with SO Summary
UPDATE-3 TO MEGHDOOT 7.0
eMO issue and paid details of attached Sub offices should be tallied with SO summary data.
UPDATE-3 TO MEGHDOOT 7.0
11.
Error Report – eMO Tally with SO Summary
In case eMO issue or paid data entered for sub offices does not tally with data in SO summary, an error
report will be displayed as below.
12.
eMO Issue Returns
UPDATE-3 TO MEGHDOOT 7.0
The eMO issue returns reports can be generated for first or second period of a month. The report can of
two types: Date wise returns and Office wise returns
Date wise returns will fetch data based on date and Office wise report fetch data based on the offices
under the HO. Please see screenshots below.
MO Paid Returns
UPDATE-3 TO MEGHDOOT 7.0
Similar to eMO issue returns report, paid reports also can be generated for first or second period of a
month. The report can of two types: Date wise returns and Office wise returns.
Date wise returns will fetch data based on date and Office wise report fetch data based on the offices
under the HO. Please see below screenshots.
Page 28 of 28
September, 2012
Update-3 to Meghdoot 7.0
Release Document
Centre for Excellence in Postal Technology,
Mysore 570010
september 15
Contents:
Brief Description
Pre-Requisite
th
Installer Application
UPDATE-3 TO MEGHDOOT 7.0
General Instructions for up-gradation
Detailed up-gradation procedure
New features/modifications
Annexure
1. Brief Description
This document acts as an upgrade guide for upgrading all Meghdoot applications from to corresponding
update-3 version. The Update-3 to Meghdoot 7.0 consolidates following applications:
Installer Application
Point of Sale(including Despatch)
eMO
ePayment
pstman
MO Compilation
Accounts
AccountsPBS (Schedules)
Sub Accounts
Treasury
acountsMIS
R Net Communication (For Post Offices)
R Net Communication (For MBC/BPCs)
R Net (For RMS Offices)
Pincode
Page 2 of 28
September 15
2. Pre-Requisite
UPDATE-3 TO MEGHDOOT 7.0
The pre-requisite for Update-3 is Update-1 to Meghdoot version 7.0 released by CEPT on 05.12.2011,
which is available on ftp site at location
ftp://ftp.ptcinfo.org/Meghdoot7/Updates/
Installer Application
An Installer application is developed in order to automate the process of Up-gradation in Smaller Post
offices. The salient features of Installer application are:
It upgrades all the database scripts one by one
It copies the exe files and dll files to the respective application path
It registers the dll files with the system.
Procedure to use the Installer application:
It has to be copied to the machine along-with the update-3 folder.
The Checkbox "Server" has to be selected, if it is a server machine. In such a case, database
scripts will be executed one by one.
The application paths of all the Meghdoot modules installed in that machine have to be
provided.
Click on OK to start the up-gradation process. If any error occurs while execution, please send
the Log file created by the application to CEPT, Mysore and the procedure for manual up-
gradation as mentioned in Point-5 below may be followed.
As it is machine specific application, its use will be more in smaller Post Offices where all the
applications are operated in one or two systems. In bigger offices, where exclusive systems are
available for independent modules, the normal manual up-gradation process may be followed. The
process of automatic up-gradation of all the modules over the network will be released in the next
version of the Installer application.
Page 3 of 28
September 15 th , 2012
UPDATE-3 TO MEGHDOOT 7.0
4. General Instructions for Up-gradation
Ensure that Up-gradation is carried out after Day End in all modules.
Ensure that the office is upgraded with Update-1 to Meghdoot Version 7.0 dated 05.12.2011.
Ensure that backups of all databases and mdb files are taken and securely preserved.
Ensure 100% successful running of the database up-gradation. If any error occurs while
executing any exl file, please send the log file to CEPT Help Desk (
Support@ceptmysore.net
The up-gradation folder contains the following sub folders:
DatabaseScripts folder containing the exl files to be run to upgrade the databases •
Applications folder containing the executable file(s)/Dll files, which are to be copied to the
application folders by replacing the existing ones •
Support Folder containing Pincode application and other support documents.
Detailed Procedure for the following major modifications in this update, is furnished at the end
of this document. The same may be brought to the notice of all concerned officials
Offline Transmission of WNX Transactions as Annexure I
Collection of Online Examination Fee through ePayment system as Annexure II
eMO Issue/Paid returns (incorporated in MO Compilation module) as Annexure III
Please upgrade the applications in the following order:
eMO
emo
ePayment
ePayment Point of Sale
Point of Sale
Despatch
Dspatch
Sub Accounts
Sb Accounts
reasury
reasury
Postman
Postman
AccountsMIS
AccountsMIS
R Net Communication
R Ne
t Communication
MO Compilation
MO Compilation
Accounts
Accounts
AcountsPBS
AccountsPBS
Page 4 of 28
September 15
UPDATE-3 TO MEGHDOOT 7.0
5. Detailed Upgradation Procedure (Please follow the order mentioned below strictly)
eMO
eMO
top eMO and eMO Client applications.
Ensure that other emo related applications viz., Point of Sale, Postman etc; are not running.
Run emo_1.exl, eMO_2.exl, eMO_3.exl, eMO_4.exl, one by one, using Script Tool
Replace existing emo.exe and emoclient.exe available in respective installation paths
with the new versions provided
ePayment
Stop ePayment application.
Ensure that other ePayment related applications are not running.
Upgrade eCounter database by running eCounter_1.exl, eCounter_2.exl and eCounter_3.exl
using script tool.
Replace the existing ePaymentClient.exe with the new ePaymentClient.exe in ePayment
Client installation path.
Point of Sale and Despatch
Point of Sale and Despatch
Run the script Counter.exl and Counte_1.exl using Script Tool.
Replace the existing PointOfSale.exe with the new PointOfSale.exe in Point Of Sale Client
installation path. Replace the existing Despatch.exe with the new Despatch.exe in the installation path.
Copy the WNX.DLL to the Point Of Sale Client installation path and register the DLL.
Copy the ClientSoftware folder to the C drive of each client system and share the folder.
Copy the WNXMasterdata folder to the server.
Sub Accounts
Sub Accounts Run the script SUBACCOUNTS.exl using Script Tool.
Replace the existing SubAccounts.exe with the new SubAccounts.exe in SubAccounts Client
installation path.
Page 5 of 28 September 15
Treasury
Treasury
UPDATE-3 TO MEGHDOOT 7.0
Run the scripts Treasury_1.exl, Treasury_2.exl using Script Tool.
Replace the existing Treasurer.exe with the new Treasurer.exe in Treasurer Client
Postman
Postman
installation path.
Replace existing Postman.exe with new one.
Replace existing EMODelivery.dll with new one.
Replace existing EVPDelivery.dll with new one.
Register both EMODelivery.dll and EVPDelivery.dll
Run Postman.exl with script tool.
AccountsMIS Client (DET)
Replace existing Meghdoot Accounts MIS Client.exe with new one.
Replace the ServerObject.dll and AccountMISClient.dll with the new ones.
R Net Communication for Post Offices
Stop the R Net communication Client.
Ensure that the Counter and Postman database up-gradation is over successfully.
Take the backup of Old communication Client.
Replace the R Net communication exe with the new one.
Run the R Net communication exe.
If any error is reported, please send the mail to support@ceptmysore.net with error screen
shot and Log, TXD and RXD folders.
MO Compilation ( for Head Post Offices only)
MO Compilation ( for Head Post Offices only)
Replace existing MOCompilation.exe with newone.
Run MOCompilation.exl with script tool.
Login as MO Compilation Supervisor and go to My Office Environment menu option and
provide all required details and click on ‘OK’ button to save entries.
Page 6 of 28
UPDATE-3 TO MEGHDOOT 7.0
Accounts ( for Head Post Offices only)
Accounts ( for Head Post Offices only)
Copy AccountsFix folder to Desktop.
Run AccountsFix.exe available therein.
eplace the existing Accounts.exe with the new one
ountsPBS ( for Head Post Offices only)
AccountsPBS ( for Head Post Offices only)
the new Schedule.exe and replace the old exe with the new exe in the same location.
Run the Schedule.exl with script tool.
Run NICPLI.exl with script tool
6. New Features/Modifications done in this Update-3
Point of Sale
Option for booking WNX Transactions offline.
VP booking facility to Registered News Papers.
Option for uploading bulk Service eMOs.
ervice tax updation for Speed Post.
Service tax updation for NPS.
Validation for PLI and RPLI transactions.
Provision for acceptance of PLI and RPLI premium containing Paisa.
Rectified the error in PLI Transaction with Cheque.
Rectified the error in Statistical Report.
Provision for configuring the office as Mail Business Centre/Business Processing Centre.
Generation of Unique Receipt Number for Collection of Online Examination Fee.
From now onwards, all Registered Letter category articles have to be booked with Barcode
only .
Page 7 of 28
September 15
Despatch
Despatch
UDATE-3 TO MEGHDOOT 7.0
Closing of more than one bag to the same destination in same despatch.
Rectified the error while bulk uploading of Special Journal articles.
Rectified the error in Bundle Report & save to bundle option.
After preparing HVMO list, in order to include it in REGB bag please select "Include HVMO
List".
In Post Offices, provision made to close registered bags only to concern L1 or L2 offices.
In BPC/MBCs, provision made to close bags to any post office/L1 Office/L2 Office in the
country
Only one operator of despatch module can be able to despatch the bags whose configuration
need to be done in the following option.
Despatch -> Supervisor -> Master ->Bags Despatch User.
Provision made to despatch all the registered bags closed which is in the following option
Despatch -> Operator -> Prepare -> Despatch Bags.
Provision made to close more than one bag and bundle for same office and concern reports
has been changed.
Login info displaying in the menu item in order to identify who has been logged in.
Allowing only valid pin code in Redirected, Special Journal detailed booking and bulk
upload (text & excel).
Rectified the Collation error while preparing the HVMO List.
While preparing the bundle / bag, in the search option of article
a. Rectified the issue blinking against some other article in case of article not found.
b. Provision made to scroll the list automatically to the selected article.
Rectified the BPC abstract problem.
Rectified the binary truncation error while uploading the special journal articles through excel
file.
Page 8 of 28
eMO
UPDATE-3 TO MEGHDOOT 7.0
Flush data option provided for eMO Administrator for flushing of old Bulk payee data in
addition to flushing of Booking data to backup database so as to enhance the performance
of eMO module. The Procedure for flushing old data is:
Stop all the emo and emo realted applications.
•
Take the backup of the emo database
•
Login as Administrator. Only for first time you have to create backup database to flush old
emo data.
Give the cut off date since installation of emo 2008
Data may be moved for month by month, if data is more it should be done for day to day
basis (for some dates)
Once Data for 5-6 months is moved please shrink the database both emo and emobackup,
so that efficiency of shrinking will be more
eMO Client module will transmit eMO compilation data to central server
ePayment
Collection of Examination Fee through ePayment system has been introduced. The detailed
procedure for this scheme is furnished under Annexure II.
SP COD Biller creation : While creating the SPCOD biller in ePayment Website, please select
Biller Type as "SPCOD" and then put tick mark in the check box "Whether eVP/SPCOD Biller".
Sub Accounts
The following new Account Heads for SPCOD Delivery receipts and payments have been added
Account head Description Category ReceiptorPayment
spcodcollection SPCODCollection General Receipts
spcodfee SPCOD Fee General Receipts
spcodpayments SPCOD Payments General Payments
Provision made for upload of eMO related files received along with Daily Accounts.
Separate classification of amounts related to IEMO Paid in Summaries/Cash Account etc.,
Fixed the problem related to SQL 2005 – "Transaction context in use by another session"
Page 9 of 28
September 15
Treasury
UPDATE-3 TO MEGHDOOT 7.0
Provision for payment of SPCOD Collections to the SPCOD Billers through the Option Treasurer
–Payments—SPCOD Payments.
Report of SPCOD Payments made to the SPCOD Billers is provided through the Option
Treasurer – Reports –SPCOD Payment.
Classification of amounts of SPCOD collection after payment under ‘SPCOD Payments’,
‘SPCOD Fee’, Taxes etc., in Summaries/Daily Account as like ‘EBill Payments’,
‘EBillCommission’ .
Separate classification of ‘SPCODCollection’ made through Postman towards delivery of
SPCOD articles at the Delivery Office in Summaries/Daily Account.
Generation of Text file for EMO issue along with Other Daily Account files at Sub Office for the
purpose of eMO Compilation at Head Office.
Generation of Text file for EMO Paid along with Other Daily Account files at Sub Office for the
purpose of eMO Compilation at Head Office.
Separate classification of Foreign MOs Paid (IFS) through Postman under the Head of Account
‘IEMOPaid’ in Summaries/ Daily Account.
Provision for capturing the details of MTCN Number, Name of the Payee while making
payments towards ‘WUMTS’ through the Option Treasurer—Payments--Other payments for
transfer of WU Transactions Data through Accounts MIS for reconciliation/pairing work.
Pensioner’s Name column added in the ‘Pensions Paid’ Report at Sub Offices in Treasury.
Provision for Handling the NPS invalid transactions for Refund to the subscribers at Mysore
HO. (Released and deployed at Mysore HO with Update 2 for Meghdoot 7.0)
Page 10 of 28
Postman
UPDATE-3 TO MEGHDOOT 7.0
Delivery of Speed Post COD (SP COD) articles through Postman module. Please go through
complete SOP released by Directorate on SP COD scheme.
Provision for Receipt of Bag
Generation of Bag Receipt and Bag Opening message
Generating the messages for eVPP articles for the purpose of RNet tracking
Accounts
Option provided for dumping monthly data for calculation of Income tax.
Calculation of Income Tax as per new rates.
GDS details such as Date of Joining, Date of Birth and PRAN Number are being captured for
the purpose of detailed reports.
Error of Incorrect balance and Installment in GPF sanction has been solved.
AccountsPBS
PLI-RPLI cursor problem while generation of CSV file rectified
Data entry/fetching/Preparation of schedules for Ebillers which are inactivated in ECOUNTER
has been rectified. (Earlier unable to prepare the schedule for inactivated Ebillers)
EB commn digit problem rectified (fractions allowed in commn )
EMO issue over flow error rectified
EMO paid over flow error rectified
In PLI RPLI Policy Numbers, slashes or hyphens is not allowed continuously. For eg -- or // are
not allowed.
Under Modification of policy numbers in PLI / RPLI Premium -Operators are allowed to
Modify the Policy numbers (earlier only selection was allowed.)
Page 11 of 28
UPDATE-3 TO MEGHDOOT 7.0
Search option is provided in Modify option of PLI/RPLI policy numbers. The operator can type
one or two digits of policy numbers and click on search and select the Number if already
exists.
Problem in net amount, renewal amount, first year premium is corrected in view option..
Policy Premium amounts in fraction are accepted e.g. 48.50 is accepted as premium
AccountsMIS (DET)
Identification of Fake Reporting offices at CEPT Central Server.
Generation of new file for the Western Union Money Transactions happened in the Project
Arrow office.
Transmission of Western Union Money Transactions file to CEPT Central Server
RNet Communication
Transmission of WNX articles booked through Point of Sale to WNX Server.
BPC/MBC selection option.
Rectified ‘trxcheck.log’ problem.
Blocking frequent requests from R Net communication to central server. Therefore, a
minimum of half an hour time lap should be there between two successive requests to Central
Server. However, this will not apply for transmission of transactional data to/from central
server.
MO Compilation
eMO Compilation (Issue and Paid returns) facility has been incorporated in MO Compilation
module from this version onwards. Therefore, the modifications done to incorporate eMO
returns are explained in detailed below
Page 12 of 28
September 15
PDATE-3 TO MEGHDOOT 7.0
•
Only offices identified as WNX Booking Centres need to follow the following procedure.
•
AirwayBill configuration and Piece Id Configuration need to be done as per the series
allotted to each office by WNX.
Hither to the WNX transactions are being booked and transmitted online, by connecting to WNX
server for each activity. As this process is taking too much time for booking of each WNX
Transaction, the process of booking has been made offline.
Now onwards, booking of WNX transactions will happen in locally like any other counter
transaction and the booked data will be transmitted Communication to WNX server. For
initializing the new process, please follow the below procedure:
Select the option ‘WNX Configuration’ through Supervisor--> Configure option and click
on ‘Update Service’.(This can be done from the Server machine)
After clicking on Update service, Select the browse button and browse to the
WNXMasterData folder.
A message "WNXMaster updation is in progress…" will appear. Click on OK button and
wait for the completion of master data updation.
Airway bill configuration need to be done through Supervisor --> Configure --> WNX
Configuration --> AirwayBill
Configuration need to be done with the Airway bill series and Piece Id Series applicable
to each office. These details will be supplied by WNX.
Select the option 'World Net Express' through Operator --> ForeignMail --> Airmail for doing
WNX Transactions.
Rest of the procedure remains unchanged.
UPDATE-3 TO MEGHDOOT 7.0
ection of Examination Fee through ePayment System
The biller should be created in e-Payment web site by selecting the Biller Type as
'EXAMINATION FEE'.
Unique receipt number of 14 digits will be generated through Point of Sale module.
No transaction cancellation facility in Point of sale.
The transaction data will be transmitted to e-Payment central server during the next call of e-
Payment Client for downloading to the biller. (Without waiting for Point of sale Submit account
and Supervisor verification).
Biller download format should be configured in e-Payment web site for required periodicity.
Transaction data will be downloaded to biller periodically containing the unique receipt number.
Full transaction data will be transmitted to e-Payment server only after submit account and
supervisor verification as per ePayment system and sent for payment to office of payment.
Page 14 of 28tember 15
UPDATE-3 TO MEGHDOOT 7.0
Procedure for using eMO options in in MO Comilation
The new features include:
1.
Background
2.
Fetch Local eMO Data
3.
eMO Issue Data – HO
4.
eMO Paid Data – HO
5.
eMO Tally with HO Summary
6.
Error Report - eMO Tally with HO Summary
7.
Fetch SO eMO Data
8.
eMO Issue Data –SO
9.
eMO Paid Data – SO
10.
eMO Tally with SO Summary
11.
Error Report - eMO Tally with SO Summary
12.
eMO Issue Returns
13.
eMO Paid Returns
Each feature given above is explained in detail in the document.
TO MEGHDOOT 7.0
New background of MO Compilation application is as follows.
2.
Fetch Local eMO Data
UPDATE-3 TO MEGHDOOT 7.0
This option can be used to fetch local emo issue and paid details to MO Compilation application based
on the date range provided and options selected.
Page 17 of 28
3.
eMO Issue Data - HO
UPDATE-3 TO MEGHDOOT 7.0
Instead of fetching data, there is provision to enter eMO issue details of the local office. Operator has to
select HO Date and enter eMO value, commission, total number of eMOs, first PNR number and last PNR
number of the day. In case any eMOs were cancelled on the day, that entry also should be made after
checking "Error Entry" option.
In addition to data entry, provision has been provided for viewing, modifying and deleting the data.
The screenshot is given below.
September 15
4.
eMO Paid Data - HO
UPDATE-3 TO MEGHDOOT 7.0
There is option to enter details of eMO paid in the local office. Select HO date and enter total value of
eMOs paid and number of eMOs paid on the date. In case any error entry is there, it can be entered in
the space provided.
There is provision to view, modify and delete paid details also. Please see below given screenshot.
5.
eMO Tally with HO Summary
UPDATE-3 TO MEGHDOOT 7.0
One new feature in MO Compilation is tallying eMO data with HO summary. The eMO issue and paid
details of local office should be tallied with HO Summary. Tallying should be done for each HO date for
which data is entered before taking returns report.
UPDATE-3 TO MEGHDOOT 7.0
6.
Error Report – eMO Tally with HO Summary
In case any difference between the data entered in MO Compilation and that in HO Summary, an error
report will get displayed. Screenshot of one sample report is given below. of 28
September 15
7.
Fetch eMO SO Data
th
, 2012
UPDATE-3 TO MEGHDOOT 7.0
This feature helps to fetch eMO issue and paid details of attached Sub Offices. Operator has to select Ho
Date, SO name, date range and options. The emo issue or paid details of selected SO for given date
range will be fetched and entered to MO compilation application with selected HO date.
Page 22 of 28
September 15
th
8.
eMO Issue Data – SO
, 2012
UPDATE-3 TO MEGHDOOT 7.0
There is data entry option to enter emo issue details of an attached sub office. Operator has to select
HO date, SO name, SO date and has to enter total eMO value, commission, total number of eMOs, first
and last PNR numbers of the day.
There is provision to view, modify and delete the data entered.
Please see below screenshot. Yesterday’s last PNR number is shown as "0" because no data was entered
for an earlier date.
Page 23 of 28
September 15
9.
eMO Paid Data - SO
th
, 2012
UPDATE-3 TO MEGHDOOT 7.0
This option helps to do data entry of eMO paid details of an attached sub office. There are options to
view, modify and delete paid details. Please see below screenshot.
Page 24 of 28
September 15
th
, 2012
10.
eMO Tally with SO Summary
UPDATE-3 TO MEGHDOOT 7.0
eMO issue and paid details of attached Sub offices should be tallied with SO summary data.
UPDATE-3 TO MEGHDOOT 7.0
11.
Error Report – eMO Tally with SO Summary
In case eMO issue or paid data entered for sub offices does not tally with data in SO summary, an error
report will be displayed as below.
12.
eMO Issue Returns
UPDATE-3 TO MEGHDOOT 7.0
The eMO issue returns reports can be generated for first or second period of a month. The report can of
two types: Date wise returns and Office wise returns
Date wise returns will fetch data based on date and Office wise report fetch data based on the offices
under the HO. Please see screenshots below.
MO Paid Returns
UPDATE-3 TO MEGHDOOT 7.0
Similar to eMO issue returns report, paid reports also can be generated for first or second period of a
month. The report can of two types: Date wise returns and Office wise returns.
Date wise returns will fetch data based on date and Office wise report fetch data based on the offices
under the HO. Please see below screenshots.
Page 28 of 28
Module wise major modifications
| Module | Changes made to the Software | Improvement in Operations/Service |
| Point of Sale | Booking of Offline WNX Transactions | Hitherto, WNX server needs to be connected for every event of booking process. This offline booking reduces the transaction time at counter considerably. |
| VP booking facility for the Registered Newspaper | Booking of Registered Newspaper with VP facility is introduced, which was not available earlier. | |
| PLI/RPLI validations prescribed by PLI Directorate, at the time of booking | Due to these validations, data mis-match between the NIC PLI data file and Meghdoot can be reduced considerably. | |
| Despatch | Closing of more than one bag to the same destination in same despatch | Till now, only one bag can be closed in Despatch module to a particular destination Post Office in a single despatch. This is relaxed. |
Implementation of MNOP concept for the Rigistered Bags | Post Offices can close bags only to the L1/L2 Mail Offices, as per the MNOP concept. | |
| Postman | All Delivery related options for Speed Post Cash on Delivery articles. The product is yet to be launched. | Facilitates delivery/despatch of SPCOD articles through Post office and its attached BOs. |
Bag Receipt and Bag Opening Options for Registered Bags | Facilitates capturing the Bag receipt and Bag opening scan as required for MNOP review on RNet | |
Transmission of data of eVP articles to RNet server | Facilitates complete tracking of eVP articles through RNet website. | |
| MO Compilation | eMO Compilation options provided | eMO Compilation options introduced with this release automates the process of submitting Issue/paid returns to DA(P). |
| eMO | Flushing of old Bulk payee data in addition to flushing of Booking data to backup database | This enhances the performance of eMO module operation especially in bigger offices where Bulk Booking and Bulk Delivery is happening. It is ensured that even after flushing the old data, the reports for the older dates can be seen as usual. |
Capturing the data of eMO Compilation and transmission to Central Server | Facilitates cross checking of eMO compilation figures received from Head Offices | |
| ePayemnt | Collection of Examination Fee | New service for Collection of online Examination Fee introduced |
Speed Post Cash on Delivery data transmission. articles. The product is yet to be launched. | Transmission SPCOD articles data from the Office of Delivery to Office of payment for effecting payment through Treasury. | |
| Treasury | Capturing the Western Union Transaction Data | Provision to feed data of individual WUIMT transactions, so as to transmit the data through AccountsMIS application for consolidated figures at central server |
Provision for Speed Post Cash on Delivery Payment . . The product is yet to be launched. | Facilitates payment of SPCOD delivered amount | |
| Accounts | Calculation of Income Tax as per new rates | |
| Schedules | PLI/RPLI validations prescribed by PLI Directorate, at the time of data entry by Schedules Clerk. | Due to these validations, data mis-match between the NIC PLI data file and Meghdoot can be reduced considerably. |
| AccountsMIS (DET) | Identification of offices doing fake reporting . | Post Offices cannot resort to transmit duplicate DET data. |
| Capturing the Western Union Money Order Transactions | Creation of a separate file with individual transactions of WUMT transactions and transmission of the same to Central Server for centralized pairing. | |
| Installer Application | New Application to upgrade all the modules of Update-3 | Automates the up-gradation process of all the applications in a particular system |
Subscribe to:
Posts (Atom)