Back to bug 20253

Who When What Removed Added
jeremy.evans 2021-09-27 08:13:17 UTC CC jeremy.evans
katrin.fischer 2023-10-01 21:25:46 UTC Summary Optionally use buyer's purchase order number from Edifact quote in basketname Optionally use buyer's purchase order number from EDIFACT quote in basket name
hdunne-howrie 2025-05-20 13:20:57 UTC CC hdunne-howrie
aude.charillon 2025-05-20 15:46:53 UTC CC aude.charillon
martin.renvoize 2025-07-08 12:31:35 UTC Assignee koha-bugs martin.renvoize
CC martin.renvoize
martin.renvoize 2025-07-08 15:32:33 UTC Status NEW Needs Signoff
martin.renvoize 2025-07-10 17:11:35 UTC Attachment #183859 Attachment is obsolete 0 1
martin.renvoize 2025-07-10 17:11:37 UTC Attachment #183860 Attachment is obsolete 0 1
martin.renvoize 2025-07-10 17:11:39 UTC Attachment #183861 Attachment is obsolete 0 1
martin.renvoize 2025-07-10 17:11:41 UTC Attachment #183862 Attachment is obsolete 0 1
martin.renvoize 2025-07-11 15:36:16 UTC Attachment #183953 Attachment is obsolete 0 1
martin.renvoize 2025-07-11 15:36:20 UTC Attachment #183958 Attachment is obsolete 0 1
martin.renvoize 2025-07-11 15:37:06 UTC Attachment #183954 Attachment is obsolete 0 1
martin.renvoize 2025-07-11 15:37:25 UTC Attachment #183957 Attachment is obsolete 0 1
martin.renvoize 2025-07-11 15:37:33 UTC Attachment #183955 Attachment is obsolete 0 1
martin.renvoize 2025-07-11 15:37:42 UTC Attachment #183956 Attachment is obsolete 0 1
martin.renvoize 2025-07-11 15:37:51 UTC Comment 3 Tag obsolete
martin.renvoize 2025-07-11 15:37:55 UTC Comment 4 Tag obsolete
martin.renvoize 2025-07-11 15:37:57 UTC Comment 5 Tag obsolete
martin.renvoize 2025-07-11 15:38:00 UTC Comment 6 Tag obsolete
martin.renvoize 2025-07-11 15:38:02 UTC Comment 7 Tag obsolete
martin.renvoize 2025-07-11 15:38:04 UTC Comment 8 Tag obsolete
martin.renvoize 2025-07-11 15:38:07 UTC Comment 9 Tag obsolete
martin.renvoize 2025-07-11 15:38:10 UTC Comment 10 Tag obsolete
martin.renvoize 2025-07-11 15:38:12 UTC Comment 11 Tag obsolete
martin.renvoize 2025-07-11 15:38:15 UTC Comment 12 Tag obsolete
martin.renvoize 2025-07-11 15:38:18 UTC Comment 13 Tag obsolete
martin.renvoize 2025-07-11 15:38:21 UTC Comment 14 Tag obsolete
martin.renvoize 2025-07-11 15:38:24 UTC Comment 15 Tag obsolete
martin.renvoize 2025-07-11 15:38:28 UTC Comment 16 Tag obsolete
martin.renvoize 2025-07-11 15:38:29 UTC Comment 17 Tag obsolete
martin.renvoize 2025-07-11 15:38:33 UTC Comment 18 Tag obsolete
martin.renvoize 2025-07-11 15:38:36 UTC Comment 19 Tag obsolete
martin.renvoize 2025-07-11 15:38:38 UTC Comment 20 Tag obsolete
martin.renvoize 2025-07-11 15:38:57 UTC Comment 20 Tag obsolete
martin.renvoize 2025-07-11 15:39:00 UTC Comment 19 Tag obsolete
martin.renvoize 2025-07-11 15:39:03 UTC Comment 18 Tag obsolete
martin.renvoize 2025-07-11 15:39:06 UTC Comment 17 Tag obsolete
martin.renvoize 2025-07-11 15:39:09 UTC Comment 16 Tag obsolete
martin.renvoize 2025-07-11 15:39:13 UTC Comment 15 Tag obsolete
martin.renvoize 2025-07-11 15:39:18 UTC Comment 14 Tag obsolete
martin.renvoize 2025-07-11 15:39:22 UTC Comment 13 Tag obsolete
martin.renvoize 2025-07-11 15:39:31 UTC Comment 14 Tag important
martin.renvoize 2025-07-11 15:39:35 UTC Comment 15 Tag important
martin.renvoize 2025-07-11 15:39:39 UTC Comment 17 Tag important
martin.renvoize 2025-07-11 15:39:43 UTC Comment 18 Tag important
martin.renvoize 2025-07-11 15:39:47 UTC Comment 19 Tag important
martin.renvoize 2025-07-11 15:39:51 UTC Comment 20 Tag important
martin.renvoize 2025-07-18 14:01:53 UTC Blocks 40383
martin.renvoize 2025-08-07 15:27:13 UTC Attachment #184001 Attachment is obsolete 0 1
martin.renvoize 2025-08-07 15:27:16 UTC Attachment #184002 Attachment is obsolete 0 1
martin.renvoize 2025-08-07 15:27:18 UTC Attachment #184003 Attachment is obsolete 0 1
martin.renvoize 2025-08-07 15:27:21 UTC Attachment #184004 Attachment is obsolete 0 1
martin.renvoize 2025-08-07 15:27:23 UTC Attachment #184005 Attachment is obsolete 0 1
martin.renvoize 2025-08-07 15:27:26 UTC Attachment #184006 Attachment is obsolete 0 1
martin.renvoize 2025-08-07 15:27:28 UTC Attachment #184007 Attachment is obsolete 0 1
martin.renvoize 2025-08-07 15:28:16 UTC Comment 28 Tag important
martin.renvoize 2025-08-07 15:28:22 UTC Comment 13 Tag obsolete
martin.renvoize 2025-08-07 15:28:23 UTC Comment 16 Tag obsolete
martin.renvoize 2025-08-07 15:28:25 UTC Comment 21 Tag obsolete
martin.renvoize 2025-08-07 15:28:28 UTC Comment 22 Tag obsolete
martin.renvoize 2025-08-07 15:28:30 UTC Comment 23 Tag obsolete
martin.renvoize 2025-08-07 15:28:33 UTC Comment 24 Tag obsolete
martin.renvoize 2025-08-07 15:28:35 UTC Comment 25 Tag obsolete
martin.renvoize 2025-08-07 15:28:38 UTC Comment 26 Tag obsolete
martin.renvoize 2025-08-07 15:28:41 UTC Comment 27 Tag obsolete
martin.renvoize 2025-08-07 16:38:58 UTC QA Contact testopia kyle
martin.renvoize 2025-09-24 09:13:17 UTC Depends on 38489
martin.renvoize 2025-09-24 09:35:56 UTC Attachment #185221 Attachment is obsolete 0 1
martin.renvoize 2025-09-24 09:35:59 UTC Attachment #185222 Attachment is obsolete 0 1
martin.renvoize 2025-09-24 09:36:01 UTC Attachment #185223 Attachment is obsolete 0 1
martin.renvoize 2025-09-24 09:36:03 UTC Attachment #185224 Attachment is obsolete 0 1
martin.renvoize 2025-09-24 09:36:05 UTC Attachment #185225 Attachment is obsolete 0 1
martin.renvoize 2025-09-24 09:36:08 UTC Attachment #185226 Attachment is obsolete 0 1
martin.renvoize 2025-09-24 09:36:10 UTC Attachment #185227 Attachment is obsolete 0 1
martin.renvoize 2025-09-24 09:36:12 UTC Attachment #185228 Attachment is obsolete 0 1
martin.renvoize 2025-09-24 09:52:43 UTC Attachment #186860 Attachment is obsolete 0 1
martin.renvoize 2025-09-24 09:52:46 UTC Attachment #186861 Attachment is obsolete 0 1
martin.renvoize 2025-09-24 09:52:48 UTC Attachment #186862 Attachment is obsolete 0 1
martin.renvoize 2025-09-24 09:52:50 UTC Attachment #186863 Attachment is obsolete 0 1
martin.renvoize 2025-09-24 09:52:53 UTC Attachment #186864 Attachment is obsolete 0 1
martin.renvoize 2025-09-24 09:52:55 UTC Attachment #186865 Attachment is obsolete 0 1
martin.renvoize 2025-09-24 09:52:57 UTC Attachment #186866 Attachment is obsolete 0 1
martin.renvoize 2025-09-24 09:52:59 UTC Attachment #186867 Attachment is obsolete 0 1
martin.renvoize 2025-09-24 09:54:17 UTC Status Needs Signoff Signed Off
martin.renvoize 2025-10-01 11:09:28 UTC Attachment #186868 Attachment is obsolete 0 1
martin.renvoize 2025-10-01 11:09:31 UTC Attachment #186869 Attachment is obsolete 0 1
martin.renvoize 2025-10-01 11:09:33 UTC Attachment #186870 Attachment is obsolete 0 1
martin.renvoize 2025-10-01 11:09:35 UTC Attachment #186871 Attachment is obsolete 0 1
martin.renvoize 2025-10-01 11:09:38 UTC Attachment #186872 Attachment is obsolete 0 1
martin.renvoize 2025-10-01 11:09:40 UTC Attachment #186873 Attachment is obsolete 0 1
martin.renvoize 2025-10-01 11:09:42 UTC Attachment #186874 Attachment is obsolete 0 1
martin.renvoize 2025-10-01 11:09:45 UTC Attachment #186875 Attachment is obsolete 0 1
martin.renvoize 2025-10-01 11:10:20 UTC Comment 29 Tag obsolete
martin.renvoize 2025-10-01 11:10:22 UTC Comment 30 Tag obsolete
martin.renvoize 2025-10-01 11:10:25 UTC Comment 31 Tag obsolete
martin.renvoize 2025-10-01 11:10:28 UTC Comment 32 Tag obsolete
martin.renvoize 2025-10-01 11:10:30 UTC Comment 33 Tag obsolete
martin.renvoize 2025-10-01 11:10:33 UTC Comment 34 Tag obsolete
martin.renvoize 2025-10-01 11:10:36 UTC Comment 35 Tag obsolete
martin.renvoize 2025-10-01 11:10:38 UTC Comment 36 Tag obsolete
martin.renvoize 2025-10-01 11:10:40 UTC Comment 37 Tag obsolete
martin.renvoize 2025-10-01 11:10:43 UTC Comment 38 Tag obsolete
martin.renvoize 2025-10-01 11:10:47 UTC Comment 39 Tag obsolete
martin.renvoize 2025-10-01 11:10:49 UTC Comment 40 Tag obsolete
martin.renvoize 2025-10-01 11:10:51 UTC Comment 41 Tag obsolete
martin.renvoize 2025-10-01 11:10:53 UTC Comment 42 Tag obsolete
martin.renvoize 2025-10-01 11:10:55 UTC Comment 43 Tag obsolete
martin.renvoize 2025-10-01 11:10:58 UTC Comment 44 Tag obsolete
martin.renvoize 2025-10-01 11:11:01 UTC Comment 46 Tag obsolete
martin.renvoize 2025-10-01 11:11:05 UTC Comment 47 Tag obsolete
martin.renvoize 2025-10-14 10:58:00 UTC Attachment #187165 Attachment is obsolete 0 1
martin.renvoize 2025-10-14 10:58:02 UTC Attachment #187166 Attachment is obsolete 0 1
martin.renvoize 2025-10-14 10:58:05 UTC Attachment #187167 Attachment is obsolete 0 1
martin.renvoize 2025-10-14 10:58:08 UTC Attachment #187168 Attachment is obsolete 0 1
martin.renvoize 2025-10-14 10:58:10 UTC Attachment #187169 Attachment is obsolete 0 1
martin.renvoize 2025-10-14 10:58:13 UTC Attachment #187170 Attachment is obsolete 0 1
martin.renvoize 2025-10-14 10:58:16 UTC Attachment #187171 Attachment is obsolete 0 1
martin.renvoize 2025-10-14 10:58:18 UTC Attachment #187172 Attachment is obsolete 0 1
martin.renvoize 2025-10-14 10:58:21 UTC Attachment #187173 Attachment is obsolete 0 1
martin.renvoize 2025-10-14 11:00:16 UTC Comment 63 Tag important
martin.renvoize 2025-10-14 11:00:20 UTC Comment 64 Tag important
martin.renvoize 2025-10-14 11:00:24 UTC Comment 48 Tag obsolete
martin.renvoize 2025-10-14 11:00:27 UTC Comment 49 Tag obsolete
martin.renvoize 2025-10-14 11:00:30 UTC Comment 50 Tag obsolete
martin.renvoize 2025-10-14 11:00:32 UTC Comment 51 Tag obsolete
martin.renvoize 2025-10-14 11:00:35 UTC Comment 52 Tag obsolete
martin.renvoize 2025-10-14 11:00:37 UTC Comment 53 Tag obsolete
martin.renvoize 2025-10-14 11:00:40 UTC Comment 54 Tag obsolete
martin.renvoize 2025-10-14 11:00:42 UTC Comment 55 Tag obsolete
martin.renvoize 2025-10-14 11:00:44 UTC Comment 56 Tag obsolete
martin.renvoize 2025-10-14 11:00:47 UTC Comment 57 Tag obsolete
martin.renvoize 2025-10-14 11:00:50 UTC Comment 58 Tag obsolete
martin.renvoize 2025-10-14 11:00:53 UTC Comment 59 Tag obsolete
martin.renvoize 2025-10-14 11:00:55 UTC Comment 60 Tag obsolete
martin.renvoize 2025-10-14 11:00:59 UTC Comment 61 Tag obsolete
martin.renvoize 2025-10-14 11:01:01 UTC Comment 62 Tag obsolete
kyle 2025-10-24 17:03:38 UTC Attachment #187876 Attachment is obsolete 0 1
kyle 2025-10-24 18:30:03 UTC Status Signed Off Passed QA
kyle 2025-10-24 18:30:04 UTC Attachment #184000 Attachment is obsolete 0 1
kyle 2025-10-24 18:30:06 UTC Attachment #187874 Attachment is obsolete 0 1
kyle 2025-10-24 18:30:08 UTC Attachment #187875 Attachment is obsolete 0 1
kyle 2025-10-24 18:30:10 UTC Attachment #187877 Attachment is obsolete 0 1
kyle 2025-10-24 18:30:11 UTC Attachment #187878 Attachment is obsolete 0 1
kyle 2025-10-24 18:30:13 UTC Attachment #187879 Attachment is obsolete 0 1
kyle 2025-10-24 18:30:15 UTC Attachment #187880 Attachment is obsolete 0 1
kyle 2025-10-24 18:30:16 UTC Attachment #187881 Attachment is obsolete 0 1
kyle 2025-10-24 18:30:18 UTC Attachment #187882 Attachment is obsolete 0 1
kyle 2025-10-24 18:30:20 UTC Attachment #187883 Attachment is obsolete 0 1
lucas 2025-11-03 21:15:47 UTC Version(s) released in 25.11.00
Status Passed QA Pushed to main
lucas 2025-11-03 21:18:35 UTC CC lucas
Keywords release-notes-needed
lucas 2025-11-03 23:56:41 UTC Keywords additional_work_needed
martin.renvoize 2025-11-04 16:51:03 UTC Status Pushed to main Passed QA
lucas 2025-11-05 14:14:21 UTC Status Passed QA Pushed to main
martin.renvoize 2025-11-07 09:23:49 UTC Status Pushed to main Passed QA
lucas 2025-11-07 14:46:35 UTC Status Passed QA Pushed to main
Keywords additional_work_needed
martin.renvoize 2025-11-07 17:11:33 UTC Text to go in the release notes Libraries can now configure EDI vendor accounts to use the buyer's purchase order number from EDIFACT quote messages (RFF+ON segments) as the basket name instead of the EDIFACT filename, when enabled:
- Extracts the purchase order number from incoming QUOTE messages (RFF+ON segment)
- Uses this number as the basket name in Koha
- Includes the purchase order number in outgoing ORDER messages (BGM segment) according to EDIFACT, falls back to using the filename
- **Optional feature**: Completely backwards compatible - existing behaviour unchanged unless explicitly configured

