eMO Updates 161010

Some additional reports has been given which may facilitate to reduce the - Pending Not Paid EMOs.

Please do the following
1. Download the emoupdate.zip file
2. Extract the contents. There will be following files eMO,

emo15102010.exl , emooffices29092010.exl, emoPincodes29092010.exl and a Readme.txt file

3. if you have not upgraded the emodatabase with Meghdoot 6.6 sp1 released during April /May 2010, please upgrade with Meghdoot 6.6 SP1. Without upgradation, if this update is applied it may cause some errors in the new reports.
4. Take a backup of emo database and existing emo.exe and place in safe location.
5. If steps 2 and 3 are statisfied, proceed with instructions in Readme.txt
6. Anyissues /errors during upgradation please mail to ptcdesk@gmail.com. 
Download 

How to add BO in SPCC Office updation

FIRST YOU HAVE TO ADD THE BOS AS THE LINKED OFFICES. FOR THAT GO TO THE FOLLOWING . YOU HAVE TO LOGIN WITH USER NAME & PASSWORD FOR YOUR SPC.A SITE WITH A BANNER AS SPEED NET OFFICE UPDATION WILL BE OPENED.THERE GO IN THE FOLLOWING MANNER , ADD ADDITIONAL OFFICES . FILL UP THE OFFICE DETAILS SUCH AS BO'S NAME ITS PINCODE , IMPORTANT YOU HAVE TO GIVE OPTION NO FOR THE IS DELIVERY OFFICE : NO. AND THEN CLICK SEND . SAME WAY UPDATE ALL THE BOS . THEN GO TO DOWNLOADS . IN THAT Download ALL data CircleWise -> SELECT YOUR CIRCLE (TAMILNADU). AND THEN CLICK DOWNLOAD . A TEXT FILE WHICH CONTAINS THE FILE NAME AS SPCC------(your spc pincode) WILL BE DOWNLOADED.THEN GO TO SPEED NET COMMUNICATION , GO TO TOOLS -> UPDATE OFFICE DATA FROM SERVER BROWSE THE FILE DOWNLOADED AND THEN CLICK UPDATE NOW. A MESSAGE WILL APPEAR AS " YOUR OFFICE DATA HAS BEEN SUCCESSFULLY UPDATED MESSAGE WILL APPEAR. NOW GO TO SPEED NET APPLICATION . GO TO DELIVER -> INVOICING -> ARTILE FOR OTHER OFFICES . THERE YOU CAN FIND THE BO NAME IN THE TAB OFFICES. INVOICE THE ARTICLE FOR THAT BO AND AFTER DELIVERY REMARKS COMES UPDATE THE SAME THROUGH REMARKS FROM OTHER OFFICES -> SPEED POST. CALL THE SPEED NET COMMUNICATION. THATS ALL .

Accounts Update

Accounts Update 28/07/2010 For Increment & Pay Drawl Problems
Download

While doing submit accounts ‘Server not configured for RPC’

Solution: Run the following query using query analyzer (replace ‘myserver’ with your server name):
exec sp_serveroption @server='myserver', @optname='rpc', @optvalue='true'
go
exec sp_serveroption @server='myserver', @optname='rpc out', @optvalue='true'
go
Note: The above error is related to SQL Server configuration settings and not related to the application. (RPC is Remote Procedure Call).

Daily Accounts Head Problem

execute the attached script using script tool.
if the accountheads are required for the current date execute the following:
use treasury
go
update_megh66_accountheads

if the accountheads are required for a particular date:
use treasury
go
update_megh66_accountheads_bydate 'ddmmyy'
in this ddmmyy explanation is as follows:
if the date is 16/04/2010 then it will be equal dd/mm/yyyy so the ddmmyy will be 160410. This can be applied to any date on the same analogy.Download

Point of Sale Submit Account Problem after SP1

The Error in POS Submit Account-
Run time error '3704' operation is not allowed when the object is closed
Run time error '440' Automation error OK
counter13042010.exl

Invalid Column Name pliotl in SOSummaryb030510 - Temporary Solution

Change the Column name / Date and Run this Query

USE BOSUBACCOUNTS
ALTER TABLE Sosummaryb030510 ADD pliotl Numeric(15,2) NULL

