or book the local articles without pincode and fetch the data
Friday, October 30, 2009
Thursday, October 29, 2009
New Exe of Postman Module dated 24-10-09
Download new Postman updates dated 31-10-2009
1) Restriction of addresses to a single beat in Pre-sorting of RL/MO/Parcels. Now all the addresses under the delivery jurisdiction of the office will be displayed
2) Error that ‘Cash is not yet issued to postman’ coming at the time of taking eMO Returns
3) Number of Speed Post articles received (being fetched through DET) is coming wrongly
4) Automation error coming in emoàreturnsàView/modify option is rectified
5) Automatic selection of emos with up/down arrow keys
6) Returned to Sender option in Window Deposit
7) If Meghdoot server and Speednet Server are not in the same network, please check up the guidelines mentioned in page-2, so that the speednet data can also be fetched smoothly through DET
1) Restriction of addresses to a single beat in Pre-sorting of RL/MO/Parcels. Now all the addresses under the delivery jurisdiction of the office will be displayed
2) Error that ‘Cash is not yet issued to postman’ coming at the time of taking eMO Returns
3) Number of Speed Post articles received (being fetched through DET) is coming wrongly
4) Automation error coming in emoàreturnsàView/modify option is rectified
5) Automatic selection of emos with up/down arrow keys
6) Returned to Sender option in Window Deposit
7) If Meghdoot server and Speednet Server are not in the same network, please check up the guidelines mentioned in page-2, so that the speednet data can also be fetched smoothly through DET
Tuesday, October 27, 2009
Friday, October 23, 2009
Account MIS
AccontMIS data Transfer & Dayend Sequence
1. SpeedNet
2. Postman
3. Pointofsale
4. Subaccounts
5. Treasury
6 SanchayPost DayEnd & Execute ( Sanchaypost Project Arrow Report : trans_time.exe available in C:\SP5\PA folder )
Then AccountMIS data Trasfer
1. SpeedNet
2. Postman
3. Pointofsale
4. Subaccounts
5. Treasury
6 SanchayPost DayEnd & Execute ( Sanchaypost Project Arrow Report : trans_time.exe available in C:\SP5\PA folder )
Then AccountMIS data Trasfer
Wednesday, October 21, 2009
Problem in accounts mis regarding signature scanning figures
please use "Transaction Time report" which should be installed from Sanchay Post 6.5 version and use for Sanchay Post Data generation which is generated only after Day end
use the trans_time.exe available in C:\SP5\PA folderIt will used to update SB Branch KPIs. ( The old one available in C:\SP5Comm\)
If not available install from Meghdoot 6.6 - AccountMIS folder
use the trans_time.exe available in C:\SP5\PA folderIt will used to update SB Branch KPIs. ( The old one available in C:\SP5Comm\)
If not available install from Meghdoot 6.6 - AccountMIS folder
Monday, October 19, 2009
eMO communication Problem
eMO communication problem Download Patch Dated 16-10-2009
Problem and Solution Download
SpeedNet Communication Problem
1.
Open the hosts file (c:\windows\system32\drivers\etc) and check for entry Speednetmsg.ptcmysore.gov.in
if entry exists delete that and add entry 218.248.43.148 speednetmsg.ptcmysore.gov.in
2.download file ModifySpeednetURL from http://www.sendspace.com/file/6lflv6 . Please execute it on the machine where communication is installed after adding .exe extention to the file name.
Right click on file and click on run as administrator
Friday, October 16, 2009
Wednesday, October 7, 2009
Detail procedure for updating old eMO which are already paid but not updated
Disaster Recovery – Request for Data:
This option is used for getting the pending unpaid eMOs. Once request is processed the pending unpaid eMOs will be send to the client
Select transaction ->Disaster Recovery -> Request for Data (eMO supervisor.)
o Select office for which the request should be given.
o Enter the remarks click on OK.
Disaster Recovery – eMOs Paid entry:
This option should be used only for entering the payment details for eMOs which are paid already but not updated in the server.
Select Data Entry-> Disaster Recovery -> eMO Paid entry. (eMO Operator)
o Select Office name.
o Select PNR Numbers from the list.
o Enter Head Office Account Date.
o Enter eMO payment date and SO Account date.
o Click on OK.
o (Note: SO paid information will be transmitted to central server once the paid details are tallied with accounted figures by the supervisor.)
o View and delete option is also available for making any changes office wise.
Disaster Recovery – Paid Verification:
This option is used for verifying the disaster paid details and tallying with accounted figures.
Select transaction ->Disaster Recovery -> Paid Verification.
o Select Head Office Account Date and click on fetch.
o eMO figures and accounted figures will be displayed for all the offices.
o Select the office for which eMO figures and Account figures are tallied and click on verified button.
o If any discrepancy is noticed please enter the reason for the discrepancy in amount.
o Paid details will be verified on clicking on verify button.
Disaster Recovery – Redirection:
This option is used for redirecting eMOs received through Disaster Recovery option .
Select transaction ->Disaster Recovery -> eMO Redirection
o Select Office Name for which the Redirection should be done.
o The list of eMOs pending for that office will be displayed .
o Select the PNRnumber. Then select the reason.
o Enter the address to which it is redirected.
o Click on OK.
Disaster Recovery – eMOs not to be Paid:
This option is used to eliminate the eMOs which are already paid or redirected but received again for payment.
Select transaction ->Disaster Recovery -> eMOs not to be paid
o This option will give the list of eMOs which are neither paid nor redirected.
o If any of the eMOs is already received from other office, paid manually or redirected but not properly updated, you can update that eMOs as not to be paid with suitable remarks.
o Select PNRNumber.
o Enter Remarks.
o Click on OK
.o The eMOs which are entered as not be paid will not be available for invoicing in the Postman module or Redirection option in eMO.
CC Bridge Version 4.0
This version has the new option to
1. Import SO Discharge data from Sanchay Post database (Version 6.5)
2. Enter date of accounting while importing SO data for a single date
CC Bridge Version 4.0 Download
This option is used for getting the pending unpaid eMOs. Once request is processed the pending unpaid eMOs will be send to the client
Select transaction ->Disaster Recovery -> Request for Data (eMO supervisor.)
o Select office for which the request should be given.
o Enter the remarks click on OK.
Disaster Recovery – eMOs Paid entry:
This option should be used only for entering the payment details for eMOs which are paid already but not updated in the server.
Select Data Entry-> Disaster Recovery -> eMO Paid entry. (eMO Operator)
o Select Office name.
o Select PNR Numbers from the list.
o Enter Head Office Account Date.
o Enter eMO payment date and SO Account date.
o Click on OK.
o (Note: SO paid information will be transmitted to central server once the paid details are tallied with accounted figures by the supervisor.)
o View and delete option is also available for making any changes office wise.
Disaster Recovery – Paid Verification:
This option is used for verifying the disaster paid details and tallying with accounted figures.
Select transaction ->Disaster Recovery -> Paid Verification.
o Select Head Office Account Date and click on fetch.
o eMO figures and accounted figures will be displayed for all the offices.
o Select the office for which eMO figures and Account figures are tallied and click on verified button.
o If any discrepancy is noticed please enter the reason for the discrepancy in amount.
o Paid details will be verified on clicking on verify button.
Disaster Recovery – Redirection:
This option is used for redirecting eMOs received through Disaster Recovery option .
Select transaction ->Disaster Recovery -> eMO Redirection
o Select Office Name for which the Redirection should be done.
o The list of eMOs pending for that office will be displayed .
o Select the PNRnumber. Then select the reason.
o Enter the address to which it is redirected.
o Click on OK.
Disaster Recovery – eMOs not to be Paid:
This option is used to eliminate the eMOs which are already paid or redirected but received again for payment.
Select transaction ->Disaster Recovery -> eMOs not to be paid
o This option will give the list of eMOs which are neither paid nor redirected.
o If any of the eMOs is already received from other office, paid manually or redirected but not properly updated, you can update that eMOs as not to be paid with suitable remarks.
o Select PNRNumber.
o Enter Remarks.
o Click on OK
.o The eMOs which are entered as not be paid will not be available for invoicing in the Postman module or Redirection option in eMO.
CC Bridge Version 4.0
This version has the new option to
1. Import SO Discharge data from Sanchay Post database (Version 6.5)
2. Enter date of accounting while importing SO data for a single date
CC Bridge Version 4.0 Download
UPGRADATION TO MEGHDOOT VERSION 6.6 / PROJECT ARROW OFFICES
UPGRADATION TO MEGHDOOT VERSION 6.6 / PROJECT ARROW OFFICESWhile running Accounts MIS client, error message displayed as “Unable to continue due to the following error: There is a problem with SQL server. Login failed for user 'arrow'.”If Accounts MIS application was being used in Meghdoot Version 6.5 earlier and you have upgraded to Meghdoot Version 6.6, contact PTC Mysore for solution.If Accounts MIS application is installed afresh and the above mentioned error occurs, following are the possible actions:
a) If Sanchay Post Version 6.0 or earlier version is used, upgrade to Version 6.5 immediately.
b) If you are already using Sanchay Post Version 6.5, use DBAnalyzer to check whether you have upgraded to Version 6.5 successfully. While checking, if DBAnalyzer displays error code 1: Z, run 'ARROW.EXE' to create the Project database & login.
c) If you have shifted operations to a new server after upgradation to Sanchay Post Version 6.5, run 'ARROW.EXE' to create the Project database & login and then restore the Project database's backup, if available. Not restoring your backup of Project database or removal of the existing Project database and recreating it using 'ARROW.EXE' will result in loss of previous transaction data.INSTRUCTIONS FOR USING ARROW.EXE
2. Unzip the downloaded file, copy it to the DBAnalyzer folder and run the exe file.
3. Use latest DBAnalyzer >> 'Check databases' >> Version 6.5 and verify if
Tuesday, October 6, 2009
Monday, October 5, 2009
Saturday, October 3, 2009
Thursday, October 1, 2009
FTP Configuration ( S.O to H.O Data Transfer)
FTP SERVER CONFIGURATION
Ø Computer connect with existing server (through LAN cable)
Ø O.S. Windows 2000 Server with IE 6 & SP4 or Windows 2003
Ø Internal (or) external Dialup modem (both end HO and SO)
Ø Parallel phone connection from existing phone (both end HO and SO)
AT HO
:1. Install windows 2000 server and 2003 server and create active directory. Give server name and domain like XXXftpserver, XXXftpdomain. Give ip number (give running number in your HO domain and not to give your existing HO server IP number)
2. Install modem driver and check diagnostics.
3. Go to control panel add and remove programs windows components wizard IIS enable all services (ftp transfer protocol ftp service)
4.
a. Start -+ Program – Admin Tools – Internet Service Manager
b. Click Domain Name – It Shows Server Name
c. Right click the server name – select ‘new’ – select ‘ftp site’ – give name – give IP address (your computer).
d. Give TCP Port – 21 (always)
e. Give path – D:\SBFTP\Received (Create directory)
f. Give permission – read and write – click finish.(By default created ftp site will be stopped)
g. Right click newly created FTP site – property – check IP address and TCP port and give connections ‘unlimited’
5. a. Select admin tools – routers and remote access
b. Right click server name – configure routing and remote services – click manual selection.
c. Select server name – ports – right click – select property – click selected modem – configure – make tick in ‘inbound only and inbound and out bound’.
d. Give phone number of this server
6. a. Select admin tools – select active directory users and computers.
b. Create a new user (like XXXftp, YYYftp…) and give the password same in user name.
c. Right click created new user – select ‘dialin’ tab – make tick in ‘allow access’ – select ‘member of’ tab – make the user in domain user and give administrator rights to that user.
d. Create a network user as available in existing server and give Administratory rights (this domain) to that user.
7. Check the IIS and RRAS running correctly.
8. a. Install MSSQL 2000 client connectivity only (not to install full setup)
b. Click client connectivity – give the server name (existing old server name) alias
9. Install Bridge and Plugin. ( or Copy SB Plugis 2.5.3 Version )
AT SOS :
1. Install modem and create a dialup connection with username, password, and phone number created at HO level same as HO.
2. Install bridge and Plugin ( or Copy SB Plugis 2.5.3 Version ) and configure the FTP.
(Please delete old ‘PATCH’ database and create new thro ‘SB Plugin’ software)
Ø Computer connect with existing server (through LAN cable)
Ø O.S. Windows 2000 Server with IE 6 & SP4 or Windows 2003
Ø Internal (or) external Dialup modem (both end HO and SO)
Ø Parallel phone connection from existing phone (both end HO and SO)
AT HO
:1. Install windows 2000 server and 2003 server and create active directory. Give server name and domain like XXXftpserver, XXXftpdomain. Give ip number (give running number in your HO domain and not to give your existing HO server IP number)
2. Install modem driver and check diagnostics.
3. Go to control panel add and remove programs windows components wizard IIS enable all services (ftp transfer protocol ftp service)
4.
a. Start -+ Program – Admin Tools – Internet Service Manager
b. Click Domain Name – It Shows Server Name
c. Right click the server name – select ‘new’ – select ‘ftp site’ – give name – give IP address (your computer).
d. Give TCP Port – 21 (always)
e. Give path – D:\SBFTP\Received (Create directory)
f. Give permission – read and write – click finish.(By default created ftp site will be stopped)
g. Right click newly created FTP site – property – check IP address and TCP port and give connections ‘unlimited’
5. a. Select admin tools – routers and remote access
b. Right click server name – configure routing and remote services – click manual selection.
c. Select server name – ports – right click – select property – click selected modem – configure – make tick in ‘inbound only and inbound and out bound’.
d. Give phone number of this server
6. a. Select admin tools – select active directory users and computers.
b. Create a new user (like XXXftp, YYYftp…) and give the password same in user name.
c. Right click created new user – select ‘dialin’ tab – make tick in ‘allow access’ – select ‘member of’ tab – make the user in domain user and give administrator rights to that user.
d. Create a network user as available in existing server and give Administratory rights (this domain) to that user.
7. Check the IIS and RRAS running correctly.
8. a. Install MSSQL 2000 client connectivity only (not to install full setup)
b. Click client connectivity – give the server name (existing old server name) alias
9. Install Bridge and Plugin. ( or Copy SB Plugis 2.5.3 Version )
AT SOS :
1. Install modem and create a dialup connection with username, password, and phone number created at HO level same as HO.
2. Install bridge and Plugin ( or Copy SB Plugis 2.5.3 Version ) and configure the FTP.
(Please delete old ‘PATCH’ database and create new thro ‘SB Plugin’ software)
Sanchay Post >> S.O to H.O Data Transfer
How to reset the sequence number to 1 at SO?
Use the option ‘DBAnalyzer >> DBUtilities >> 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 >> DBUtilities >> 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 data transfer 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 HOHO 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 retryLogout and login to SOSB module and retryAsk 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).
Subscribe to:
Posts (Atom)