**For acquisitions staff:**

1. Go to Administration → Acquisitions → EDI accounts
2. Edit a
Keywords release-notes-needed
Text to go in the release notes purchase order numbers
- Staff entered purchase order numbers on vendor websites but couldn't easily find corresponding baskets in Koha
- Three different references could exist for the same order depending on whether viewing quotes, orders, with error logging for conflicts
- **Protected basket names**: Basket names derived from purchase order numbers are read-only to maintain integrity
- **Automatic order blocking**: Prevents automatic and manual ordering for baskets with duplicate, you'll receive clear error messages preventing conflicts

**Technical workflow:**

Quote RFF+ON segment → Basket Name → Order BGM segment

This follows EDIFACT specifications where the purchase order number from incoming quote messages should be, dramatically improving searchability and cross-referencing between Koha and vendor systems.

**The problem:**

Previously, when processing EDIFACT quotes standards
- Maintains reference consistency throughout the complete ordering workflow

**Key features:**

- **Complete round-trip workflow**: Purchase order number flows from QUOTE → Basket Name → ORDER message
- **Duplicate detection**: Validates vendor EDI account
3. Enable "Use purchase order numbers"
4. Save the configuration

After this:
- Baskets created from EDIFACT quotes will use the purchase order number as the basket name
- You can easily search for and identify baskets using the, or the vendor system