UPDATE  Sosummaryb030510
set pliotl =0

Day End Problem

Temporary Solution
Download

Sub Accounts Missing Head 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 '010510'

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

DET figure mismatch

Problem in fetching column no.7 and 51of data extraction toolPostman220410.exl

Point of Sale SP2

The following modification are done in the service pack 2 for PointOfSale6.6 attached herewith.

1.Rectified the error in RPLI receipt printing.
2.Rectified the error in submit account related to MTNL transactions.
3.Rectified the error in submit account related to EPP transactions.
4.FCCode and Register number are made mandatory for NPS transactions.
5.Validations for NPS transactions according to the selection of service type.
Download Here

POS Solution

Point of Sale DayEnd Problem
Download

Local Article DET Problem

If you are having any grievance regarding local articles, then pls run run the enclosed script using the script tool.This postman15042010.exl will eliminate the condition that you should use only one of the two options i.e.,either  fetch from counter option or take receipt using bag details. 

 

Hence after running this exl, you should take receipt of all the local articles using the Bag Details option on the next date.  The DET will not take the receipt of the articles fetched using the fetch from counter option.

Hence pls note that all the local articles should be taken receipt by using the Bag Details option hereafter.
Postman150410 patch Download the Postman150410.exe from here

FAQ Meghdoot 6.6.1 (Service Pack-1)

Point of Sale

1.      RPLI transactions cannot be booked.

Solution: Do not enter Date Of Acceptance and Agent Code while doing RPLI transactions till a new service pack is supplied.

2.      Stored procedure missing error while doing submit account.

Solution: EMO database upgradation should be done before Counter upgradation. You should do emo database upgradation and then do the counter database upgradation.

3.      The following error log after counter database upgradation.

1. COUNTER

22:36:28:============================================

22:36:28:         SCRIPT EXECUTION DETAILS (counter)

22:36:28:============================================

22:36:29:[Column names in each table must be unique. Column name 'AgentCode' in table 'PostalLifeInsurance' is specified more than once.] : Script Execution Error : While executing statement ALTER TABLE PostalLifeInsurance ADD AgentCode nvarchar(15) NULL

22:36:29:[Column names in each table must be unique. Column name 'FirstYearPremium' in table 'PostalLifeInsurance' is specified more than once.] : Script Execution Error : While executing statement ALTER TABLE PostalLifeInsurance ADD FirstYearPremium money NULL

22:36:29:[Column names in each table must be unique. Column name 'DateOfAcceptance' in table 'PostalLifeInsurance' is specified more than once.] : Script Execution Error : While executing statement ALTER TABLE PostalLifeInsurance ADD DateOfAcceptance datetime

Solution: These error messages will come if counter database is upgraded twice. These error messages  can be ignored.

4.      Active X component cannot create object.

Solution: Reinstall the application after deleting the old installation cab files. If you are getting any error while registering the dlls then do the following

Register the dll by entering the following in the Run dialog box window.(Start - Run)

Regsvr32 ApplicationPath\dllname

eg.Regsvr32 H:\POS\cash.dll

5.      While doing submit accounts ‘Server not configured for RPC’

Solution: Run the following query using query analyzer

exec sp_serveroption @server='myserver', @optname='rpc', @optvalue='true'

go

exec sp_serveroption @server='myserver', @optname='rpc out', @optvalue='true'

go

in the myserver replace the myserver with your servername.. It will solve the RPC problem

6.      While doing submit accounts error ‘Operation is not allowed when the object is closed’

Solution : Run Counter13042010.exl using script tool.

7.      While booking MO Videsh, Countries and currencies are not coming

Solution :  If countries, currencies are not coming in Movidesh booking then patch is available in ftp site...

ftp://ftp.ptcinfo.org/ForSKRegionAndCoimbatoreRegionProjectArrowTesting/MOVidesh/EuroGiroTest.rar

8.      While performing Day End, Multiple step operation generated errors. Check each status value

Solution: Please download the zip file from http://www.sendspace.com/file/r7xz78. Unzip it and follow the instruction given in readme.

9.      Invalid object name 'ECounter..ENVIRONMENT'.

Solution : Upgrade eCounter database

TREASURY

1.      In treasury module while entry in postman returns error shown ‘POSTMAN DATA BASE IS NOT AVAILBLE QUITTING’

