Bug 4960 - No way to enter custom purchase order number
Summary: No way to enter custom purchase order number
Status: CLOSED FIXED
Alias: None
Product: Koha
Classification: Unclassified
Component: Acquisitions (show other bugs)
Version: Main
Hardware: All All
: P5 - low normal (vote)
Assignee: Bugs List
QA Contact: Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-07 21:08 UTC by Nicole C. Engard
Modified: 2015-12-03 22:00 UTC (History)
4 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nicole C. Engard 2010-07-07 21:08:49 UTC
There needs to be a way on order to enter a purchase order number that will then print on the PDF receipt.  Most organizations do not have purchase orders that are sequential for book orders only (the library may have sequential POs for all their orders - supplies, books, etc) and the ID generated by the DB won't work for them.
Comment 1 Colin Campbell 2010-07-08 10:05:03 UTC
See Bugs 3803, 3804, 4456

The field purchaseordernumber allowed this but was removed from display/edit in the merge of the new 3.2.

In development done for UN FAO in Rome it has been enhanced to be searchable, and on order creation is created (it encodes the order type, a unique id and year for serials). It is the main access used in acquisitions (and serials -> acq links).

Unfortunately, the functional developments in the acquisitions development merged into 3.2 were at variance with features in daily use at fao (3.1). My intention is that once 3.2 is released to compare the two systems and release a series of patches to supply the functionality not met in 3.2 for 3.4.

A trivial patch to this end would be to make purchaseordernumber editable on order creation/edit again. but that would effect translation so would not be a candidate for 3.2
Comment 2 Katrin Fischer 2012-04-07 17:35:00 UTC
Hi Nicole, 
does the basketname in the (no longer so new) acquisition module fix this?
Comment 3 Katrin Fischer 2015-02-21 22:57:59 UTC
Closing this bug as fixed, assuming that the basket name can be used for the custom purchase order number.
Comment 4 Mark Tompsett 2015-04-04 21:23:29 UTC
Katrin, what about 4456?
Comment 5 Katrin Fischer 2015-05-15 21:34:07 UTC
I think we have a place for the number with the basket name, but it still might be nice to have an option to automatically generate what goes in there, so 4456 is still valid.