The file K_INDEX is a customer created and mainted file on their server that is meant to serve as an index for what PO CSVs created and transmitted from K3S have already been consumed. POs are unique to K3S via the combination of Location ID and PO Number. PO Numbers can be reused at different locations, but not at the same location.
A customer’s PO consumption process would be expected to download the PO CSV from the SFTP server, inspect the PO Number and see if there is an entry within an index. If a previous entry is not matched the PO can be consumed and the process would add a new entry.
If a duplicate is found the PO CSV file downloaded would be discarded.
Below is a recommended template to accomplish this task. Note there are places for a K3S PO Number and a Customer PO Number. As many customers do not use the K3S PO number past initial consumption recording both numbers will be beneficial in checking for duplicates.
The birth date is for logging of the date consumed.
The Status is suggested to customers for internal logging purposes. Can use different statuses to mark initial consumption and updating to new Customer PO number.
NOTE This index is a customer driver responsibility on their server. K3S is not responsibile for maintaining this file.
LOCN 5 COLHDG('Location' 'ID')
BIRTH 10 COLHDG('PO' 'birth' 'date')
K3SPONUM 10 COLHDG('K3S' 'PO' 'Number')
CUSPONUM 10 COLHDG('Customer' 'PO' 'Number')
STATUS 10 COLHDG('PO' 'Status')
