CARGO - CFI import/maintenance



Specialist sub-system to process Ferrous type cargo/inventory from arrival at the warehouse through Sales and Delivery. The processes  are a consolidated equivalent of existing TRADE processes e.g. TRADE/split to create a Cargo,  TRADE/IMage-Allocate-tranches to create Sales, Delivery Orders (DO) are a subset of TRADE (right-click 'deliveries').

1. Import

Purpose is to Import files (.csv) with details of cargo deliveries to the warehouse
File definitions are maintained in IGI with the style = CARGO. This is the standard ITAS methodology
for interface definitions.

Select Import process and then select the file to be imported. The IGI would be setup with the default directory to locate
the .csv but the user can specify their own directory.  The completion of the Import process results in the.csv being moved to a sub directory named as .old.
The report is also copied to the company OPRINT folder.


The Import file structure is .csv with fixed number of columns:

1.   Warehouse, mandatory, ITAS CLI code nominated as a Warehouse (without .P), e.g. CNWARE1
2.   Purchase Contract Number , mandatory, valid ITAS trade reference (6 digits only), e.g. P00123
3.   Vessel Name, mandatory, valid ITAS VEESEL code, e.g. CHING HO
4.   Shipping status, mandatory, valid ITAS PHYSCODES/Shipping status, e.g. W
5.   Arrival at warehouse date, mandatory, YYYYMMDD format
6.   Coil Reference at warehouse, mandatory freeformat max 120 characters
7.   Product Name, mandatory, valid ITAS PHYSCODES/Commodity (grade). Will validated with TRADE commodity parts 1 + 2
8.   Specification, mandatory, valid ITAS PHYSCODES/Government Standard Specification
9.   Thick*Width*Length, mandatory, 3 x numeric values separated by *.  Note Length cn = 'C' to indicate that no Length parameter is being processed
10. Producer Name, optional, valid ITAS CLI code nominated as a Mill (without .P) e.g. USASTEX
11. Producer Name Ref, optional, freeformat max 40 characters
12. Bags/Pieces, optional, numeric interger (number of pieces),
13. Quantity (Mill Weight), mandatory, numeric, decimal places validated with TRADE weight code
14. Warehouse weight, optional, numeric, decimal places validated with TRADE weight code
15. Storage location, optional, freeformat max 20 characters
16. Coil Ref of Mill, optional, freefomat max 15 characters,
17. Mill Contract Ref, optional, freefomat max 120 characters,
18. Packing Code, optional, valid ITAS PHYSCODES/Packing Code,

The imported details will be displayed on a grid and can be amended prior to being imported.
All the fields will need to pass their validity checking before OK to import (Select = ticked).
The import process will search the ITAS trades that match on 6 digit reference and  also match
on Gov Standard /Specification AND Thickness and Width and Optionally Length.  Error messages are shown per grid row.
If the user attempts to Select and there are still error conditions, messages are shown.
The row number of the csv is shown in the grid. This will enable the user to easily identify the erroneous
data in the .csv.  Items that are NOT selected will be removed from the process. This means that
they will need to be either manually maintained in TRADE or create a new .csv with correct
information and re-Import.


A report will be produced showing ONLY the imported splits, with their new TRADE reference.


The data imported creates a TRADE based on following criteria; use the TRADE (6 digits) to locate
an open status TRADE with Shipping status blank, with tonnage available to assign CARGO  which
matches on  Thickness and Width. 

The import data creates ITAS data as follows
1.   phys01_warehouse 
2.   phys01_contract
3.   phys01_vessel
4.   phys01_afi
5.   phys01_arrivaldate
6.   phys01_coilno (ad)
7.   phys01_grade
8.   phys01_ferrousgovstd (ad)
9.   phys01_ferrousgauge, phys01_ferrouswidth, phys01_ferrouslength (ad)
10. phys01_mill (aa)
11. phys01_clref
12. phys01_bags
13. phys01_conquan
14. phys22_conquan (phys22_type=W)
15. phys01_locator (aa)
16. phys01_warrant
17. phys01_cargo (aa)
18. phys01_packcode


2. Cargo List Maintenance


Unallocated contracts are available for processing in the Cargo List Maintenance screen. The Filter screen allows the required contracts to be selected.



 
The contracts are recalled in a grid as above.

Users with the 'OPS' privilege can click edit to amend the contracts. The quantity can be changed but the weight difference will not affect the parent trade i.e. the process will operate as if the change was made in TRADE.

Users with the CMP privilege 'TRADER' can perform the following functions:

Lock / Unlock :  

To be used when the Trader does not want to raise a Sales contract immediately e.g. sale details are not finalised. Trader will use this lock cargo function to update Cargo status to ‘Locked’ with trader’s name and timestamp.  Users with 'ADMIN' privilege can also unlock these trades.

Create Sales:  

TRADE Sale will be created for the selected cargo splits. If more than one cargo with different warehouses, coils or specifications are selected; a Sale contract will be created with a split trade per warehouse, specification etc.
The user can be prompted to enter a cost matrix.  
The purchases and sales will be allocated

Preallocation:  

As per the create sales function but contracts will be pre-allocated rather than allocated.
Confirm preallocation converts the preallocation to a real allocation.
 

3. Deliveries

This process will enable creation of DOCDES forms to authorise customer/third-party to retrieve the goods from the external warehouse. User makes selections to retrieve the Sales with DO balances. For each DO created a system unique number (ctrl103 - DO code) will be assigned; email options will be enabled in this procedure.
The DOCDES form created is secured in DOCMAN and is available subsequently for view/reprint/send.  The delivery details (phys07) can be viewed from TRADE/Deliveries where there is the feature to recreate a new DO form as a new version of same delivery.

4. Reverse Deliveries

This process will adjust the balance of DO quantity i.e. remove delivery detail record.


Was this helpful?
Thanks for your feedback