Configure Order Number for Export

Description

Allows configuration of order numbers via a template. When an order file is generated the order number template will be used to generate a unique order number for that specific order. Remember that an order is created once the requisition is approved (and will always be associated with that requisition)

As an implementor, I want to configure how order numbers are generated so that order numbers follow an to match the expected input for the ERP system.

The description of which can be found in the OpenLMIS Configuration Guide in the section, "Setup the order-number format and EDI file format". The "configuring the format for Order Number" section is the requirements for this story, mainly:

  • ability to specify Order number prefix (optional)

  • ability to specify Program code (optional)

  • ability to specify regular/emergency suffix (optional)

  • UUID

The order number generated for each order should match the 1.0/2.0 functionality, and applies to all orders generated by OpenLMIS, regardless of program.

Acceptance Criteria

  • template allows an implementor to designate an order number prefix (8 alphanumeric characters)

  • template allows an implementor to select (and deselect) the program code to be used

    • if selected, the program code is generated within the order number

  • template must include the sequence code (see 2.0 and make sure sequence code is being generated the same way) when the order number is generated

  • template allows an implementor to select (and deselect) the regular/emergency suffix

    • if selected, an R or E is generated within the order number

  • when the template is exercised (via API) an order number is generated based on the user defined criteria

  • order number is generated when the warehouse manager 'coverts' the requisition to order

  • the order file contains the generated order number

Please ask if you have any questions on the acceptance criteria or the desired behavior.

Activity

Show:
Paulina Borowa
October 25, 2016, 12:34 PM

Currently all works.
What I checked:
1. Create orderNumberConfigurations:


2. Check the proper display of the orderCode:


3. Update orderNumberConfigurations:


4. Check the proper display of the orderCode after changes:


5. Check validation for prefix:

Paulina Borowa
October 24, 2016, 1:44 PM
Edited

There is a problem with update orderNumberConfigurations, when I try to set:
{
"id": "a577c996-5beb-4824-b001-2c654699cc95",
"orderNumberPrefix": "Pref999",
"includeOrderNumberPrefix": true,
"includeProgramCode": false,
"includeRequisitionTypeSuffix": false
}


I get status 200 ok, but when I try to check by GET in URL: http://10.222.17.205/requisition/api/orderNumberConfigurations?access_token=b3688c3a-2809-4d6b-8045-5519447992be
it shows no changes:

Pengfei Cui
October 19, 2016, 6:09 PM

SUCCESS: Integrated in

OpenLMIS-referencedata-service-Sonar #176
OLMIS-401: Add demo data for convert to Order (pmuchowski: f59a9d0a16084aa33e85bbd0300203bf0a80ec8d)

Pengfei Cui
October 19, 2016, 6:05 PM

SUCCESS: Integrated in

OpenLMIS-requisition-service-Sonar #400
OLMIS-401: Fixed convert to Order issues (pmuchowski: 052765c594aab53366096e81b0ae2d58214be313)

Pengfei Cui
October 19, 2016, 6:04 PM

SUCCESS: Integrated in

OpenLMIS-referencedata-service #203
OLMIS-401: Add demo data for convert to Order (pmuchowski: f59a9d0a16084aa33e85bbd0300203bf0a80ec8d)

Done

Assignee

Paweł Gesek

Reporter

Mary Jo Kochendorfer

Labels

Time remaining

0m

Epic Link

Sprint

None

Fix versions

Affects versions

Priority

Major