**The solution:**

EDI vendor accounts now have a "Use purchase order numbers" option that purchase order numbers
- **Fallback handling**: If no purchase order number is found in the QUOTE used as the document message number in the BGM segment of outgoing ORDER messages.

**Sponsored by:** Westminster City Council, Royal Borough of Kensington and Chelsea, OpenFifth, Koha would use the filename as the basket name. This created several challenges:
- Different reference numbers in Koha vs vendor systems made cross-checking difficult
- Baskets created from quotes showed generic filenames rather than meaningful purchase order numbers are unique per vendor same reference numbers you use with vendors
- The basket name field will be read-only (to preserve the purchase order number reference)
- If duplicate purchase order numbers are detected
martin.renvoize 2025-11-12 15:40:57 UTC Text to go in the release notes standards
- Maintains reference consistency throughout the complete ordering workflow

**Key features:**

- **Complete round-trip workflow**: Purchase order number flows from QUOTE → Basket Name → ORDER message
- **Duplicate detection**: Validates vendor EDI account
3. Enable "Use purchase order numbers"
4. Save the configuration

After this:
- Baskets created from EDIFACT quotes will use the purchase order number as the basket name
- You can easily search for and identify baskets using the, or the vendor system

**The solution:**

EDI vendor accounts now have a "Use purchase order numbers" option that purchase order numbers
- **Fallback handling**: If no purchase order number is found in the QUOTE used as the document message number in the BGM segment of outgoing ORDER messages.