Solution:  Run the following query using query analyzer

exec sp_serveroption @server='myserver', @optname='rpc', @optvalue='true'

go

exec sp_serveroption @server='myserver', @optname='rpc out', @optvalue='true'

go

in the myserver replace the myserver with your servername.. It will solve the RPC problem

2.      Accounts Heads not coming

Solution: Please run treasury1.exl using script tool.

After executing the script, run query analyzer and execute the following query selecting treasury database.

update_megh66_accountheads_bydate 'ddmmyy'

ddmmyy stands for the date on which account heads not appeared. ex: if the date is 06/04/2010 then ddmmyy will be 060410

DESPATCH

1.      While performing Day End, Multiple step operation generated errors. Check each status value

Solution: Please download the zip file from http://www.sendspace.com/file/r7xz78. Unzip it and follow the instruction given in readme.

2.      Station articles are not fetching in Despatch

Solution:  Local delivery / Station articles will not be fetched for despatch in the Despatch module.You can fetch local article for delivery through postman module. The data will be correctly fetched in DET.

POSTMAN

1.      Local articles are showing not sent out for delivery in DET

Solution:  The option "Fetch from Counter" should be used on the day of invoicing these articles to Postman beats.  For ex: If you have booked local articles today and you want them to be sent to beats on tomorrow, you should not use the Fetch from Counter option today.  This option to be exercised on the next dayonly.

In such a situation, even if you don’t fetch today, all these local articles will be treated as "Despatched" in DET.  Hence Pls use the Fetch from Counter option on the date of invoicing the articles to postman.

SUB ACCOUNTS

For any type of error coming after upgradation pl.do the following.

Restore the backup of Sub accounts, Sub Treasury, BO Sub accounts taken before upgradation....and continue your work till solution is provided by PTC.

eMO

1.      Object reference not set error while doing paid verification

Solution: Please ensure that eMO Account heads are created properly. SubAccount and SupplySubaccount databases are running and correct treasury server name is given while configuration. Ensure that Socodemapping is done correctly. Ensure that HOAccount date and SOaccount dates are entered correctly both in eMO operator and subaccount modules.

Meghdoot 6.6 SP1 Solution

If countries, currencies are not coming in Movidesh booking then patch is available in ftp site... ftp://ftp.ptcinfo.org/Meghdootv6.6/PointOfSale/eurogiroCountryProblem/EuroGiro.zip

Delete Duplicate Account Head in Subaccounts ( Change into Current Date = ‘yyyy-mm-dd’) Use Subaccounts EXECUTE [H_DeleteDuplicate] @TransDate = '2010-04-09'

For treasury problem : Run the attached Treasury1.exl file using script tool. ( Download ) After executing the script, run query analyzer and execute the following query Use Treasury execute update_megh66_accountheads_bydate 'ddmmyy' Note: ‘ddmmyy’ stands for the date on which account heads not appeared. ex: if the date is 09/04/2010 then ddmmyy will be 090410

For Accounts PBS Problem: 1. If u are getting the error while generating PLI file then Please run the following query using query analyzer on NICPLI database select * from NICPLI..NICMASTER where pliorrpli ='P' see the results, If no record is returned , it means that there are no PLI record in ur NICPLI database and thus u are getting the BOF error. So u will have to transfer the pli records from master csv file, which u have downloaded from website, using bridge software and select "Delete old records and insert new records" option button. Then transfer rpli records using "Append records" option button. 2. If u are getting the error while generating RPLI file then Please run the following querry using query analyzer on NICPLI database select * from NICPLI..NICMASTER where pliorrpli ='R' see the results, If no record is returned , it means that there are no RPLI record in ur NICPLI database and thus u are getting the BOF error. >So u will have to transfer the pli records from master csv file, which u have downloaded from website, using bridge software and select "Delete old records and insert new records" option button. Then transfer rpli records using "Append records" option button."

All Download

All Downloads
All patches and scripts which may downloaded from here

SQL 2005 Schedule Backup

To schedule a database backup operation by using SQL Server Management Studio in SQL Server 2005, follow these steps:

