13. Reports
13.1 On Screen Reports
Most on screen reports have a similar format and are native to openerp: overview of lines is shown, and various filter buttons and fields are present. Default filters can be cleared and other filters added. Order of button filters added will impact on results. Expand all button can be used to see more detailed line information
Custom filters: It is possible with most on-screen reports to create a new filter using the custom filters. As above, this is native to openerp, and unfortunately known to include bugs, which only openerp would be able to fix. As a result, where the need for particular reports which do not work for the on-screen reports in UniField has been raised, most often a new report /Export has been developed to respond to this need due to inability to fix Custom/ native filters on screen reports
13.1.1 Field Order analysis
Menu mapping: Orders / Reporting / Field Order analysis
Overview of Field Orders.
– Commitment Delay = Avg. no. of days between FO creation and FO confirmation.
13.1.2 Purchase analysis
Menu mapping: Purchases/ Reporting / Purchase Analysis
Overview of Purchase Orders.
– Days to validate = Avg. no. of days between PO creation and PO validation.
– Days to deliver = Avg. no. of days between PO creation and PO Delivery Requested date
13.1.3 International Transport cost follow up
Menu mapping:Purchases / Reporting / Transport Costs
This report gives an overview of costs which have been added in the Transport mode value field in Purchase Orders which are to International Suppliers.
– Creation date = Creation date of International PO
13.1.4 Local Transport cost follow up
Menu mapping:Purchases / Reporting / Transport Costs
This report gives an overview of costs of products of type Service with Reception and ticked as Transport Product in Purchase Orders.
– Order Creation date = Creation date of PO containing transport line
– Delivery Confirmed date = Confirmed delivery date of PO containing transport line
13.1.5 Stock Moves
Menu mapping:Warehouse / Traceability / Stock Moves
Report showing all stock moves whether due to INs, OUTs, discrepancies, inventory corrections, initial stock inventories etc.
– Actual Receipt date = Date of stock move –actual date if move is closed, or expected date if not yet closed
– Scheduled date = Expected date of Stock move
13.1.6 Received Products
Menu mapping: Warehouse / Product Moves / Receive Products
Received Products screen by default shows all receptions which are expected / in progress. Possible to use header filters to search for a specific product/document/state etc
13.1.7 Delivered Products
Menu mapping: Warehouse / Product Moves / Deliver Products
On screen functionality to see which products have been delivered or are in progress. According to the header filters applied, the user can search by products, by partner etc
– Actual Receipt date = Date of stock move –actual date if move is closed, or expected date if not yet closed
13.1.8 Moves Analysis
Menu mapping: Warehouse / Reporting / Moves Analysis
Provides an overview of stock movements in and out of the instance.
Planned Lead Time = Avg. no. of days between stock move(s) creation and either (if closed) their actual processing date, or (if not yet closed) their expected move date.
Executed Lead Time = Avg no. of days between stock move(s) creation and their expected move date
Delay = Avg. no. of days between the expected date of stock move(s) and actual (processing) date of stock moves
13.1.9 Receptions Analysis
Menu mapping: Warehouse / Reporting / Receptions Analysis
Screen to see which products have arrived and analyse this data.
Planned Lead Time = Avg. no. of days between stock move(s) creation and either (if closed) their actual processing date, or (if not yet closed) their expected move date.
Executed Lead Time = Avg no. of days between stock move(s) creation and their expected move date
Delay = Avg. no. of days between the expected date of stock move(s) and actual (processing) date of stock moves
13.1.10 Reserved products (US-2542)
Menu mapping: Warehouse / Inventory Management / Reserved products
13.1.XXX many new reports missing
Menu mapping: Warehouse / Reporting / XXXXX
Unreserved Stock report
In & Out report
Receptions report
Deliveries Report
Expired/Damaged report
Products Situation report
Destruction report (Menu mapping: Warehouse / Traceability/ Destruction report)
Stock out => to be seen with new RR
13.2 Other reports / display functionalities
13.2.1 Batch recall
Menu mapping: Warehouse / Traceability / Batch Recall
This was deemed a necessary functionality for system supplying drugs and dangerous goods. This functionality does not actually do the “recall” or trigger any stock movements, but it displays location of products/batches. Product and relevant batch or expiry date is selected and destination locations are shown.
13.2.2 Mission Stock report and Consolidated Mission Stock report (US-7742)
Menu mapping: Warehouse / Inventory Management / Mission Stock or Warehouse / Inventory Management / Consolidated Mission Stock Report
This Excel report displays products relating to the instance. When run at Coordo level for option “full view”, report will display all products across the mission (including Coordo and any projects linked to that Coordo). The button “Update in background” means that the system will draw from the most recently product data (qtys etc) from that instance. For the products in other projects, these will be updated according to the configured frequency of synch for the scheduled actions (Admin>Scheduler>Scheduled Actions), which would usually be every 12 hours.
The system will display all stocks according filters entered, with the product code “reference”, name, unit of measure, along with the following information:
- Instance stock: all the stocks of all internal locations (including med, log, input and output, cross docking, intermediate stocks, internal consumption units) of the selection (ie instance full view etc which you selected),
- Warehouse stock: Stock (and children) but no input or output locations,
- Cross Docking location: all stocks in this location
- Secondary stock: sum of all intermediate stocks (if in existence)
- Internal consumption units: sum of all internal consumption units (if in existence)
- Quarantine Qty: to indicate stock levels in Quarantine (analyse+before scrap)
- Input Qty: for stock levels in the Input location
- Output/Packing/Dispatch/Distribution Qty” for stock levels in these 4 locations
- AMC (Average Monthly Consumption) of the product (average from the last 3 entire completed months)
- FMC (Forecasted Monthly Consumption)
- Quantity which is in the Pipeline: quantity expected to be received (ie PO has been validated)
In Pipeline Qty = Quantity of products Validated in a PO up till present in Incoming Shipment for which the status of the stock move is Available
The Consolidated MSR will display from COO the detailed locations of each mission. That is to say that each location name will be displayed in the file (and not aggregated as Intermediate Stock or ICU).
Last development detailed functional specifications can be found in Jira ticket US-7742).
13.2.3 Inventory Level ( inventory analysis) or Export Inventory Level
Menu mapping: Warehouse / Inventory Management / Inventory Level or Export Inventory Level
Report showing stock levels for instance, with various extra filters possible (Locations, product expiry dates etc). Available in Excel export format also with some additional options such as selection of Inventory level at a date in the past, selection of products <0 with movement in the past X months…
The analysis requires user parameters; for example it’s very useful to be able to analyze expiry dates of products in stock. Available to export in Export Excel format
Quantity = for all internal stock locations of instance, if “Real” is selected, then this is real qty in stock. To calculate this the system will only calculate using closed stock moves. If “Future” is selected then the system will calculate this using stock moves with status Closed, Available and Not Available.
13.2.4 Stock level by location
Menu mapping: Products / products
UniField allows you to check the stock levels in all locations for a given product, a single product is selected, and if product is of type ED / BM this attribute should be selected too. System will display real and virtual stock quantities for all Internal locations “Instance full view”, including configured locations. View can be changed to Partner or Virtual locations also.
13.2.5 Stock Card
Menu mapping: Products / products.
13.2.6 Expiry Quantities report
Menu mapping: Warehouse / Reporting / Expiry / Expiry Quantities
The report has two differentiated areas: products already expired and products likely to expire based on real consumption. Location can be selected and period of calculation is mandatory. Available in PDF or excel exports.
– Stock = Total qty of product, including all batches in stock.
– Expiry Qty = Total number of specified batch which will expire
13.2.7 Products likely to expire
Menu mapping: Warehouse / Reporting / Expiry / Products likely to expire
Report showing products with their respective quantities that are likely to expire, based on the selectable options Forecasted Monthly Consumption, Average Monthly Consumption or Real Average Consumption. Period to date is mandatory. If checkbox “Only products with total expired > 0” is ticked, results will be limited to this. (Recommended option).
The system will display a list of all products, the monthly consumption (ie the quantity according to the AMC/FMC/RAC). The next columns will show each month within the timeframe entered as a filter value. Under each month, line by line will be the qty of each product which will expire, and next to this, if relevant, another number (in brackets). The first number represents the quantity of products in stock that have batch numbers which expire in the given month. The second number (in brackets) represents the quantity of products which will expire if we consider that stocks will be used according to the consumption calculation entered. The I symbol appears next to each. For more information about a particular product which will expire, the 
can be clicked on and a screen will display the particulars for this product qty. Report can be exported to Excel or PDF.
13.2.8 Weekly Forecast Report
Menu mapping: Warehouse / Reporting / Expiry / Products likely to expire
Report showing the quantity of goods in location taking into account their consumption according to the AMC/FMC/RAC selected as well as quantities which will expire and also those in the pipeline. It is mandatory to select location. The report shows current stock value and the filters can be used to show weekly or monthly periods up to a maximum of 20 weeks/months. Stock qty will never display negative quantities. For the pipeline qty, the report considers all quantities for the product in the preceding Unifield stock location, for example, if goods have been received in Input, and the Internal move to LOG is in draft, then the Pipeline Qty will consider this qty as in the pipeline for the expected date of the internal move. When calculated for LOG/MED locations this will take into account the pipeline according to what is coming into the warehouse (ie via input). This means that the virtual stock from a ( Validate or) Confirmed PO will also be considered. Report produced in Excel.
- Expiry Qty = Total qty of products which will have expired by the date selected.
- Wk1 (etc) = For each week, the number of products which will expire over the course of this week (taking the forecast into account).
13.2.10 Purchase Order Follow up
Menu mapping: Purchases / Purchase Management/ Purchase Order Follow up
Value can be selected in filters (PO ref, IN ref, Supplier ref, Customer ref) and information will be displayed for specific PO. Can be exported to Excel and PDF: This report is less used as PO follow up per supplier has since been developed.
% of line received = Percentage of quantity received (sum of qty in IN closed / Qty of line)
13.2.11 Field Order Follow up
Menu mapping: Orders / Orders / FO Follow up
Value can be selected in filters ( Internal ref, Customer ref) and information will be displayed for specific FO. Can be exported to Excel and PDF: This report is less used as FO follow up per client has since been developed.
13.2.12 Field Order Follow Up per Client
Menu mapping: Orders / Reporting / FO Follow up per Client
Requested report showing line level information for Field Orders within an instance. Includes different options for filters and exports, including FO status. This report was designed with agreement that at least one filter would always be applied, although this has not been enforced, but may become necessary, depending on usage. Available in Excel and PDF.
– Received = Creation date of Field Order
– RTS = Ready to Ship date – Expected date of Shipment or Expected date of Picking Ticket / OUT associated with this FO line.
13.2.13 PO Follow Up per Supplier
Menu mapping: Purchases / Reporting / PO Follow up per Supplier
Requested report showing line level information for Purchase Orders within an instance, showing Analytical Distribution, and information for received lines including if there has been a unit price change at reception. Available in Excel and PDF
13.2.14 Purchase Order line allocation report
Menu mapping: Purchases / Purchase management / PO lines allocation report
Report displays cost centre and expense accounting codes allocation to an order or a single product. One, multiple or all orders can be selected. Can be exported to excel or PDF (via action menu).
13.2.XXXX missing reports
Menu mapping:
Supplier Performance
Donation report
Loan report
IR follow up per location
IR Track changes
