Configure order file template

As an implementor, I want to configure the order file template so that my order files are generated with my desired columns and formats to enable transfer of data via an FTP.

Looking forward: At some point we may want to create an order file template per facility in case programs source their data from different warehouses with different ERPs. We still need to research this and will stick to the current 2.0 functionality for now. Currently we will create one global order file. However, please keep this in mind when designing and thinking about implementing this story.

Make sure to review the epic description to understand the larger picture of this feature.

Acceptance Criteria
Verify that:

• an implementor can indicate to include or not include column headers (boolean)

• Order Number column is generated using the order number template (https://openlmis.atlassian.net/browse/OLMIS-401#icft=OLMIS-401)

• All column headers can be defined (renamed) by the implementor

• Facility code column populates the facility code from the requisition information

• Product Code column populates the product name from requisition information/reference data

• Product Name column populates the product name from requisition information/reference data

• Approved quantity column populates based on the approved quanitity column in the requisition

• Period information populates based on the requisition

• Period format is defined by the implementor, choices include

  • MM/yy

  • MM/yyyy

  • etc. - please include all options that are in 2.0 (update the story with all the options there)

• Order date populates based on the date converted (PLEASE check 2.0 behavior - this may be on the approved date...needs to be verified)

• Order date format is defined by the implementor, choices include

  • same as period format

• Implementor can define the Order file prefix (PLEASE check 2.0 behavior if the prefix needs to match the Order Number Template prefix - I'm not sure)