1. Start SQL Server Management Studio.
2. In the Connect to Server dialog box, click the appropriate values in the Server type list, in the Server name list, and in the Authentication list.
3. Click Connect.
4. In Object Explorer, expand Databases.
5. Right-click the database that you want to back up, click Tasks, and then click Back Up.
6. In the Back Up Database - DatabaseName dialog box, type the name of the backup set in the Name box, and then click Add under Destination.
7. In the Select Backup Destination dialog box, type a path and a file name in the Destinations on disk box, and then click OK.
8. In the Script list, click Script Action to Job.
9. In the New Job dialog box, click Steps under Select a page, and then click Edit if you want to change the job parameters.
*Note In the Job Step Properties - 1 dialog box, you can see the backup command.
10. Under Select a page, click Schedules, and then click New.
11. In the New Job Schedule dialog box, type the job name in the Name box, specify the job schedule, and then click OK.
* Note If you want to configure alerts or notifications, you can click Alerts or Notifications under Select a page.
12. Click OK two times.

You receive the following message:
The backup of database 'DatabaseName' completed successfully.

* Note To verify the backup job, expand SQL Server Agent, and then expand Jobs. When you do this, the SQL Server Agent service must be running.

Meghdoot News

Meghdoot 6.6.4 Version is under Testing. Will be released early

Network Printing

Printing Through USB Port

Share the Printer name( in the Printer attached System)
Go to Command Prompt
Create a Batch file like this thro edit command ( Eg. NETPRINT.BAT)
@ECHO ON
NET USE LPT1: \\SYSTEMNAME\SHARENAME /PERSISTENT:YES
CLS

Add the Batch file into Windows startup menu in the required client system
Install the Attached DOS2USB Software ( Download DOS2USB)

Network Print Setup
Share the Printer name( in the Printer attached System)
In Other Clients:
Go to Command Prompt
Create a Batch file like this thro edit command ( Eg. NETPRINT.BAT)

@ECHO ON
NET USE LPT1: \\SYSTEMNAME\SHARENAME /PERSISTENT:YES
CLS

Add the Batch file into Windows startup menu in the required client system

SB Data Transfer

SB Table Transfer.

OCX Files : http://www.box.net/shared/6d1469dtab
Download and rename as SB Table Transfer.exe. and execute from any where

Restore the Source database ( may be EDSO or any SO database for Computerisation)

1. It a self executing software for transfer of Tables between two Sanchaypost – SB databases.
2. It is used to transfer the tables from EDSO / GDS SO to Merged SO
3. It is useful to New SO Computerisation ( for SB)
4. It used to Update PO Code for the particular tables

*Check any Duplicate Account No in relevant the SQL table manually and delete
The Required DLL/ OCX files are attached h/w
SB Transfer Download

ePayment Reset Registraton

Re-register the office both from web and client.
For resetting the existing registration please do the following.
1. Download the resetregistrtation.zip file from http://www.sendspace.com/file/0dp1l5
2. Unzip the zip file to get ResetRegistration and Readme.txt files
Go through the Readme.txt file and execute the exe as per instructions

When Speedpost Booked, Despatch, Delivery articles are shown as NA then

Despatch Module:
1- Download the Despatch latest 270110.zip file from http://www.sendspace.com/file/jr0rjr
and unzip it. Rename the it to DESPATCH.EXE
2- Replace the existing exe with new
3- Update counter database with exl files using Scripttool in following sequence

1 counter16122009.exl
2 Counter21012010.exl
3 and last Counter22012010.exl

Postman Module :
Download the zipped folder postman21122009.zip from http://www.sendspace.com/file/xc6hs0.
Unzip and follow the guidelines in the readme file therein.

Pls do shift end using the new postman exe after completing all the work.
Pls provide your feedback whether your problem is solved or not

Day End Sequence:
You have to strictly follow the shiftend sequence where POS shiftend should be at last. i.e.
The sequence of shift end is
Despatch, Postman, Speednet, Point of sale

For doing day end in postman, there are no conditions, except that
i) returns of all the speed post articles invoiced to postman should have been taken and
ii) if any speed post articles are to be despatched (returns taken as returned to sender/redirected) then such articles should be included in the concerned despatch bag
There is no any other conditions for other modules.

BNPL articles:
Regarding BNPL articles, ensure that the data entry of BNPL articles is done before doing day end of Point of Sale. Also ensure flush data is done in Speednet.