**Sponsored by:** Westminster City Council, Royal Borough of Kensington and Chelsea, OpenFifth, Koha would use the filename as the basket name. This created several challenges:
- Different reference numbers in Koha vs vendor systems made cross-checking difficult
- Baskets created from quotes showed generic filenames rather than meaningful purchase order numbers are unique per vendor same reference numbers you use with vendors
- The basket name field will be read-only (to preserve the purchase order number reference)
- If duplicate purchase order numbers are detected Libraries can now configure EDI vendor accounts to use the buyer's purchase order number from EDIFACT quote messages (RFF+ON segments) as the basket name instead of the EDIFACT filename, when enabled:
- Extracts the purchase order number from incoming QUOTE messages (RFF+ON segment)
- Uses this number as the basket name in Koha
- Includes the purchase order number in outgoing ORDER messages (BGM segment) according to EDIFACT, falls back to using the filename
- **Optional feature**: Completely backwards compatible - existing behaviour unchanged unless explicitly configured

**For acquisitions staff:**

1. Go to Administration → Acquisitions → EDI accounts
2. Edit a purchase order numbers
- Staff entered purchase order numbers on vendor websites but couldn't easily find corresponding baskets in Koha
- Three different references could exist for the same order depending on whether viewing quotes, orders, with error logging for conflicts
- **Protected basket names**: Basket names derived from purchase order numbers are read-only to maintain integrity
- **Automatic order blocking**: Prevents automatic and manual ordering for baskets with duplicate, you'll receive clear error messages preventing conflicts

**Technical workflow:**

Quote RFF+ON segment → Basket Name → Order BGM segment

This follows EDIFACT specifications where the purchase order number from incoming quote messages should be, dramatically improving searchability and cross-referencing between Koha and vendor systems.

**The problem:**

Previously, when processing EDIFACT quotes
, you'll receive clear error messages preventing conflicts

**Technical workflow:**

Quote RFF+ON segment → Basket Name → Order BGM segment

This follows EDIFACT specifications where the purchase order number from incoming quote messages should be numbers"
4. Save the configuration

After this:
- Baskets created from EDIFACT quotes will use the purchase order number as the basket name
- You can easily search for and identify baskets using the same reference numbers you use with vendors
- Libraries can now configure EDI vendor accounts to use the buyer's purchase order number from EDIFACT quote messages (RFF+ON segments) as the basket name instead of the EDIFACT filename used as the document message number in the BGM segment of outgoing ORDER messages. The basket name field will be read-only (to preserve the purchase order number reference)
- If duplicate purchase order numbers are detected , dramatically improving searchability and cross-referencing between Koha and vendor systems.

**For acquisitions staff:**

1. Go to Administration → Acquisitions → EDI accounts
2. Edit a vendor EDI account
3. Enable "Use purchase order

Back to bug 20253