EXPEDIMP - Import Trade Calloffs
What is EXPEDIMP
The purpose is to import limited Sale Delivery details based on existing TRADEs and EXPED their weight/value through the STOCKS sub-system.
This procedure will import any number of Sales delivery instructions constructed in a .xls with FIXED format as
Row 1 fixed cell names as CONTRACT,TAKE ON REF,COUNTER PARTY REF,NSM INVOICE,INV DATE,TONNAGE CWT,SALE $,DEL CLIENT
Subsequent columns are a variable number of Cost Types with their code exactly as maintained in PHYSCODES/Cost Types e.g. NET 2%, MISC, WHO
Subsequent rows are validated and reported with the following criteria:-
Contract: validated as Sale contract , open status
Take On ref: No validation, secured in new TRADE split in ‘Other Ref’
Counter Party Ref: no validation, secured in new TRADE split in ‘Counter party Reference’
NSM Invoice: See note1. Secured in new TRADE split in ‘BL reference’
Inv Date: present and validated as >= TRADE contract date and <= ITAS date. Secured in new TRADE split in ‘BL date’ and Call-off date
Tonnage CWT: present and numeric and correct decimal places for TRADE UOM and there must be sufficient weight unallocated on sale TRADE
Sale$: present and numeric and correct decimal places
Del Client: Delivery Client, to be secured on new TRADE split
Cost types: no validation, except numeric and correct decimal place. See Note2 for action on TRADE data
The validation will ensure that there is sufficient weight to complete the assignment of Stock to the expedited Sale. The user will select the STOCK Unit at start of process. EXPEDIMP will remember the STOCK unit previously applied.
All validation errors and successful imports are shown on the report created, which is also secured in OPRINT with the import file name.
If there is an import validation failure i..e there are un-recognised headings, then NO import occurs and the message is output to the log and shown on a report. The log is kept in itas/log/expedimp.log
The successful import of a delivery instruction will create a Sale TRADE split record, assign the relevant STOCK to transit and produce the supporting accounting documents. The transit account is maintained in S01 (ctrl50_transbucket) and the Stock account is entered by user in the EXPEDIMP process.
Note1: There is a tickbox option on the main screen that will check and report whether the NSM Invoice is a duplicate for that TRADE.
Note2: Costs are handled in 1 of 2 methods. If the Cost Type already exists on the SALE template (.000 record), replace the current estimate with import AMOUNT and ensure the original estimate is factored accordingly to represent an amount. If the Cost Type does NOT exist on SALE .000, create new cost row with original estimate = ZERO and the current estimate is import value.