DET figures are available for some days and not available for some other days. This may be probably due to operational problems on those days. Please check.

Simple Upgradation Procedure from Sanchaypost version 6.5 into R2 ( 15/02/2010)

Upgradation Procedure from Sanchaypost version 6.5 into R2 ( 15/02/2010)   ( Download the latest from the following links) 1.Execute the SP5.exe in all Client Machine where SanchayPost software installed 2.Execute the Server Only.exe in Server or any one Client Machine 3.A.  Use ‘DBAnalyzer >> SQL Compatibility Level’ option.                 B.  Use ‘DBAnalyzer >> DBUtilities >> Clear log file’ for all SB databases.                 C.  Use ‘DBAnalyzer >> Missing Tables' for all SB databases and ensure that no tables are missing.                 D. Use DBAnalyzer >> ‘Database Discrepancies >> SCS >> Account numbers with SI without previous quarter interest withdrawal’. 4. Perform Day End in Version 6.5   A.After day end,  Go to DBAnalyzer folder in SBServer and execute Patch65R2.EXE from the same location. Wait till the message 'Upgraded successfully' is displayed.   B. Check for upgradation status using 'DBAnalyzer >> Version 6.5R2' to ensure that the upgradation is successful.
SanchayPost 6.5 R2 Updates for All Clients (15/02/2010)	http://www.box.net/shared/2cjin15ak3
SanchayPost 6.5 R2 Updates for Server Only (15/02/2010)	http://www.box.net/shared/1sho7890gc

eMO Head Creation for Branch Offices

Please execute the following query

Use treasury
GO
exec update_megh66_accountheads
GO

Department created Postmasters Cadre in the GP Rs 4800, 4600, 4200 and 2800

The Postal Department is more than 150 years old and the qualification for feeding cadre (Postal Assistant) to this Department was only Matriculation. Recently, the qualification for Postal Assistant has been changed as Higher Secondary with some basic computer knowledge.

These officials are promoted to LSG/HSG-II/HSG-I Postmasters as per seniority and the service to the public is depend upon these cadre only. Fast track examination conducted for LSG promotion was also stopped due to various reasons.


However to improve the efficiency further and to cope up with the present technlogical issues, Department has issued orders vide Order No 13-2/2010-PE-I dated 3.2.2010 to constitute Postmaster Cadre which is reproduced as follows:-

It has been decided with the approval of the Competent Authority to constitute a separate cadre of Postmasters with following number of posts by carving them out from the existing General Line Cadre Posts and Postal Services Group - B of Postal Wing and to designate them as Senior Postmaster, Postmaster Grade-III, Postmaster Grade-II and Postmaster Grade-I as detailed below:-

SlNo	Existing Cadre	Proposed Cadre	Number of Posts
1.	Postal Services Group - B Officer	Senior Postmaster Rs 9300-34800 + GP Rs 4800 (PB-3) and Rs 5400 after 4 years(PB-2)	116
2	Higher Selection Grade-I (HSG-I)	Postmaster Grade-III Rs 9300-34800 + GP Rs 4600 (PB-2)	495
3	Higher Selection Grade-II (HSG-II)	Postmaster Grade-II Rs 9300-34800 + GP Rs 4200 (PB-2)	511
4	Lower Selection Grade (LSG)	Postmaster Grade-I Rs 9300-34800 + GP Rs 2800 (PB-2)	2097

The Posts will be deemed to have been designated as Senior Postmaster, Postmaster Grade-III, Postmaster Grade-II and Postmaster Grade-I with effect from the dates these are filled up.
The consequential action like framing of Recruitment Rules shall be taken by the Personnel Division.

1. Sanchay Post for SOSB is in operation at HO

If Sanchay Post software for SOSB is in operation at HO, then the following steps are to be performed at SO.

• The network operating system has to be installed.

• SQL server has to be installed.

• Sanchay Post Software has to be installed.

• Make a folder called ‘POST’ in the drive where SB databases are intended to be created. Ensure availability of enough space in the selected drive.

• Using ‘Database Operations  Create DB’ option of Sanchay Post, database has to be created.

• Take a backup of the SO database (available at HO)

