As I have said before - we are moving to a program named EPIC for ome of our financial jobs/processes. They need to send me a csv based on the table defs, but now I have a few questions about this file - All importing to APCINVOICE:

I have a couple of questions about the refund file before I ship it off to Epic.

CVI-VENDOR - Spec states that this field is alpha. Can I put a numeric value here for the vendor ID?
CVI-BATCH-NUMB - Is this the date of the file? YES
CVI-TAX-PNT-DATE - Is this the date of the file? YES
CVI-DUE-DATE - Is this the date of the file? Date the invoice is due.
CVI-PO-NUM - Is this hardcoded to "KDBAYN"?
CVI-DIST-CODE - Is this hardcoded to "PTR"?
CVI-INVOICE-GROUP - Is this hardcoded to "PTR"?
CVI-ACCR-CODE - Is this hardcoded to "IVNA"?
CVI-PROC-LEVEL - Is this hardcoded to "1"?
CVI-BASE-INV-AMT - States field is required but it is blank. Is blank OK?
CVI-CHECK-DATE - States field is required but it is blank. Is blank OK?
CVI-TRAN-INV-AMT - Does this need to be left zero padded?

CVI-OLD-VENDOR - Spec says this field is not being used but there is a space in the file.
CVI-AUTO-MATCH - Spec says this field is not being used and there is no space in the file.

Anyone work this table - that knows the specs?

There is some good information on the support site documenting the ins and outs of this Interface. I would look there.

Any particular resource? I just pulled up the Conversion file .pdf?

Basically, I quoted the table specs - again - see below:



I have a couple of questions about the refund file before I ship it off to Epic.

CVI-VENDOR - Spec states that this field is alpha. Can I put a numeric value here for the vendor ID? Yes. This is the invoiced vendor number. Must be a valid record in the Vendor file.
This field may be left blank if the One-Time Vendor field = Yes.
*The field type for this field is defined in Vendor Group (AP00.1).

CVI-BATCH-NUMB - Is this the date of the file? Yes

CVI-TAX-PNT-DATE - Is this the date of the file? Yes

CVI-DUE-DATE - Is this the date of the file? No. The invoice due date. Used by Cash Requirements (AP150) or Bill of Exchange Generation (AP151) to select the invoice for payment. If left blank, the Terms Code assigned to the invoice, alternate location (type P or B), or vendor, if assigned, will be used to calculate due date and discount information. This field is required if the vendor or location does not have a terms code assigned and you do not assign a terms code to the invoice.

CVI-PO-NUM - Is this hardcoded to "KDBAYN"? Yes.

CVI-DIST-CODE - Is this hardcoded to "PTR"? Yes.

CVI-INVOICE-GROUP - Is this hardcoded to "PTR"? Yes.

CVI-ACCR-CODE - Is this hardcoded to "IVNA"? Yes.

CVI-PROC-LEVEL - Is this hardcoded to "1"? Yes.

CVI-BASE-INV-AMT - States field is required but it is blank. Is blank OK? The amount of the invoice in the company base currency. This field is required for nonbase currency invoices with an historical status when no currency exchange rate is entered.

CVI-CHECK-DATE - States field is required but it is blank. Is blank OK? Yes.

CVI-TRAN-INV-AMT - Does this need to be left zero padded? Yes.


CVI-OLD-VENDOR - Spec says this field is not being used but there is a space in the file. THIS FIELD IS NOT CURRENTLY USED.

CVI-AUTO-MATCH - Spec says this field is not being used and there is no space in the file. Not currently being used.

I have attached what I am using as a reference. Let me know if I should ask someone else these questions. Being relatively new I am still working out who to go to for what.