The file K_POXREF contains entries for each K3S PO Number and ERP generated PO Number in pipe delimited CSV format. Each day this file should start empty. We recommend clearing K_POXREF as the last step before creating the K_READY file for the day. If your environment will be using the K3S generated PO number, then the K_POXREF file will be used as a confirmation process to communicate to K3S the PO was successfully inserted into your ERP host system. In this scenario the K3SPONUM and CUSPONUM fields will contain the same value.
COMP 1 COLHDG('Company' 'ID')
LOCN 5 COLHDG('Location' 'ID')
BIRTH 10 COLHDG('PO' 'birth' 'date')
K3SPONUM 10 COLHDG('K3S' 'PO' 'Number')
CUSPONUM 10 COLHDG('Customer' 'PO' 'Number')
Field explanations:
Company ID
COMP 1 COLHDG('Company' 'ID')
This 1 character value is used throughout the Replenish system to identify the company being processed.
Examples: Company name code
Brandon Company B
Johnson Limited J
Daniels Auto D
Location ID
LOCN 5 COLHDG('Location' 'ID')
This 5 character value is used to identify the distribution center where this product is being replenished.
Examples: Loc ID Location name
01 Charlotte, NC
02 Raleigh, NC
001 Columbia, SC
002 New York, NY
003 Chicago, IL
KY001 Lexington, KY
TX001 Houston, TX
TX002 Dallas, TX
BIRTH
BIRTH 10 COLHDG('PO' 'birth' 'date')
This is the date of PO approval in *ISO format (CCYY-MM-DD)
K3SPONUM
K3SPONUM 10 COLHDG('K3S' 'PO' 'Number')
This is the K3S generated PO Number used to first approve the PO. Usually it will have a prefix of K3S.
CUSPONUM
CUSPONUM 10 COLHDG('Customer' 'PO' 'Number')
This will be the PO Number created by the ERP from the K3S generated PO. If you are using the PO confirmation process this field will contain the same value as the K3SPONUM field.