• Backup of respective SO database is to be restored at the SO with the same database name using SQL Server Enterprise Manager. The steps involved are listed below:

 Select ‘POST’ database. Select Tools  Data Transformation Services  Import Data from the menu. This will launch the DTS Export / Import Wizard.

 Select the SO database as the source database in ‘Choose a Data Source’ screen.

 ‘POST’ database will be automatically selected as the ‘Destination’.

 Select the option ‘Copy objects and data between SQL Server databases’ in ‘Specify table copy or query’ screen.

 Select the tables to be imported. (Assumed that no data is available at SO for the tables you are selecting).

 A message will be received on successful data transfer.

• After this transfer, data fed at HO in respect of the SO, up-to the day begin date of SOSB module at the time of backup will be available in the SO. Subsequently, Daily LOTs are to be fed in Sanchay Post till the current date to make the operations at SO on-line.

o List of tables to be transferred for each scheme is given below:

Scheme Table name

MIS mindxreg

mledger

PPF ppf_indexreg

ppf_ledger

ppf_loandet

ppf_extended_period

TD td_withdraw

td_indexreg

td_ledger

SCS scs_index

scs_ledger

scs_withdraw

scs_docs

RD accountopen_through_agent

rdindex

rdjrnl

rddflt

rdmisc

rdbulk_index

rdbulk_ledger

institution_details

SB indexreg

ledger

nomineeinfo

introducer

interestposting

ibb

NSS nss_indexreg

nss_ledger

Solution for KPI % differ due to Despatch & Postman Module

DESPATCH

Kindly download here DESPATCH.zip from here and replace the exe at respective folder.

download

Unzip it and go through the DESPATCH 6.6 error.doc file.

Also run Fetch_Local_Counter_Articles21102009.exl file using script tool. This is for fatching  the Local RL/RP articles booked counter for delivery at same office jurisdiction.

Ensure that shiftend of Speednet, Dispatch is done prior to doing Shiftend in Point of Sale.

The sequence may apply for hassle free and correct figure access at KPI end.

1st- Despatch Module i.e. RL/RP etc.

2nd- Speednet Return entry then Despatch from Speednet module

3rd- Postman. Ensure all the cash submission done by postman at treasury and VPL transaction and booking should completed at all concern module.

4th- Point of Sale

5th- SubAccounts & Treasury

6th- Sanchay Post DayEnd. Ensure the Sign Scanning pending from DB Analyser

If you are using Speednet in separate system don’t use the Speed Dispatch options available in DESPATCH module.

POSTMAN

Please use the new postman exe is available at ftp site.

Go through the Postman Update-1.doc for the solutions provided.

Signature Scanning Software

Signature Scanning made easy
Signature Scanning Software
Scanning Procedure
Picture Resize Software

ePayment Communication Problem

Due to migration of ePayment database server and redeployment of applications the ePayment web site address has been changed from 07/12/2009 as below.
https://services.ptcmysore.gov.in/epayment
The ePayment communication exe has to be updated in all ePayment offices before connecting to ePayment central server on 07/12/2009.
 1.  Please unzip the attached file ePaymentCommunication.zip. Unzip it u will get 6        files
    a. EBillCommunication.txt
    b. EBillCommunication.exe.config 
    c. ptcmyscs_root.cer
    d. RegisterCACft.txt
    e. ePaymentServerObject.dll
    f. readme.txt
 2.  Please change the extention of the following files as .exe.
       RegisterCACft.txt
       EBillCommunication.txt
     Please change the extention of the following files as .dll
     ePaymentServerObject.txt
     Please change the extention of the following files as .cer
       ptcmyscs_root.txt
 3.   Please go through the readme.txt and  follow thw procedure specified.
ePayment New Communication Download Here

Sanchay Post Updates & Instructions

Wishes you a very happy & prosperous new year.. 2009!
1- Update all your clients with the latest patches periodically, backup your databases regularly and have a trouble-free year ahead.
2- Update the Holiday List at Sanchay Post & Sub Account level for hassel free operation.
DB Analyser Latest
Passbook Printing
Passbook Printing for Vista

eMO Reset Registration

Download
Download the file from above link and unzip and apply accordingly.
Before apply Take the Backup of eMOClient folder safely with eMO database.
Take all the printout of received eMO for payment and disposal.