267723: Difference between revisions
Middletong (talk | contribs) |
Middletong (talk | contribs) No edit summary |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 614: | Line 614: | ||
|- | |- | ||
| <center>1</center> | | <center>1</center> | ||
| EST- | | EST-267723 MW-7UDAYY Purchase Order Extract v1.0 | ||
| <center>1</center> | | <center>1.0</center> | ||
| <center> | | <center>30/07/09</center> | ||
|} | |} | ||
| Line 630: | Line 630: | ||
|- | |- | ||
| <center> | | <center>0.1</center> | ||
| <center> | | <center>10/08/09</center> | ||
| <center>Draft</center> | | <center>Draft</center> | ||
| Initial version | | Initial version | ||
| <center> | | <center>MJC</center> | ||
|- | |- | ||
| <center>1</center> | | <center>1.0</center> | ||
| <center>12/01/09</center> | | <center>12/01/09</center> | ||
| <center>Issue</center> | | <center>Issue</center> | ||
Latest revision as of 13:40, 29 April 2010
267723 - MW-7UDAYY / Purchase Order Extract
Copyright OBS Logistics © 2010
The information contained herein is the property of OBS Logistics and is supplied without liability for errors or omissions. No part may be reproduced or used except as authorised by contract or other written permission. The copyright and foregoing restriction on reproduction and use extend to all media in which the information may be embodied
FUNCTIONAL OVERVIEW
Client Requirement
We require a full extract out of the new Purchase order screen,
Apart from the full details - we also need the date and time when the po was first approved from the audit log - other fields like the OMS ref once the po has been generated via TI is also required.
Added by Mark Wilson via email 05/08/09:
The additional requirements are for the Country and Postcode from the Location file to be added against the Source and Destination locations against the order line.
Also - when we run the report this is by schedule date (Cargo ready date) parameter and we are able to select the Status i.e. just Accepted - when we run ALL - this is to remove Deleted and Cancelled orders - so this will show operationally what we have to action in the other status.
Solution
A new extract format will be added to the Export form’s options called ‘Purchase Order Extract’ a date range will be available for selection and will restrict the export contents to only records that have a delivery date within the date range entered. The export format will be a CSV type file separated by the user parameter EXP_DELIMITER if set or the default ‘,’
The fields contained in the export will be taken from the following screen:
In addition the date of a PO’s first status change to ‘APPROVED’ will be reported along with any OMS reference(s) generated from the Create Ti function. NB if users change the booking reference of the order then the linkage will be broken and orders may not be reported. The TI’s Generated flag will be displayed in the export, this could then be used to identify these orders. A header row will be displayed at the top of the export to assist with field identification i.e:
PO Reference, PO Status, Cust Status, Supp Bkg Action….etc 434387015960407,CONFIRMED,Open,SBA NO ACTION,….etc
Included in costing is 0.25 days for UAT assistance, any further implementation/testing support would need to be agreed on a T&M basis.
Scope
This change will be applied to system version 10.5 on IIBTST and once approved on IIBPRD. NB this will be developed in such a manner as to be compatible with any database that has the Purchase Order Module installed.
Data
A new record will be added to the REP_REPORT table :
FUNCTIONAL DESCRIPTION
Extract Definition
| POSITION | ITEM NAME | MTS SLOT IMPORT FIELD TYPE | FORMAT | VALUES |
|---|---|---|---|---|
| 1 | PO Reference | PO_REFERENCE | VARCHAR2(24) | 435488015976936 |
| 2 | PO ID | PO_ID | VARCHAR2(12) | 435488 |
| 3 | Item Number | ITEM_NUMBER | VARCHAR2(12) | 015976936 |
| 4 | PO Number | PO_NUMBER | VARCHAR2(12) | 460-73197 |
| 5 | Cost Centre | COST_CENTRE | VARCHAR2(12) | EXEL |
| 6 | Customer | CUSTOMER | VARCHAR2(12) | Tesco |
| 7 | Source | SOURCE | VARCHAR2(12) | TE-202210 |
| 8 | Source Postcode | Derived from GEO_LOCATION based on Source matching a location id | VARCHAR2(9) | 34 520 |
| 9 | Source Country | Derived from GEO_LOCATION based on Source matching a location id | VARCHAR2(3) | TR |
| 10 | Hub | HUB | VARCHAR2(12) | TR |
| 11 | Destination | DESTINATION | VARCHAR2(12) | TE-460 |
| 12 | Destination Postcode | Derived from GEO_LOCATION based on Destination matching a location id | VARCHAR2(9) | NN6 7EA |
| 13 | Destination Country | Derived from GEO_LOCATION based on Destination matching a location id | VARCHAR2(3) | GB |
| 14 | Cargo Ready | CARGO_READY | DATE | 06-JUL-2009 |
| 15 | Schedule Name | SCHED_NAME | VARCHAR2(12) | 090706 |
| 16 | Product Type | PROD_TYPE_ID | VARCHAR2(12) | AMBIENT |
| 17 | Status | STATUS resolved from STATUS_ID linked to SCH_PO_STATUS | VARCHAR2(2) | PROVISIONAL |
| 18 | Delivery Date | DELIVERY_DATE | DATE | 13-JUL-2009 |
| 19 | Transport Mode | TRANSPORT_MODE | VARCHAR2(12) | TRUCK |
| 20 | Original UOM | ORIG_UOM | VARCHAR2(20) | BHG |
| 21 | Original DU | ORIG_DU | VARCHAR2(20) | 401 |
| 22 | Original QTY | ORIG_QTY | NUMBER(24,4) | n/a |
| 23 | Unit Cost | UNIT_COST | NUMBER(12,4) | 36.0600 |
| 24 | Unit Currency | UNIT_CURRENCY | VARCHAR2(3) | EUR |
| 25 | Item Description | ITEM_DESCRIPTION | VARCHAR2(100) | RATIO AW09 CHK SRUCH WST |
| 26 | Load Type | LOAD_TYPE | VARCHAR2(12) | FTL |
| 27 | Freight Terms | FREIGHT_TERMS | VARCHAR2(12) | CCX |
| 28 | PO DU Type | PO_DU_TYPE | VARCHAR2(20) | BHG |
| 29 | PO Qty | PO_QTY | NUMBER(24,4) | 401 |
| 30 | PO Version | PO_VERSION | VARCHAR2(12) | 12 |
| 31 | Booking DU Type | BOOKING_DU_TYPE | VARCHAR2(20) | BHG |
| 32 | Booking DU Qty | BOOKING_DU_QTY | NUMBER(24,4) | 401 |
| 33 | Transit DU Type | TRANSIT_DU_TYPE | VARCHAR2(20) | n/a |
| 34 | Transit DU Qty | TRANSIT_DU_QTY | NUMBER(24,4) | n/a |
| 35 | Transit Weight | TRANSIT_WEIGHT | NUMBER(12,2) | n/a |
| 36 | Transit Volume | TRANSIT_VOLUME | NUMBER(25,5) | n/a |
| 37 | Sub Transit DU Type | SUB_TRANSIT_DU_TYPE | VARCHAR2(20) | n/a |
| 38 | Sub Transit DU Qty | SUB_TRANSIT_DY_QTY | NUMBER(24,4) | n/a |
| 41 | Receipted Date | RECEIPTED_DATE | DATE | 07-JUL-2009 |
| 42 | Supplier Bkg Action | SUPP_BKG_ACTION | VARCHAR2(50) | SBA NO ACTION |
| 43 | Supplier Bkg Action 1 | SUPP_BKG_ACTION1 | VARCHAR2(12) | SBA NO ACTION |
| 44 | Supplier Bkg Action 2 | SUPP_BKG_ACTION2 | VARCHAR2(12) | SBA NO ACTION |
| 45 | Supplier Bkg Action 3 | SUPP_BKG_ACTION3 | VARCHAR2(12) | SBA NO ACTION |
| 46 | Customer Status | CUST_STATUS | VARCHAR2(12) | Open |
| 47 | Delivery Priority | DEL_PRIORITY | VARCHAR2(2) | n/a |
| 48 | Special Instructions | SPECIAL_INSTRUCTIONS | VARCHAR2(4000) | ItemType:P|StyleCode_Desc:KC920411|V
endorPartNumber:|PO_Created_DateTime:2009-05-15T00:00:00+00:00|LastModified_DateTime:2009-05-15T00:00:00+00:00|PO_StatusEffDateTime:2009-05-T00:00:00+00:00|PO_NumberRedirected:|PO etc…. |
| 49 | TI Generated | TI_GENERATED | VARCHAR2(1) | Yes |
| 51 | Source System | SOURCE_SYSTEM | VARCHAR2(12) | POM |
| 52 | Created By | CREATED_BY | VARCHAR2(40) | MTS_OWNER |
| 53 | Created Date | CREATED_DATE | DATE | 20/07/2009 14:04:10 |
| 54 | Updated By | UPDATED_BY | VARCHAR2(40) | ALTINTASK
|
| 55 | Updated Date | UPDATED_DATE | DATE | 10/08/2009 08:49:43 |
| 56 | Approved Date | Derived from first entry for SCH_PO_AUDIT where PO_ref is matching current row and audit text contains APPROVED use CREATED_DATE | DATE | 06/08/2009 12:53:39 |
| 57 | Order Reference | OMS Reference from SCH_ORD where Booking Ref = PO Reference | VARCHAR2(12) | 999603
|
REFERENCES
| EST-267723 MW-7UDAYY Purchase Order Extract v1.0 |
DOCUMENT HISTORY
| Initial version | ||||
| Reviewed and Issued |
AUTHORISED BY
| Matt Crisford | Development Manager | |
| Peter Greer | TMSCC MTS Product Manager |
