https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20253
Martin Renvoize (ashimema) <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Text to go in the| |Libraries can now configure release notes| |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, | |dramatically improving | |searchability and | |cross-referencing between | |Koha and vendor systems. | | | |**The problem:** | | | |Previously, when processing | |EDIFACT quotes, 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 | |- 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, or the vendor | |system | | | |**The solution:** | | | |EDI vendor accounts now | |have a "Use purchase order | |numbers" option that, 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 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 purchase order | |numbers are unique per | |vendor, 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 purchase order | |numbers | |- **Fallback handling**: If | |no purchase order number is | |found in the QUOTE, 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 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 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, | |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 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 Keywords|release-notes-needed | -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
